← All ideas IDEA-045 5.8 us caregiver-tools developed

Stop the 'did anyone give Mom her pill?' anxiety — one shared medication log that updates by SMS and a link, so siblings see 'I gave it' confirmations without ever creating an account.

Problem

Adult children rotating in-home care for an aging parent cannot reliably tell whether someone already gave today's pill — it spirals into anxious group-text 'did you?' and the fear of either double-dosing or missing a dose. Existing apps require every sibling to install, log in, and stay logged in, which secondary siblings refuse to do.

Audience

Adult children, 2–4 siblings rotating in-home caregiving for a parent on 5–25 active prescriptions, where 1 person is the primary caregiver and 1–3 are less-engaged siblings who will not install another app or log into MyChart

Reasoning

Source signals

SIG-20260426-us-caregiver-tools-sibling-medication-handoff-uncertainty: «The hardest part isn't the schedule — it's the uncertainty… you don't want to double-dose, but you also don't want to miss a dose»
SIG-20260426-us-caregiver-tools-mychart-sibling-google-calendar-rejection: «I tried a shared family google calendar but my sibling wouldn't use it»
SIG-20260426-us-caregiver-tools-printable-binder-anti-app-cohort: «handoff to ER nurses, paid CNAs, and the elderly parent themselves» — supports our PDF/ER one-pager feature

What we ship

**Core features (MVP)**

Primary creates a "care circle" in 30 seconds: parent name + list of meds (with schedule).
Any sibling marks "I gave {med} now" via a tokenized link (no login) or by replying to SMS.
Everyone in the circle gets an SMS push-copy: "Anna gave Mom evening meds at 6:42pm — dose #3 today".
Read-only "today" page: see what's been given, what's overdue, who marked it last.
Weekly printable PDF "who, when, what" — for the doctor and the binder.

**Primary user flow**

1. Primary creates circle on landing — enters name, email, phone.

2. Adds 2–5 meds with schedule (templates: BP/diabetes/dementia).

3. Gets a magic link per sibling, sends them by their own SMS.

4. Sibling opens link → "today" page → taps "I gave X" → done.

5. Free: 1 parent, 5 meds. Pro: unlimited meds, multi-parent, weekly PDF + ER one-pager. $9/mo.

**What it looks like**

**Landing page**: hero "Stop the 'did anyone give Mom her pill?' anxiety", phone screenshot of circle view, CTA "Create your circle — no app to install".
**Main app screen**: vertical day-timeline with check marks; bottom three big buttons "I gave morning / afternoon / evening".
**Output / notification**: SMS "✅ Anna gave Mom evening meds at 6:42pm. View today: {link}".

**MVP build plan (10 days)**

Day 1–3: Postgres schema (circles, members, meds, schedules, doses), FastAPI auth for primary + magic-link for siblings, basic CRUD.
Day 4–6: Twilio SMS, Resend email digests, mobile-first React UI.
Day 7–8: Stripe paywall (Pro), PDF report via WeasyPrint.
Day 9–10: landing, deploy to CF Pages + Railway, smoke test, launch.

Reasoning

The pain is captured verbatim in r/AgingParents — «the hardest part isn't the schedule — it's the uncertainty» — and a separate thread says «I tried a shared family google calendar but my sibling wouldn't use it». Every commercial caregiver app (CircleCare, Brelti, Carevio, TendTo, Lotsa Helping Hands) assumes the whole family wants to collaborate, but in reality secondary siblings refuse to log in. That's the wedge: **single-sided onboarding** — primary creates the circle, secondaries get an SMS link and tap one button, no account ever. Stack is plain (FastAPI + Postgres + Twilio + Stripe) and fits a 10-day window. We do not store PHI under HIPAA scope: caregiver-supplied notes only (med name, parent's first name — not diagnosis, not clinic, not provider).

Quick competitive read

**CircleCare / Lotsa Helping Hands / Brelti / Carevio / TendTo** — all require every sibling to create an account; this is exactly the pain we solve. None of them have a no-login secondary mode.
**Hello Caremap, CareZone (shut down 2024)** — single-caregiver focused, not multi-user coordination.
**Pill-reminder apps (Medisafe, MyTherapy)** — answer "what to take and when", not "who already gave it today".
**White space**: "no-login for siblings" as a marketing wedge — none of the larger players lead with this. Competitive pressure: ~6/10 — the market exists but the positioning lane is open.

> **Stage 5b update (2026-04-26)** — profiled 5 direct competitors (CircleCare, Brelti, Carevio, TendTo, CareClinic). All five require every sibling to either (a) install an app and create an account, or (b) at minimum sign up via web. **Brelti literally uses our wedge copy** ("did anyone give Mom her meds?") but is iOS-only with mandatory signup — confirming the pain is mainstream while the no-login execution remains uncontested. Pricing benchmark: $5–$12/mo Family tier is the consumer floor; CareClinic's $9.99 = category benchmark. Market density: **medium** (5 active commercial competitors, all with the same fundamental onboarding flaw).

Initial pricing hypothesis

Free: 1 parent, 5 meds, 7-day history. Pro: $9/mo or $79/yr — unlimited meds, multi-parent, PDF report, ER one-pager, full history. Developed-tier consumer subscription willingness averages $8–12/mo — we land in the lower band, which fits caregiving (people pay if it spares them family negotiation).

Distribution hypothesis

1) **Reddit r/AgingParents and r/CaregiverSupport** — solo-dev "show & tell" post leading with the no-login wedge (community pain — posts with this exact framing pull 100+ upvotes).

2) **SEO landings** for "shared medication log siblings", "medication tracker no app required", "caregiver text updates without app".

3) **TikTok / IG caregiver micro-influencers** (gerimillerCG, the_caregiver_space) — DM outreach with free Pro promo codes in exchange for a review.

Source signals (3)

SIG-20260426-us-caregiver-tools-sibling-medication-handoff-uncertainty:
SIG-20260426-us-caregiver-tools-printable-binder-anti-app-cohort:
SIG-20260426-us-caregiver-tools-mychart-sibling-google-calendar-rejection:

Score breakdown

market_size	7/10
pain_severity	6/10
build_feasibility	7/10
speed_to_revenue	6/10
regulatory_safety	5/10
competitive_pressure	3/10
recurring_revenue_fit	7/10

MVP stack

frontend	Cloudflare Pages + React + Tailwind
backend	Railway + FastAPI + Postgres
ai	Claude Sonnet 4.6 via API (only for natural-language one-tap log entries like 'gave evening meds, BP a bit high')
payments	Stripe Subscriptions (premium upgrade only)
storage	Postgres
external_integrations	['Twilio SMS', 'Stripe', 'Resend (email digests)']

Estimated build: 10 days

Regulatory

soft_block

Blocks: D-001

HIPAA grey-zone (D-001, manual_review): consumer-direct apps where family members voluntarily log a relative's medication intake are generally NOT HIPAA-covered, because the operator is neither a covered entity (provider/payer/clearinghouse) nor a business associate. The IDEA correctly scopes data to caregiver-supplied notes (med name + parent first name, no diagnosis, no provider, no EHR integration). However, the literal trigger "prescription management" is present, and the product handles prescription names + schedules on a named individual, which sits adjacent to PHI. Build-time mitigations required: (a) Terms of Service explicitly stating the app is not HIPAA-covered and is not for use by covered entities; (b) no marketing claim of "HIPAA-compliant"; (c) no integrations with EHRs/MyChart/provider portals (would flip status to covered). State-law advisories (US-only build): California CMIA (Confidentiality of Medical Information Act) extends "medical information" protections to non-HIPAA businesses that "offer software designed to maintain medical information" — this DOES apply, requires written authorization patterns, breach-notification regime. Texas HB 300 has a similarly broad definition. Recommend baking CMIA-grade handling into the data model from day one (encryption-at-rest, access logs per circle, granular delete). TCPA / FCC SMS compliance: SMS is the core delivery channel. Twilio A2P 10DLC registration mandatory for high-volume transactional+notification traffic. Secondary siblings receiving "Anna gave Mom evening meds" SMS need opt-in proof — the magic-link onboarding must capture consent (e.g., first SMS: "Reply YES to receive medication updates for Mom's care circle"). Standard STOP/HELP keywords required. Not a disqualifier — this is the standard TCPA build pattern Twilio supports out of the box. Not a medical device (D-006 clean): the product logs human-administered doses, makes no dosing recommendations, no diagnostic claims, no clinical decision support. AI use is restricted to natural-language entry parsing. Out of scope for FDA SaMD per the Policy for Device Software Functions. AVOID adding any "should they take it now?" features — that would re-open SaMD classification. BUILD RECOMMENDED with the above guardrails. Soft-block, not disqualified.

Competitors (5)

Brelti — $4.99/monthly
Brelti is our single most direct competitor by positioning — they have literally the same headline. But they share the fundamental flaw of every commercial caregiver app: every sibling must install th
CareClinic — $9.99/monthly
CareClinic uses a single-account-multi-profile model, NOT a multi-account-shared-circle model. The primary caregiver manages everything from their own account; siblings either share that login or get
Carevio — $5/monthly
Carevio is the closest to our web-first approach — a link opens in a browser, no app install. But every sibling still has to create an account and complete a signup flow. We remove that entire step fo
CircleCare — $6.99/monthly
CircleCare's invite flow is email → download app → create account → log in. That is precisely the friction wall we remove with SMS+magic-link no-login flow. They target the "whole care team" (includin
TendTo — $11.99/monthly
TendTo is the most "enterprise-deep" of our 5 competitors: bills, provider portal, AI insurance helper, 25 GB document vault. That is product overshoot for our narrow "did anyone give the pill?" use c