Sales Transformation
Sales transformation roadmap: what to decide, in what order, and who owns it
5 mins read
KEY TAKEAWAYS
A sales transformation roadmap is a sequence of decisions with owners and evidence. A list of tools and go-live dates is only part of it.
Agree the commercial outcome and the process before choosing or configuring technology. Microsoft's own implementation guidance makes the same point.
Give every phase a gate: the evidence that has to exist before the next phase starts.
Name an owner for each workstream, and a separate owner for running it after launch.
Record the baseline before rollout, so you can tell later whether the change worked.
A sales transformation roadmap sets out the decisions a change programme has to make, the order to make them in, and an owner and a piece of evidence for each step. Many roadmaps are built the other way round: a CRM go-live date, a training plan and a list of tools, with the process decisions left until something breaks.
The order that holds up is to agree the commercial outcome, understand how the business sells today, design the future process, then build and roll out the technology. Each phase ends with a gate, a short list of evidence that has to exist before the next phase starts. It's the sequence behind our sales process and CRM transformation work.
Why roadmaps stall
Roadmaps tend to stall for one of three reasons. The technology gets chosen before the process is agreed, so the team rebuilds today's process in a new system. Nobody owns the outcome: IT owns the build, sales owns the targets, and the benefit goes missing in the gap between them. Or success is never defined up front, so a year later nobody can say whether it worked.
Microsoft's implementation guidance for Dynamics 365 is direct about the first. It calls it "a common mistake" to assume the new system defines your processes, and says to define business processes before working on requirements. Coming from a software vendor, that is a useful reminder that process first is more than a consultant's preference.
The roadmap in five phases
Phase | What must be decided | Typical owner | Gate: evidence before moving on |
|---|---|---|---|
1. Outcome | The commercial problem, the measures and today's baseline | CRO or sales director, with finance | A written baseline for the measures you expect to move |
2. Current state | How deals actually move today, where they stall and where data is recorded | Sales operations, with sales managers | A map of today's process and its main breaks, agreed by sales leadership |
3. Future process | Stages, exit criteria, qualification, forecast categories, data standards and roles | Sales director | Written stage definitions and data standards, signed off before any configuration |
4. Build and pilot | Configuration, data migration, integrations and a pilot with one team | IT, revenue operations or an implementation partner | The pilot team running deal reviews from the new process, with issues logged and fixed |
5. Rollout and run | Training, the management rhythm and who maintains the system | Sales leadership, with a named system owner | Reviews run from the new process, and a first read of the baseline measures |
Phase 3 carries most of the commercial thinking. Our guide to sales process stages covers how to write exit criteria, and our CRM transformation guide explains what the sales director should own and what to hand to IT.
The roadmap on one page
Keep one line for each workstream, with these fields. The template is illustrative, so adapt the fields to your programme.
Field | What to record |
|---|---|
Commercial problem | The issue this workstream fixes, in the business's own words |
Baseline | Today's value for the measure you expect to move, and the date it was taken |
Decision needed first | The choice that has to be made before the work starts |
Dependency | What must be finished elsewhere before this can begin |
Accountable owner | One named person |
Evidence to move on | What proves the workstream is ready for the next phase |
Review date | When the owner reports back |
Owner after launch | Who keeps it working once the project team moves on |
Most roadmaps leave out the last field. Every new tool, automation or AI agent needs someone to look after it. If nobody is named, the work lands on whoever is nearest when something breaks. AI tools need this most of all, because AI is only as good as the process behind it.
Where common frameworks fit
Frameworks help with parts of a roadmap, and none of them covers the whole thing. A qualification method such as MEDDPICC gives sellers a shared standard for opportunity evidence, so it belongs in phase 3. Prosci's ADKAR model covers how individual people adopt a change; Prosci describes it as a model for individual change rather than a complete change methodology, so it belongs in phase 5.
Merlin5's own sequence, what, then why, then change, sits in front of all of it: establish what is happening in the numbers, diagnose why, then decide what to change.
What a good roadmap gives you
When BPP's leadership wanted to know where to focus before committing to a transformation, Merlin5's work ended in a prioritised roadmap rather than a long list of disconnected recommendations. Littlefish took the same approach, and came away with a practical roadmap and stronger leadership alignment around priorities. The BPP and Littlefish case studies show how each programme was sequenced.
Where to start
Write down the commercial outcome and today's baseline before any conversation about tools.
Map how deals move today, including the workarounds.
Name one accountable owner for each workstream, and one for running it after launch.
Frequently asked questions
Should we choose the CRM first or design the process first?
Design the process first. The stages, exit criteria and data definitions decide what the CRM needs to do. If you choose and configure the platform first, the platform ends up deciding your process for you.
How long does a sales transformation take?
It depends on the scope, the state of the data and how quickly sales, marketing and finance agree definitions. Agreeing the future process often takes longer than configuring it, so plan time for phase 3 rather than squeezing it.
Sources
Microsoft Learn, "Implement a solution based on business processes", Dynamics 365 implementation guide, updated 2026. https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/process-focused-solution
Prosci, "The Prosci ADKAR Model". https://www.prosci.com/methodology/adkar
NEXT STEP
Find what's limiting growth, in three weeks
The Growth Assessor™ shows where your commercial engine is constrained and what fixing it is worth, so the roadmap starts with the right problem.
Take The Growth Assessor™
WRITTEN BY
Chris Thomas