Sales Transformation
Sales operating model: design it before you choose or configure the CRM
8 mins read

KEY TAKEAWAYS
A sales operating model sets who sells to which customers, what each stage has to prove, who owns which decisions and how the business is reviewed. The CRM should record those choices, not make them.
Design it before you choose or configure a platform. Otherwise the configuration can end up settling questions that sales leadership never agreed.
Write it to a standard a partner can build from: roles, stage evidence, forecast rules, data owners and the review rhythm, each with a named owner.
Scope the design and the build as separate pieces of work, with a sign-off between them. Agreeing how the business sells is different work from configuring a system.
If leaders still disagree on definitions, the model isn't ready to build. In Merlin5's experience, agreeing definitions is what sets the pace.
Design the sales operating model before you choose or configure a CRM. The operating model sets who sells to which customers, what each stage of a deal has to prove, who owns which decisions and how the business is reviewed each week. The platform should then record and enforce those choices. When the order is reversed, the risk is that configuration settles questions sales leadership never agreed, and the team ends up selling the way the system was set up.
This guide is for a sales director, CRO or COO who is about to choose a CRM, reconfigure one or brief a partner. It covers what the operating model contains, how to tell when it's ready to build from, and whether to buy the design separately from the build. The wider order of a change programme is set out in our sales transformation roadmap, and choosing who builds the system has its own guide on choosing a CRM implementation partner.
What a sales operating model covers
A sales operating model is the written design of how the sales organisation works: its structure, roles, process, data and forecasting rules, and the management rhythm that holds them together. It isn't an org chart and it isn't a CRM specification, although both are drawn from it.
Bain's Commercial Excellence X-ray, an undated diagnostic graphic, treats the commercial operating model as a category of its own, covering structure, accountabilities, governance and ways of working. It also describes every part of the commercial engine as interconnected. That is the practical reason to design these pieces together rather than one at a time.
In practice, a usable model answers these questions:
Coverage and roles. Which customers each team serves, who owns each account, and where handoffs happen between marketing, inside sales, field sales and account management.
Process and stage evidence. The stages a deal passes through, and the evidence needed to leave each one. Our guide to sales process stages shows how to write these as exit criteria.
Decision rights. Who can approve a discount, move a deal between forecast categories, reassign an account or close a deal as lost.
Forecast and pipeline rules. What counts as pipeline, how each forecast category is defined, and who commits the number.
Data ownership. Which fields matter, who keeps them accurate, and the rule for duplicates.
Management rhythm. The weekly and monthly reviews, what each one decides, and which report it runs from.
Measures. The few numbers that show whether the model is working, with today's value.
Merlin5's own deliverables include a commercial operating system blueprint: the design of the commercial operating model across process, CRM, forecasting, reporting and governance.
Why the operating model comes before the platform
A CRM can only enforce decisions that have already been made. If stage evidence, decision rights and forecast rules aren't written down, whoever configures the system can end up making those decisions instead, one field at a time.
Microsoft's implementation guide for its Dynamics 365 products makes the point from the vendor's side. It says successful implementations start with a clear understanding of the business model, which it also calls the target operating model, and that the system should serve and fit your operations. Its short version is "Technology is an enabler." The guide is written for Microsoft's own products, but the reasoning doesn't depend on the platform.
Merlin5 says it in fewer words: the operating model comes before the platform. The process comes before the configuration, and the customer comes before the technology.
When the order is reversed, these are the kinds of problem that can surface after go-live: stages mean different things to different teams, required fields go unused, the forecast still lives in a spreadsheet and managers stop trusting the reports. Our guide to recovering low CRM adoption deals with that situation. In our view, settling the design first is less disruptive than unpicking a live configuration.
Is your sales operating model ready to build from?
It's ready when a partner could configure the CRM from it without inventing business rules. Test it against these questions. Each "no" is a decision still to be made.
Can every sales leader describe each stage in the same words, and name the evidence needed to leave it?
Does every account have one owner, with a written rule for handoffs between teams?
Are the forecast categories defined, with a named person who commits the number?
Does each required field support a decision that someone actually makes?
Is it written down who approves discounts, exceptions and reassignments?
Does every weekly and monthly review have a purpose, an owner and a report it runs from?
Have you agreed the measures of success, and recorded today's value for each?
Microsoft's 2024 implementation strategy guidance gives opportunity conversion rate as an example of the tangible measure it has in mind. It also says the business teams own and design the process flows, while IT organises the technical delivery. That split matters here: the questions above are for sales leadership to answer, not the project team.
If sales leaders are still arguing about definitions, the model isn't ready, and that argument may well set the timetable. Merlin5's FAQ on its own process work says the same thing: the design moves faster than most expect, and the pace is set by agreeing definitions across teams that have been using their own.
Strategy only, or design and build together?
Buy the operating model design as its own piece of work, with its own scope and sign-off, even if the same firm will also do the build. The two jobs need different people in the room and produce different things.
Microsoft's process guidance draws the line clearly: implementing an existing process with new technology takes different effort from defining or agreeing new processes. We'd expect design work to be mainly sales leaders' time, spent in workshops, deal reviews and debates about definitions. Build work is mainly configuration, data migration, integration and testing.
Option | What you get | Choose it when |
|---|---|---|
Design only | A written operating model the business has signed off | You haven't chosen a platform, or want build proposals priced on the same scope |
Design and build, scoped separately | One provider, with a sign-off gate between design and configuration | You want continuity but still want to see what each part costs |
Build only | Configuration of a design you already own | The model is written, signed off and passes the readiness test above |
The version we'd treat as riskiest is the one where design is folded into the build and nobody signs it off. Microsoft's implementation guidance warns that a statement of work describing only high level activities leads to confusion over who does what, and it recommends stating what is out of scope. It also notes that work late in a project, including training and change management, is often cut to meet the budget. Write both into the plan from the start, or the operating model may stay on paper.
Keep the model current once the CRM is live
The operating model will keep changing: a new segment, a new inside sales team, an acquisition. Each change should go through the model first and the CRM second. Our guide to keeping sales process and CRM aligned covers how to do that when CRM releases are slow.
McKinsey made a related point in April 2020, writing early in the pandemic. Its article on agility and stability in B2B sales argued that agility in B2B sales means putting a new operating model in place, built around the customer and supported by the right processes and governance, and that stable practices give agile teams their structure. That was written for a crisis, but we think the balance still holds: change the model deliberately, and keep the core routines stable while you do.
Without that discipline, a model can drift. Merlin5's page for revenue leaders describes businesses of £1 to 2 billion in those terms: complexity is the constraint, and the model accreted rather than being designed.
Where Merlin5 fits
Merlin5 designs the commercial process first and then configures the platform to enforce it. Its FAQ separates this from a CRM implementation: an implementation configures the platform you have chosen, while Merlin5's work designs the process the platform is meant to support. It is platform agnostic, with no licence to sell and no implementation partner to protect.
For revenue leaders, commercial operating systems are one of Merlin5's eight ways in: stronger sales processes, forecasting disciplines, CRM adoption and governance. Where the design is sound but the routines haven't stuck, Merlin5's commercial discipline work covers CRM adoption, pipeline governance and data quality.
If you're also being asked about AI tools, the same foundations apply. Our guide to AI readiness for sales teams covers what to fix before buying.
Where to start
List the decisions your weekly sales meeting should make, and who makes each one.
Have three sales leaders each write down what the same two stages mean, without conferring, and put the answers side by side.
Before you ask for CRM proposals, run the readiness questions above and list every "no".
Frequently asked questions
What is a sales operating model?
It is the written design of how the sales organisation works: who covers which customers, the stages and evidence a deal needs, who holds which decisions, the forecast and data rules, and the review rhythm. The CRM records it; it doesn't replace it.
Who should own the sales operating model?
The sales leader, with sign-off from the leadership team. A sales or revenue operations team can maintain it day to day, and IT or a partner configures the CRM from it. The project team delivers the build but shouldn't own the design.
Do we need a new CRM to change our operating model?
Usually not. Merlin5's view is that most organisations already have a platform capable of supporting a well designed process, and that the missing piece is the process rather than the software. Design the model first, then test what your current platform can do.
How long does designing a sales operating model take?
We'd say it depends most on how quickly leaders agree definitions. Merlin5 publishes a range of two to three months on average for its broader sales process and CRM work, varying with the size of the organisation, the state of the data and stakeholder availability. That range covers the wider engagement, not design alone, so treat it as context rather than a promise for a design-only scope.
Sources
Microsoft Learn, "Implement a solution based on business processes", Dynamics 365 implementation guide, updated 3 February 2026. https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/process-focused-solution
Microsoft Learn, "Plan a Dynamics 365 implementation strategy", Dynamics 365 implementation guide, updated 5 January 2024. https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/implementation-strategy
Bain & Company, "An X-ray for Your Sales Ailments" (Commercial Excellence X-ray), undated. https://www.bain.com/contentassets/e84135eb13a24ed7a5a3a6d6e4536130/commercial-excellence-xray.pdf
McKinsey & Company, Driedonks and Paulowsky, "Two ingredients for successful B2B sales: Agility and stability", 23 April 2020. https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/two-ingredients-for-successful-b2b-sales-agility-and-stability
NEXT STEP
See where your sales process breaks
Before you brief a partner, get an outside view of how you sell today and what your current CRM can support. Start with a sales process review.
Book A Sales Process Review

WRITTEN BY
Chris Thomas