Convergence Radar Convergence Engine

← Feed

F

Cardiac Diary: Consumer ECG Export Organizer + Cardiologist-Ready PDF

17/100

Web app that merges Apple Health / KardiaMobile ECG exports with symptom logs into a timeline and a clean PDF for cardiology appointments β€” organization only, no diagnosis.

Kill. Β· created 2026-07-10 02:59 UTC

saasailong-termrevisit later

Scorecard

newness 3/10
convergence 2/10
demand evidence 1/10
existing spend 2/10
solo feasibility 8/10
speed to mvp 7/10
speed to revenue 2/10
distribution 3/10
competitive gap 2/10
expansion 3/10
founder fit 3/10

Penalty flags
long trust cycle no clear buyer no urgent pain platform policy risk (βˆ’18 from raw 33)

Opportunity brief

What changed
A Mexican small entity (Smart Health Solutions S.A.P.I. de C.V.) filed a US utility patent with 2024 priority on a portable device + method for monitoring and identifying cardiac events (FACT from input). The proposed opportunity is the unclaimed adjacent whitespace: workflow software around EXISTING consumer ECG hardware rather than any new device or identification algorithm (inference).
Why now
Consumer ECG capture (Apple Watch, KardiaMobile) is mainstream, but the input asserts the organization/presentation layer around those recordings is fragmented (inference in input, not sourced). No deadline, mandate, or forcing event exists β€” 'why now' is weak; this is a nice-to-have timing story, not a forced one (hypothesis).
Converging signals
Only one signal is actually present: a single patent filing indicating a small entity believes consumer cardiac monitoring is commercially valuable (FACT). The `signals`/`demand_evidence` array is EMPTY β€” there is zero supplied evidence of complaints, hiring, spend, or mandates. Everything beyond the patent filing is inference.
Customer pain
HYPOTHESIS ONLY: patients with AFib/palpitations accumulate dozens of watch ECGs and struggle to present them coherently to a cardiologist in a 15-minute visit. Plausible, but NO pain evidence was provided in this input, so it cannot be scored as demonstrated.
Who pays
Hypothesized buyer: individual heart patients (B2C, $5-15/mo or one-off report fee). This is a discretionary consumer health purchase by anxious patients β€” historically low willingness to pay, high churn, and no one is compelled to buy (hypothesis). No forced buyer, no employer, no mandated filer.
Solved today
Apple Health already exports each ECG as a PDF; the Kardia app (AliveCor) already generates clinician-shareable reports, and its KardiaCare subscription includes summary reports and human review; apps like Qaly sell human ECG labeling/review; many patients just show the phone to the doctor (hypothesis β€” competitor facts are from general knowledge, not supplied sources).
Why current solutions are bad
Exports are per-recording, not longitudinal, and symptoms live in a separate notes app β€” the timeline correlation view is genuinely missing from the free tiers (hypothesis). But 'mildly inconvenient' is not 'urgent, budgeted pain.'
Proposed product
Non-diagnostic web app: user uploads Apple Health export (ZIP/XML) and/or Kardia PDFs, logs symptoms/medications, app aligns everything on one timeline and generates a dated, cardiologist-ready PDF summary pack before each appointment. Explicitly presentation-only: no rhythm classification, no event identification, no alerts β€” which is also the patent design-around and the FDA line.
MVP version
1-2 weeks solo: Apple Health XML/ECG parser + Kardia PDF ingest, symptom log form, timeline view, ReportLab/HTML-to-PDF appointment summary, Stripe for a $9 one-off report or $7/mo. All parsing is deterministic Python; genuinely fast to build.
30-day build
Ship MVP; post in r/AFib, r/heartpalpitations (rule-compliant), AFib Facebook groups and StopAfib forums offering free report generation to 25 users; collect whether cardiologists actually reacted well to the PDF. This doubles as the missing demand validation.
60-day build
If (and only if) free users convert to paying and report the PDF changed their appointment, turn on Stripe, add medication/BP/weight tracking, SEO pages for 'export Apple Watch ECG for cardiologist' queries.
90-day revenue plan
Realistic ceiling by day 90: tens of paying users at $7-9 = a few hundred dollars MRR (hypothesis). No mechanism visible for fast four-figure revenue β€” consumer health SaaS grows slowly without ad spend, which the founder avoids.
Distribution path
Reddit/forum communities, SEO on long-tail export/appointment queries, possibly AFib patient influencers. No portal of forced filers, no per-transaction wedge, no channel where demonstrated value compels purchase. This is exactly the slow consumer distribution the founder profile avoids.
Pricing hypothesis
$9 one-off appointment report or $7/mo subscription (hypothesis). Low ACV means volume is required, which conflicts with the no-ad-spend constraint.
Technical difficulty
Low. Apple Health export parsing and PDF generation are well-trodden; the ECG waveform rendering from Apple's raw samples is the only mildly fiddly part. 8/10 solo-feasible.
Legal / regulatory risk
Moderate and asymmetric: (a) the patent design-around depends on never 'identifying' events β€” any drift into classification (even a summary stat like 'possible AFib episodes: 4') risks both infringement and FDA SaMD territory (caveat stated in input; not legal advice); (b) storing cardiac data + symptoms is sensitive health data β€” not automatically HIPAA (no covered entity) but privacy expectations and state laws (e.g. WA My Health My Data) apply (hypothesis); (c) trust burden of 'upload your heart data to an unknown solo dev site' is real.
Platform dependency
High: entirely dependent on Apple Health export format and Kardia PDF format, both of which can change without notice; Apple could ship longitudinal ECG summaries natively in any Health app update and erase the product.
Founder fit
Poor-to-moderate. This has NONE of the proven-edge shape: no regulation compelling anyone to file, no government portal, no per-filing monetization. It IS a consumer health app adjacent to 'heavily regulated medical products' and requires patient trust-building β€” both on his avoid list. His parsing/automation skills apply, but that's true of many better-fit ideas.
Breakout potential
Limited. Best case is a niche lifestyle SaaS; expansion paths (clinician-side dashboard, other wearables) drift toward regulated or enterprise territory he avoids.
Final recommendation
KILL for now. The build is easy but the business is weak: no supplied demand evidence, no forced buyer, consumer trust cycle, platform dependency, and it sits on his avoid list rather than his proven government-portal edge. Only revisit if organic complaint-mining later surfaces strong, repeated 'how do I show my cardiologist my watch ECGs' pain with willingness to pay.
Next action
Spend max 2 hours complaint-mining r/AFib and StopAfib.org for explicit 'organizing ECGs for my cardiologist' pain with money signals; if fewer than ~10 strong recent instances, archive permanently and redirect effort to a mandate/portal-shaped opportunity.

Kill arguments (adversarial)

Competitors

β€’ AliveCor Kardia / KardiaCare (link) β€” Owns the hardware, app, clinician-shareable reports, and a paid subscription with summary reports β€” the incumbent free/cheap solution for its own users (general knowledge, not from supplied sources).
β€’ Qaly (link) β€” Paid app offering human review/labeling of Apple Watch and Kardia ECGs plus history tracking β€” already monetizing this exact user (general knowledge, not from supplied sources).
β€’ Apple Health (native) (link) β€” Free per-recording ECG PDF export built into every iPhone; Apple could add longitudinal summaries at any time, erasing the wedge (general knowledge).

Source citations (facts)

No citations captured.

Actions