CertPace — death-certificate expediter for funeral homes

1. One-liner

Pre-validates every death-certificate field and auto-chases the stalling physician, so funeral directors file in days, not weeks.

2. Trend signal — why now?

Three things converged in the last 18 months. First, the chase got louder and public. In a January 2026 testimony cycle, Virginia funeral directors told a legislative subcommittee that physician-signature delays in the Electronic Death Registration System (EDRS) “prevent cremations, delay life-insurance and benefit payments, and prolong family grief,” prompting a substitute bill (HB156) requiring medical certifiers to take an EDRS tutorial. The same month, a Georgia TV station ran “Death certificate delays leave some Georgia families in legal limbo.” Families are quoted on the record going after physicians’ licenses. This is no longer a back-office annoyance — it’s making local news.

Second, every state is now on or migrating to an EDRS, and the first funeral-software-to-EDRS auto-integrations only shipped recently (Batesville’s Halcyon ↔ Georgia EDRS was announced as “the first” of its kind, and Passare’s EDRS link is Pennsylvania-only). That means the machine plumbing into state systems is finally real — but coverage is a one-state-at-a-time patchwork, and nobody owns the layer above the portal: validation and follow-up.

Third, document-AI got cheap and good enough to read a hospital face sheet, an ID, and an SSA record, and to catch the exact field errors registrars bounce on — name mismatches, missing suffixes, diacritical characters, un-attempted Social Security Verification, out-of-order workflow steps.

Provenance:

• Signal 1 (demand): Funeral directors testify EDRS physician-signature delays stall cremations + insurance; VA HB156 substitute proposed — https://citizenportal.ai/articles/7347200/subcommittee-recommends-substitute-requiring-edrs-tutorial-for-medical-certifiers-after-funeral-directors-describe-delays — 2026
• Signal 2 (feasibility/economic): “First” funeral-software↔state-EDRS integration just shipped (Halcyon↔Georgia); Passare EDRS is PA-only — coverage is a patchwork with no validation/chase layer — https://www.halcyondcms.com/blog/batesville-announces-first-integration-with-georgia-electronic-death-registration-system-to-streamline-death-record-reporting/ — 2025
• Signal 3 (demand, families): “Death certificate delays leave some Georgia families in legal limbo” — on-record family quotes about chasing physician signatures — https://www.newschannel10.com/2026/01/27/death-certificate-delays-leave-some-georgia-families-legal-limbo/ — 2026-01-27 Category: Workflow automation

3. The opportunity

The death-certificate workflow has two distinct failure points, and the incumbents address neither.

Failure point A — the bounce. Records get rejected by the registrar over avoidable demographic errors: a name that doesn’t match the legal ID, a missing suffix or maiden name, a diacritical mark in a field that only accepts the 26 English letters, a Social Security Verification that wasn’t attempted before submission, or steps done out of jurisdictional order. Each bounce costs a day or two of resubmission.

Failure point B — the chase. The funeral director can’t finalize until the medical certifier (attending physician, hospice MD, ME) completes their half in the EDRS. Doctors are off-shift, lack portal access, list cause-of-death as “pending,” or wrongly believe they aren’t responsible. The director’s only tool today is the phone and a sticky note. There’s no system that knows which cases are stuck on whom, for how long, and escalates automatically.

Incumbents — Passare (2,400 firms), CRäKN/Tribute, Osiris, SRS, Halcyon — are case-management systems of record. Where they touch EDRS at all, it’s a “send your data to the state portal with a few clicks” form-filler, and only in the one or two states they’ve built for. None of them validate before you submit or run the follow-up loop on the certifier. CertPace is a thin, AI-first layer that sits beside whatever software the firm already uses and kills both failure points.

4. Target market

• Primary customer: Owner/managers and arrangement directors at independent US funeral homes and small crematories — 1 to 4 locations, no in-house IT. They run on Passare/CRäKN/Osiris or, surprisingly often, paper and a whiteboard.
• Why they buy: Their words, from the public record — “You should know that that doctor is legally bound to sign your mother’s death certificate. And the fact that he won’t is a problem” and “a missing certified death certificate or unsigned form can add weeks to the process.” Every stalled certificate is a family calling the director daily, an insurance payout frozen, and a cremation that can’t legally proceed. It is reputational and emotional pain, felt on multiple open cases at once.
• Rough TAM reasoning: ~15,700 funeral homes in the US; NFDA member firms average ~113 cases/year, all-in average ~179. Even at a modest per-case or per-seat price, the segment that runs lean and feels the chase most acutely — the independents — is a multi-thousand-firm SAM. I’m not chasing the corporate chains (SCI, etc.); they’ll build in-house.
• Why now for them: EDRS filing deadlines are tightening (VA mandates medical certification within 24 hours; failure is grounds for Board of Medicine discipline). Tighter clocks mean the chase is now a compliance exposure, not just a courtesy, and directors are actively looking for help.

5. Product sketch (MVP)

• Pre-flight validation: upload (or forward) the hospital face sheet, ID, and family intake; CertPace flags the exact fields a registrar will bounce — name/suffix mismatches, diacritical characters, missing biographical data, un-attempted SSV, wrong jurisdiction — before anything is submitted.
• Pending-cases board: one screen showing every open case, who it’s stuck on (family signature, certifier, ME, vital-records office), and how many hours past the legal clock it is.
• Certifier chase agent: auto-sends the physician/hospice/ME office a plain, polite, escalating sequence (email + SMS + fax-ready PDF) with the exact EDRS steps and deadline, then nudges on a schedule until signed — instead of the director re-dialing.
• Escalation pack: when a certifier blows the legal window, one click generates the registrar/medical-board-ready record of attempts (timestamps, contacts, no-responses) directors today assemble by hand.
• Copy-quantity advisor: recommends certified-copy counts per case based on the estate (policies, accounts, titles) so families don’t reorder weeks later.
• State rules pack: per-state field rules, deadlines, and order-of-operations encoded so a director working a multi-state metro doesn’t lose a day to the wrong sequence.
• Works alongside, not instead of: lightweight import from Passare/CRäKN exports or a standalone intake form — no rip-and-replace of the system of record.

6. AI angle — what’s load-bearing

Remove the AI and this collapses into a spreadsheet. AI is doing three jobs that previously required a trained human: (1) reading messy source documents (face sheets, IDs, handwritten intake) and mapping them to the strict registrar field schema, including catching the non-obvious rejection triggers like diacritics and suffix mismatches; (2) drafting context-aware, escalating outreach to certifiers that references the specific case, the specific missing step, and the specific legal deadline in the certifier’s state — not a generic reminder; (3) classifying case status (“stuck on ME review” vs “stuck on family signature” vs “ready to file”) from unstructured updates so the board is always right. The validation rules are the moat-seed; the document parsing and outreach are the labor that turns a 2-week chase into a managed queue.

7. Localization angle

N/A — this is a US-only play by design. The wedge is the localization: US death registration is a 57-jurisdiction patchwork (50 states + DC + territories + a few independent city registrars), each with its own EDRS, field rules, and deadlines. That fragmentation is exactly why a generic global tool can’t exist and why incumbents only cover one or two states. The “localization” here is encoding state-by-state rules — start with 3–4 high-volume states (CA, TX, FL, GA) and expand.

8. Business model — path to $1M–$5M ARR

• Pricing: $149/mo base per funeral home (up to a case volume), or $2–4 per case for higher-volume firms. Sits comfortably under what a single delayed-payout headache costs the firm in goodwill.
• ACV: ~$2,000/firm/year blended (base + overage).
• Rough math to $1M ARR: ~500 firms × ~$2,000 = $1M. That’s ~3% of the 15,700-firm universe.
• Rough math to $5M ARR: ~2,000 firms (Passare’s footprint is 2,400, so this is a proven-reachable density) plus a per-case overage tier as multi-location groups adopt. Add a certified-copy fulfillment referral cut and an insurance-claims-packet upsell.
• Expansion path: more states unlocked → larger reachable base; per-case overage as volume grows; “claims-ready packet” upsell (death cert + attempt log bundled for the family’s insurer); white-label for state funeral-director associations.

9. Go-to-market wedge — first 100 customers

• State association channels: there are ~50 state funeral-director associations plus Selected Independent Funeral Homes. Sponsor/present at 3–4 state conventions (CA, TX, FL, GA) where directors gather specifically to complain about EDRS. One workshop (“file in 3 days, not 3 weeks”) in front of 200 directors converts in person.
• The complaint trail: funeral directors vent in NFDA forums, the r/askfuneraldirectors community, and Facebook groups like “Connecting Directors.” DM/post the directors who’ve publicly complained about EDRS and physician delays with a 90-second Loom showing the chase board on their own state’s rules.
• Crematory beachhead: cremation cases are where the signature delay hurts most (cremation legally can’t proceed until filed). Target the ~independent crematories and high-cremation-rate firms first — sharpest pain, fastest “yes.”
• Per-state launch PR: when CertPace adds a state, pitch the local trade press (Funeral Director Daily, Connecting Directors) — “first tool to validate + chase certifiers in [State].” Free, repeatable, 50 times over.
• Referral from the pain witnesses: every escalation pack a director wins with goes to a registrar and a medical board — directors talk; a firm that stopped losing 2 weeks tells the next firm at the next regional meeting.

10. Build complexity — justification

Medium. Document parsing, outreach orchestration, and a case board are off-the-shelf (vision-capable LLM + standard web/SMS/email stack). The custom work is the per-state rules engine (field validation, deadlines, order-of-operations) — encoded from public registrar handbooks, expanded one state at a time, not a research problem. Deeper EDRS write-back integrations are nice-to-have, not v1: the MVP delivers value purely as a validation + chase layer that produces a filing-ready record and the outreach, even where it can’t yet auto-submit. Small team, 3–4 months to a 3-state v1.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	A workflow/validation tool; the funeral home remains the filer of record. No registrar authority claimed.
Ethical — no harm / dark patterns	✅	Reduces grieving families’ wait and directors’ burden. The escalation is factual, not coercive.
Market exists (evidence above)	✅	Public legislative testimony, news coverage, 2,400-firm incumbent, tightening deadlines.
1–5 person team can build this	✅	Off-the-shelf AI + web stack; rules engine expanded incrementally.
Launchable with <$50K / ₹40L	✅	No capex; cost is build time + a few state conventions.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	17/20	Hair-on-fire: stalled cremations, frozen insurance, families calling daily, compliance clocks with board discipline. Felt on multiple open cases at once.
Demand evidence	15	12/15	Multiple independent signals — legislative testimony, on-record family quotes, news coverage, large paying incumbent. Not yet a clean “people are buying this specific validation+chase product” signal, hence not 14.
Build feasibility	15	11/15	Core is off-the-shelf; per-state rules engine is real work and EDRS write-back varies by state. 3-state v1 in ~3–4 months.
Distribution clarity	15	11/15	Named channels (state associations, trade press, director forums) and a sharp beachhead (crematories). Conversion math is convention-driven, not yet a scraped-list certainty.
Revenue mechanics	15	11/15	Pricing benchmarks against incumbent norms; $1M needs ~500 firms (3% of universe). Per-case overage is a clean expansion lever.
Time to first revenue	10	8/10	Acute pain + low price = fast yes; first paying firm within weeks of a state going live, but gated on having ≥1 state’s rules encoded.
Defensibility	10	5/10	Execution + accumulating per-state rules and chase-outcome data. An incumbent (Passare) could bolt this on — the bet is they’re slow and state-by-state, and CertPace owns the chase workflow they ignore.
Total	100	75/100

13. Qualitative modifiers

Founder-fit tags

operations-heavy · domain-expertise-required — needs a founder (or close advisor) who has actually worked a funeral home or vital-records desk. The product’s credibility lives in getting the per-state rules and the certifier-outreach tone exactly right; get the tone wrong and you torch the firm’s relationship with the hospital.

Key assumptions to validate (3–5)

1. Assumption: Directors will pay ~$149/mo for a tool that lives beside their system of record rather than replacing it. How to test: 20 director interviews + a paid pilot offer; measure how many put a card down for a 3-state beta.
2. Assumption: AI pre-validation catches enough real registrar-bounce errors to matter. How to test: run 50 historical real cases (anonymized) through validation; measure caught-error rate vs. what actually bounced.
3. Assumption: Automated certifier outreach measurably shortens time-to-signature without souring the hospital relationship. How to test: A/B the chase agent vs. director-as-usual on a pilot firm’s open cases; measure days-to-sign and any complaints.
4. Assumption: Per-state rules are encodable from public handbooks at a sustainable pace (≥1 state/2 weeks). How to test: time-box encoding CA + TX from published registrar manuals.

Risk flags

1. Platform dependency / incumbent encroachment: Passare or CRäKN could add validation + chase as a feature for their installed base. Mitigant: own the workflow they treat as out-of-scope, and stay multi-state-neutral (works regardless of their software).
2. Regulatory variance: 57 jurisdictions, each able to change EDRS rules. Encoding is ongoing maintenance, not one-and-done — a real cost line, though also a moat.
3. Trust/tone risk: over-aggressive automated nudging to a physician’s office can backfire on the funeral home’s local relationships. The outreach must feel like the director, not a debt collector.

14. Structured verdict

Score:                  75/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Operations-minded founder with a funeral-industry or vital-records advisor
Time to revenue:        6–10 weeks after first state's rules are encoded
Capital to launch:      $15–30K (build time + 2–3 state conventions)
Top 3 assumptions to validate first:
  1. Directors pay ~$149/mo for a beside-not-instead-of tool — 20 interviews + paid-beta card-down rate
  2. AI validation catches the errors registrars actually bounce — 50 historical real cases, measure catch rate
  3. Auto-chase shortens days-to-signature without souring hospital ties — A/B on a pilot firm
Kill criteria:
  - Abandon if <15% of 40 directors will put a card down for a 3-state paid beta
  - Abandon if validation catch-rate on historical cases is <50% of real bounces
  - Abandon if pilot firms report the chase agent damaged a certifier/hospital relationship

15. Next step — 1-week validation sprint

• Day 1–2: Pull the public registrar handbooks for two high-volume states (CA + TX); encode their field-validation rules and deadlines by hand. Collect 30–50 anonymized historical cases from one friendly firm (or use sample data) and run them through the rules.
• Day 3–4: Book and run 15–20 calls with independent directors and crematory operators (sourced from r/askfuneraldirectors, Connecting Directors, and state-association member lists). Show the chase board and validation flags on their own state’s rules. Ask the closing question: “Would you pay $149/mo for this, starting with a paid beta?”
• Day 5: Go/no-go. Go if ≥6 of ~20 directors say yes and put a card down for a paid beta, and the validation pass catches a credible share of the historical bounces. Otherwise, narrow to crematories-only or kill.

The falsifiable result: card-down rate on a paid beta and measured validation catch-rate — not “directors said it sounded useful.”