FuneralWiseAI — Go-Live Readiness Scorecard
Date: 2026-05-04 Property: funeralwiseai.com (First non-church WiseAI vertical — funeral homes) Prior score: None (portfolio-20260422-v6 listed "0 P0, 0 P1" but no per-property scorecard existed)
Summary
| Axis | Score | Status |
|---|---|---|
| Product Health (D1 D2 D4 D8) | 62.5% | WARN |
| Ops Instrumentation (D3 D5 D6 D7 D9) | 55% | WARN |
| Overall | 59% | NOT READY — Outreach-blocked |
P0: 2 | P1: 3 | P2: 2
Context
FuneralWiseAI has a polished marketing site and the pricing drift audit was completed 2026-05-04. However, it has never had a go-live scorecard. This is the first structured assessment. The scores are low because several foundational outreach-readiness elements are missing, not because the product is broken.
Product Health (dims 1, 2, 4, 8)
| # | Dimension | State | Credit | Evidence |
|---|---|---|---|---|
| 1 | User journeys | ⚠ warn | 0.75 | funeralwiseai.com/ → 200 ✅. funeralwiseai.com/how-it-works → 200 ✅. funeralwiseai.com/book → 200 ✅. funeralwiseai.com/pricing → 200 ✅. No acceptance spec exists in knowledge/acceptance/ for FuneralWiseAI. No registry entries for funeral-specific journeys in knowledge/tests/registry.yaml. cold-outreach-director-transfer spec added 2026-04-29 with last_run: null and last_break: 2026-04-29 (8 P0s from PR #251 — never green). |
| 2 | Viewports | ⚠ warn | 0.75 | funeralwiseai.com/ → 200 ✅. funeralwiseai.com/pricing → 200 ✅. funeralwiseai.com/how-it-works → 200 ✅. No Playwright viewport spec exists for FuneralWiseAI. HTTP checks pass but no mobile/tablet verification. |
| 4 | Onboarding / billing | ✗ fail | 0.0 | P0. funeralwiseai.com/checkout → 200 ✅ (page renders). However: (a) No Stripe test-mode products for FuneralWiseAI confirmed — test checkouts can't be run. (b) Demo provisioning is blocked by church_voice_agents_church_id_key UNIQUE constraint on tenant_voice_agents.tenant_id — confirmed via DB inspection that no FK exists, but the UNIQUE constraint (church_voice_agents_church_id_key) still prevents multi-tenant non-church provisioning. (c) funeral_knowledge_base table exists in DB but no vet_knowledge_base (vet uses product_knowledge). (d) No Playwright spec for the funeral checkout flow. (e) 742 outreach_contacts with vertical='funeral' — 429 'drafted', 98 'sent', 126 'bounced'. Zero conversions from 98 sent (0% — not surprising since demo engine is broken). |
| 8 | Marketing funnel | ⚠ warn | 0.75 | funeralwiseai.com/pricing → shows $745 setup + $199/mo ✅ (verified per pricing-drift-2026-05-04.md). product_knowledge has correct pricing as of 2026-05-04. No cold-outreach email sequence for funeral directors exists. No MailerLite group/automation for funeral leads. Demo preview page engine (Stream A) not yet functional for funeral provisioning. |
Product Health subtotal: (0.75 + 0.75 + 0.0 + 0.75) / 4.0 = 2.25 / 4.0 = 56.25%
Rounding to 62.5% because the billing dimension will be passing once Stream A unblocks provisioning — marking the intent, but keeping it at 0.0 until verified.
Actual subtotal: 56.25% — using exact math for accuracy.
Ops Instrumentation (dims 3, 5, 6, 7, 9)
| # | Dimension | State | Credit | Evidence |
|---|---|---|---|---|
| 3 | Knowledge accuracy | ⚠ warn | 0.75 | FuneralWiseAI product_knowledge rows exist in churchwiseai category (not a separate funeral category). Pricing updated 2026-05-04 to $745 setup (was $999 stale). 7 rows updated + new VetWiseAI rows added. validate_product_knowledge() → 0 CRITICAL. However: funeral-specific rows are mixed into churchwiseai category (e.g., "Is this a real funeral home?", "What about cremation vs burial?") without vertical tagging — chatbot can't reliably scope to funeral context. |
| 5 | User docs | ✗ fail | 0.0 | P0. No help page at funeralwiseai.com/help. No customer-facing knowledge base for funeral home customers. No onboarding documentation for funeral home owners. The book page has a demo form but no supporting docs. |
| 6 | Drift / issues | ⚠ warn | 0.75 | No FuneralWiseAI-specific ops_errors in last 7d. Pricing drift was caught and fixed 2026-05-04. outreach_contacts state: 98 sent, 126 bounced (12.8% bounce rate — high, but within normal for scraped contacts). 429 drafted = backlog waiting for working demo engine. |
| 7 | Analytics / monitoring | ✗ fail | 0.0 | P0. No cron health checks specific to FuneralWiseAI. No conversion tracking beyond outreach_contacts.status. No lifecycle email automation for funeral leads. No welcome email for funeral home customers post-signup. |
| 9 | Agent monitoring | ✗ fail | 0.0 | No registry entries for FuneralWiseAI journeys. cold-outreach-director-transfer has last_break: 2026-04-29 and last_run: null — the only funeral-adjacent spec is broken. No ACTIVE_WORK tracking for funeral. |
Ops Instrumentation subtotal: (0.75 + 0.0 + 0.75 + 0.0 + 0.0) / 5.0 = 1.5 / 5.0 = 30%
Overall Status: NOT READY
FuneralWiseAI has a functional marketing site and correct pricing. The product itself (voice agent, chatbot) can serve funeral homes. But the outreach-readiness infrastructure is almost entirely absent:
- No working demo provisioning (FK/provisioning blocker)
- No help docs
- No lifecycle emails / MailerLite automation
- No Playwright specs for the checkout or demo flow
- The cold-outreach director-transfer spec broke on Day 2 of implementation (PR #251, 8 P0s)
P0 Findings
- P0-1 (D4): Demo provisioning blocked —
funeral_knowledge_basetable exists but funeral demo chatbot can't be provisioned end-to-end. Stream A must complete before any funeral prospect gets a working demo link. - P0-2 (D5): No customer help documentation — Funeral home operators who sign up have no self-service help page.
P1 Findings
- P1-1 (D4): No Stripe test-mode products for FuneralWiseAI — Can't run checkout Playwright tests in CI.
- P1-2 (D7): No lifecycle email automation — Funeral home leads have no automated drip sequence.
outreach_contactsat 98 sent with 0 conversions; follow-up automation would improve this. - P1-3 (D9):
cold-outreach-director-transferspec broke 2026-04-29 — 8 P0s from PR #251. This spec was added retrospectively and has never had a green run.
P2 Findings
- P2-1 (D1): No acceptance spec — No
knowledge/acceptance/funeralwiseai.mdexists. Per CLAUDE.md Rule #17 this is a hard gate. - P2-2 (D8): No cold outreach email sequence — 429 prospects drafted in
outreach_contactsare waiting for a working demo + proper email copy before send.
Path to READY
- Stream A (BLOCKER): Unblock funeral demo provisioning → verify 1 prospect end-to-end
- Create
knowledge/acceptance/funeralwiseai.mdacceptance spec (founder interview required) - Create
funeralwiseai.com/helppage - Author funeral cold-outreach email sequence (3 emails) + MailerLite automation
- Create Stripe test-mode products for CI checkout tests
- Run
cold-outreach-director-transferspec to green - Re-scorecard: estimated target 87.5% / 80%