← All ideas IDEA-046 5.9 us caregiver-tools developed

Make the invisible visible — a one-tap log that turns your week of hospital runs, prescription pickups and overnight stays into a month-end PDF you can text to siblings: '47 hours, $1,200, 11 visits — here's what I need this month'.

Problem

Sole/primary adult-child caregivers — usually a daughter aged 40–60 carrying a parent with chronic conditions while 1–2 siblings live in another state and contribute zero hands-on care — don't need another shared calendar (siblings won't open it). They need a one-page month-end report they can text to their family that shows hours, dollars, visits, and asks: 'I need help with X this month'. Existing apps demand collaboration; the real pain is unilateral accountability.

Audience

Sole or primary adult-child caregivers (often a daughter aged 40–60) of a parent with chronic conditions, with 1–2 out-of-state siblings who contribute money or sympathy but zero in-person logistics; primary spends 15–60 hrs/week on care and tracks hours/expenses in head, paper, or Notes app

Reasoning

Source signals

SIG-20260426-us-caregiver-tools-long-distance-visibility-without-sibling-buyin: «I would help, but I live in Seattle… List every task you do weekly and monthly. State the hours involved.»
SIG-20260426-us-caregiver-tools-mychart-sibling-google-calendar-rejection: «My sibling wouldn't use it» — confirms unilateral-tool premise
SIG-20260426-us-caregiver-tools-sibling-medication-handoff-uncertainty: corroborates the "uneven sibling effort" cohort

What we ship

**Core features (MVP)**

5-second quick-log: "doctor visit 2h + $40 cab" via voice or 3 taps. Hashtags (#doctor, #pharmacy, #overnight) auto-tagged by LLM.
Daily and weekly calendar view — primary sees their own load.
End-of-month auto PDF "Mom's care, October 2026": 47 hrs, $1,200, 11 visits, category breakdown, 3 receipt photos, and "What I need from you next month" block.
Tokenized share link — siblings open it in a browser, no account needed; see PDF and a "Contribute via Stripe" button (top up a shared budget).
Quarterly trend — is load growing? "Q3 visits +35%."

**Primary user flow**

1. Primary signs up (email + password). 5-min onboarding: "tell me about your parent and a typical week".

2. Daily — 1–5 quick-logs (voice/tap). LLM converts to structured entries.

3. On the 1st of next month — auto-PDF in email + share link.

4. Primary edits the "what I need" section (AI-prefilled), texts siblings the link.

5. Pro features: custom PDF branding (for families sharing with extended kin), receipts gallery, IRS "medical expenses" export.

**What it looks like**

**Landing page**: hero "Stop writing the 4-paragraph guilt-trip text. Send the report instead." — pain-driven copy with a real mock PDF.
**Main app screen**: day feed with big buttons "log visit / log expense / log overnight". Side panel shows running total "this week: 18h / $340 / 4 visits".
**PDF**: 1-page report with "hours by week" graph, category pie chart, receipt photo gallery, explicit "Asks" block with 2–3 bullets.

**MVP build plan (9 days)**

Day 1–3: Postgres schema (caregivers, parents, log_entries with tags), FastAPI CRUD, voice-to-tag LLM pipeline.
Day 4–5: PDF generator (WeasyPrint), tokenized share-link URLs.
Day 6–7: Stripe Subscriptions, share-link contribute flow.
Day 8–9: pain-copy landing, deploy, launch on Reddit.

Reasoning

The pain is documented at eldersafetyhub.com ("Distance as permission. Living far away becomes a blanket excuse"), in tendto.ai blog (the exact accountability narrative), and in roughly every fourth r/AgingParents thread. The existing caregiver-app market is optimized for "coordination" — everyone logs in, everyone contributes. The reality of a primary caregiver is the case where siblings refuse to log in, and they need a mirror tool. That's a different product narrative and distribution channel (anti-coordination), same code base. TendTo is the only competitor on this narrative, and they bundle it inside a broader apparatus. Our focus is laser, in 9 days. Regulatory risk is low: caregiver logs their own hours and dollars, no medical data, no diagnosis.

Quick competitive read

> **Updated 2026-04-26 by competitor-analyst (5 CMPs profiled).** Market density: **LOW** — 1 direct (TendTo) + 4 adjacent. Confirms the synthesizer's wedge thesis.

**TendTo (tendto.ai)** [`CMP-IDEA-046-tendto`] — only direct competitor on the accountability narrative; launched March 2026 by Mark Krieger / Thoughtful Labs LLC, $11.99–$19.99/mo. Bundles bills + meds + docs + AI; still requires whole-family login. Their mechanic is collaborative; ours is unilateral.
**ianaCare (ianacare.com)** [`CMP-IDEA-046-ianacare`] — 7yo B2B2C app (employer-sponsored, free to user) for supporter-network coordination (meals/rides/respite). Zero overlap with hour-log + PDF + IRS export; complementary at best.
**Lotsa Helping Hands** [`CMP-IDEA-046-lotsa-helping-hands`] — 21yo donation-funded meal-train calendar; 4-person team, no funding since 2014. Owns the meal-rota SEO but not the accountability narrative; unlikely to extend into our space.
**CaringBridge** [`CMP-IDEA-046-caringbridge`] — 29yo 501(c)(3) nonprofit health-journal platform, $6–8M annual donor revenue, 56 staff. Long-form prose for acute crises; orthogonal to numerical chronic-care accountability — co-exists, not substitute.
**AARP Prepare to Care + Financial Workbook** [`CMP-IDEA-046-aarp-prepare-to-care`] — fillable PDF + planning guide, no software. **Demand-creation engine, not competitor**; viable distribution partner via AARP "Valuable Apps" listings, Substacks, and Family Caregivers Facebook group.
**TimeCamp / Toggl / generic time-trackers** — confirmed not caregiver-positioned; absent from any caregiver discovery surface.
**Family Medical Organizer / Caregiver activity logbook printables** — paper/PDF templates; not SaaS, no PDF auto-generation.

**White-space confirmation**: HIGH (~7–8/10). Only TendTo touches the accountability narrative, and they bury it inside a multi-feature suite at 60-min onboarding. The "sole-caregiver, single-purpose, month-end PDF" wedge is unoccupied. Pricing benchmarks ($12/mo Pro) clear TendTo's Family tier.

Initial pricing hypothesis

Free: 7-day history, monthly PDF without branding. Pro: $12/mo or $99/yr — unlimited history, custom PDF branding, IRS export, receipt gallery, voice-to-log. Developed-tier consumer subscription willingness ~$8–12/mo, and here WTP skews higher (caregiver burden is acute) — we sit at the upper end.

Distribution hypothesis

1) **Reddit r/AgingParents** (especially the distance-caregiving flair) and r/CaregiverSupport — solo-dev post "I built a tool for sole caregivers — month-end report PDF, no shared apps required", aimed squarely at the "siblings do nothing" frustration.

2) **Facebook caregiver groups** (closed groups like "Caring for Aging Parents", 80K+ members) — DM admins, organic post.

3) **Substack caregiver-newsletters** (the-cost-of-caring, caregiver-burnout writers) — sponsored mention $200–500.

Source signals (3)

SIG-20260426-us-caregiver-tools-long-distance-visibility-without-sibling-buyin:
SIG-20260426-us-caregiver-tools-sibling-medication-handoff-uncertainty:
SIG-20260426-us-caregiver-tools-mychart-sibling-google-calendar-rejection:

Score breakdown

market_size	6/10
pain_severity	6/10
build_feasibility	7/10
speed_to_revenue	6/10
regulatory_safety	8/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 (turns voice notes 'drove Mom to cardiologist, 90 minutes, $40 lunch' into structured entries; drafts the empathic-but-firm month-end ask)
payments	Stripe Subscriptions
storage	Postgres + Cloudflare R2 (receipt photos)
external_integrations	['Stripe', 'Resend (PDF email delivery)', 'Twilio SMS (share link)']

Estimated build: 9 days

Regulatory

clean

Clean for US consumer launch — no hard disqualifier triggers and no soft-block triggers. HIPAA (D-001) does NOT apply: the caregiver self-logs their own activity (hours, mileage, receipts, free-text notes like "took Mom to neurologist"); the app is not a Covered Entity or Business Associate, and data is consumer-controlled (PHR-style, outside HIPAA scope per HHS guidance). Hard line to keep: do NOT integrate EHR/MyChart/FHIR feeds — pulling data from a Covered Entity puts the app inside HIPAA via a BAA and flips this to disqualified. PCI-DSS (D-002) is satisfied by Stripe Subscriptions tokenization. No crypto (D-004), no money-transmission (D-005) provided "Contribute via Stripe" is built as Stripe Connect Standard direct charges to the primary caregiver's account — never a custodial pool that holds funds on behalf of multiple parties. No medical-device claim (D-006). EU AI Act high-risk (SB-004) does not apply: the LLM only structures the user's own voice notes into tagged log entries, no hiring/credit/education/law-enforcement use case. Build-stage advisories (none are blockers, but bake into legal copy and product): 1) Marketing language: never claim "HIPAA-compliant" — say "your records, in your hands" or "PHR-style". Claiming HIPAA when out of scope invites FTC enforcement under the Health Breach Notification Rule (extended in 2024 to consumer health apps). 2) FTC Health Breach Notification Rule: even outside HIPAA, this app likely qualifies as a "vendor of personal health records" under 16 CFR Part 318 — a breach of identifiable health info triggers consumer + FTC + media notification within 60 days. Plan a breach playbook and S3/R2 encryption-at-rest from day one. 3) California CMIA: California treats software "designed to maintain medical information" as subject to CMIA confidentiality rules (encryption, written authorization for disclosure beyond the user). The IRS-export and receipt-gallery features push the app into this scope for CA users — implement consent capture for the share-link recipients and add CMIA-style disclosure clause in ToS. 4) "IRS medical expenses export" must be framed strictly as record categorization, not deduction advice — boilerplate "Consult a tax professional, this is not tax advice" avoids CPA/CFP-licensure exposure and IRS Circular 230 issues. 5) Long-term-care insurance claim docs: the PDF will plausibly be used as evidence for LTC reimbursement. Stay strictly informational ("here is your log") and never market as "submit this for your LTC claim" — that drifts toward insurance-claims-assistance, which is state-licensed (public adjuster rules) in several states. 6) Voice recording — two-party-consent states (CA, FL, IL, MD, MA, MT, NV, NH, PA, WA): caregiver self-dictation is fine (their own voice). If voice notes ever capture the parent or a third party (e.g., during a phone call), wiretap statutes apply — gate the feature to single-speaker capture only or require explicit "is anyone else in the recording" consent screen. 7) Parent-as-data-subject: the log details a competent adult parent's medical visits. Capture caregiver's attestation during onboarding ("I have authority/consent to log this person's care") and offer a parent-removal-request flow. 8) Tokenized share-link with sibling Stripe contribute: keep links short-lived, single- use-friendly, and revocable; the URL token IS the auth boundary for siblings without accounts. Region advisory — EU/UK expansion is a HARD redesign, not a translation: parent's medical visits are GDPR Art. 9 special-category health data. Caregiver consent does not satisfy Art. 9 for the parent (who is a separate data subject). Expansion to uk-ie/dach/france/iberia/italy/nordics/benelux/cee would re-trigger D-003 (manual_review) and require an Art. 6 + Art. 9 dual lawful basis, DPIA, possibly a DPO, plus parent consent capture or vital-interests/legitimate-care framing. Treat this as a v2 jurisdiction decision, not a copy-paste. India (DPDP Act 2023) and Brazil (LGPD Art. 11) have similar sensitive-data treatment. UK GDPR mirrors EU treatment.

Competitors (5)

AARP Prepare to Care Guide + Family Caregiving Resources
AARP is not a competitor — it is a **demand-creation engine for IDEA-046**. Every caregiver who downloads the Financial Workbook PDF is admitting "I should be tracking this systematically" — but ten m
CaringBridge
CaringBridge and IDEA-046 share zero overlapping features, but they share a **frame** — both are "I'll write you a long thing instead of calling everyone individually." CaringBridge solves the acute-p
ianacare
ianaCare is the textbook "coordination" tool the IDEA's reasoning section calls out: it is built for the case where supporters *want* to help and the caregiver just needs better logistics. It is exact
Lotsa Helping Hands
Lotsa is the canonical "supporter-network optimist" tool — and the [IDEA-046 reasoning](../ideas/IDEA-046-care-burden-monthly-report.md) explicitly names it as proof that the existing market is over-s
TendTo — $11.99/monthly
TendTo is a horizontal "everything app" — bills + meds + docs + appointments + AI in one shared workspace. IDEA-046 is the opposite: a **single-purpose, single-user, output-first tool** whose entire d