Skip to module content
๐Ÿง AI Academy
0/91
Sign in
Module 20 ยท ~7 min

Mapping Capabilities to Sprint Offers

The sellable catalog: seven sprints + the umbrella retainer.

Reading progress
0/8 ยท 0%

The big idea

๐Ÿ’กKey idea
The sprint catalog is seven fixed-scope, fixed-price engagements, each 2โ€“4 weeks, each ending with a working system, a skills package, a runbook, and a review-loop cadence. Sprint 0 (AI OS Audit) is the wedge โ€” cheap, fast, diagnostic, and it writes the SOW for everything below it. Sprint 1 (Revenue Data Foundation) delivers the fastest visible ROI. Sprints 2โ€“6 cover Outbound, Paid Media, Content, GEO, and Research & Intelligence. After the sprints comes the OS Operations umbrella retainer โ€” review loops, eval maintenance, model/stack upgrades, quarterly MCP audits, skill library evolution. Sprints are the acquisition vehicle. The retainer is where the margin lives.
Quick check
1 question ยท instant feedback
0/1
  1. Sprint 0 (AI OS Audit) is:

Numbers that matter

7
Sprint offers (0โ€“6) + one umbrella retainer.
โ‚ฌ15โ€“30k
Sprint price band โ€” anchored under one quarter of the GTM engineer hire it replaces.
Quick check
1 question ยท instant feedback
0/1
  1. The margin in this business model lives in:

Deep dive

3/3 open

Sprint 0 is the AI OS Audit. It's your cheapest, fastest engagement โ€” and the one that earns the right to sell everything else.

What it covers: a workflow inventory, an AI-nativeness score (using the ladder from Module 1), a context-debt assessment (Module 16), an MCP-readiness check of the existing stack, a permission-risk review of anything already automated, and a prioritized roadmap with effort/impact ratings.

Deliverables: an audit document, workflow maps, and a 90-day plan.

Why it wins: it's diagnostic, not prescriptive. It gathers real data about the client's situation before any build begins. And it writes the SOW for every sprint below it. Skipping it is the workshop-brainstorm failure mode โ€” you build what you guessed the client needed.

**Sprint 1 โ€” Revenue Data Foundation.** CRM resurrection via waterfall re-enrichment (20โ†’80% coverage), scoring rubric, seven-server MCP core install, Slack reporting agent. Run this first for most clients โ€” it delivers visible ROI fast and funds the rest of the roadmap.

**Sprint 2 โ€” Outbound Engine.** One signal-driven play built end-to-end, with a 50-prospect pilot over two weeks included in scope.

**Sprint 3 โ€” Paid Media Copilot.** Read/write/retract stack per platform, autonomy rungs 2โ€“3, permission matrix in the SOW. The Google Ads suite, already parameterized, is 70% pre-built.

**Sprint 4 โ€” Content OS.** Voice cards, pipeline skill-chain, atomizer, Canva MCP, hook library. Natural upsell: the Digital Twin retainer.

**Sprint 5 โ€” GEO.** Access + extractability + entity/earned-media + citation dashboard. Natural follow-on: quarterly refresh retainer.

**Sprint 6 โ€” Research & Intelligence Desk.** Deep-research agent, pre-meeting brief skill, competitor delta monitor.

Every sprint should funnel toward the OS Operations retainer. This is the post-sprint engagement that covers: weekly review loops and eval maintenance, model and stack upgrades as the ecosystem shifts, a quarterly MCP audit, skill library evolution, and new-play development as the client's needs grow.

This is where the margin lives. Sprints are how you acquire the relationship. The retainer is how you make the relationship compound.

Selling a sprint without a clear path to the retainer is leaving money on the table โ€” and leaving the client without the ongoing improvement mechanism that makes the sprint worthwhile.

Quick check
1 question ยท instant feedback
0/1
  1. Sprint 1 is Revenue Data Foundation because:

How to run it

  1. Start with Sprint 0
    It writes the SOW for everything below.
  2. Fixed scope + fixed price + 2โ€“4 weeks
    Every sprint, no exceptions.
  3. Runbook + review-loop cadence per sprint
    The retention mechanism, from day one.
  4. Every sprint funnels to OS Operations retainer
    That's where the margin lives.
Quick check
1 question ยท instant feedback
0/1
  1. Sprint 3 (Paid Media Copilot) is 70% pre-built because:

In the field

๐Ÿ”ฌWorked example
Sprint 1 Revenue Data Foundation: CRM resurrection (waterfall re-enrichment 20โ†’80% coverage), scoring rubric, seven-server MCP core install, Slack reporting agent. Fastest visible ROI; run first for most clients.
๐ŸšซWhen not to reach for it
Don't lead with Sprint 3 (Paid Media Copilot) unless Sprint 0 already surfaced it as the top opportunity. Sprint 0 writes the SOW for everything below and prevents mis-scoping.
Quick check
1 question ยท instant feedback
0/1
  1. Every sprint should ship with:

Pitfalls & takeaways

Failure modes

  • Skipping Sprint 0 for a big client 'because they know what they want' โ€” exactly the workshop-brainstorm failure the strategy volume names.
  • Selling sprints without the retainer follow-on โ€” leaving the margin on the table.
  • Selling any single sprint without the review-loop cadence โ€” the retention mechanism is missing.

Durable takeaways

  • Sprint 0 is the wedge; it writes the SOW for everything below.
  • Sprints are acquisition; the retainer is margin.
  • Fixed scope + fixed price + review-loop cadence, every time.
  • Parameterizing the Google suite pre-builds 70% of Sprint 3.

Do the work

๐Ÿ‹๏ธProve you learned it

Write the Sprint 0 (AI OS Audit) scope doc: contents, deliverables, price band, timeline, sample deliverables. Then draft the OS Operations retainer scope: monthly deliverables, cadence, price band, kill-switch conditions.

0 chars
๐Ÿ“ฆArtifact to produce
Sprint catalog with fixed scope + fixed price + runbook template + review-loop cadence per sprint.

Sources

  • ยท GMS Field Manual ยง20 (Mapping Capabilities to Sprint Offers)