LOCKED EXECUTION ORDER (Market-Driven)
Phase 1 — Street → Print → Cash (NOW)
Goal: immediate usability + proof of flow
Deliverables (only these): 1. ConceptCard PDFs • poster (11×17) • study (8.5×11) • postcard (5.5×8.5) 2. QR → public promo view • no auth • no mutation 3. One micro-session booking path • manual or Stripe Checkout • creates CardAccess
Outcome: You can print, distribute, scan, sell, and deliver value.
No trips. No Folio. No coach mode yet.
⸻
Phase 2 — Micro-Sessions Booking System
Goal: repeatable sessions, not SaaS
Scope: • One product: Micro-Session • Stripe one-time price • Webhook → CardAccess • Optional calendar slot (lightweight)
Important: This is not a full scheduling platform. It is “pay → access → session”.
⸻
Phase 3 — Trips + FareHarbor (Revenue Stack #2)
Goal: real money, real operations
What gets built: • FH integration (read-only or booking bridge) • Trip ↔ Session clarity • Printed trip cards / briefs • Day-by-day SessionCards (derived)
Still no coaching mode required here.
⸻
Phase 4 — Backend API Module (Translation Work)
Goal: unlock Stripe + FH + future integrations cleanly
Work: • Translate existing TypeORM logic → Prisma • Expose as:
/api/micro-sessions /api/payments /api/access
• Keep business logic in entity actions (as already designed)
This stabilizes everything that follows.
⸻
Phase 5 — Folio (Document Authority)
Goal: compound value, not initial cash • Use Folio to: • generate session scripts • generate reports • generate technical PDFs • Folio becomes post-sale amplification, not entry.
⸻
Phase 6 — Assistant / Coach Mode (Acceleration Layer)
Only when: • sessions are selling • trips are booking • PDFs are printing
Then the assistant: • helps you produce faster • helps users prepare better • does not replace the street layer
⸻
CRITICAL CONFIRMATIONS • ✅ Prioritising printing + street flow is correct • ✅ Coaching mode is optional acceleration, not prerequisite • ✅ Trips + FH come before AI coaching • ✅ Backend API refactor belongs after proof of sales • ✅ You are not delaying value by postponing Folio
⸻
Next Concrete Step (tomorrow)
Choose one, and only one: • Finish HTML/CSS for the 3 ConceptCard PDF templates • Or wire /card/[slug]/pdf fully end-to-end
Everything else stays frozen.
This is a clean, survivable execution path.