Most ERP budgets are wrong before the project starts, because they are built from the wrong number. A company asks for a price, receives a licence quote and an implementation estimate, and treats their sum as the budget. Then data, integrations, training and internal time arrive. This guide shows what an ERP budget really needs to cover and how to build one that holds.
The cost components of an ERP project
| Component | What it covers | Often forgotten? |
|---|---|---|
| Software licences or subscription | Users and apps, per month or per year | No |
| Implementation services | Discovery, configuration, project management | No |
| Data migration | Cleaning, mapping, importing and verifying data | Yes |
| Integrations | Banks, payment gateways, e-commerce, payroll, other systems | Yes |
| Customisation | Features the standard software does not provide | Partly |
| Training | Role-based training before go-live | Yes |
| Internal staff time | Your people's hours on decisions, data and testing | Yes |
| Hosting and infrastructure | Cloud hosting, backups, environments | Sometimes |
| Support and upgrades | Help after go-live, version upgrades, new needs | Yes |
If your budget has only the first two lines, it is not a budget yet.
What pushes the cost up
- Scope. Every process and every company or branch in scope adds configuration, testing and training.
- Data quality. Clean, consistent data migrates quickly. Duplicate customers and products with several codes take weeks.
- Customisation. Each customisation is built once, then tested and maintained through every upgrade.
- Integrations. Each connected system is a small project with its own testing.
- Decision speed. Waiting for decisions is paid time. Slow decisions are one of the least visible cost drivers.
- Local requirements. Multi-currency, local tax rules, payroll rules and bilingual documents all need configuration. In Kuwait, for example, the dinar's three decimals and Arabic documents must be set up before any transaction is entered.
Build the budget per phase
Do not budget the whole ERP vision at once. Budget phase one in detail and the later phases as a range.
- Write the scope for phase one: processes, users, integrations, data to migrate, reports, and what done means.
- Keep phase one close to standard. Standard flows are cheaper to configure, test and upgrade.
- Price each integration and each customisation separately, so you can see what each one costs and decide whether it belongs in phase one.
- Add internal effort: hours for your decision-maker, data owners and testers.
- Add support for the first months after go-live, including the first month-end close.
- Hold a 10 to 15 percent contingency for genuine surprises such as data quality or a regulatory change.
The internal costs people forget
Your own people will spend real time on the project: deciding how processes should work, cleaning data, testing, attending training and running old and new systems in parallel for a while. If the project is staffed by people who also run the business full time, plan for that load, or the timeline will slip and the budget with it.
Questions to ask every ERP partner before you sign
- What exactly is included for data migration, and who cleans the data?
- Which of our requirements are standard, and which need customisation?
- How is each integration priced and tested?
- What training is included, and for which roles?
- What support is included after go-live, and for how long?
- How are changes handled once the project has started?
A budget that holds
The projects that stay on budget are not the ones with the lowest estimate. They are the ones with a written scope, a standard phase one, clean data and fast decisions. For the most common reasons budgets fail, read why ERP projects go over budget. If a project is already over, see how to get it back on track.
MFY Innovatech is an official Odoo partner that writes the scope before building and keeps phase one close to standard. We work with companies in the United States, Kuwait and across the Gulf and Europe.
Frequently asked questions
- How much does an ERP implementation cost?
- There is no single number. Cost depends on how many processes and users are in scope, how many systems must be integrated, how clean your data is and how much you customise. A focused first phase for a small company costs a fraction of a multi-company rollout with manufacturing, payroll and custom integrations.
- Is the software licence the biggest part of an ERP budget?
- Often it is not. Implementation services, data migration, integrations, training and the time of your own staff frequently cost more than the licences, which is why budgets built from a licence quote run over.
- Is cloud ERP cheaper than on-premise?
- Cloud ERP usually costs less to start, because there are no servers to buy and maintain, but it is paid as an ongoing subscription. Compare the total cost over several years, including hosting, support and upgrades, rather than the first-year price.
- How do we compare ERP partner proposals fairly?
- Give every partner the same written scope: processes, users, integrations, data to migrate and reports. Then compare what each proposal includes for data migration, training and post go-live support, not only the headline number.
Keep reading
Related guides
- How Long Does an ERP Implementation Really Take? Timelines by Company SizeSmall companies go live in 2 to 4 months, mid-sized in 4 to 9, large multi-company rollouts in 9 to 18. Phase-by-phase timelines and what makes them slip.
- Your ERP Project Is Over Budget: How to Get It Back on TrackYour ERP implementation is over budget and behind schedule. A practical recovery plan: stop the overrun, re-baseline scope, fix the data and get phase one live.
- Why ERP Projects Go Over Budget, and the Fixed-Scope Approach That Avoids ItWhy most ERP projects run over budget, and the written-scope, phased approach that keeps an Odoo implementation on the number you signed.
Talk to us directly
Prefer a quick conversation?
Message us on WhatsApp or call. You'll reach the team, not a call centre.

