After the Sprint: the model, cadence, and decisions kept current.
The Engagement is the monthly continuation for owners who completed a Control Sprint and want the model maintained, the cadence run, and the decision layer kept alive instead of rebuilt every quarter. Same operator. Same method. Same calculation engine. Kept current.
The Sprint stands alone. The Engagement is for owners who want it to stay alive.
Some Sprint clients take the model, run it themselves, and never return. That is the Sprint working as designed. The model is theirs, the calculation engine is visible, and the decision pack is enough to operate against for the next twelve months. Nothing about the firm depends on those clients converting into a retainer.
Other Sprint clients want the model maintained on a monthly cadence, the cash forecast refreshed weekly, and an operator on call when a hire, contract, or capex decision lands. That is the Engagement.
Both outcomes are normal and counted as success. The Engagement is never a precondition for the Sprint. The Sprint is never a sales funnel for the Engagement. The continuation decision happens after the Sprint, with the working model already in your hands, which is the only way the choice is honest.
Control Sprint
Ten business days. Fixed fee. Model and decision pack handed over.
Continuation decision
After delivery. Some clients stop here. Some continue. Both healthy.
Ongoing Engagement
Monthly cycle. Weekly cash refresh. Decision support between cycles.
Exit
30 days’ notice from either side. Model stays with you. Portal access ends.
What the Engagement keeps current.
The Sprint built it. The Engagement keeps it running on a fixed cadence. Each capability has a named cadence and a named output.
Sprint and Engagement, axis by axis.
The Engagement is not a different product. It is the Sprint method, kept running. Each axis below shows what carries forward, what extends, and what gets added once the cadence starts.
How the month runs.
One monthly cycle. One weekly cycle. Between-cycle decision support when it is needed. The score below maps the rhythm across one month.
The cadence shown is the $5M–$20M standard scope. The under-$5M tier runs the cash forecast monthly, with the same monthly review.
Monthly cycle
- /Data cut-off after the client closes the previous month in their accounting system.
- /Model refreshed against actuals. Variance and margin review.
- /Reviewed commentary written. Portal refreshed and published.
- /Monthly review call, or written brief, depending on how the client prefers to operate.
Decision support
- /Hires, pricing, capex, cash events, customer concentration, contract exposure, pre-commitment readiness.
- /Async by default. Scheduled when the decision warrants it.
- /Unwritten rule: if a number drives a decision in the next two weeks, the Engagement covers asking and answering it.
Monthly retainer. Fixed by revenue band.
Three tiers, set by your annual revenue. The band your business falls into is the fee, and it is fixed in writing before the first invoice. Multi-entity work stays quoted on scope. No annual lock-in.
- /Single entity
- /Monthly management pack
- /13-week cash flow updated monthly
- /Monthly review call
- /Decision support between cycles
- /Single entity
- /Weekly cash refresh
- /Monthly model refresh and review
- /Decision support between cycles
- /Heavier tempo
- /Deeper margin detail
- /Multi-driver models
What the Engagement is not.
The work is defined as much by what it excludes. Each row is a category the Engagement does not cover, and where it belongs instead.
The Engagement supports owner-level decisions. It does not run daily finance operations and is not designed to.
Start with the Sprint.
The Engagement begins after a Control Sprint. If you want to discuss the retainer directly without a diagnostic first, that conversation runs on a separate call. Less common path, still real.