ERP Quote (ERPQ): How to Read One and What a Fair Price Includes
An ERP quote, sometimes shortened to ERPQ, is a priced proposal for implementing, hosting and supporting your ERP system. A fair one splits software, configuration, data migration, training and ongoing support into separate lines so you can compare bids properly.
Most buyers get burned the same way. They pick the cheapest number on the page, sign, then meet a steady drip of change requests for the work the quote quietly left out. The point of this guide is simple. Read the quote like a finance person, find the gaps before you sign, and know what a sensible price actually covers.
Key Takeaways
- An ERP quote should itemise five things: software or subscription, configuration, data migration, training and ongoing support.
- A low headline figure often means missing scope, so the gap turns up later as billed change requests.
- Always compare the three-year total cost, not the upfront number, because cloud and on-premise shift cost between setup and monthly fees.
- Data migration and testing are the lines most quotes underprice, and they are the ones that sink go-live dates.
- Ask for a banded estimate first, then a fixed scope for phase one, so the price has real work behind it.
- A quote with no running support cost is incomplete, not generous.
What a good ERP quote should contain
A real ERP quote answers six questions before you have to ask them. What software am I buying and on what licensing basis. Who configures it and how many days of work that takes. How does my current data get in, cleaned and checked. Who trains my team and for how long. What happens after go-live and what it costs each month. And what sits outside this price.
If a proposal skips any of those, it is not finished. You are reading an estimate dressed as a quote.
Here is the structure we expect every ERPQ to follow, whatever supplier produces it.
| Line item | What it covers | Why it matters |
|—|—|—|
| Software / subscription | Odoo licences or Odoo.sh plan, per user per month | Sets your recurring base cost before any work |
| Configuration | Setting up modules, workflows, roles, reports | The bulk of a first-phase fee |
| Data migration | Extract, clean, import and verify your records | The line most often underpriced |
| Training | Hands-on sessions for each team | Drives whether people actually use the system |
| Testing and go-live | User acceptance testing, cutover, early support | Protects your launch date |
| Ongoing support / hosting | Monthly retainer and hosting | The real cost of living with the system |
When each line carries a number and a short note, you can hold two quotes side by side and see where they differ. When they are bundled into one figure called “implementation”, you cannot.
The line items that make or break the price
Three lines decide whether a quote is honest.
The first is data migration. Moving ten years of customers, suppliers, stock and open transactions out of spreadsheets or a legacy ERP is slow, fiddly work. A quote that prices it at a day or two has either seen a very clean dataset or has guessed. Ask what happens if your data needs more cleaning than expected, and get that answer in writing.
The second is configuration days. This is where a cheap quote hides. Ten days of setup looks great next to twenty, right up to the point where the ten-day supplier starts raising change requests in week three. Ask what the day count assumes about your processes. If the answer is vague, the number is too.
The third is training. People do not adopt a system they were shown once on a slide. Count the training days, check who they are for, and ask whether follow-up sessions after go-live are included or extra.
Cloud or on-premise: how hosting changes the quote
Hosting is the single biggest reason two quotes for the same Odoo project look different. It moves cost around rather than removing it.
Cloud hosting on Odoo.sh gives you a lower upfront figure. You pay a monthly platform and subscription fee, and the supplier manages backups, updates and uptime. Your setup line shrinks, and your recurring line grows. If you want to see how that model reads on a real proposal, explore Odoo.sh cloud.
On-premise flips it. You carry the server, the setup and the maintenance, so the one-off number climbs and the monthly number falls. Teams with existing infrastructure, strict data residency rules or heavy customisation often prefer it. The detail sits on our explore on-premise Odoo page.
The honest comparison is the three-year total. Add the setup cost to thirty-six months of running cost for each option. The headline figure lies. The three-year total tells the truth.
Hidden costs that turn a cheap quote expensive
Some costs live in the gaps between lines. Watch for these.
Change requests. If the quote scopes a narrow set of workflows, anything beyond it bills by the day. Ask what counts as a change and what the day rate is.
Integrations. Payment gateways, e-commerce storefronts, payroll and bank feeds rarely appear in a basic quote. If you run them today, you will need them from day one, so get them priced now.
Custom development. Bespoke reports or modules sit outside standard configuration. A fair supplier flags these early and quotes them separately.
Second-phase work. The “first 100 days then beyond” split is deliberate. Phase one gets you live on the core. Phase two adds the refinements once real usage shows what matters. Ask what phase two is likely to contain so the number does not surprise you in month four.
How to compare two ERP quotes fairly
Put both quotes in the same table and line them up. If one has six lines and the other has three, the three-line quote is missing work, not saving you money. Fill the gaps by asking what each supplier assumes about the lines they left out.
Then normalise the comparison:
1. Match the scope. Make sure both cover the same modules, user count and data volume.
2. Add the three-year total for each, setup plus thirty-six months of support and hosting.
3. Read the exclusions. The “out of scope” section tells you more than the price does.
4. Check the payment terms. A twelve-month payment plan changes cash flow even when the total is identical.
Only after those four steps does the price mean anything. A quote you cannot compare is a quote you cannot trust. If you want a worked example of how our figures are built, view pricing.
What we include in an ERPQ at ERP Solutions
As a certified Odoo partner working with South African and UK mid-market teams, we quote the full picture or we do not quote at all. Every ERPQ we send names the software basis, the configuration days, the data migration approach, the training plan, the go-live support and the monthly running cost. Exclusions sit in their own section so nothing hides.
We also band the estimate before we fix it. You get a realistic range early, based on your user count and modules, then a fixed scope for phase one once we have looked at your data and processes. That way the number is anchored to work we have actually sized, rather than a guess we both pay for later.
FAQ
What is an ERP quote (ERPQ)?
A priced proposal that sets out the cost to license, configure, migrate, train on and support an ERP system. A fair one itemises each part so you can see what you are paying for.
Why do two ERP quotes for the same project differ so much?
Usually because they count different work. One includes data migration, testing and training. The other quotes software and a few setup days, then bills the rest as change requests later.
Should an ERP quote include ongoing support?
Yes. Ask for the monthly support and hosting figure alongside the one-off setup cost. A quote with no running cost is missing it, not giving it away.
How much does an Odoo implementation cost in South Africa or the UK?
It depends on user count, modules and data complexity. Ask for a banded estimate first, then a fixed scope for phase one so the number has something real behind it.
Cloud or on-premise, which gives a lower ERP quote?
Cloud lowers your upfront number and moves cost into a monthly fee. On-premise raises the setup figure and cuts the recurring one. Compare the three-year total.
Get a quote you can actually read
If you want an ERP quote that itemises every line, bands the estimate honestly and fixes the scope for phase one, we can build one for your business. Book a discovery call and we will size the work against your data, your user count and your real processes, then send you a figure with the work behind it.