How we run a Revenue System Sprint

A Revenue System Sprint is six weeks of focused work on one named revenue gap. The deliverable is a working system, not a planning memo. Here is the week-by-week shape.

Week 0 (pre-kickoff): the contract

Before kickoff, three things are in writing. The named gap (the specific revenue gap we are closing). The metric (the one number we are moving). The dollar value (what closing the gap is worth annually). If any of those is fuzzy, we delay kickoff until they are sharp.

Week 1: the map

Day one is the 60-minute whiteboard exercise. Hand-drawn, no software, no Miro template. We map the buyer path from first signal to closed revenue. By the end of the hour, the worst handoff is visible to everyone in the room. The map becomes the architecture for the Sprint.

Weeks 2-3: the build

This is where the named owner on the client side earns the title. We pair every workday on the actual fix. If the gap is qualification, we rewrite the qualification rubric and load it into the CRM. If the gap is sequencing, we build the touch-2 and touch-3 cadence in the email platform. If the gap is handoff, we build the SDR handoff tree with the rules in version control.

Week 4: the dogfood

We run the new system on real leads for a full week. No theory, no synthetic test data. The named owner runs the workflow end to end. The CS team watches and tunes. Every break is a Linear ticket, every fix ships same-day.

Week 5: the dashboard

The buyer needs to see the number move without us in the room. We ship a dashboard that the client opens on day one and every day after. It shows the named metric, the dollar value moved, and the audit trail of which fixes landed which results.

Week 6: the handoff

We document. The named owner takes possession. We do a one-hour exit review where the client demonstrates running the system without us. The Sprint ends on Friday of week 6, on the named ship date, no extensions.

What we do not extend the Sprint for

• Internal stakeholder reviews that the named owner did not schedule.
• "While we're at it" requests outside the named gap.
• Tool migrations the client decided to do mid-sprint.
• Hiring decisions the client postponed.

What ends a Sprint early

If the named metric is already moving by week 3, we stop building and run a measurement week. Faster is better than fuller. The contract is for the result, not the calendar.

If the dogfood in week 4 shows the system is not moving the metric, we run a one-week recovery. If recovery does not converge, we refund the unearned portion and publish what we learned. That has happened twice. It is in the open.