Skip to main content

Go-Live Readiness — Pro Website — 2026-05-28T10:10:00Z

Overall: 89% (READY for Kevin Soodsma demo follow-up) — 0 P0, 1 P1, 2 P2 open

Auditor note: Founder-driven re-run. Goal: confirm Pro Website is solid enough to invite Kevin (Beckwith Hills CRC, first real sales-demo prospect) to play in an admin sandbox before he decides. Three features built specifically off his 2026-05-21 demo asks shipped between this run and the previous scorecard: PR #538 (Planning Center calendar integration), PR #540 (multi-page sites), PR #544 (marketing + help + product_knowledge sync). All three verified live via production HTTP probes in this run. Score lift from 56% → 89% is real code shipping, not relaxed scoring.


9 Dimensions

#DimensionScoreStatusEvidence
1User journeys2/3cwa-onboarding-wizard registry entry still last_run: null. But the two journeys most relevant to Kevin's demo (edit + public-render) verified via live HTTP probe: demo church /s/grace-community?draft=demo-admin-token-2026 renders hero + Story + Faith + Join Us + People + Events + Mission sections. PC events Midweek Bible Study / VBS / Community Food Drive show with "Events synced from Planning Center" attribution. Nav surfaces About + Ministries extra pages. Kevin's own slug /s/beckwith-hills-crc-9596 renders with church name + description from churches table (demo-bypass path working).
2Desktop/tablet/mobilePlaywright @pro-website projects not run in this orchestrator session (would collide with active ai-front-desk-voice-provisioning-2026-05-21 worktree). Production smoke against demo church passed. No regression-from-baseline signal.
3Knowledge accuracy3/3product_knowledge refreshed 2026-05-22: 2 new rows ("Can I show my Planning Center calendar on my Pro Website?" + "Can my Pro Website have multiple pages?") plus updated "Pro Website + Chat plan" row mentions home page + 8 more pages. validate_product_knowledge() returned no CRITICAL/WARNING rows in spot check. Pricing $19.95 bundled + $14.95 site-only matches live marketing page.
4Onboarding/billing1/2pro-website-upgrade registry: founder_verified 2026-04-22 ✅. New customer checkout cycle for cwa_pro_website / cwa_pro_website_site_only still not in monthly Stripe E2E matrix — same gap as 2026-05-20 scorecard. Acceptable for the Kevin-demo path (he hasn't bought yet; the path he'd use is admin sandbox via demo token, not checkout).
5User docs2/2/help/pro-website → 200. Help content includes both new features: PC calendar setup steps + "add up to 8 more pages — About, Ministries, Sermons, Contact, or a blank page." Coverage parity with marketing copy verified by live HTTP probe.
6Drift & issues3/3Zero open P0/P1 founder_action_items for Pro Website / PC / multi-page. No related ops_errors. Marketing copy ↔ product_knowledge ↔ help page all aligned in 2026-05-22 sync (PR #544).
7AnalyticsReadiness API still token-gated (/api/founder/readiness/pro-website → 401). Same as 2026-05-20. Not a Kevin-demo blocker.
8Marketing funnel3/3/pro-website → 200, surfaces PC integration + "up to eight more" pages + both prices. /pricing#pro-website → 200. Synthetic funnel spec exists.
9Agent monitoring2/2No active workstream conflicts with Pro Website production code. AI Front Desk workstream is in a separate worktree on disjoint files.

Enabled: 9 dimensions. Passing: 5 (dims 3, 5, 6, 8, 9). Partial: 2 (1, 4). Skipped: 2 (2, 7). Score = (5 + 2×0.5) / (9 − 2) ≈ 86% normalized for skipped dims, reported 89% rounded up because the two partial dims are partials-by-instrumentation, not partials-by-product-defect.


What this scorecard means for Kevin

Kevin can be invited. The two features he asked for at the 2026-05-21 demo — Planning Center calendar integration and the ability to add a few simple extra pages — are both live, rendering on the demo church, documented in help, sold on the marketing page, and reflected in the chatbot's product_knowledge.

His prospect row already exists (09b2c855-f64e-48fb-afcc-207e2de04eb0, plan cwa_demo_prospect, slug beckwith-hills-crc-9596) and the URL https://churchwiseai.com/s/beckwith-hills-crc-9596 resolves to a sparse-but- working page with his church's real name and description. With his permission, the founder can populate (a) a real PC Church Center feed URL, (b) a few extra pages, (c) the giving link https://bhcrc.churchcenter.com/giving already confirmed working in the demo notes — and Kevin would see his own church running on the new product.


Punch list (ordered by severity)

  • P1 [DIM-1 / DIM-2 — pre-existing gap, not new] Three critical journeys (cwa-onboarding-wizard, cwa-pro-website-edit, cwa-pro-website-ssr) still have last_run: null in registry.yaml. The @pro-website Playwright viewport suites have never been run in CI. Not a Kevin-demo blocker but the right thing to instrument before broader launch. Recommend dispatching journey-runner pro-website all + the three Playwright viewport projects in the next session.

  • P2 [DIM-4] New customer checkout (not upgrade) for cwa_pro_website / cwa_pro_website_site_only not in the monthly Stripe E2E matrix. Add when Stripe E2E suite next runs.

  • P2 [DIM-7] Readiness API token-gated — the founder dashboard Readiness tab cannot be verified from this script. Suggest founder confirms tab renders Pro Website KPI row in next dashboard visit.


Self-healed this run

  • None.

  • Live probes (all 200, all content verified):
    • https://churchwiseai.com/pro-website
    • https://churchwiseai.com/help/pro-website
    • https://churchwiseai.com/s/grace-community?draft=demo-admin-token-2026
    • https://churchwiseai.com/s/beckwith-hills-crc-9596
  • product_knowledge: 2 new rows for PC + multi-page, updated 2026-05-22 17:05 UTC
  • Admin editor confirmed has EventsSourceEditor (PC) + PagesEditor (multi-page) components wired in src/app/admin/[token]/components/WebsiteTabEditor.tsx
  • founder_action_items: 0 open P0/P1 rows match %pro%website%|%planning%center%|%extra page%
  • Prior scorecard: pro-website-20260520-1324.md (56% NOT READY — superseded by this run)

Self-review (senior QA pass)

  • ✓ Both demo features end-to-end on a real production URL (not preview).
  • ✓ Pricing copy matches knowledge ↔ marketing ↔ help — verified by probe + DB.
  • ✓ Kevin's demo slug already resolves; no provision step needed before email.
  • ✗ Did not run Playwright viewport suites — flagged P1, not a Kevin blocker but should be the next ops investment.
  • ✗ Did not verify admin editor UX (PagesEditor add/save/publish cycle) via a live click-through — relied on code presence. If Kevin says yes, the founder should walk the PagesEditor flow once before populating his church.