A sequenced plan for closing the gaps the diagnosis found; every initiative named, sized, owned and scheduled, in the order that makes each phase cheaper than the last.
The plan is organised into three horizons. They are not equal phases of a project; each one does a different job, and the order is set by dependency rather than enthusiasm.
The plan is assembled from your pillar scores and overall score, your critical gaps, your revenue-at-risk decomposition, the priorities agreed in the session, your business profile and economics, and a short discovery that goes past what a self-assessment can tell me about your tools, your team, and what is really happening rather than what was designed.
A plan is only executable if each item on it can be picked up by someone who was not in the room. That is what these fields are for, and it is the difference between a strategy document and a schedule of work.
Pillar - which of the ten capabilities it strengthens.
Objective - the outcome it is meant to produce.
Owner - one accountable person.
Expected return - that pillar's share of the revenue at risk.
KPIs - how success gets measured.
Timeline - which horizon it belongs to.
Gap addressed - the specific missing item from your diagnosis.
Key actions - the concrete actions to close it.
Effort and impact - rated, and used to sequence.
Dependencies - what has to be in place first.
Milestone - defined as an observable state, not an activity.
"Every lead captured in the CRM within five minutes", not "worked on lead capture". A milestone you can argue about is not a milestone.
This roadmap is delivered as a visual timeline (at-a-glance view) and a detailed initiative schedule beneath it, which becomes the document implementation actually executes against.
Demand is one input. What happens to that demand afterwards (how fast it is answered, how consistently it converts, whether the customer stays) decides what the demand is actually worth.
A chain performs at the level of its weakest link. A business can be genuinely excellent at four capabilities and still be stuck, because one weak link caps everything downstream of it.
This is not a failure of intelligence. It is a structural blindspot: you can see the parts of the machine you personally touch, and the loss almost always sits in the handovers between functions, where it belongs to nobody and appears on nobody's report.
No competent professional prescribes before examining. A structured diagnosis across all ten capabilities is fast and costs nothing while implementation is expensive and hard to reverse. Doing them in that order turns implementation from a bet into a targeted intervention.
No competent professional prescribes before examining. A structured diagnosis across all ten capabilities is fast and costs nothing while implementation is expensive and hard to reverse. Doing them in that order turns implementation from a bet into a targeted intervention.
The revenue-at-risk figure is not audited and is not a guarantee. It is only as accurate as the numbers you put in. Its purpose is to make the size of a gap concrete, not to produce a figure for a board pack.
The price is stated before we speak, not quoted afterwards. That is the point of fixing it so you can decide whether the plan is worth buying without a conversation, and I cannot price against how much you appear to be able to pay.
Once commissioned, the roadmap takes 5 to 7 business days to build after a short discovery session and it is presented to you rather than emailed as a deliverable.
The roadmap is a plan you own outright. What happens next is your decision.
Every initiative carries enough detail to be actioned by someone who was not in the room, that is what the eleven fields are for. Many clients take this path, and it is a complete successful outcome rather than a failure to convert.
Your team executes; the direction, review and course-correction come from outside. Monthly, with a six-month commitment.
The systems are built with you; installed, documented, and handed over so they run without the person who built them. A fixed project price for a defined scope.
Some clients take both; consulting retainer and systems implementation. Where a roadmap contains initiatives their team can run and others it cannot, implementation covers the systems that need building while the retainer keeps direction on the rest.
Not a strategy deck.
It is a schedule of work with owners, dependencies, and metrics attached. If it cannot be executed by someone reading it cold, it has not been written properly.
Not a commitment to anything else.
The plan is your when it is delivered. There is no clause, no retainer attached, no expectation that you buy the implementation.
Not a guarantee of return.
Every initiative carries an expected return derived from an estimate, and an estimate is what it stays. What the plan produces depends on quality of execution, some of which will be yours.
Not available without a diagnosis.
There is no roadmap that skips the scan, the report and the session.
The scan takes about 15 minutes and returns your score, your maturity stage, an estimate of the revenue at risk each year, and a written report naming the gaps.