The /velocity-deliver orchestrator coordinates 5 specialist skills across a 60-day founder journey. You focus on QA + presenting + energy. It handles everything else.
One coordinator, five specialists, clear handoffs. The orchestrator tracks every founder's state so you never have to remember where they are.
/velocity-deliver [name]/velocity-deliver [name] --amendThe orchestrator remembers context, tracks state, pulls dependencies, and knows what comes next. You just show up.
The checklist model: This is not a rigid sequence. It is a state-tracked workflow. FSMs have judgment. You can override order, skip milestones when appropriate, and adapt to each founder's pace. The system tracks state so nothing falls through the cracks.
Every founder gets the same high-quality experience, every time. The system is the style. The restraint is the signal.
Every founder call is 50 minutes of presentation + coaching, followed by 10 minutes of amendment. The orchestrator handles the amend flow so you can close the loop before the next call starts.
| Time | Block | Details |
|---|---|---|
| 7:00 - 7:30 | Command Center | Review dashboard, check founder states, prep for first call |
| 7:30 - 8:00 | Build Block 1 | Generate deliverables for upcoming calls |
| 8:00 - 12:00 | Calls (4 founders) | 50 min present + 10 min amend per founder |
| 12:00 - 12:30 | Lunch | |
| 12:30 - 1:00 | Build Block 2 | Generate deliverables for afternoon calls |
| 1:00 - 4:00 | Calls (3 founders) | 50 min present + 10 min amend per founder |
| 4:00 - 4:30 | Wrap-Up | Deliver amended assets, update states, prep tomorrow |
7 calls/day x 5 days = 35/week x 4 = 140/month. Each founder needs ~10 touchpoints in 60 days = 120 founders per FSM.
What we expect from every FSM. No ambiguity. No excuses.
| Area | Standard | Why |
|---|---|---|
| Fathom | ON every call, no exceptions | Transcripts feed every downstream skill. No transcript = generic output. |
| Prep | Review founder state before every call | Walking in cold wastes 10 minutes and kills trust. |
| QA | Human eyes on every asset before presenting | AI generates. Humans validate. Never ship without looking. |
| Delivery | Within 24 hours of the call | Speed signals care. Delay signals disorganization. |
| Next Call | Booked before current call ends | Founders who leave without a next call go cold. |
| Accountability | Weekly Slack check-in with every founder | Between calls, silence is abandonment. |
| Escalation | Flag issues with a suggested fix, not just the problem | Leaders bring solutions, not complaints. |
| Client Wins | Share every wow moment in #dfy-feedback | Wins compound morale and prove the system works. |
If a founder goes a full week with zero touchpoints, that is a system failure. Weekly Slack check-ins exist to prevent this.
Every deliverable must have human eyes on it before it reaches the founder. AI generates. You validate. No exceptions.
No transcript means every downstream deliverable is generic. If Fathom fails, schedule a follow-up immediately.
Next call should always be booked before the current one ends. If the founder is asking, you have already failed.
From zero to delivering your first asset. Follow these steps exactly.
Open Terminal on your Mac. Type claude and hit Enter.
Type: /velocity-deliver register [founder_name]
The orchestrator pulls from HubSpot, creates milestone rows, and initializes the founder's state tracker.
Type: /velocity-deliver [founder_name] to see the full milestone checklist and current state.
Type: /velocity-deliver [founder_name] build brand positioning - the orchestrator pulls all dependencies and invokes the specialist skill.
Review every deliverable with human eyes. Check voice, accuracy, formatting, and completeness before presenting.
Share screen, walk the founder through the asset, capture their reaction and feedback live.
After the call: /velocity-deliver [founder_name] --amend
The orchestrator extracts the founder's feedback from the transcript and applies targeted amendments.
Final asset sent within 24 hours. State automatically updates. The system knows what comes next.
Everything you need at a glance. Bookmark this tab.
View all founders and their current milestone states.
View a specific founder's checklist and next action.
Generate the deliverable for a specific milestone.
Run the post-call amendment flow with Fathom transcript.
Mark a milestone as delivered and advance the state.
Register a new founder and initialize their journey.
Known issues and how to fix them. Most problems resolve in under 2 minutes.
Check that all required inputs are present (Fathom transcript, intake data, prior deliverables). Retry once. If it fails again, escalate to Don or Matt with the error output.
If MCP cannot pull founder context automatically, manually provide the files. Point Claude Code to the founder's folder: ~/founders/[name]/
Check spelling. Try searching by email address instead of name. HubSpot search is case-sensitive on some fields.
Remind the founder of the 80% method: we get it to 80% perfect, then iterate on the last 20% together. If they are requesting a fourth round of edits, deliver as-is and address remaining notes on the next call.
Contact Don for a manual Supabase fix. Do not attempt to edit state rows directly. Provide the founder name and the expected vs actual state.