HFHS Growth + Customer Care Plan
The four workstreams from the committed plan run as parallel swim-lanes (that's how the work is owned). The five outcomes are the checkpoint spine: one demo roughly every week, each a complete story assembled from pieces of multiple lanes. Everything built by Friday Sep 4; QA week lands the Gate 2 demo Sep 11.
Dashed bars are hard blockers with named dates: the capture standard unblocks the guided-flow build (D3), the consent review unblocks coaching expansion (D4). The Wherk dev lane threads through all four workstreams in demo order - that's the sequencing, not extra headcount.
Create a promise from a real Westport visit. Watch it appear on the master list with an owner and a due date. Let one go past due - watch it escalate HM → GM → Emily.
Why first: it's the smallest build and the biggest trust win - and every later demo writes promises into it, so each week the list gets visibly fuller.
AI drafts three visit summaries. Approve one, edit one, reject one - only the approved and edited versions reach a customer. Kill a provider mid-send and watch the outbox retry without double-contacting anyone.
Why second: it's infrastructure disguised as an outcome. The home plan (D3), coaching drafts (D4), and follow-up sequences (D5) all run through this queue - building it once here means the later demos inherit it.
An HM completes a guided Westport visit - checklist, photos, notes, offline, no completion until requirements are met. In real-time, the AI-generated home plan (profile updates, repairs, projects, promises) lands in the approval queue; approve it and watch the home record and commitment list update.
Why the longest window: this is the ten-day outcome. Ingestion testing with the Westport HMs starts Monday Aug 3 and runs underneath D1 and D2, so by the time the dedicated build window opens Aug 11 the extraction quality is already field-tested - the build week is the guided flow, the real-time loop, and the record views. The dedicated build still only starts on time if the capture standard is signed by Aug 7 (dashed flag in the WS2 lane).
Open a live lead: score, reasons, and recommended membership level on screen. Show the validation numbers against historical outcomes. Watch routing send it to the right rep because of the score, not despite it.
Why six days is enough: Jack's lane runs the scoring design and historical validation during weeks 1–3 (the long purple bar in WS1), so this window is build-and-wire, not research. If validation isn't green by Aug 20, this demo ships "reasons shown, routing manual."
Type an address → instant house profile → lead scored and routed → free inspection booked → guided visit → leave-behind report → automated follow-up drafted and approved → membership close. Every piece was demoed alone in D1–D4; this demo proves they're one pipeline.
Why last: it's the integrating outcome - it can only be true once the other four are. Five days is enough because it's wiring demoed pieces together, not building new ones. Friday's demo doubles as the freeze: whatever passes is what QA hardens.
All five outcomes are fully covered by the four workstreams - but three of the five span two workstreams, and WS4 produces no outcome of its own: it proves the other four (gold sets, E2E testing, scorecard, onboarding). That's why the build is organized by workstream and the checkpoints by outcome.
| Plan outcome | Built by | Demo |
|---|---|---|
| 1 - Sales decision support | WS1 (scoring, routing, coaching) | D4 · Aug 28 |
| 2 - Unified conversion journey | WS1 (assessment, follow-up) + WS2 (first visit) | D5 · Sep 4 |
| 3 - Single verified home record | WS2 (guided flow, home plan) + WS1 (standardized profile) | D3 · Aug 20 |
| 4 - Tracked commitments | WS2 (master list) + WS3 (vendor promises, alerts, escalation) | D1 · Aug 5 |
| 5 - Human-approved automation | WS2 (staff approval) + WS3 (outbox, duplicate prevention) | D2 · Aug 10 |
| Verification of all five | WS4 (gold sets, E2E testing, scorecard, onboarding) | Gate 2 · Sep 11 |
No new build. Gold-set validation (calls + first visits, scored for accuracy, omissions, hallucination), end-to-end failure testing (offline visits, failed providers, retries, approvals, negative feedback, duplicate prevention), pilot scorecard live, onboarding materials out. Friday Sep 11: the Gate 2 demo - the same run as D5, on a hardened system. Contractual checkpoint Mon Sep 21.