SEO NavigatorTransformation Playbook

1st Batch — Transformation Playbook

From manual agency to AI-native centaur, in four phases. Every phase is a self-contained, interactive deployment plan — check off tasks, watch the gates fill, and run the calculators. Pick your phase from the tabs below; your progress saves automatically in this browser.

4Phases
28Sprints
15Gates
~68hJake total
6Agents
7Pillars

What this is. The complete 1st Batch transformation, organized into four deployment phases that map to the four architecture layers. Each phase ships the part of the system that earns its keep before the next phase builds on top of it — revenue-touching delivery first, then automation, then strategy, then scale.

How to use it. Click a phase tab to open its full playbook. Tick a task and it saves on this device; the tab badge and the gate meters fill as you go. Each phase has its own calculator and a source cross-reference back to the underlying 1st Batch documents. Nothing is sent anywhere — progress lives only in your browser.

The 120-day journey — click any phase to open it
Why this order

☳ Bottom-up by revenue impact

The phases deploy the architecture in the order that pays: Layers 3+4 (what serves clients) before Layer 2 (what automates it) before Layer 1 (the story) before scale. Strategy decks don't pay salaries — executed delivery does.

📈 Founder hours fall every phase

The whole point of the centaur model: as the system matures, Jake does less execution. ~20h → ~22h → ~11h across the 90-day transformation, then ~15h to run the next-90 scale cycle — while throughput climbs.

◆ Gates, not vibes

Each phase ends only when its gate criteria are met — a live client, a validated agent, a proven metric. The gate meters in each tab fill as you check off the tasks underneath them.

🧮 Grounded, with one honest caveat

Phases 1–3 are tightly grounded in the 1st Batch source docs. Phase 4 is a forward projection beyond the documented 90-day plan — clearly flagged as such inside that tab.

Who reads what
RoleLives mostly inWhat they own
Jake (Founder)P1P2P3P4Approvals, gates, positioning, Go/No-Go. Responsible for little, accountable for all.
Brooklyn (CRM)P1SNMS build, Conversation AI + NEPQ, the 14 workflows, vertical snapshots.
Trung Le (IT/Dev)P1P2P4Website / Astro builds, IT infrastructure (DNS, webhooks, hosting), deployment + UAT, GHL snapshots.
Hung (AI Automation)P2P3P4Agent fleet, orchestration harness, n8n automation, Command Center, agent prompts & wiring.
Nhu + ContentP1P3QueryMind pipeline, city pages, case-study flywheel, positioning copy.
Phanh (SEO)P2SEO Sentinel system prompt + rubric, audit validation, organic SEO strategy.
Sang + Tung (Ads)P1P2Meta + Google templates, Ad Arbitrage agent, paid lead channel.
Ngọc (HR)P3Role cards, AI-native hiring rubric, OKR performance system.
Sales ManagerP3P4Core Four outbound, prospect list, conversions, expansion.
PMP2P3P4Agent Registry, reporting, beta data, Go/No-Go prep, roadmap.
The North Star
SEO Navigator — the first AI-native marketing agency built for car detailing in the USA. Half the price of the competition, the full marketing ecosystem, run by a small team commanding a swarm of specialist AI agents.
7 pillars · 6 agents · 30+ skills · ~165h/week recovered · $7–12B TAM. Human judgment holds the reins; AI does the running.
P1

MONETIZE

Layers 3+4 · Service Delivery + Ops · 21 days · ~20h Jake
Phase 1 progress
0%  0 / 0
Governing Principle — Hormozi Scaling Roadmap, Stage 3 (Stabilize)
"Deploy the layers that touch revenue first. Strategy decks don't pay salaries — executed service delivery and the systems that run it do. Fix the one thing clients feel, make the founder a non-bottleneck, then scale."
Layer 3 (Service Delivery · HOW) + Layer 4 (Operations · RUN) ship before Layer 2 (Technical · WHAT) and Layer 1 (Strategic · WHY). Phase 1 sets up Stage 5 (Productize) — the Managed-Agent “Hybrid OS” layer in Phase 2.
Week
Owner
00

Team Introduction Sequence

How to roll this out so 11 people understand the architecture without drowning in 62 documents on Day 1. Each person reads only the 2–3 docs tied to their role.

Step 1 · Day 0 · 30 min

Jake-only: Master Index walkthrough

Open the 1st Batch Master Index with department leads (Brooklyn, Nhu, Sang, Tung). Walk the 4-layer map. Frame it: “We start at Layers 3 and 4 — what serves clients and runs ops. Layers 1 and 2 come in Phase 2.”

Step 2 · Day 1 · 20 min / dept

Department-specific briefings

Brooklyn: SNMS Ultimate CRM + Launchpad gaps. Nhu: QueryMind + content templates. Sang: Meta skills + Lead Gen Engine. Tung: Google Ads Knowledge Pack. Each lead reads only their docs.

Step 3 · Day 3 · 15 min

TeamPlay v4 board kickoff

Open SNMS Build Tutorial TeamPlay v4 — the 688-task board across 7 departments. Each person sees their task count, hard gates, and the 10-week timeline. Assign ClickUp tasks. Focus: “Here's what you own.”

Step 4 · Weekly · 15 min

Monday standup vs. the board

Each Monday, review TeamPlay progress by department against the 4 hard gates (Week 1 docs, Week 2 content brief, Week 7 email, Week 7 Urable webhook). Track % complete against the timeline.

Hormozi — minimize Effort & Sacrifice

Reading 2–3 role-relevant docs instead of all 62 shrinks the Value Equation denominator to near-zero. Lower perceived effort → faster adoption. The rollout itself is designed as an offer the team will actually “buy.”

W1

Cash-First Sprint Days 1–5

Get the CRM client-ready and the Skills Libraries into the team's hands. These two systems directly generate and retain revenue — nothing else ships until they work.

S-1A SNMS CRM → Client-Ready Days 1–3 Brooklyn-led
Goal: One real client can be onboarded onto SNMS with Conversation AI in Auto-Pilot, the NEPQ Flow Builder qualifying leads, and at least 3 of the 14 workflows live.
TaskOwnerHrsSource
Configure Conversation AI Primary Bot — Auto-Pilot, 1s wait time, Knowledge Base seeded (web crawler + FAQ + service pricing) Brooklyn 3h SNMS Ultimate CRM → AI Config / P1
Build NEPQ Flow Builder qualification — 4 Capture nodes: Situation → Problem → Implication → Need Payoff Brooklyn 4h SNMS Ultimate CRM → Pillar 2
Activate WF-01 (Speed-to-Lead), WF-02 (Appointment Confirmed), WF-03 (No-Show Recovery) — test all triggers Brooklyn 3h SNMS Ultimate CRM → Workflows
Approve the 21-capability tech stack (18 native GHL + 3 third-party: Instantly.ai, Postmaster, Urable bridge) Jake 1.5h SNMS Ultimate CRM → Tech Stack
Rank the 21 net-new Launchpad tutorials by revenue impact (AI Employee differentiators first) Jake 1.5h Customer Launchpad → Gap Analysis
Record first 3 AI-Employee differentiator videos: Voice AI, Conversation AI Auto-Pilot, Reviews AI Nhu + Minh Chau 4h Customer Launchpad → Coverage Matrix
Hormozi — Speed to First Value

The CRM is the delivery vehicle. Until it works for one client, nothing else matters. On a $1,200 ceramic ticket at ~$200 CAC, payback is well under one month — LTV:CAC clears the 3:1 bar on the first job.

S-1B Skills Libraries → Team Competency Days 3–5 Pillar leads
Goal: Every pillar lead has run the 4-column knowledge cascade (skill defaults → agency customization → client-specific → published) for at least one client. Jake stops being the bottleneck.
TaskOwnerHrsSource
Deploy Google Ads Knowledge Pack — Tung completes the agency-customization column for 1 client (200+ keywords available) Tung 3h GA Knowledge Pack
Deploy Meta skills — Sang completes agency column for Lead Gen Engine + Campaign Accelerator (8-agent pipeline) Sang 3h Meta skills suite
Nhu maps the QueryMind flow (topical map → brief → CQS audit → article) for 1 client Nhu 2h QueryMind → 4 pipelines
Design delivers Brand Board (D.7) Week 1 — upstream of all 17 Canva snapshot templates Nam + Le 6h TeamPlay v4 → Dept 05
Jake reviews all completed agency columns, flags variances against skill defaults Jake 1.5h All Skills Library files
Hormozi — Scaling Roadmap Stage 3, Stabilize

Skills Libraries are the playbooks that let the team deliver without Jake. The 4-column cascade transfers knowledge from skill defaults through to client-specific execution — the system that converts the founder from operator to reviewer.

1 Gate 1 — Revenue Infrastructure 0%
  • 1 real client onboarded on SNMS with Conversation AI + NEPQ flow live
  • At least 3 of 14 workflows activated and tested (WF-01, WF-02, WF-03)
  • All pillar leads completed their Skills Library agency column for 1 client
  • First 3 AI-Employee differentiator videos recorded; Brand Board delivered
  • 21-tutorial Launchpad backlog ranked by revenue impact
Pass → proceed to Week 2. Fail → extend Week 1 by 2 days. Do not advance with an incomplete CRM or an untrained team.
W2

Onboarding Engine Days 8–12

Turn the working CRM + Skills Libraries into a repeatable onboarding system across all 5 verticals: ceramic coating, PPF, window tint, interior detailing, and fleet.

S-2A Department Onboarding × 5 Verticals Days 8–10 All depts
Goal: Each department can onboard a new detailing client in any of the 5 verticals using their Skills Library + CRM combination — with no Jake involvement.
TaskOwnerHrsSource
Build 5 vertical-specific SNMS snapshots (ceramic, PPF, tint, interior, fleet) with pre-loaded workflows + pricing Brooklyn 6h SNMS Ultimate CRM → Data Model
Configure the 4-Campaign Revenue Engine per vertical (C-1 ASC+, C-2 Manual ABO, C-3 Creative Lab, C-4 Retarget) Sang 5h Meta Campaign + Lead Gen
Build Google Ads templates: keyword clusters + negative lists per vertical Tung 4h GA Keyword Architect
Create a content-brief template per vertical via QueryMind topical map → CQS pipeline Nhu 3h QueryMind pipeline
IT: Urable → GHL inbound-webhook bridge built and tested on 1 live client Trung Le 4h TeamPlay v4 → Dept 04
Hormozi — Productize (reduce variance)

Five reusable vertical snapshots mean every new client starts from a proven template, not a blank page. Less effort per onboard, less variance in delivery, faster speed-to-value — the numerator of the Value Equation rises while the denominator falls.

S-2B Pattern C City Pages Days 10–12 Content + Jake QA
Goal: The Pattern C city-page system is operational for franchise / multi-location clients (Ceramic Pro, Sun Stoppers model), proven on 1 client with CQS-passing pages.
TaskOwnerHrsSource
Configure the Pattern C template with entity-authority schema (JSON-LD, sameAs, potentialAction) Jake 3h Pattern C templates
Produce the first 5 city pages using the Pattern C template + QueryMind brief Nhu + Tran 5h City-page templates
Koray City Page Auditor QA pass — 6 CQS-aligned dimensions scored on all 5 pages Jake 1h Koray Auditor + Consensus Audit skills
Design builds city-page visual assets (Nam: hero images; Le: map / location graphics) Nam + Le 4h TeamPlay v4 → Dept 05
Hormozi — make the Core Offer unmistakably valuable

Pattern C city pages are the SEO deliverable franchises buy. Seeing 5 live, schema-rich, CQS-scored pages inside their first two weeks spikes the Dream Outcome × Perceived Likelihood side of the equation — the strongest retention signal there is.

2 Gate 2 — Repeatable Onboarding 0%
  • 5 vertical-specific SNMS snapshots created and tested
  • Google Ads + Meta Ads templates built for all 5 verticals
  • 1 new client fully onboarded with no direct Jake involvement (team-only)
  • Pattern C template producing CQS-passing city pages
  • Urable ↔ GHL webhook bridge tested on live data
Pass → proceed to Week 3. Fail → identify the bottleneck department and assign Jake pairing time to that one department only.
W3

Retention Machine Days 15–21

Build the monthly reporting rhythm and prove the whole stack works end-to-end. This is the “Track Attendance” horseman of Hormozi's Five Horsemen of Retention.

S-3A Monthly Reporting System Days 15–17 Jake + leads
Goal: An automated monthly-report pipeline is operational. SEO Sentinel runs at ~$1.75/run, replacing ~3h of manual work. Reports flow from data collection to client-ready output.
TaskOwnerHrsSource
Configure Monthly Report Index — the WF4 hub with the Managed-Agent MVP task pipeline Jake 3h Monthly Report Index
Build the client-facing Monthly Report template with per-pillar KPI dashboards + MoM deltas Jake 2h Monthly Report — Jake
Sang + Tung populate the first live report with Meta + Google Ads performance data (1 client) Sang + Tung 3h Meta Perf Hub + GA Auditor skills
Nhu populates the SEO section — rankings, traffic, content velocity, QueryMind throughput Nhu 2h QueryMind QA
Brooklyn populates the CRM section — lead flow, conversion rates, workflow trigger counts, AI response metrics Brooklyn 2h SNMS Ultimate CRM → Go Live
Hormozi — Five Horsemen, “Track Attendance”

The monthly report is the single most powerful retention tool. Clients who see measured progress stay; clients who don't, churn. At ~$1.75/run via SEO Sentinel vs. ~3h of manual work, the report pays for itself on the first client and removes the most common reason agencies lose accounts.

S-3B Prove It Works — End-to-End Days 17–21 Jake + all leads
Goal: Run one client through the full stack — CRM onboarding, ads launch, content, city pages, monthly report — and measure against the 90-Day Transformation graduation criteria.
TaskOwnerHrsSource
Select 1 existing client as the “proof case” — run full Centaur delivery across all 7 pillars Jake 2h AI driven agency → 7 Pillars
Measure: time-to-first-deliverable, team hours vs. old process, client-satisfaction signal Jake 2h 90-D Transfo → criteria
All department leads document blockers, process gaps, and “what I wish I had” for Phase 2 input All leads 1h ea TeamPlay v4 → all depts
Jake compiles the Phase 1 retrospective — what worked, what broke, what to systematize in Phase 2 Jake 2h Master Index → L3+L4
3 Gate 3 — Phase 1 Complete: MONETIZE Proven 0%
  • Monthly-report pipeline produces a complete, client-ready report in under 2 hours (vs. 6+ hours, old process)
  • 1 proof-case client received full 7-pillar Centaur delivery within the Phase 1 window
  • All department leads can onboard a new client without Jake pairing
  • Time reduction ≥ 30% faster than the pre-architecture process (90-Day plan criterion)
  • Retrospective documented with an explicit Phase 2 input list
Pass → graduate to Phase 2: SYSTEMATIZE (Layer 2 technical deployment, 90-Day Sprint 2). Fail → extend by 1 week and re-run Sprint 3B with retrospective adjustments.
$

Money Model & Offer Stack

Phase 1 doesn't just deploy systems — it activates two stacked money models. Layer the four offer types so LTV climbs and CAC is recovered fast. Toggle between the detailing-client engine (what SNMS sells for the shop) and the agency's own offer (what SEO Navigator sells to the shop).

Attraction

Free / low-cost wash + inspection

$0–$49

Conversation AI books it in 30 sec. Penny-gap volume play — gets the vehicle (and owner) in the bay.

Core

Ceramic coating / detail

$599–$1,500

The thing they buy. NEPQ flow qualifies; close-rate target 35%+.

Upsell

PPF + tint bundle

$1,500–$6,500

Classic “can't have coating without paint protection” pairing. Lifts average ticket sharply.

Downsell

Payment plan / interior-only

$199+

GHL Payments split. Captures the no-yet buyer instead of losing them.

Continuity

Annual maintenance + VIP

$150→$850 CLV

3-year post-purchase nurture, tiered VIP, referral trigger links. Repeat-rate target 60%+.

Hormozi — stack offers multiplicatively

The SNMS 6-Pillar engine raises customer lifetime value from the industry's ~$150 to $850+ by chaining attraction → core → upsell → continuity. Phase 1 ships the CRM workflows (WF-01…WF-14) that make every stage automatic.

Attraction

Free Local SEO / AI-visibility audit

$0

Lead magnet. Consumable in <15 min, shows the gap, opens the conversation.

Core

Website build (client-owned)

~$2,500–$4,500

Half of Detailers Roadmap's $5,500–$9,250 — same quality, owned by the client.

Upsell

Bundled retainer (SEO + Ads + CRM)

monthly

The full 7-pillar ecosystem. Where the real LTV lives.

Downsell

Single-pillar starter

scoped

One pillar (e.g. Google Ads only) for budget-constrained shops; expand later.

Continuity

“Hybrid OS” managed-agent retainer

~$1,500–$2,000/mo

The Phase 2 productized layer. Agent swarm runs delivery; margin triples.

Hormozi — Productize for LTV:CAC

The Hybrid OS is the second premium product to the same client base — Stage 5 of the Scaling Roadmap. It's gated to Phase 2 on purpose: don't sell the autonomous layer until the agent fleet is running. Phase 1 proves the manual version first.

Unit Economics Calculator

Live LTV, payback, and LTV:CAC for either money model. Defaults are grounded in the source docs — ceramic AOV, 55% service margin, agency Hybrid OS retainer. Drag the sliders to pressure-test the numbers before you commit budget.

Inputs

$1,200
55%
2.5×
$200

Outputs

Lifetime value (LTV)$1,650
LTV : CAC ratio8.3:1
Gross profit / customer$1,650
Payback period0.1 orders
Healthy — LTV:CAC clears the 3:1 target. Acquire aggressively.
Hormozi — 3:1 is the floor, not the goal

Below 3:1, you're buying revenue at a loss once overhead is counted. The agency model runs subscription LTV = (monthly profit ÷ churn); the client model runs transactional LTV = AOV × margin × lifetime purchases. Both are wired into the toggle above.

RACI Ownership Matrix

Who is Responsible, Accountable, Consulted, and Informed across the six Phase 1 workstreams. Jake is Accountable everywhere (the founder owns the outcome) but Responsible almost nowhere — the point of Phase 1 is to make that true.

Workstream JakeBrooklynNhu / ContentSangTungDesignTrung Le (IT)
CRM build & AI configARIIICC
Skills Library cascadeACRRRII
Vertical onboarding snapshotsARCRRCC
Pattern C city pagesAIRIIRI
Monthly reporting pipelineRCCCCIC
Urable ↔ GHL integrationACIIIIR
R Responsible — does the work A Accountable — owns the outcome C Consulted — input before I Informed — told after

Risk Register

The honest risks tracked in the strategic vision, plus the execution risks specific to a 21-day deployment. Each carries a likelihood, an impact, and a mitigation already wired into the plan.

R-01Founder bottleneck returnsLikelihood: MedImpact: High

If Jake stays Responsible (not just Accountable), the whole Stabilize thesis collapses and throughput caps at his calendar.

Mitigation: Gate 2 explicitly requires a team-only onboarding with zero Jake involvement. The RACI matrix keeps Jake out of the Responsible column on 5 of 6 workstreams.

R-02CRM not truly client-readyLikelihood: MedImpact: High

Conversation AI or the NEPQ flow looks configured but fails on a real lead — the delivery vehicle stalls and every downstream sprint inherits the debt.

Mitigation: Gate 1 demands a live client with 3 tested workflows, not a demo. The 42 TeamPlay test cases run before go-live.

R-03Dependency chain slips (DNS → email → content)Likelihood: MedImpact: Med

Trung's DNS/deliverability work (Dept 04) blocks Sang's email, which blocks Nhu's newsletters, which block Brooklyn's CRM campaigns. One slip cascades.

Mitigation: The dependency map below front-loads DNS and the Brand Board to Week 1. Both are critical-path and tracked as hard gates.

R-04Anthropic platform riskLikelihood: LowImpact: High

Heavy reliance on Managed Agents + Claude Skills. A pricing or feature change would expose the model. (Tracked in the strategic vision.)

Mitigation: Skill definitions are portable to other frontier models; all client data lives in GHL / WordPress / ClickUp, not Anthropic infrastructure. Phase 1 stays manual — agent dependency is a Phase 2 concern.

R-05Team overwhelm / low adoptionLikelihood: LowImpact: Med

62 documents and a 688-task board can paralyze an 11-person team if dropped all at once.

Mitigation: The Team Introduction Sequence gives each person only their 2–3 docs. Weekly 15-min standups track against gates, not the full backlog.

Critical-Path Dependency Map

The one chain that determines whether Phase 1 ships on time. It runs straight through the TeamPlay v4 board's hard gates — technical plumbing unblocks email, which unblocks content, which feeds the CRM.

Trung Le
DNS & deliverability

DKIM / SPF / DMARC + Urable webhook

Sang
Email deliverability

Warm-up, inbox placement

Nhu
Newsletters & nurture

50 newsletters, 375 SMS

Brooklyn
CRM campaigns live

WF-01…WF-14 enrolled

Parallel critical item: Design's Brand Board (D.7, Nam) is upstream of all 17 Canva snapshot templates — it must land in Week 1 so both designers reference the same palette and typography. Hard gates on the path: Week 1 docs · Week 2 content brief · Week 7 email · Week 7 Urable webhook. Phase 1 covers the first two; the Week 7 gates carry into the full 10-week TeamPlay build.

Source Document Cross-Reference

Every sprint traces back to specific 1st Batch documents. Links resolve to the real files in this folder.

SprintPrimary source documentsLayer
S-1ASNMS Ultimate CRM, Customer LaunchpadL3 · Service Delivery
S-1BGoogle Ads Skills, Meta Skills, QueryMind, TeamPlay v4L3 L4
S-2ASNMS (Data Model), Meta Campaign Accelerator, Google Ads Keyword Architect, TeamPlay (Dept 04)L3 L4
S-2BPattern C templates, Schema Generator, TeamPlay (Dept 05)L3
S-3AMonthly Report Index, Monthly Report — Jake, Performance Hub + Auditor skillsL4 · Operations
S-3BAI driven agency (7 Pillars), 90-D Transfo, Master IndexL3 L4

What Comes Next — Phase 2: SYSTEMATIZE

After Gate 3 passes, Phase 2 deploys Layer 2 (Technical Architecture): the 6-agent Managed-Agent fleet, the n8n automation playbook, and the productized Hybrid OS retainer.

Phase 2 Preview — 90-Day Transformation Sprint 2 (Days 31–60)
Layer 2 codifies the AI systems that make Phase 1's manual processes autonomous. Deploy 6 agents in 8 days — PM Pulse, SEO Sentinel, Content Catalyst, Revenue Relay, Ad Arbitrage, Build Bot — recovering ~165 hours/week across the fleet.
Targets: SOP accuracy ≥ 90%, agent-fleet accuracy ≥ 85%, ≥ 30% hour reduction. Gaps closed: G1 Agent Fleet, G4 Hybrid OS, G7 Outbound + Brand. Jake ~22h · Team ~40h.
P2

SYSTEMATIZE

Layer 2 · Technical Architecture · 30 days · ~22h Jake
Phase 2 progress
0%  0 / 0
Governing Principle — Hormozi Scaling Roadmap, Stage 5 (Productize) → Stage 6 (Optimize)
"Better beats more. Don't hire bodies to scale delivery — deploy the system that does the delivery, then sell the system as a product. The agent swarm is the second premium product to the same client base."
Layer 2 (Technical · WHAT) ships on top of the proven Layer 3+4 base. The Hybrid OS retainer that the fleet enables is the LTV:CAC multiplier — gated to the end of Phase 2 on purpose. Maps to the 90-Day Transformation, Sprint 2 (Days 31–60).
Week
Owner
00

Pre-Deploy Readiness

Four things must be true before a single agent runs. Confirm these in the Day-0 kickoff so Week 1 isn't spent chasing access.

Check 1 · Platform access

Managed Agents beta enabled

Anthropic Managed Agents beta access confirmed, beta header set, and the $0.08/session-hour pricing model understood. Sprint 1 test budget ~$50–100 approved.

Check 2 · Integrations

MCP + triggers wired

SEO Utils MCP reachable; external API keys ready (Apify, Firecrawl, Google Maps, OpenAI, Gemini, Perplexity); ClickUp status trigger + Slack slash-command path scoped.

Check 3 · Ownership

Roles assigned

Hung owns AI automation (harness, agents, n8n). Trung (IT) owns infrastructure + website/Astro. Phanh owns Sentinel's system prompt + rubric. Jake approves spend + the architecture map. PM owns the ClickUp Agent Registry.

Check 4 · Phase 1 closed

Gate 3 passed

Phase 1 must be green: CRM live, repeatable onboarding, monthly reporting working. Layer 2 automates these proven manual processes — don't automate what isn't yet proven.

Hormozi — sequence beats speed

Building the agent fleet before the manual model is proven is the classic premature-optimization trap. Phase 1 earned the right to automate; Phase 2 cashes it in. Readiness checks keep the order honest.

W1

Harness + First Agent Days 1–8

Build the reusable orchestration harness once, then deploy SEO Sentinel v1 as the proof agent. This is the hard week — the abstraction built here is what makes agents 2–6 trivial.

S-1A Reusable Orchestration Harness Days 1–5 Hung-led
Goal: A generic harness that triggers Managed-Agent sessions, streams their events, and routes their outputs — with a per-agent config-file pattern so every future agent plugs in with zero code changes.
TaskOwnerHrsSource
Build the dispatcher + config-file pattern (./agents/<name>.json: agent_id, kickoff prompt, ClickUp fields, delivery channels) Hung 6h Reuse PRD — Orchestration
Implement session lifecycle state machine + SSE event handling with reconnect logic Hung 5h Reuse PRD → lifecycle
Add idempotency, logging, and the HITL gate handler (stubbed for v1 — goes live with PM Pulse in Week 3) Hung 4h Reuse PRD → HITL
Deploy to VPS and pass the 7-test integration suite Hung 3h Reuse PRD → tests
Approve Anthropic API spend budget (~$50–100 Sprint 1) + sign off on the harness architecture Jake 1h PRD Local Automation
Hormozi — build the asset once

The harness is the leverage. Built properly once for Sentinel, it carries Catalyst, Revenue Relay, Ad Arbitrage, Build Bot, and PM Pulse for free. The abstraction pays for itself on the second agent — classic “better beats more.”

S-1B SEO Sentinel v1 — Proof Agent Days 5–8 Phanh + Hung
Goal: One Managed Agent — SEO Sentinel — runs the 5 Local SEO Automation modules against a real client on demand at ~$1.75/run, ~20–30 min, replacing ~3 hours of analyst work. Read-only: it audits, it never publishes.
TaskOwnerHrsSource
Create the SEO Sentinel agent + environment config; wire 5 modules (GBP, On-Page, Geographic grid, Citations, AI Visibility) via bash + SEO Utils MCP Hung 5h PRD Local Automation → §7
Phanh writes the v1 system prompt + scoring rubric (coverage, accuracy, structure) Phanh 3h SEO Lead Handoff
Wire triggers: ClickUp status → “Ready” and Slack slash-command; output posts to Slack + updates the ClickUp task Hung 3h PRD → triggers
Run T1 + T2 dry runs on a synthetic client; iterate the system prompt with the Phanh Phanh 2h PRD → testing
Hormozi — proof over promise

Sentinel is read-only on purpose: the riskiest thing an agent can do is publish. Prove accuracy on audits first, earn trust, then graduate to client-facing actions behind HITL gates. ~$1.75/run vs. ~3 analyst hours is the unit win that funds the whole fleet.

A Gate A — First Agent Validated 0%
  • Orchestration harness deployed to VPS; 7-test integration suite green
  • SEO Sentinel agent exists; agent_id recorded in ClickUp + version control
  • All 5 modules run end-to-end against a real client at ~$1.75/run
  • T1 validation passed — Sentinel's audit matches the reference on coverage / accuracy / structure (Phanh sign-off, ~Day 18 of the PRD roadmap)
Pass → proceed to Week 2 and start cloning agents. Fail → hold the fleet — a broken harness or inaccurate Sentinel poisons every agent built on top of it.
W2

Graduate the Fleet Days 9–15

Cash in the harness abstraction: plug in Content Catalyst and Revenue Relay via config files, no new orchestration code. In parallel, stand up the n8n playbook as the no-Managed-Agent fallback path.

S-2A Agents #2 & #3 via Config Days 9–12 Hung + pillar leads
Goal: Content Catalyst and Revenue Relay run on real client data — each added by dropping in an agents/<name>.json with zero changes to the dispatcher. This is the test of whether the harness abstraction actually holds.
TaskOwnerHrsSource
Drop in catalyst.json — wire Content Catalyst to QueryMind MCP (brief gen, meta optimization, AEO scoring) Hung 3h Reuse PRD → config pattern
Content Lead writes Catalyst's system prompt + rubric; validate brief output vs. a reference brief Nhu 3h QueryMind pipelines
Drop in revenue-relay.json — wire Revenue Relay to GoHighLevel MCP (follow-up sequences, lead scoring) Hung 3h SNMS CRM + Reuse PRD
Confirm the zero-code claim: log the diff — only config files added, dispatcher untouched Jake 1h Reuse PRD → acceptance
Hormozi — leverage compounds

Agent #1 took a week. Agents #2 and #3 take a config file each. That curve is the entire thesis of Layer 2 — build the system, then the marginal cost of capacity collapses toward zero.

S-2B n8n Playbook — Fallback Path Days 12–15 Hung + Phanh
Goal: The 4-module n8n Local SEO Automation playbook runs hands-free from a single form — a no-Managed-Agent path that saves 30+ hours/client/month and de-risks platform dependency.
TaskOwnerHrsSource
Build the 4 n8n modules: GBP Intelligence (44-point), On-Page Engine, Geographic grid (9/25-pt via Apify), Citation/NAP Hung 6h Local SEO Automation Playbook
Wire the pipeline: web form → n8n parallel APIs → Code scoring → OpenAI HTML report → SendGrid → Airtable Hung 4h n8n Playbook → flow
Phanh validates n8n report output parity against a Sentinel run on the same client Phanh 2h n8n Playbook
Hormozi — never one channel deep

Two paths to the same outcome (Managed Agent + n8n) is risk reversal at the infrastructure level. If Anthropic pricing or features shift, delivery doesn't stop — the n8n path keeps the SEO audits flowing.

B Gate B — Fleet Scales by Config 0%
  • Content Catalyst + Revenue Relay both running on real client data
  • Zero-code claim verified — agents added by config file only, dispatcher unchanged
  • n8n 4-module playbook runs hands-free from a single form submission
  • n8n output reaches parity with the Managed-Agent audit on the same client
Pass → proceed to Week 3 — the remaining agents + coordinator. Fail → if adding an agent needed code changes, fix the harness abstraction before going further.
W3

Coordinate & Command Days 16–22

Complete the fleet (Ad Arbitrage, Build Bot), then deploy PM Pulse — the coordinator that delegates to specialists and activates the HITL gates for client-facing output. Wire it all into the Unified Command Center.

S-3A Agents #4 & #5 + PM Pulse Coordinator Days 16–19 Hung + leads
Goal: Ad Arbitrage and Build Bot deployed by config; PM Pulse coordinator delegates to all 5 specialists, synthesizes outputs, posts to Slack — with the HITL gate now live for anything client-facing.
TaskOwnerHrsSource
Deploy Ad Arbitrage (ad-arbitrage.json) — Google + Meta reporting, copy variants, audit reports; Sang/Tung write its rubric Sang + Tung 3h Manage Agent SEO swarm
Deploy Build Bot (build-bot.json) — migrations, schema audits, Lighthouse + Playwright UAT Hung 3h Manage Agent SEO
Deploy PM Pulse coordinator — multi-agent delegation, output synthesis, Slack posting Hung 4h AI Orchestration diagram
Activate + test the HITL Slack gate on a client-facing deliverable (email draft / GBP post) — nothing ships without approval Jake 2h Reuse PRD → HITL
Hormozi — the human keeps the reins

PM Pulse is where agents start producing client-facing work, so the HITL gate goes live here. The centaur model holds: AI throughput, human approval before anything reaches a client. Speed without a quality gate is just faster mistakes.

S-3B Unified Command Center + Agent Registry Days 19–22 Hung + PM
Goal: One ClickUp + Slack control surface where every agent's runs, costs, and outputs are visible, and an Agent Registry that makes the fleet auditable and governable.
TaskOwnerHrsSource
Stand up the Unified Command Center (ClickUp + Slack) across the 7 workstreams Hung 4h Automating Agency Workflows
Build the ClickUp Agent Registry v1 — agent_id, owner, scope, cost/run, last run, status per agent PM 3h SN Workstream PM
Define governance: spend caps per agent, escalation paths, and the weekly agent-fleet review cadence PM 2h SN Workstream PM → governance
Hormozi — what gets measured gets managed

The Command Center turns six invisible cloud agents into a dashboard a human can run. Cost-per-run, accuracy, and hours saved are visible per agent — the basis for the Phase 2 graduation metrics and every optimization that follows.

C Gate C — Full Swarm Coordinated 0%
  • All 6 agents deployed (PM Pulse + 5 specialists) — the 8-day deploy target met
  • PM Pulse delegates to specialists and synthesizes outputs end-to-end
  • HITL Slack gate tested — no client-facing output ships without human approval
  • Unified Command Center + Agent Registry live; per-agent cost and status visible
Pass → proceed to Week 4 — productize. Fail → if coordination or HITL is shaky, keep specialists running solo and delay PM Pulse rather than shipping ungated output.
W4

Productize the Hybrid OS Days 23–30

Turn the working swarm into a sellable product, enroll the first 2 beta clients, and prove the graduation metrics: SOP accuracy ≥90%, fleet accuracy ≥85%, and ≥30% hour reduction.

S-4A Hybrid OS Package + 2 Beta Clients Days 23–26 Jake + PM
Goal: The Hybrid OS retainer is packaged as a real offer (~$1,500–$2,000/mo), the GHL snapshot is built, and 2 existing clients are enrolled as betas. Enrollment is a phone call, not a project.
TaskOwnerHrsSource
Package the Hybrid OS offer — scope, deliverables, price anchor vs. Detailers Roadmap, guarantee Jake 3h AI driven agency → Hybrid OS
Build the Hybrid OS GHL snapshot (the productized delivery container) Trung Le 5h 90-D Transfo → G4 Hybrid OS
Enroll 2 beta clients — one call each, grandfather pricing in exchange for feedback Jake 2h 90-D Transfo → beta
Hormozi — Productize (Scaling Roadmap Stage 5)

A second premium product to the same client base is the highest-leverage LTV:CAC move there is. The swarm already runs delivery, so gross margin on the Hybrid OS is structurally higher — that's the “triple the margin” claim made real.

S-4B Prove the Metrics — Full UAT Days 26–30 Jake + all leads
Goal: Run the full 12-agent UAT (334 checks, ~$9.65/run) on the beta clients and measure the swarm against the graduation bar. Document a Phase 2 retrospective with Phase 3 input.
TaskOwnerHrsSource
Run the 12-agent parallel UAT (239 of 334 checks automated, ~40 min, ~$9.65/run) on both beta clients Trung Le 3h AI driven agency → UAT
Measure the bar: SOP accuracy ≥90%, fleet accuracy ≥85%, ≥30% hour reduction vs. manual Jake 2h 90-D Transfo → criteria
Compile the Phase 2 retrospective — what to optimize (Stage 6) and Phase 3 (Layer 1) input Jake 2h Master Index → Layer 2 review
D Gate D — Phase 2 Complete: SYSTEMATIZE Proven 0%
  • 6-agent swarm live and coordinated through PM Pulse with HITL gates
  • Fleet accuracy ≥85% and SOP accuracy ≥90% on beta-client UAT
  • ≥30% hour reduction vs. the pre-agent manual process, measured
  • Hybrid OS packaged and 2 beta clients enrolled and live
  • Retrospective documented with an explicit Phase 3 (Layer 1) input list
Pass → graduate to Phase 3: AMPLIFY (Layer 1 strategic positioning, outbound flywheel, hiring plan; 90-Day Sprint 3). Fail → hold beta enrollment, fix the failing metric, and re-run UAT before scaling.

The Agent Fleet

Six Managed Agents on Anthropic infrastructure — one coordinator and five specialists — deployed in 8 days versus four weeks of DIY. Hours saved are weekly capacity recovered across the client book. Pricing is standard tokens + $0.08/session-hour, no idle charges.

PM Pulse
Coordinator

Delegates to specialists, synthesizes their outputs, posts to Slack. Owns the HITL gate for client-facing deliverables.

coordination layerWeek 3
🛰
SEO Sentinel
Specialist

Reports, audits, rank monitoring, AEO. Runs the 5 Local SEO modules at ~$1.75/run, replacing ~3h of analyst work.

~37h/wkWeek 1
Content Catalyst
Specialist

Brief generation, meta optimization, AEO scoring — wired to QueryMind MCP.

~30h/wkWeek 2
🔁
Revenue Relay
Specialist

GHL automation, follow-up sequences, lead scoring — wired to the GoHighLevel MCP.

~28h/wkWeek 2
📊
Ad Arbitrage
Specialist

Google + Meta reporting, ad-copy variants, audit reports across both ad platforms.

~25h/wkWeek 3
🔧
Build Bot
Specialist

Site migrations, schema audits, Lighthouse + Playwright UAT runs.

~18h/wkWeek 3
~165h recoverable per week across the fleet once all six are live — the capacity that funds the Hybrid OS margin and removes the “hire to scale” tax.

SEO Sentinel Deployment Pipeline

The end-to-end chain for Agent #1, straight from the Master Index's Layer 2 pipeline. Each link is a real document — WHAT the agent does, HOW it's triggered, WHO owns the deliverables, and the n8n alternative path.

PRD
What it does

PRD Local Automation — 19-section spec, 5 modules

Harness
How it triggers

Reuse PRD — config pattern, SSE, HITL

Handoff
Who owns it

SEO Lead Handoff — prompt + rubric

n8n
Fallback path

Local SEO Automation Playbook — 4 modules

Why this order matters: the harness is built generic so agents 2–6 inherit the trigger + streaming + HITL plumbing for free. The n8n path is deliberately parallel — it delivers the same SEO audit without depending on the Managed Agents platform, which is the single biggest tracked risk (R-01 below).

Agent ROI Calculator

Live payback and return for the fleet. Defaults are grounded in the source docs — SEO Sentinel replaces ~3 analyst hours at ~$1.75/run. Toggle to the fleet view to see total weekly capacity recovered in dollars.

Inputs

3.0 h
$25
32
$1.75

Outputs

Labor value created / mo$2,400
Agent cost / mo$56
Net savings / mo$2,344
Return on agent spend43×
Deploy — the agent returns far more than it costs. Every run is almost pure margin.
Hormozi — the real ROI is the freed human

The dollar return is large, but the point isn't token savings — it's that ~165 hours/week of human capacity move from execution to judgment, relationships, and selling the Hybrid OS. That reallocation is what triples margin, not the $1.75 line item.

RACI Ownership Matrix

Phase 2 is the AI-automation buildout — Hung is Responsible for the technical spine (agents, harness, n8n); Trung (IT) owns infrastructure, deployment, and website/Astro builds. Jake stays Accountable and owns the two judgment calls that can't be delegated: spend approval and the HITL gate on client-facing output.

WorkstreamJakeHung (AI)PhanhContent (Nhu)Ads (Sang/Tung)PM
Orchestration harnessARIIIC
SEO Sentinel v1ARRIII
Fleet graduation (agents 2–5)ARCCRI
PM Pulse + HITL gatesRRCCCA
Command Center + RegistryIRIIIA
Hybrid OS productizationRCIIIC
R Responsible — does the work A Accountable — owns the outcome C Consulted — input before I Informed — told after

Risk Register

Phase 2's risk profile is higher than Phase 1's — you're now dependent on a beta platform and shipping AI-produced work toward clients. Each risk has a mitigation already wired into the plan.

R-01Anthropic platform dependencyLikelihood: MedImpact: High

The fleet runs on Managed Agents (public beta). A pricing change, feature deprecation, or outage would hit delivery directly — this is the top risk named in the strategic vision.

Mitigation: The n8n playbook (Week 2) delivers the same SEO audits without Managed Agents. Skill definitions are portable to other frontier models; all client data lives in GHL / WordPress / ClickUp, never on Anthropic infrastructure.

R-02Agent ships a bad client-facing outputLikelihood: MedImpact: High

Once PM Pulse produces email drafts or GBP posts, an unreviewed error reaches a client and damages trust.

Mitigation: HITL Slack gate is mandatory for any client-facing action (Week 3). Sentinel and the early agents are read-only by design — trust is earned on audits before agents touch published output.

R-03Harness becomes a single point of failureLikelihood: LowImpact: High

Every agent plugs into one orchestration layer. A harness bug or VPS outage takes the whole fleet down at once.

Mitigation: 7-test integration suite gates the harness before any agent rides on it (Gate A). Idempotency + reconnect logic built in; the n8n path is an independent fallback for the highest-volume workflow.

R-04Fleet accuracy misses the 85% barLikelihood: MedImpact: Med

Agents run, but outputs aren't reliable enough to graduate — the Phase 2 metric fails and beta clients get sub-par work.

Mitigation: Per-agent rubrics + side-by-side validation against reference outputs at each gate. Gate D blocks scaling until ≥85% fleet accuracy and ≥30% hour reduction are measured, not assumed.

R-05Cost / token overrunLikelihood: LowImpact: Low

Runaway runs or verbose prompts inflate spend beyond the ~$1.75/run economics.

Mitigation: $0.08/session-hour with no idle charges keeps the floor low. The Agent Registry sets per-agent spend caps and the Command Center surfaces cost-per-run weekly. Sprint 1 budget is a contained ~$50–100.

Source Document Cross-Reference

Every sprint traces to specific Layer 2 documents in the 1st Batch. Links resolve to the real files in this folder.

SprintPrimary source documentsTheme
S-1AReuse PRD — Agent Orchestration, PRD Local AutomationManaged Agent Arch
S-1BPRD Local Automation, SEO Lead HandoffSentinel Pipeline
S-2AReuse PRD (config pattern), QueryMind, SNMS CRMManaged Agent Arch
S-2BLocal SEO Automation Playbook (n8n)Workflow Automation
S-3AManage Agent SEO (swarm), AI Orchestration, Reuse PRD (HITL)Managed Agent Arch
S-3BAutomating Agency Workflows, SN Workstream PMWorkflow Automation
S-4AAI driven agency (Hybrid OS), 90-D Transfo (G4)Productization
S-4BAI driven agency (UAT), Managed Agent — Monthly ReportProductization

What Comes Next — Phase 3: AMPLIFY

With delivery automated and the Hybrid OS proven on betas, Phase 3 deploys Layer 1 (Strategic North Star): positioning, the outbound → content flywheel, and the hiring plan — then scales beta clients to paying.

Phase 3 Preview — 90-Day Transformation Sprint 3 (Days 61–90)
Layer 1 turns a working machine into a growing business: sharpen the “first AI-native detailing agency” positioning, build the outbound + case-study flywheel (every won deal feeds the content engine), and hire against the workforce plan — train Agent Managers, don't add operators.
Closes the remaining gaps: G7 Outbound + Brand, plus HR & workforce strategy. Hormozi Scaling Roadmap Stage 6 (Optimize) → Stage 7 (Categorize). Better beats more — optimize the fleet before expanding it.
P3

AMPLIFY

Layer 1 · Strategic North Star · 30 days · ~11h Jake
Phase 3 progress
0%  0 / 0
Governing Principle — Hormozi Scaling Roadmap, Stage 6 (Optimize) → Stage 7 (Categorize)
"Better beats more. The system runs — don't add operators to grow. Sharpen the story, turn won deals into the lead machine, and hire Agent Managers. The founder's hours fall while throughput climbs: 20h → 22h → 11h across the three phases."
Layer 1 (Strategic · WHY) is deployed last on purpose — positioning only compounds once there's a proven machine behind it. Maps to the 90-Day Transformation, Sprint 3 (Days 61–90): “Measure, Iterate, Scale.”
Week
Owner
00

Pre-Amplify Readiness

Phase 3 is the lightest phase for Jake (~11h) precisely because Phases 1–2 did the heavy lifting. Confirm these before you start telling the story.

Check 1 · Phase 2 closed

Swarm live, betas running

Phase 2 Gate D green: 6-agent swarm coordinated through PM Pulse, Hybrid OS packaged, 2 beta clients live. You can't sell “AI-native” until it's true.

Check 2 · Proof in hand

Real results to point at

Beta outcomes, time-savings data, and UAT scores from Phase 2 are collected. Positioning runs on proof — raw, recent, numbered — not adjectives.

Check 3 · Role shift

Jake moves to story + decisions

With delivery automated, the founder's job is positioning, the Go/No-Go call, and key relationships — not execution. ~11h across the month, by design.

Check 4 · Pipeline ready

ClickUp + Claude for HR

Ngọc has the recruitment (Track A) and OKR (Track B) pipelines scaffolded so hiring can run on the same centaur model as delivery.

Hormozi — proof is the best marketing

The 13 Proof Principles rank raw, recent, third-party-verified, numbered results above any claim. Phase 3 spends its energy turning the machine's real outputs into the story — not inventing a story and hoping the machine catches up.

W1

Positioning & Proof Days 61–68

Prove the fleet works with a Health Report, then rewrite the agency's story around it. Maps to the 90-Day plan's Weeks 9–10 (Agent Review + Positioning).

S-1A Agent Fleet Health Report v1 Days 61–64 Jake + pillar leads
Goal: Prove the swarm against the bar — compile accuracy, time savings, error types and override frequency for all 6 agents, calculate total delivery-hour reduction vs. baseline, and retrain prompts. Target: ≥85% accuracy, ≥30% hour reduction.
TaskOwnerHrsSource
Pillar leads collect per-agent data: accuracy rate, time saved, error types, override frequency (all 6 agents) Pillar leads 6h 90-D Transfo → Wk 9–10
Jake writes Health Report v1 — total delivery-hour reduction vs. baseline; verdict against ≥85% / ≥30% Jake 3h Managed Agent — Monthly Report
IT applies prompt refinements + Skills wiring updates; PM updates the Agent Registry Hung + PM 3h Reuse PRD
Hormozi — measure before you market

The Health Report is both the optimization input (retrain the weak agents) and the marketing input (the numbers become the proof in the positioning). One artifact, two jobs — that's the leverage of measuring honestly.

S-1B AI-Native Positioning — Website + Sales Days 64–68 Jake + Content
Goal: Rewrite the agency's story around the proven machine — “the first AI-native detailing agency” — across the website, sales deck, and proposals, anchored on the six moats and the half-price-full-stack positioning statement.
TaskOwnerHrsSource
Rewrite seonavigator.online About + services pages with AI-native messaging Jake 3h AI driven agency → positioning
Update the sales deck + proposals with the six-moat narrative and beta proof points PM 2h SEO Transfo Exec Plan
Content Lead drafts 3 social posts from the positioning brief (the “Rule of 100” engine starts here) Nhu 2h AI driven agency → moat
Hormozi — branding is association

A brand is a bouquet of associations. Pair SEO Navigator with “first AI-native,” “half the price, full ecosystem,” and real detailing results. The positioning statement does the work: Detailers Roadmap builds a pretty site and walks away — we run the whole engine for less.

A Gate A — Proven & Positioned 0%
  • Health Report v1 published — fleet hits ≥85% accuracy and ≥30% hour reduction (or weak agents retrained)
  • Website About + services pages rewritten with AI-native messaging
  • Sales deck + proposals updated with the six-moat narrative and beta proof
  • First 3 positioning social posts drafted
Pass → proceed to Week 2 — turn the story into a lead engine. Fail → if the fleet misses the bar, fix accuracy first; positioning on top of a shaky machine backfires.
W2

Outbound → Content Flywheel Days 69–75

Build the lead machine on Hormozi's Core Four and Dennis Yu's Task Library, then close the loop: every won deal becomes a case study, every case study becomes content, every piece of content generates the next lead.

S-2A Core Four Lead Engine Days 69–72 Sales + Content
Goal: All four lead channels live with a documented cadence — warm outreach (ACA), cold outreach (9-word email), posted content (70-20-10 hooks), and paid ads — run on the Rule of 100.
TaskOwnerHrsSource
Build the outbound list (50–100 detailing shops) + warm-outreach ACA scripts and the 9-word cold email Sales Mgr 4h TeamPlay → Dept 07 Sales
Stand up the posted-content cadence: 70-20-10 hook rotation, Rule of 100 (100 min/day on marketing) Nhu 3h Dennis Yu → Content Factory
Point a small paid-ads budget at the new positioning (Ad Arbitrage agent generates variants) Sang + Tung 3h AI driven agency → Pillars 3–4
Hormozi — the Core Four + Rule of 100

Every business reaches buyers through exactly four channels. You don't need a fifth — you need to actually run the four, 100 units a day. Warm outreach converts ~10× cold, so start there, then layer content and paid on top.

S-2B Won-Deal → Case Study → Content Loop Days 72–75 Content + PM
Goal: Operationalize Dennis Yu's flywheel — a Task Library entry that turns every won deal into a case study (Definitive Article), publishes it, and writes a Meta Article so results feed back into the content engine.
TaskOwnerHrsSource
Write the “won deal → case study” Definitive Article + QA checklist + Skill.md (the invocation methodology) Nhu 3h Dennis Yu → Definitive Articles
Publish the first 2 case studies from Phase 2 beta wins; Content Catalyst drafts, human approves (HITL) Nhu + Minh Chau 3h AI driven agency → flywheel
Wire the loop in ClickUp: deal marked “Won” auto-creates a case-study task in the content queue PM 2h Automating Agency Workflows
Hormozi — the closed loop is the moat

Every closed deal feeds the content engine; every publication feeds the schema graph; every update informs the ads. A traditional agency wires this with spreadsheets and loses the loop by month three. Dennis Yu's Meta Article step is what keeps it self-reinforcing.

B Gate B — Flywheel Turning 0%
  • All four lead channels live with a documented daily cadence (Rule of 100)
  • Outbound list built (50–100 shops) + warm/cold scripts in use
  • “Won deal → case study” Definitive Article written; loop automated in ClickUp
  • First 2 case studies from beta wins published (HITL-approved)
Pass → proceed to Week 3 — build the team that runs it. Fail → if outbound isn't converting, fix the offer/positioning before adding volume — more bad outreach just burns the list.
W3

Workforce & Agent-Manager Culture Days 76–82

Hire and manage for the AI-native model. Roll out HR Implementation 2026: role cards first, a hiring rubric that reserves 45% for AI-native dimensions, and OKRs that measure agent leverage — not output volume.

S-3A Role Cards + Hiring Rubric (Track A) Days 76–79 Ngọc + Jake
Goal: Every role is defined as an Agent-Manager role, and the recruitment pipeline can score candidates on the AI-native model. Role cards precede rubrics — build a rubric without a role card and you score for the wrong competencies.
TaskOwnerHrsSource
Finalize the 9 role cards (agents managed, human decisions, QA, escalation, accountability) — pilot done, 8 in parallel Ngọc 5h HR Implementation 2026 → Phase 0.5
Build the hiring rubric: 45% AI-native (AI fluency, Agent-Manager capability, Ownership Operator, QA) + 55% role skills Ngọc 3h HR Implementation 2026 → Track A
Jake validates role cards + rubric; confirm Claude drafts, Ngọc reviews every output before it reaches a candidate Jake 1.5h Who Wins in an AI Agent Economy
Hormozi — better beats more (train, don't just hire)

Stage 6 says optimize the team you have before adding bodies. The Agent-Manager role card makes “better” concrete: every hire is measured on how well they command agents, not how much they personally produce. Reserve 45% of the score for that.

S-3B OKRs, KPIs & Avatar Refinement (Track B) Days 79–82 Ngọc + Jake + PM
Goal: Performance runs on OKRs whose KPIs measure agent leverage (hours recovered, override rate, agents managed). In parallel, refine the customer avatar — the top 20% that drive 80% of revenue — and aim acquisition there.
TaskOwnerHrsSource
Stand up Track B OKR system in ClickUp; KPIs = hours recovered, override rate, agents managed (not output volume) Ngọc 3h HR Implementation 2026 → Track B
Run the Vista avatar pass: survey clients, sort by spend + retention, define the top-20% avatar to target Jake 2h AI driven agency → ICP
Brief the team on Ownership Operator culture; tie the avatar definition into outbound targeting (Week 2 engine) PM 1.5h Who Wins in an AI Agent Economy
Hormozi — 20% of customers = 80% of revenue

The Vista method: survey everyone, find the 3–5 traits of your top spenders, then speak only to that avatar. Replacing the bottom 80% with more of the top 20% is a path to 5× growth — without serving a single additional logo.

C Gate C — Workforce System Live 0%
  • 9 role cards signed; every role defined as an Agent-Manager role
  • Hiring rubric live — 45% reserved for AI-native dimensions
  • Track B OKRs measure agent leverage (hours recovered, override rate, agents managed)
  • Top-20% customer avatar defined and wired into outbound targeting
Pass → proceed to Week 4 — scale and close the 90 days. Fail → ship the pilot role card + rubric now; finish the remaining cards into the next 90-day cycle rather than blocking the close.
W4

Scale & Close the 90 Days Days 83–90

Make the Go/No-Go call on the Hybrid OS, convert betas to paying, then ship the positioning video and the final scorecard. Maps to the 90-Day plan's Weeks 11–12 (Beta Evaluation + Video + Close).

S-4A Hybrid OS Go/No-Go + Convert Betas Days 83–86 Jake + PM
Goal: Decide whether the Hybrid OS scales. Decision gate: both betas retained + outcomes equivalent to done-for-you + delivery cost ≥40% down = Go. If Go, convert betas to paying and outline the Tier 3 launch plan.
TaskOwnerHrsSource
PM collects beta feedback + prepares the Go/No-Go data (retention, outcome parity, delivery-cost reduction vs. DFY) PM 4h 90-D Transfo → Wk 11–12
Jake writes the Go/No-Go memo; if Go, convert both betas to paying and outline the Tier 3 launch plan Jake 2.5h AI driven agency → Hybrid OS
If Go: PM builds the Tier 3 onboarding sequence from Jake's outline PM 3h 90-D Transfo → Tier 3
Hormozi — the virtuous pricing cycle

If delivery costs drop ≥40% while outcomes hold, the Hybrid OS enters the virtuous cycle: premium price → quality customers → higher margin → reinvest in quality. That's the structural “triple margin” the centaur model promises — now proven on real betas, not a spreadsheet.

S-4B Positioning Video + Final Scorecard Days 86–90 Jake + Content
Goal: Ship the story and close the loop. Record a 3-minute positioning video (problem → solution → proof, one take), score every metric on the final 90-day scorecard, capture lessons, and write the next 90-day plan.
TaskOwnerHrsSource
Record the 3-min positioning video: problem → solution → proof. One take, ship it Jake 2.5h 90-D Transfo → Wk 11–12
Content Lead polishes + publishes the video and the 3 social posts; cross-check against Authority Hacker assets Nhu 4h Authority Hacker → 7 Pillars
Complete the final 90-day scorecard — score every metric, capture lessons, write the next 90-day plan Jake 2h Master Index → full review
Hormozi — ship it, then iterate

One take, ship it. The scorecard isn't the finish line — it's the lookback that seeds the next 90-day cycle. Stage 7 (Categorize) begins where this ends: triage what's working, organize the swarm and the team, and run it again.

D Gate D — 90-Day Transformation Complete 0%
  • Hybrid OS Go/No-Go memo written; if Go, both betas converted to paying
  • Delivery cost ≥40% down vs. done-for-you with equivalent outcomes
  • 3-minute positioning video recorded and published
  • Final 90-day scorecard complete — all 7 gaps (G1–G7) closed or at a documented Go/No-Go
  • Next 90-day plan drafted
Pass → the AI-native transformation is live and the centaur agency is running. Begin the next 90-day cycle at Stage 7 (Categorize): scale the avatar, expand the fleet, specialize roles. Fail → hold at the failing metric — a No-Go on Hybrid OS is a valid, data-backed outcome, not a failure.

The Six Moats — What Phase 3 Sells

Positioning isn't adjectives; it's the defensible reasons a competitor can't catch you in 12 months. These six moats — straight from the strategic vision — are the spine of every sales page, proposal, and social post built this phase.

🧠
Methodology
QueryMind + CQS

Koray Semantic Content Network + a proprietary 6-dimension scoring framework + AI Overview consensus. Built over 2+ years, tuned to detailing.

2+ yrs to copyMoat 1
Infrastructure
6-Agent Swarm

Coordinator + 5 specialists on Anthropic infra, 30+ Claude Skills, 6 MCP servers. Requires research-preview access + orchestration depth.

Phase 2 builtMoat 2
🚗
Vertical Depth
Detailing-only

200+ detailing keywords pre-loaded, 450+ GHL templates, 6 hook archetypes validated on detailing ads. Generic agencies start from zero.

200+ keywordsMoat 3
💰
Cost
Half price, 3× margin

Distributed team + AI execution = half of Detailers Roadmap's price at triple the margin. Incumbents can't match without rebuilding delivery.

~50% their priceMoat 4
UAT
239 auto checks

12-agent UAT covers 334 checks across every pillar in ~40 min at ~$9.65. A traditional agency burns ~20 human hours on the same scope.

239/334 automatedMoat 5
👥
Culture
Agent Managers

The whole team is trained to manage AI agents. Copying the skills doesn't give you the team that can run them at scale — that's Week 3's work.

11 people retrainedMoat 6
$7–12B US detailing TAM, fragmented across thousands of indie shops — and no competitor has gone AI-native. The moats are why that gap stays open long enough to capture it.

The Lead Flywheel

Hormozi's Core Four feed the pipeline; Dennis Yu's Task Library closes the loop. The output of delivery becomes the input to acquisition — a self-reinforcing engine, not a funnel that empties.

Win
Won deal

Beta or new client closes

Definitive
Case study

Catalyst drafts, human approves

Core Four
Distribute

Warm · cold · content · paid

Meta
Measure & feed back

Meta Article → new leads

Why it compounds: Dennis Yu's invocation pattern — “according to [methodology], do [task], QA, write a Meta Article, publish” — means every completed deal documents its own results and those results become the next case study and the next ad. Warm outreach converts ~10× cold, so the loop is seeded warm, then amplified by content and paid. The 13 Proof Principles rank these real, numbered case studies above any claim.

Scale Projection Calculator

Where the flywheel takes revenue. Defaults assume the Hybrid OS retainer (~$1,750/mo) and the centaur capacity claim — the same small team can serve 50–100 clients. Drag to see MRR, annual run-rate, and whether 12-month growth stays within capacity.

Inputs

8
$1,750
70%
2

Outputs

MRR (now)$14,000
Gross profit / mo$9,800
Annual run-rate (ARR)$168,000
Clients in 12 months32
Within centaur capacity — the swarm can serve this book without adding operators.
Hormozi — grow the avatar, not the headcount

Margins triple because AI runs ~70% of execution — so growth flows to profit, not payroll. The capacity check matters: when 12-month clients approach ~100, that's Stage 7 (Categorize / Specialize) territory, where you replace generalists with specialists rather than burning out the team.

RACI Ownership Matrix

Phase 3 is the founder's phase — positioning, the Go/No-Go call, and the avatar are his to own. But even here he's Responsible for only the irreducible judgment calls; Sales, Content, and HR carry the execution.

WorkstreamJakeSales MgrContent (Nhu)Ngọc (HR)PMAds
Fleet Health ReportRIIICC
Positioning & brandACRIRI
Core Four lead engineARRICR
Content flywheel loopIIRIAI
Hiring & OKRsAIIRCI
Hybrid OS Go/No-GoRIIIRI
R Responsible — does the work A Accountable — owns the outcome C Consulted — input before I Informed — told after

Risk Register

Phase 3's risks are growth risks — the story, the pipeline, the team, and scale. Each has a mitigation already built into the plan.

R-01Founder is the single point of salesLikelihood: HighImpact: High

Positioning, the Go/No-Go, and key relationships all sit with Jake. If sales never leaves his calendar, growth caps the moment he's busy — the exact bottleneck Phases 1–2 removed from delivery.

Mitigation: The Core Four engine + Sales Manager (Dept 07) + the automated content flywheel move top-of-funnel off Jake. He keeps only the high-judgment close and the Go/No-Go memo.

R-02Positioning doesn't differentiateLikelihood: MedImpact: High

“AI-native” is becoming a crowded claim. If the story is adjectives without proof, it blends in and the price premium evaporates.

Mitigation: Positioning is anchored on the six concrete moats + real beta results (13 Proof Principles: raw, recent, numbered). Gate A blocks positioning until the Health Report proves the machine.

R-03Scaling breaks delivery qualityLikelihood: MedImpact: High

Winning faster than the swarm + team can absorb degrades outcomes — and a public AI-native promise makes quality slips very visible.

Mitigation: The Scale calculator's capacity check flags the ~100-client ceiling; HITL gates hold quality; Stage 7 (specialize) is the planned response to capacity, not heroics.

R-04Wrong hire profileLikelihood: LowImpact: Med

Hiring strong individual operators who can't manage agents rebuilds the old, non-leveraged agency one seat at a time.

Mitigation: Role cards precede rubrics; 45% of every hiring score is reserved for AI-native dimensions; KPIs measure agent leverage, not personal output.

R-05AI Overview compresses top-of-funnelLikelihood: MedImpact: Low

Google's AI Overviews shrink organic click-through — a structural headwind for the SEO pillar's lead gen.

Mitigation: The Consensus Audit skill targets AIO eligibility, and positioning spans SEO + Ads + CRM, so downstream revenue doesn't depend on organic clicks alone.

Source Document Cross-Reference

Every sprint traces to specific Layer 1 documents in the 1st Batch. Links resolve to the real files in this folder.

SprintPrimary source documentsTheme
S-1A90-D Transfo (Wk 9–10), Managed Agent — Monthly ReportAI-Native Transformation
S-1BAI driven agency (moat + positioning), SEO Transfo Exec PlanAI-Native Transformation
S-2ADennis Yu — AI Agents Marketing, TeamPlay (Dept 07)External Methodology
S-2BDennis Yu (Definitive/Meta), Automating Agency WorkflowsExternal Methodology
S-3AHR Implementation 2026, Who Wins in an AI Agent EconomyHR & Workforce
S-3BHR Implementation 2026 (Track B), AI driven agency (ICP)HR & Workforce
S-4A90-D Transfo (Wk 11–12), AI driven agency (Hybrid OS)AI-Native Transformation
S-4B90-D Transfo (scorecard), Authority Hacker → 7 PillarsExternal Methodology

The Full Journey — 90 Days, Three Phases

Phase 3 closes the loop. The three playbooks deploy the 1st Batch architecture bottom-up by revenue impact: serve clients, automate delivery, then amplify. Founder hours fall at every step.

Phase 1
MONETIZE

Layers 3+4 · ~20h Jake · CRM + onboarding + reporting

Phase 2
SYSTEMATIZE

Layer 2 · ~22h Jake · 6-agent swarm + Hybrid OS

Phase 3
AMPLIFY

Layer 1 · ~11h Jake · positioning + flywheel + team

Next 90
Stage 7

Categorize · scale the avatar, specialize roles

~57 founder hours + ~117 team hours across 12 weeks deploys the full centaur operating model: structured knowledge, an Agent-Manager team, a 6-agent fleet, and a productized Hybrid OS — serving 50–100 clients on the staffing of ten. The next 90-day cycle starts at Hormozi Stage 7 (Categorize): triage, organize, and specialize.
The North Star
SEO Navigator — the first AI-native marketing agency built for car detailing in the USA. Half the price of the competition, the full marketing ecosystem, run by a small team commanding a swarm of specialist AI agents.
7 pillars · 6 agents · 30+ skills · ~165h/week recovered · $7–12B TAM. Human judgment holds the reins; AI does the running.
P4

SCALE

Next 90 · Days 91–180 · Stage 7 Categorize · ~15h Jake
Phase 4 progress
0%  0 / 0
Governing Principle — Hormozi Scaling Roadmap, Stage 7 (Categorize) → Stage 8 (Specialize)
"The machine works and the story lands. Now triage and organize: concentrate on the avatar that pays, specialize the roles, license the system you built, and carry it into new markets. Growth flows to margin, not headcount."
The next 90-day cycle the transformation hands off to. Three movements — Scale the Book, Productize & License, Expand Markets — sequenced so each funds the next.
Read this as a roadmap, not a spec

Phases 1–3 deploy the documented 4-layer architecture and the 90-day plan. Phase 4 goes beyond the source docs into the post-transformation scale cycle. It's grounded where the docs point forward — the 50–100 client capacity claim, the “next 90-day plan” handoff, the Tier 3 launch, GHL SaaS mode, and Hormozi Stages 7–9 — but the specific targets and dates are projection. Treat the numbers as planning assumptions to pressure-test, not commitments.

Movement
Owner
M1

Scale the Book Days 91–120

Categorize the client base, double down on the avatar that pays, and specialize roles so the team can serve 50–100 clients on the staffing of ten without quality slipping.

S-1ATriage & Avatar ConcentrationDays 91–105Jake + PM
Goal: Sort every client by spend and retention, define the top-20% avatar precisely, and reweight acquisition + service toward it — the Vista method, applied at scale.
TaskOwnerHrsSource
Rank all clients by spend × retention; tag the top 20% and the bottom 20% (graduate, fix, or fire)PM3hVista avatar (Phase 3 carry-over)
Write the sharpened ICP one-pager (3–5 traits of the top spenders) and feed it to the Core Four engineJake2hAI driven agency → ICP / moat
Re-aim outbound + retargeting at the avatar; sunset or reprice the worst-fit accountsSales Mgr3hPhase 3 → Core Four
Hormozi — 20% of customers = 80% of revenue

Replacing the bottom 80% with more of the top 20% is a path to 5× growth without serving a single extra logo. Concentration, not addition, is the Stage 7 move.

S-1BSpecialize Roles & CapacityDays 105–120Ngọc + Jake
Goal: Move from generalists to specialists (Stage 7→8) and confirm the agent fleet + team can absorb 50–100 clients. Better beats more — train and specialize before hiring.
TaskOwnerHrsSource
Finalize the remaining role cards; redefine generalist seats as specialist Agent-Manager rolesNgọc4hHR Implementation 2026
Capacity test: run the fleet against a simulated 50-client load; flag bottleneck agents to scaleHung3hReuse PRD / Agent Registry
Approve any specialist hire only against the 45%-AI-native rubric; document the capacity ceilingJake1.5hHR Implementation 2026 → rubric
Hormozi — Stage 8 Specialize

At scale, generalists become the bottleneck. Replacing them with specialists — humans and agents alike — is how throughput keeps rising without quality falling.

AGate A — Book Concentrated & Capacity Proven0%
  • Clients ranked; top-20% avatar defined and wired into acquisition
  • Bottom-fit accounts graduated, repriced, or sunset
  • Specialist role cards finalized; seats redefined as Agent-Manager roles
  • Fleet capacity-tested to ~50 clients with bottlenecks identified
Pass → the book is healthy and the team can scale — proceed to Productize. Fail → fix capacity or concentration before adding any volume.
M2

Productize & License Days 121–150

Turn the SNMS + agent stack into a product other shops and agencies can buy — a second revenue line on top of the agency, sold via GHL SaaS mode / snapshot licensing.

S-2APackage the Licensable ProductDays 121–135Jake + Trung
Goal: Ship a clean, self-serve version of the system — the SNMS snapshot + skill stack + onboarding — that a non-client can deploy. The Tier 3 launch from the Phase 3 Go decision.
TaskOwnerHrsSource
Productize the SNMS snapshot for GHL SaaS mode; strip client-specific config, add setup wizardTrung Le6hSNMS Ultimate CRM · GHL SaaS mode
Bundle the customer-facing Launchpad tutorials + Definitive Articles as the self-serve knowledge baseTrung + Content4hCustomer Launchpad · Dennis Yu
Decide what's licensed vs. held back as the agency moat (keep QueryMind depth + done-for-you premium)Jake2hAI driven agency → moat
Hormozi — sell the system, not just the service

The agency proves the system; the license sells it. GHL SaaS mode lowered the bar for anyone to launch — so the defensible move is to license the proven methodology + agent stack, while keeping the deepest moat (QueryMind, done-for-you) in-house.

S-2BPricing & Go-To-MarketDays 135–150Jake + Sales
Goal: Price the license, build the offer stack, and land the first paying license customers without cannibalizing the done-for-you agency.
TaskOwnerHrsSource
Set license pricing tiers + offer stack (anchor against done-for-you; protect the premium)Jake2hHormozi offer stack
Sell the first 5–10 license seats to non-competing shops/markets; onboard via the wizardSales Mgr5hCore Four (Phase 3)
Stand up license support + churn tracking in the Command Center; define the success metricPM3hAutomating Agency Workflows
Hormozi — continuity is the compounding asset

A license is recurring revenue at near-software margin. Even a handful of seats meaningfully lifts blended ARR — and the valuation multiple on recurring license revenue is higher than on services.

BGate B — Product Live & Earning0%
  • Self-serve SNMS snapshot + knowledge base shipped (GHL SaaS mode)
  • License vs. moat boundary decided and documented
  • Pricing tiers + offer stack live; no cannibalization of done-for-you
  • First paying license seats onboarded; support + churn tracking running
Pass → a second, higher-margin revenue line is live — proceed to Expand. Fail → if licenses cannibalize the agency, narrow what's licensed before scaling sales.
M3

Expand Markets Days 151–180

Take the proven engine into bigger TAM — adjacent verticals, new geographies, and multi-location / franchise accounts — then set up the next cycle (Stage 9, Capitalize).

S-3AAdjacent Verticals & FranchiseDays 151–165Jake + Content
Goal: Prove the centaur model transfers beyond detailing. Pick one adjacent vertical and one multi-location/franchise account, and clone the pillar stack with vertical-tuned skills.
TaskOwnerHrsSource
Select one adjacent vertical (e.g. PPF-heavy auto, wraps, or a parallel local-service niche) with similar AOV/intentJake2hAI driven agency → TAM
Clone QueryMind + skills for the new vertical; build the first topical map + city-page setNhu5hQueryMind · Pattern C
Land one multi-location/franchise account; template the rollout across its locationsSales Mgr4hPattern C (franchise)
Hormozi — expand only what's proven

The engine is vertical-tuned, so expansion is cloning, not invention. One adjacent vertical and one franchise account de-risk the move before committing budget to a full market push.

S-3BNew Geographies + Next-Cycle SetupDays 165–180Jake + PM
Goal: Open one new geography on the proven playbook, then close the cycle with a scorecard and the next 90-day plan (Stage 9 Capitalize prep: the big bet — M&A or R&D).
TaskOwnerHrsSource
Launch the outbound + content engine in one new metro/region; track CAC + close rate vs. home marketSales Mgr4hCore Four · Radius optimizer
Compile the Next-90 scorecard: clients, blended MRR, license MRR, margin, capacity headroomPM3hCommand Center · Registry
Write the next 90-day plan + the Stage 9 “big bet” thesis (acquire a competitor, or invest in R&D)Jake2hHormozi Stage 9 Capitalize
Hormozi — Stage 9, the big bet

Once the engine scales across verticals and geos, the next leverage is a single concentrated bet: acquire a competitor (Detailers Movement runs 55+ staff — you do it with ten) or invest in proprietary R&D. That thesis is the output of this cycle, the input to the next.

CGate C — Engine Travels0%
  • One adjacent vertical live with cloned QueryMind + skills
  • One multi-location / franchise account rolled out across locations
  • One new geography launched; CAC + close rate benchmarked vs. home market
  • Next-90 scorecard compiled
Pass → the model is proven portable — proceed to the final review. Fail → if a new market underperforms, hold expansion and re-tune the vertical skills before spending more.
DGate D — Stage 7 Complete: Scaled0%
  • Book concentrated on the avatar; team specialized; capacity headroom to ~100 clients
  • Licensable product live and earning recurring revenue
  • Engine proven in an adjacent vertical, a franchise account, and a new geography
  • Next 90-day plan + Stage 9 “big bet” thesis written
Pass → SEO Navigator is a scaled, multi-revenue, AI-native category leader — begin the next cycle at Stage 8 (Specialize) → Stage 9 (Capitalize). Fail → a partial pass is fine: bank the movements that cleared and roll the rest into the next 90.

Where Phase 4 Sits on the Ladder

The 90-day transformation took the agency to Stage 6. Phase 4 is the climb from Stage 7 to Stage 9 — categorize, specialize, capitalize.

7
Categorize
$3M–10M/mo band

Triage and organize: concentrate on the avatar, specialize roles, license the system. This is the spine of Phase 4.

This phaseM1–M2
8
Specialize
$10M–50M/mo band

Replace generalists with specialists — human and agent. Begins inside M1 and carries into the next cycle.

Starts hereM1 / next
9
Capitalize
The big bet

Acquire a competitor or invest in R&D. The thesis is written in M3; the bet is placed in the next cycle.

Thesis in M3Next cycle
50–100clients on the staffing of ten — the centaur capacity claim from the strategic vision is exactly what Phase 4 cashes in. Detailers Movement runs the same scope on 55+ staff.

Blended Revenue & Valuation Calculator

Where two revenue lines take the business. Agency retainers + license seats → blended MRR, ARR, and a rough enterprise value at a 3× revenue multiple. Toggle agency-only vs. agency + license to see what the second line is worth.

Inputs

40
$1,750
20
$297

Outputs

Blended MRR$75,940
Annual run-rate (ARR)$911,280
Total customers60
Est. enterprise value (3×)$2.7M
Diversified — the license line adds recurring, higher-multiple revenue on top of the agency.
Hormozi — revenue mix drives the multiple

Service revenue trades at a low multiple; recurring product/license revenue trades higher. Adding a license line doesn't just add MRR — it re-rates the whole business. The 3× here is a planning placeholder; real multiples depend on growth, retention, and mix.

RACI Ownership Matrix

Phase 4 splits cleanly: Jake owns the strategic calls, Sales owns expansion + license GTM, IT owns the product build, HR owns specialization.

WorkstreamJakeSales MgrTrung (IT)Ngọc (HR)PMContent
Avatar concentrationARIIRI
Specialize rolesAICRCI
Productize / license buildAIRICR
License pricing + GTMRRIICI
Vertical / geo expansionARIICR
Next-cycle / big betRIIIRI
R ResponsibleA AccountableC ConsultedI Informed

Risk Register

Scale risks are different from build risks — dilution, cannibalization, and quality-at-volume. Each has a mitigation built into the movements above.

R-01Scaling breaks delivery qualityLikelihood: MedImpact: High

Winning faster than the fleet + team can absorb degrades outcomes — and a public AI-native promise makes slips very visible.

Mitigation: Gate A capacity-tests to ~50 clients before expansion; HITL gates hold quality; specialization (Stage 8) is the planned response, not heroics.

R-02License cannibalizes the agencyLikelihood: MedImpact: High

A cheap self-serve license could pull revenue from the high-margin done-for-you agency instead of adding to it.

Mitigation: The deepest moat (QueryMind depth, done-for-you) is held back from the license; pricing anchors the license below DFY; sell licenses to non-competing markets first.

R-03Founder is still the single point of salesLikelihood: HighImpact: Med

If positioning, pricing, and key closes stay on Jake's calendar, scale caps the moment he's busy.

Mitigation: Sales Manager owns outbound + license GTM; the content flywheel feeds top-of-funnel; Jake keeps only the high-judgment close and the big-bet thesis.

R-04New market underperformsLikelihood: MedImpact: Med

An adjacent vertical or new geography may not convert like the proven detailing home market.

Mitigation: Expand by cloning, one vertical + one geo at a time; Gate C benchmarks CAC + close rate vs. home market before further spend.

R-05Premature “big bet”Likelihood: LowImpact: High

Jumping to acquisition / heavy R&D (Stage 9) before the engine is proven at scale risks the whole business.

Mitigation: Phase 4 only writes the thesis; the bet is placed in the next cycle, gated on Stage 7–8 actually clearing first.

Source Cross-Reference & Grounding

Phase 4 is forward projection, but each movement leans on something real in the 1st Batch. Where a row says “projection,” that's a planning assumption, not a documented plan.

MovementGrounded inBasis
M1 ScaleAI driven agency, HR Implementation 2026Grounded 50–100 capacity, Vista avatar, specialize roles
M2 ProductizeSNMS Ultimate CRM, Customer LaunchpadPartly projected GHL SaaS mode is referenced as a risk; licensing is the inverse play
M3 ExpandAI driven agency (TAM), 90-D Transfo (next-90)Partly projected $7–12B TAM + “next 90-day plan” handoff; specific markets are projection
Stages 7–9Hormozi Scaling Roadmap (7–9, adapted)Framework Categorize → Specialize → Capitalize