In five days, work out what to fix or build first and how to execute it over the next 90.
What it is
5 Days to Scale is the Design sprint for Closing Foundry.
It is for founder-led teams and revenue leaders who need a clearer view of the sales system underneath growth. In five days, Closing Foundry inspects what is working, what is getting in the way and what needs to change first across ICP, value story, qualification, sales stages, buyer evidence, CRM truth and the weekly rhythm.
The output is a clear GTM blueprint and a practical 90-day plan.
It is not a workshop deck. It is a decision sprint that tells the team what to fix or build first.
Use it when
Use 5 Days to Scale when growth has slowed, pipeline is not converting, deals keep moving or the forecast needs too much explaining.
Use it when the founder is still too involved in live deals and the team needs a better system underneath selling.
Use it when the next stage will stretch the current motion: hiring sellers, opening a new market, moving upmarket or adding a sales-led motion.
Best fit
Best for B2B software and tech-enabled services teams with an active pipeline, a founder or revenue leader close to the number, and enough live deal evidence to inspect.
The system it inspects
5 Days to Scale looks across the parts of the sales system that decide whether growth is repeatable: Demand, Sales Process, Closing and Expansion.
Demand: whether the right pipeline is being created early enough, with clear use cases, outcome metrics and a point of view that connects the size of the problem to intent.
Sales Process: whether deals are moving because buyers are committing, not just because stages are being updated. This includes stage gates, inspection rhythm, qualification and what has been codified.
Closing: whether late-stage deals can survive Finance, procurement, consensus and status quo pressure. This includes business case, proposal quality and decision commitment.
Expansion: whether customers are seeing enough value to renew, grow and become proof for the next deal.
Underneath those areas, the sprint checks Product, People, Process and Repeatability.
The five days
- Day 1 — Baseline. Agree the outcomes, inspect the current reality and review interviews, pipeline and recent wins or losses.
- Day 2 — Discovery. Review problem, people, process and repeatability. Test ICP, strongest use cases, current proof and where the sales motion is under strain.
- Day 3 — Diagnosis. Identify the root cause and prioritise the few fixes that will reduce avoidable loss fastest.
- Day 4 — Alignment. Agree what needs to change across problem, people, sales motion, value proposition, messaging and hiring needs.
- Day 5 — Blueprint and plan. Produce the GTM blueprint, 90-day prioritised plan and do-it-now pack.
What you leave with
You leave with a 37-point diagnostic view, a GTM blueprint and a 90-day action plan with priorities, owners and sequencing.
You also leave with a clear next step: run the plan internally, or move into Closing OS Install if the system needs to be built and run with the team.
What good looks like
A good sprint gives the team a clearer view of what is helping growth, what is getting in the way and what needs attention first.
The team should be able to explain the main constraint, name the first operating fix, and know what needs to happen over the next 30, 60 and 90 days.
Common failure modes
The sprint fails if the team hides the real pipeline picture, turns the week into abstract strategy, tries to fix everything at once or leaves without a 90-day execution path.
The output only matters if it changes what the team does next: how deals are qualified, how risk is inspected, how the CRM is updated and how the week is run.
Relationship to Closing OS
5 Days to Scale is the Design phase of Closing OS. It can stand alone if the team needs a diagnosis and 90-day plan. It can also become the first step into Closing OS Install if the team needs Closing Foundry to build and run the system with them.
Related pages
Last modified on June 4, 2026