Ask three vendors to quote the same ERP brief and you can get numbers that differ by a factor of five. That is not because two of them are dishonest. It is because ERP pricing is driven by things the brief usually does not describe.
Here is what actually moves the number, and what a realistic budget looks like for a company of 50 to 200 people.
The five things that drive ERP cost
1. Number of processes, not number of users
Vendors quote per user because it is easy to compare. Cost is driven by modules and process variants. A 200-person company running one standard sales process is cheaper to implement than a 40-person company running four (direct, distributor, export and government tender), each with different pricing, approval and tax treatment. Count your process variants before you count heads.
2. Data quality in the systems you are leaving
Migration is the most underestimated line in every ERP project. If your item master has duplicate SKUs, inconsistent units of measure and five spellings of the same supplier, someone has to fix that. Doing it during migration costs three to four times what it costs to clean up before. Budget for a data audit in week one, always.
3. Integration count
Every external system (bank, POS, ecommerce storefront, courier, FBR or tax portal, payroll, warehouse scanners) is a separate piece of engineering with its own testing and its own failure modes. Two integrations is a footnote. Eight is a project inside the project.
4. How much you are willing to change
This is the largest single lever you control. Configuring the ERP to your existing process is expensive to build and expensive forever after, because every upgrade has to be re-tested against your customisations. Changing your process to the software costs political capital once. Companies that adopt standard process where it does not hurt them consistently finish faster and cheaper. Often 30-40% cheaper.
5. Who does change management
An ERP nobody uses correctly is a very expensive database. Training, documentation, a nominated internal owner per module and a support period after go-live are not optional extras; they are the difference between adoption and an expensive parallel spreadsheet culture. If a quote has no line for this, the cost has not disappeared. It has moved onto your staff.
What the licence price hides
For a cloud ERP, the sticker price is typically 20-35% of five-year total cost. The rest sits in implementation, migration, integration, training, and the annual maintenance that keeps it current. For a custom-built ERP the shape inverts: higher year one, then roughly 15-20% of build cost per year to maintain, with no per-user escalation as you grow. Which shape suits you depends on headcount trajectory more than anything else. A company planning to double staff should look very hard at per-user pricing over five years.
A realistic budget shape
For a 50-200 person business implementing finance, inventory, sales and purchasing, expect roughly:
- Discovery and process mapping. 5-10% of project cost. Skipping this does not save money; it moves it to change requests.
- Configuration and build. 35-45%.
- Data migration and cleanup: 10-20%, higher if legacy data is poor.
- Integrations: 10-25%, driven almost entirely by count.
- Training, rollout and hypercare. 15-20%.
If a quote is heavily weighted to build and light on migration and training, it is not cheaper. It is incomplete.
Four ways to cut cost without cutting scope
- Phase by process, not by department. Go live with order-to-cash end to end before you touch manufacturing. Departmental phasing creates half-systems that need temporary bridges.
- Clean your data before the project starts. It is the highest-return week of work available to you.
- Freeze customisation for 90 days after go-live. Most requested customisations turn out to be training gaps. The ones that survive 90 days of real use are the ones worth building.
- Nominate one internal owner with authority. Projects without a decision-maker on the client side pay for that in elapsed time, and elapsed time is cost.
The question to ask every vendor
Show me a client of my size, in my industry, and tell me what their total spend was in year one and in year three. Including everything they paid you and everything they paid someone else.
Vendors who cannot answer that have not run enough of these projects to know. Vendors who can will usually tell you something more useful than a price.
Ezitech builds and implements ERP, POS and custom business platforms for clients across 10+ industries. Get a scoped estimate rather than a headline number.
Related: What software actually costs in Pakistan — every Ezitech cost guide in one place.