The quote is never the price: Why ERP budgets overrun and how to catch it early
Sponsored content. This article was supplied by a third party and Business Money has been paid to publish it.
Ask a software vendor what a new ERP system will cost, and you’ll get a confident number. Ask a finance director who has just been through an implementation, and you’ll get a wince. The distance between those two reactions is the subject of this article.
The quote you sign is a starting position, not a final bill. Panorama Consulting Group’s 2026 ERP Report, which tracked 170 organisations with a median annual revenue of around $200 million, found that roughly 30% of projects came in over budget. The most common reason wasn’t hard negotiation or vendor greed. It was the discovery, mid-project, that the business needed technology nobody had budgeted for.
For any SME weighing up an ERP investment, understanding why the quote and the final cost diverge is the difference between a controlled spend and an awkward line on the next board report. Here’s where the gap comes from, and how to close it before you sign.
The quote and the final bill are two different questions
A quote answers a narrow question: what will the software and the core implementation service cost? The final bill answers a much broader one: what did it cost to get the whole business actually running on the new system?
Those are rarely the same figure, and decades of research make that clear:
- The Standish Group’s long-running study of IT projects found an average cost overrun of about 43%, with roughly 71% of projects exceeding their budget, timeline or scope.
- Panorama’s 2026 figures are more encouraging but still sobering. About half of projects (50.6%) finished on budget and 19.4% actually came in under. The remaining 30% overran, most of them “slightly”, though 7.1% overran significantly.
The pattern holds across twenty years of data. A quote captures the known, scoped, contracted work. Overruns come from everything the quote quietly assumed away. Treating the number on the proposal as your true cost is the first mistake, and it’s an easy one to avoid once you know what the quote leaves out.
It’s worth being precise about the cause, because it points to the fix. In Panorama’s 2026 sample, the single leading driver of budget overruns wasn’t cost inflation or scope creep in the usual sense. It was an unexpected need for additional technology that only became obvious once the project was underway: a missing integration, a reporting layer that couldn’t do what the business needed, an extra module. Schedule slippage told a parallel story. Around 22% of projects ran late, and the leading cause there was organisational rather than technical. In plain terms, most of what blows a budget is discovered during the work, not priced into the quote before it, which is precisely why so much depends on how carefully you scope the job at the start.
Where the extra money actually goes
Most overruns aren’t one dramatic miss. They’re an accumulation of line items that felt small at quoting time and grew once real requirements surfaced. The usual suspects are consistent enough that you can plan for them:
- Integrations. Every connection to another system (your accounting package, CRM, e-commerce platform or warehouse tools) adds work. Common cost models put each integration somewhere between $3,000 and $15,000, and very few businesses need only one.
- Customisation. Panorama’s research has long shown that only around 7% of companies run their ERP as-is, which means roughly 93% customise something. Heavy custom development can add 700-plus consultant hours at $150 to $350 an hour, and leaning on custom code instead of standard configuration can inflate a budget by 50% or more.
- Data migration. Moving years of messy historical records is almost always harder than expected. The more history you carry across, the higher the cost climbs.
- Training and change management. This is the line most often trimmed to make a quote look competitive, and the one that most often comes back to bite. Panorama consistently finds that organisational and people issues, not technical ones, are the hardest part of any implementation.
- Timeline pressure. Want it faster? Compressing a schedule typically adds a premium of 20% to 50%, because speed means more people working in parallel and more coordination overhead.
This is exactly why cost-modelling tools have become useful at the evaluation stage rather than after signing. For SMEs looking at popular open-source platforms, running the numbers through something like an Odoo implementation cost calculator forces each of these drivers into the open before a contract exists. The value isn’t the precise figure it spits out; scope always shifts. The value is that the exercise makes your assumptions about users, integrations, customisation and data explicit while there’s still room to change them cheaply.
A finance-led checklist for catching overruns early
You don’t need to be technical to keep an ERP budget honest. You need to ask the questions a good CFO asks about any capital project. Here’s a practical sequence:
- Separate the licence from the implementation. The subscription or licence fee is usually the smaller, more predictable number. The implementation service is where budgets actually move. Insist on seeing the two itemised separately, not blended into one headline figure.
- Pressure-test the scope behind the number. Ask exactly which integrations, how many custom workflows and how much data migration the quote assumes. A quote with vague scope is a quote designed to grow.
- Budget a contingency, and name it openly. A 15% to 20% contingency line isn’t pessimism; it’s arithmetic that matches the research. Put it in the board paper up front rather than discovering it in month four.
- Define “done” before you start. Overruns thrive on ambiguity. Agree written acceptance criteria for what a completed phase looks like. Panorama’s own audit work has flagged projects billed as “complete” that, on inspection, were not.
- Phase the rollout. A staged go-live spreads cost and risk, and gives you real data to re-forecast the next phase. It also limits the damage if something goes wrong early.
- Budget for the day after go-live. The project doesn’t end at launch. Support, fixes and adoption work continue for months, and they cost real money that rarely appears on the original quote.
The cost of skipping this discipline isn’t hypothetical. In late 2025, cleaning-equipment manufacturer Tennant Company told investors that a troubled ERP go-live had knocked roughly $30 million off quarterly sales and about $22 million off adjusted EBITDA. Its ERP spending for 2026, originally planned at around $5 million, was now expected to exceed $20 million. That’s a listed company with resources most SMEs can only dream of, and the overrun still hurt. The lesson scales down brutally: the smaller your balance sheet, the less room you have to absorb a surprise.
What good budgeting looks like
The businesses that stay on budget tend to share a habit. They treat the quote as an input to their own estimate rather than as the estimate itself. They ask the vendor to expose assumptions, they model the cost drivers independently, and they carry a named contingency into the boardroom instead of hoping they won’t need it.
It’s also worth remembering that on-budget doesn’t automatically mean successful. Panorama’s data repeatedly shows organisations that hit their financial targets but still fail to realise the benefits they expected, usually because change management was underfunded. A project that lands on budget but nobody adopts is still a poor return. Cost control and value realisation are two separate disciplines, and both deserve attention before you commit.
The bottom line
Three things are worth holding onto:
- A quote is a hypothesis, not a price. Treat it as the opening figure in a total-cost-of-ownership calculation, not the answer.
- Overruns are predictable, which makes them preventable. Integrations, customisation, migration and change management are the same culprits in study after study. Model them up front.
- The cheapest way to control an ERP budget is to spend more time on it before signing, not after.
Your next step is simple. Before you accept any proposal, write down every assumption it depends on (users, integrations, customisations, data volume and timeline) and put a number against each one. If the vendor can’t or won’t help you do that, you’ve learned something important about the vendor before it cost you anything.