The licence price is the easy part of a CRM budget, and that is better news than it sounds. Licence pricing is the one line in a CRM business case that is published, comparable and quotable months ahead of signature. Everything else in the programme, the configuration, the data migration, the integrations, the training, has a reputation for being unknowable until it is too late. That reputation is mostly out of date. The variables that decide the total are identifiable before anyone signs anything, and the organisations that identify them early consistently land close to their number.
There is a natural moment to do that work right now. Microsoft’s price and packaging update for Microsoft 365, announced on 4 December 2025, took effect on 1 July 2026, with the packaging changes rolling out from June and completing by 1 August. The increases were not trivial: Office 365 E3 rose 13 per cent from 23 to 26 US dollars per user per month, Microsoft 365 E5 rose 5 per cent from 57 to 60, Business Standard rose 12 per cent from 12.50 to 14, and Microsoft 365 F1 rose 33 per cent from 2.25 to 3. Finance teams across Europe have spent the summer re-forecasting as a result.
Worth stating plainly, because it causes real confusion: Dynamics 365 is not affected by that update. The changes cover Microsoft 365 commercial suites and standalone components, not the CRM and ERP line. If your Dynamics forecast moved this summer, something else moved it. That distinction is exactly the sort of thing worth confirming before it becomes a budget assumption, and it is a useful prompt to look at the whole cost picture rather than the one line that changed.
How much does a CRM implementation actually cost?
For most mid-market B2B organisations, the licence is the minority of the first-year cost of a CRM programme. A reasonable planning assumption is that implementation services, meaning configuration, integration, data migration and enablement, land somewhere between one and three times the first-year licence spend, with the multiple rising alongside the number of systems the CRM has to talk to. A straightforward Sales Cloud or Sales Hub rollout for a single region sits at the bottom of that range. A multi-country deployment with ERP integration, a CPQ requirement and ten years of legacy data sits at the top. The licence line is the one you can look up; the multiple is the one worth investigating.
The useful consequence is that negotiating hard on licence discount, which is where most procurement energy goes, moves the smaller number. The same energy spent narrowing integration scope or improving data quality before migration moves the larger one. Neither is wasted, but the order matters, and teams that get the order right tend to find their overall spend comes in lower without a tougher negotiation. We have written before about how hybrid pricing models are shifting leverage toward buyers, which makes this an unusually good period to be doing the arithmetic carefully.
What is a CRM pre-study, and what does it settle?
A CRM pre-study is a short, fixed-scope discovery engagement, typically two to six weeks, run before a platform is selected or an implementation contract is signed. It produces four things: a documented map of the processes the CRM must support, an inventory of the systems it must integrate with and the state of the data in them, a prioritised requirement list separating what is genuinely needed at launch from what can wait, and a costed delivery plan with the assumptions written down. Its purpose is to convert the unknowns in a CRM budget into either a known quantity or an explicitly flagged risk with a price attached.
The reason a pre-study pays for itself is that it front-loads the discoveries that otherwise arrive mid-build, when they are most expensive to absorb. Finding out in week two that the ERP exposes order history through a nightly file rather than an API is a scoping conversation. Finding out in month five is a change request. The pre-study is also the artefact that makes competing implementation quotes genuinely comparable, because every bidder is pricing the same documented scope instead of their own interpretation of a requirements workshop. That comparability is usually worth more than the document itself.
Why do CRM implementations go over budget?
When CRM programmes exceed their budget, the cause is rarely the platform and almost never a surprise in the licence line. Four drivers account for most of it: data that turned out to be in worse condition than assumed, so migration became a cleansing project; integration scope that grew as each connected system revealed its own constraints; requirements that expanded during build because they were never ranked at the start; and adoption work that was under-resourced, producing a technically complete system that people route around. Every one of those four is visible during discovery if someone is looking for it.
That is the encouraging part. These are not random events, they are a short and stable list, and the same four show up across Salesforce, HubSpot and Dynamics 365 alike. A team that prices all four deliberately at the outset, including the unglamorous data work, is not predicting the future so much as refusing to leave four known variables unpriced. The budgets that hold are usually the ones that looked slightly more expensive on day one, which is a much easier conversation to have with a board before signature than after it. We covered the selection-stage version of this in what most CRM selections get wrong.
How long should a CRM implementation take, and how do you measure the return?
A focused first phase for a single region and a single core process, typically sales, runs somewhere between three and six months from kick-off to live use. Multi-country rollouts with ERP integration and complex quoting generally run nine to eighteen months, though the better versions of those deliver a working first phase early and extend from there rather than holding everything back for one large launch. The strongest predictor of the timeline is not the platform, it is how much was settled before the build started, which is the same reason a pre-study compresses the schedule as well as the budget.
On return, the measures that hold up are the operational ones rather than a modelled revenue uplift: how much of the pipeline is actually recorded in the system, how long a quote takes to produce, how much time sellers spend on administration, and how much of the forecast is reconstructed manually at quarter end. Those can be measured before the programme starts, which is what makes them credible afterwards. Baselining them during discovery costs almost nothing and turns the eventual ROI conversation from an argument into a comparison. Adoption is where most of the return actually sits, as we argued in adoption is your best CRM investment.
Why an independent partner changes the cost conversation
An independent CRM consultant is one whose revenue does not depend on which platform you choose or how many licences you buy. The practical difference shows up in the recommendations that reduce spend. An independent partner can advise that the existing platform is fine and the real problem is data quality, that a cheaper edition covers the requirement, that a planned migration is not worth its disruption, or that the right answer is to consolidate two instances rather than buy a third system. Those conclusions are harder to reach from inside a partner network with licence targets attached, not because of bad faith but because of what the commercial model rewards.
This matters most at the two points where CRM money is actually committed, which are platform selection and scope definition. Both happen before implementation begins, and both are much cheaper to get right than to correct. It is also why the arithmetic in a pre-study is worth having from someone with no stake in its conclusion. We looked at when the consolidation answer is the right one in when CRM consolidation actually pays, and at how the EU Data Act removes switching costs from January 2027, which widens the set of options a buyer can realistically consider.
A practical sequence for the next budget cycle
Start by separating the two questions that usually get merged: what the platform costs and what the programme costs. The first is a procurement exercise with published inputs and a predictable answer. The second is a discovery exercise, and it is where the money is. Treating them as one negotiation is what produces a well-discounted licence attached to an underscoped delivery.
Then get the four cost drivers onto paper before committing: assess the real state of the data you intend to migrate, list every system the CRM must exchange information with and how, rank requirements into launch and later, and put a named budget line against enablement rather than assuming training is absorbed. Baseline your operational measures at the same time. That is a few weeks of work, it is cheap relative to the programme, and it converts most of a CRM budget from an estimate into a plan. Teams that do it are not being cautious, they are buying the ability to commit with confidence.
The Sirocco perspective
We work across Salesforce, HubSpot and Microsoft Dynamics 365, and the pattern we see is that the organisations happiest with their CRM spend are rarely the ones that negotiated the sharpest discount. They are the ones that knew what they were buying before they bought it. Our pre-studies exist for that reason, and a meaningful share of them end with a recommendation that costs the client less than the brief assumed, whether that is staying on the current platform, deferring a module, or fixing data before adding capability. As an independent partner, that is a conclusion we are free to reach.
The wider picture is genuinely favourable for buyers right now. Pricing models are becoming more flexible, switching costs are falling under EU rules from January 2027, and the capability gap between the major platforms has narrowed to the point where the decision increasingly turns on fit and delivery quality rather than feature lists. That combination gives a well-prepared European CRM buyer more leverage than they have had in years. The preparation is the part you control, and it is a few weeks of work.
If you are planning a CRM investment and want the cost picture mapped before you commit, schedule a consultation with our team.
Get in Touch
If you are building a CRM budget for the next cycle, tell us which platform you are evaluating and we will walk you through what a pre-study would settle before you commit.
