How Much of Your ERP Budget Should Go to Change Management, and What It Buys
Most ERP budgets set aside too little for change management, and it gets cut first. Here's what 10–15% of the services budget should buy, how to size it, and where employee consultation adds months.
The short answer: 10–15% of services spend, and keep it out of contingency
If you're signing off an ERP program, plan to put roughly 10–15% of your implementation services budget into ERP change management. That covers external consultants, training design and delivery, and adoption tracking. It doesn't cover internal staff time, which you'll need on top. Programs with heavy process redesign, several countries or a unionized workforce should plan for the top of that range or a bit above it.
Below 5% is a red flag. At that level, "change management" usually means a few emails and one week of classroom training before go-live. The line also has to be protected. When the build overruns, organizational change management (OCM) is the easiest item to cut, because nobody notices it's missing until order entry slows down after cutover. Give it its own budget line with a named owner, not a share of contingency.
What organizational change management on an ERP program actually covers
OCM for ERP isn't the same as communications. A credible scope has four work streams, and you should ask any partner to price each one separately:
- Stakeholder mapping and change impact assessment: who is affected, how much, and what they do today that will change.
- Role-based training: curricula built around jobs such as AP clerk, buyer and warehouse lead, not system modules.
- A super-user network: trained people inside the business who test, teach and give first-line support.
- Adoption metrics and hypercare: measuring whether people use the system as designed, then fixing the gaps.
Communications, sponsor coaching and readiness checkpoints run alongside all four. If a proposal bundles everything into one "OCM" figure with no deliverables, you can't tell what you're buying.
Stakeholder mapping is where the cost estimate comes from
The impact assessment should come before most other OCM spending, because it decides how big the rest is. A good one lists every affected role and rates the change on three dimensions: process change, system change and organizational change, such as new approval chains or a merged shared-services team.
Take an inventory planner moving from spreadsheet reorder points to MRP-driven planned orders. That's high impact. It needs real training, coaching and perhaps a revised job description. A sales rep who only looks up order status on a new screen is low impact and needs a short video. Programs that skip this step treat everyone the same. They overspend on low-impact users or, more often, under-train the minority of roles that carry most of the operational risk.
Plan on roughly three to six weeks for the assessment on a mid-market program, and finish it before the build phase is half done.
What drives ERP training cost
ERP training cost depends mostly on the number of distinct roles, the number of languages and how often the design changes late in the program. Headcount matters less. These are typical 2026 market ranges, which vary by contract and region:
- Instructional design: commonly tens of design hours per hour of finished role-based content, more for simulation-heavy material.
- Trainer and OCM consultant day rates: about $1,000–2,200 in North America, the UK and Western Europe, and roughly $300–900 for delivery teams in India, Southeast Asia or Latin America.
- Digital adoption platforms such as WalkMe, Whatfix or Pendo: often tens of dollars per user per year at mid-market volumes, frequently with sizable minimum contracts.
Translation and localized screenshots add meaningful cost per extra language, often 15–30% of the content budget. For most mid-market programs, train-the-trainer delivered through super users is better value than consultants teaching every session. Local trainers know the real exceptions, and they stay after the partner leaves. Confirm all rates with vendors, since local pricing differs widely.
Designing an ERP super user network that holds up after go-live
The super user network has the most effect on outcomes of anything in change management, and it's the part most often under-resourced. Aim for about one super user per 10–20 end users, with at least one per site and per major process. Pick people their peers already go to for help, not whoever their manager can spare.
The time cost is real. Expect roughly 20–30% of each super user's time during design and testing, and half or more of their time for the few weeks around cutover. If their day jobs aren't backfilled, the network fails quietly. Super users miss testing, end users miss coaching, and defects surface in production.
Write the role down: scope, hours, how it counts in performance reviews, and what happens to it after hypercare. Super users who get recognition stay engaged. Those handed unpaid extra work tend to leave.
Adoption metrics that tell you whether the money worked
Course completions measure attendance, not ERP user adoption. Agree on behavioral metrics before go-live, set baselines, and review them weekly through hypercare:
- Share of purchase orders raised in the system rather than off-system or retrospectively
- Manual journal entries and workaround spreadsheets per period-end close
- Help-desk tickets per 100 users, split into "how do I" and real defects
- Transactions corrected or reversed within 48 hours
- Days to first month-end close compared with the pre-ERP baseline
A high share of "how do I" tickets in week three points to a training gap, not a system fault. That's where remaining OCM budget should go. Keep roughly 15–20% of the change budget unspent at go-live for targeted fixes like this.
Worked example: sizing change management for a three-country rollout
Hypothetical example. Say a 400-person distributor is moving 180 users to a cloud ERP across Germany, Poland and Mexico. The implementation services budget is $1.6 million. The impact assessment flags 35 high-impact roles in planning, finance and warehousing.
| Change work stream | Indicative external cost (USD) |
|---|---|
| Change lead, part-time over 9 months | $60,000–75,000 |
| Stakeholder mapping and impact assessment | $15,000–20,000 |
| Role-based training design, 3 languages | $40,000–50,000 |
| Training delivery and train-the-trainer | $30,000–40,000 |
| Super-user onboarding and coaching | $15,000–20,000 |
| Adoption tracking and hypercare support | $15,000–20,000 |
| Works council consultation support (Germany) | $10,000–15,000 |
| Total external | $185,000–240,000 (about 12–15%) |
Internal time comes on top. Twelve super users at 30% for six months is about 21.6 person-months. At loaded costs of $5,000–8,000 a month, which vary a lot by country, that's another $108,000–173,000 in backfill or lost capacity. Finance should see both figures together.
Where works councils and union consultation add time
In some countries, new ERP and warehouse systems trigger formal employee consultation, and that affects the timeline more than the budget. In Germany, works councils generally have co-determination rights over technical systems capable of monitoring employee performance. That can reach ERP, WMS and time-tracking modules, and it often leads to a negotiated works agreement. France's CSE has consultation rights when new technologies are introduced. Dutch works councils have consent rights over some employee-monitoring systems, and Nordic countries such as Sweden expect negotiation with unions ahead of major changes.
Elsewhere, collective agreements matter. Unionized warehouses in the UK, Australia, Brazil, South Africa and parts of North America may have contract terms on job changes, scanning-based productivity measurement or shift patterns. In other markets the main constraint is data protection, such as the GDPR, India's DPDP Act or Brazil's LGPD, when user activity logs are analyzed.
Where consultation applies, plan for roughly two to six months and start during design, not the month before go-live. Rules differ by country and by agreement, so have local employment counsel confirm what applies to you.
Red flags in a partner's change proposal, and your next step
Push back on any statement of work that shows these:
- One combined OCM fee with no deliverables or acceptance criteria
- Training priced per session, with no role curricula or impact assessment
- No super-user time estimate, or super users "provided by client" with no hours stated
- Adoption measured only by course completions
- No works council, union or data-protection steps for in-scope countries that have them
Decision rule: if the impact assessment shows more than a quarter of users in high-impact roles, or the program covers sites where you must consult employees, budget at least 15% and protect the line in the steering committee charter. Before you sign, ask shortlisted partners to re-price change management as the four work streams above, using your own role count, languages and sites.
Quick answers
Should change management be in the system integrator's contract or bought separately?
Either can work. Separate is safer when the integrator's OCM practice is thin or when you want an independent read on readiness. If it stays with the integrator, ask for named OCM staff, separate deliverables and a fee that can't be moved into build work when the timeline slips.
How many super users do we need?
Plan on about one per 10–20 end users, with at least one per site and per major process area such as order-to-cash, procure-to-pay and warehouse. High-impact roles may need a lower ratio. Budget their time explicitly, because unbackfilled super users are a common reason networks fail.
Can a digital adoption platform replace classroom or role-based training?
It adds to role-based training but doesn't replace it. In-app guidance works well for occasional users and for reinforcement after go-live. High-impact roles still need structured training on the new process, not only the screens. Weigh the per-user subscription cost against how many occasional users you actually have.
When should ERP change management start?
Start at program mobilization, before design workshops. Finish the impact assessment before the build is halfway through. Consultation with works councils or unions, where it applies, should begin during design, because it can take several months.
Is 10–15% enough for a small company with under 50 users?
Smaller programs often need a higher share, sometimes 15–20%, because fixed costs like the change lead and training design don't shrink in line with headcount. In absolute terms the amount is modest. The bigger risk is a founder or CFO assuming everyone will just pick up the new system.
Written by the Trackmeshflow editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.