Sales Transformation
CRM business case: the evidence a CFO needs before approving the budget
8 mins read

KEY TAKEAWAYS
Give the CFO evidence they can check. Start the CRM business case with a baseline finance can reproduce: where the numbers came from, and when.
Count the full cost of ownership. Licences and the build are only part of it; internal team time, training, data work, change and running costs belong in the case too.
Time saved is capacity, not cash. Count a cash saving only when a planned cost is removed. If the time goes into selling, track pipeline as an early sign and count the benefit when it shows in closed revenue.
Show the options, including doing less. A process fix on the current platform is a legitimate option and can be the cheapest test of the benefits.
Fund in stages with named benefit owners and gates, so leadership can see whether the benefits are arriving before the next tranche is released.
Before approving CRM transformation budget, a CFO needs three things from your CRM business case: a baseline finance can check, the full cost of ownership, and benefit assumptions that can be tested once the work is under way. The weakest cases skip all three. They lead with a licence quote and a list of hoped-for gains, and treat hours saved as if they were pounds in the bank.
This guide is for a CRO or sales director preparing a request for CRM transformation budget. It covers what the CFO is approving, how to build each part of the case, and the red flags finance looks for. It doesn't cover the order of work (our guide to CRM transformation does), or choosing a partner or consultant, which have their own guides.
What the CFO is approving
A CRM transformation changes how the business sells, records and forecasts. The licence is the visible cost. People's time, before and after go-live, can be a material commitment too, and it is easy to overlook. So a CFO is approving three things at once:
a change to the sales process and the way deals are managed;
a programme of internal work across sales, operations, IT and finance;
a claim that the result will be worth more than it costs.
Microsoft's implementation guidance for Dynamics 365 makes the same point from the vendor's side. Its implementation strategy has the plan account for process, users, ownership and how success will be measured, not just the system. That is a useful frame for a business case, whichever platform you use. It is not evidence that any particular return will follow.
Start with an auditable baseline
A baseline is the current state, written down with its sources, so that the same numbers can be measured again later. Finance will trust it only if they could reproduce it.
Useful baseline measures for a CRM business case:
The four drivers of sales velocity: qualified opportunities, average deal value, win rate and cycle length, by segment. Merlin5's guide to the four drivers explains each.
Forecast record: what was forecast and what closed, quarter by quarter.
Data quality: share of open opportunities with a close date, value, next step and stage evidence.
Administration time: sampled, not guessed. A week of diaries from a handful of sellers is better than a vendor's average.
Workarounds: the number of spreadsheets used to forecast or report outside the CRM.
Record where each number came from and the date. If a figure is an estimate, label it as one. A baseline that can't be repeated after go-live can't show whether the benefits arrived.
Count the full cost of ownership
The full cost of ownership is everything the business will spend to build, adopt and run the change, inside and outside. List each cost, who carries it, and whether it is one-off or recurring.
Cost | What it includes | One-off or recurring |
|---|---|---|
Licences and subscriptions | Users, add-ons, storage, sandboxes | Recurring |
Implementation | Partner fees, configuration, integrations | One-off, plus changes later |
Data work | Cleansing, de-duplication, migration, archiving | One-off, then ongoing upkeep |
Internal team time | Sales operations, IT, finance and sellers in design workshops and testing | One-off, and easy to overlook |
Training and enablement | Course design, delivery, managers' time, time away from selling | One-off, then for every new starter |
Change and adoption | Communications, coaching, reinforcement after go-live | Initial rollout, then ongoing reinforcement as needed |
Running costs | Administration, support, release management | Recurring |
Microsoft's guidance places training inside the implementation plan rather than after it, which is a reason to budget for it from the start. Running costs matter too: every CRM change after go-live has to be specified, tested and released, and our guide to keeping sales process and CRM aligned shows how much work sits there.
Internal time is easy to overlook because it doesn't arrive as an invoice. It is still a cost, and it belongs in the case.
Write benefit assumptions finance can test
A benefit assumption says what will change, why, by how much, and how you will know. Write each one in the same format:
The mechanism. For example: stage exit criteria stop unqualified deals entering the forecast.
The measure. For example: the gap between forecast and actual.
The baseline. The current value, with its source.
The assumption. The change you expect, and why that size is reasonable.
The owner. The person accountable for the benefit, not the project.
When it should show. And the date you will check.
Cash or capacity. Whether it saves money, creates selling time, or reduces risk.
Keep the assumptions modest and explain them. A CFO can approve a cautious case with clear measures; an ambitious case with no measures is harder to approve.
Time saved is capacity, not cash
Hours saved don't reduce costs on their own. They become a cash saving only if a planned cost is removed, such as a hire you no longer need. If the hours go into selling instead, they may create revenue later, but pipeline is an early sign, not realised revenue, margin or cash.
An illustrative example, with invented numbers:
Step | Figure |
|---|---|
Sellers | 40 |
Administration saved per seller per week (from a sampled baseline) | 2 hours |
Capacity freed per week | 80 hours |
Cash saved if nothing else changes | £0 |
The 80 hours are capacity. To turn them into a benefit, the case has to say where they go. If they go into selling, set early measures, such as more first meetings or qualified opportunities per seller, and count the benefit only when it shows in closed revenue. If they replace a planned hire, name the hire and its cost; that is the route to a cash saving. If the case can say neither, record the benefit as capacity and don't put a pound figure on it.
Compare the options, including doing less
Finance will ask what happens if you spend less. Give them the options side by side.
Do the minimum. Fix the sales process and the review rhythm on the current platform. This can be the cheapest way to test whether the benefits are real. Merlin5's answer on changing CRM is "Usually not", because in its experience the missing piece is the process more often than the software.
Redesign and reconfigure. Design the process, then configure the existing CRM to enforce it.
Replace. Move to a new platform, with the process designed first.
For each option, give the cost, the benefits it can and can't deliver, the risks, and the time to first evidence. If adoption is the problem, our guide to recovering low CRM adoption covers what to try before replacement.
Approval gates and benefit owners
Staged funding protects the CFO and the sales leader. An illustrative structure:
Diagnose. Confirm the baseline and the cause. Output: a ranked list of problems and the evidence.
Design. Agree the process and data standards. Output: a design the business has signed off.
Build and adopt. Configure, train and embed. Output: the system live, and the first measures moving.
Each gate releases the next tranche only when its output exists. Each benefit has an owner in the business who reports on it at agreed dates. If the forecast still can't be trusted, our guide to sales forecasting software explains why the inputs need fixing before more technology.
Red flags in a CRM business case
The benefits come from a vendor's average, not your baseline.
Internal time and training are missing from the costs.
Hours saved appear as cash savings with no plan for the hours.
There is only one option on the table.
Nobody outside the project owns a benefit.
The case assumes adoption will follow go-live.
The partner has been chosen before the process is designed. Our guide to choosing a CRM implementation partner covers what to settle first.
Where Merlin5 fits
Merlin5's work with revenue leaders includes building the business case and prioritising, as one step in a sequence that starts with the data, the CRM review and customer interviews. Merlin5 calls this work the heavy lifting.
On CRM specifically, Merlin5 designs the sales process first and then makes the platform enforce it. It is platform agnostic and has no licence to sell, so the options in the case aren't weighted towards a product. Where the gap is adoption rather than design, the commercial discipline work covers the management routines that make the data reliable.
If you need outside help with the process design itself, our guide to hiring a sales process redesign consultant covers scope and fit.
Where to start
Write down the three decisions the CRM must support, and the measure for each.
Build the baseline for those measures from your own data, with sources and dates.
List every cost, including internal time, before you ask a vendor for a price.
Frequently asked questions
What should a CRM business case include?
A baseline with sources, the full cost of ownership including internal time, training and change, benefit assumptions with owners and measures, the options including doing less, and staged approval gates.
How do you calculate CRM ROI?
Compare the measured benefits against the full cost of ownership over an agreed period. Count only benefits you can measure against the baseline, and keep capacity benefits separate from cash unless the plan shows how the time becomes money.
Should time saved by sellers count as a cost saving?
Not on its own. It is a saving only if a planned cost is removed. Otherwise it is capacity: more selling activity and pipeline are early signs, and the benefit is realised only when it shows in closed revenue.
Who should own the benefits?
A named leader in the business, usually the sales leader for revenue measures and finance for cost measures. The project team owns delivery, not the benefits.
Sources
Microsoft, Dynamics 365 implementation guide, "Implementation strategy". https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/implementation-strategy
Microsoft, Dynamics 365 implementation guide, "Training strategy". https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/training-strategy
NEXT STEP
See where your sales process breaks
Before you ask for budget, find out what your current process and platform can do. A sales process review looks at both, so you can weigh the options with evidence.
Book A Sales Process Review

WRITTEN BY
Chris Thomas