⚠ snapshot from 2026-07-12 — pricing P0 + Stripe links now RESOLVED; live truth = Map/To-Dos
Plan — 2026-07-12

Hermes — Completion Plan & Journey Map

5 phases. Each phase has a hard finish line. Subs do the typing; Drew does the deciding.
MAP

The Client Journey

what a Hermes client walks through, start to finish
01Scan QR
→
02Call
(5-min pounce)
→
03$250 deposit
→
04Intake
(17 items)
→
05Site build
+ domain
→
06Snapshot
install
→
07GBP + web
presence
→
08Final
payment
→
09A2P
(1–4 wk)
→
10Carrier
test
→
11Publish 9
workflows
→
12GO-LIVE
(guarantee day 1)
→
13Monthly
reports
HERE Client #1 (Fortified) currently sits between step 07 — GBP and step 08 — Final payment.
P0

Unblock

👤 DREW ~1 hr do first — gates everything
👤 DREW

Resolve pricing conflict: pick ONE setup fee story ($500 vs $250 vs $250+$250 split) and it propagates to every doc.

☐Done when one number, written in CONTEXT.md as a ruling.
👤 DREW

Build 3 per-tier final Stripe links + flip Stripe TEST → PROD.

☐Done when 3 live links tested with a $1-style check, pasted into 02_SALES.
Note: nothing downstream (Connor payment → A2P → go-live) moves until this phase closes.
P1

The Hub

🤖 SUB-AGENT ~2 hrs agent work can run parallel to Phase 0
🤖 SUB-AGENT

Design clients.json schema (stage, 17 intake items w/ status, owed-by-Drew, owed-by-client, next action+owner, doc links, live URLs, cohort counter).

☐Done when schema doc + file exists.
🤖 SUB-AGENT

Seed with real Fortified state from the inventory.

☐Done when FAS's json matches reality (spot-checked by Drew).
🤖 SUB-AGENT

Retrofit HERMES_ONBOARDING_MAP.html to render from clients.json (keep the approved visuals, kill localStorage as truth).

☐Done when edit json → regenerate → change visible in browser.
🤖 SUB-AGENT

Deploy map to Cloudflare Pages.

☐Done when URL loads on Drew's phone.
🤖 SUB-AGENT

Add the discipline rule to 31_HERMES/CLAUDE.md ("any session doing fulfillment work updates clients.json before it ends").

☐Done when rule committed.
P2

Client #1 to Go-Live

MIXED OWNERS clock: A2P 1–4 wks after payment
Clock note: A2P approval takes 1–4 weeks after final payment lands — this is the longest single wait in the whole journey.

🧑‍🔧 CLIENT Connor

  • CP-575 photo
  • Business hours
  • Service-area towns
  • Formal site approval

👤 DREW

  • User seat for Connor + re-point WF-03/WF-06 + owner-phone tag
  • Voicemail greeting on (850) 266-7764
  • Verify contact@ email destination in Cloudflare
  • Finish GBP video verification
  • Collect final payment (needs Phase 0)

🤖 SUB-AGENT

  • 2-min FAS spot-check (survey 3 slides, pipeline 6 stages)
  • Post-payment: A2P submission support
  • Cross-carrier SMS test evidence
  • Publish sequence WF-C2 → C1 → 01 → 02 → 03 → 05a/b/c → 06
  • GSC / Bing / IndexNow indexing
☐Done when 9 workflows published, cross-carrier test passed, go-live confirmed, 90-day guarantee clock started, clients.json updated.
P3

Ops Gap-Fill

🤖 SUBS DRAFT 👤 DREW APPROVES before more clients land
🤖 SUB-AGENT

Monthly report: dry run once for real + reusable template.

☐Done when one actual report produced.
🤖 SUB-AGENT

Onboarding walkthrough call script (~30 min, referenced by install SOP but doesn't exist).

🤖 SUB-AGENT

Client quick-card (incl. DONE-text behavior) — the 1-pager the client keeps.

🤖 SUB-AGENT

Review-seeding mechanics doc (the 2-3 warm names play).

🤖 SUB-AGENT

Cancellation/offboarding SOP (incl. A2P-dies-on-exit script from red-team P2).

🤖 SUB-AGENT

Support channel decision + SPF/DKIM email sending domain doc.

☐Done when each doc above exists, linked from the hub, Drew thumbs-up.
P4

Scale Ready

after Phase 2 proves the machine

"Hermes Demo" sub-account (v3 + fake data) for sales calls.

☐Done when demo loads clean.

GHL pipeline mirror of hub stages via MCP + stage-change automations (the phase-2 hub add-on).

☐Done when moving a client in json reflects in GHL pipeline.

Cohort-1 retro trigger.

☐Done when fires at 5 accounts sold (currently 1/10).
RISK

Risk Strip

what could still go sideways
⏱ A2P is the longest clock — everything about Connor's revenue waits on it; that's why Phase 0 is first.
☎ Postcard scans could start ringing any day — Phase 3's sales-side is already done (script/offer page live), so selling is safe even if ops docs lag.
🗂 Hub only survives if the CLAUDE.md rule ships with it.