Budget the integration, not the license. The license is the cheap part. Here is where ERP money actually goes — and why the number your vendor quoted you is roughly 30 to 40 percent of the real figure.

The ERP sales cycle is one of the most information-asymmetric commercial transactions a mid-market company will ever enter. The vendor has implemented this system hundreds of times. They know exactly what it costs, where implementations fail, what the integrations require, and how long change management actually takes. The buyer is doing this for the first time.

The vendor’s incentive is to get the contract signed. The buyer’s incentive is to get a good system at a fair price. These incentives produce a predictable outcome: the buyer is shown a number that reflects the vendor’s cost, not the implementation’s cost.

This article is an attempt to correct that information asymmetry with real numbers.

The Standard Vendor Quote

A mid-market ERP vendor quote for a manufacturing or distribution company with 50–150 employees typically includes:

  • License/subscription fees: $3,000–$8,000/month, or $80K–$200K for perpetual license
  • Implementation services (vendor-quoted): $50K–$150K
  • Training: $10K–$25K
  • Total as quoted: $150K–$450K over three years

This is the number that appears in the executive summary, the board presentation, and the CFO’s budget request.

Here is what the number does not include.

What the Quote Leaves Out

Data migration. Every ERP implementation requires moving data from existing systems — accounting software, spreadsheets, legacy ERP, or all three — into the new system. Clean, normalized, validated data migration is typically the most labor-intensive part of an implementation. Vendor quotes routinely scope data migration as “customer responsibility” or include a fixed fee that assumes data is already clean.

It is never clean.

Budget $30K–$80K for data audit, cleanup, normalization, and migration validation on a typical mid-market implementation. If you have been operating on spreadsheets for more than five years, budget higher.

Integration development. Modern businesses run on multiple systems. Your ERP will need to communicate with your CRM, your e-commerce platform, your 3PL’s warehouse management system, your payroll processor, and your bank. Vendor quotes typically scope “standard integrations” — which means the API exists and the connection can theoretically be built.

“Can theoretically be built” and “has been built, tested, and validated for your specific use case” are separated by 200 to 600 hours of development work that belongs to you, not the vendor.

Budget $40K–$120K for integration development, depending on your system landscape. If you have custom legacy systems, budget more.

Internal labor. Every implementation requires significant time from your own team: the operations manager who knows how your processes actually work, the warehouse supervisor who needs to validate pick-and-pack logic, the controller who needs to verify that the financial period setup matches your actual close process.

This labor has a cost. It is not in the vendor quote because it does not appear in the vendor’s invoice. But your operations manager spending 40% of their time on an ERP implementation for six months is a cost. A real one.

Budget the equivalent of one to two full-time employees for six months at your average management labor rate.

Change management. Software does not change behavior. Training + reinforcement + process redesign changes behavior. An ERP implementation that fails to invest in change management produces a situation where expensive new software is used to replicate the habits of the old system.

Budget 15–20% of total implementation cost for change management, process documentation, and post-go-live reinforcement.

Post-go-live support. The vendor implementation team leaves when the system goes live. The system is not finished. There will be configurations that need adjustment, reports that need to be built, integrations that need tuning, and users who need additional support.

The first six months post-go-live require dedicated internal or contracted support. Budget $3K–$8K/month.

The Honest Number

Take a typical $250K vendor quote for a mid-market ERP implementation. Add:

  • Data migration: $50K
  • Integration development: $80K
  • Internal labor: $120K (2 FTE-equivalents × 6 months)
  • Change management: $50K (20% of $250K)
  • Post-go-live support: $36K (6 months × $6K/month)

Adjusted total: $586K.

The vendor told you $250K. The real number is $586K. This is not unusual. It is typical.

How to Not Get Surprised

1. Require the vendor to scope integration specifically. Not “standard integrations available.” Specific integrations, with specific system versions, specific data models, and specific estimated hours. If they won’t scope this way, it is because they do not want you to know what it costs.

2. Conduct an independent data audit before signing. Hire someone — a consultant, a contractor, an intern with a data background — to audit your existing data before vendor selection. You need to know your migration complexity before you are contractually committed to a vendor’s implementation scope.

3. Get a third-party implementation estimate. Before signing with any ERP vendor, get an implementation estimate from a third-party integrator who works with that vendor’s product but does not have a financial relationship with the vendor. The number will be different from the vendor’s estimate. The gap is your risk exposure.

4. Include internal labor in your ROI model. Any ROI analysis that does not account for the internal labor cost of implementation is a document designed to justify a decision, not analyze it.

5. Negotiate change management into the statement of work. Most vendors will agree to include structured change management if you ask for it and are willing to pay for it. Most buyers do not ask.

The Underlying Problem

The ERP vendor model is not designed to produce implementation success. It is designed to produce signed contracts. Post-implementation outcomes — user adoption, process improvement, actual ROI — are the customer’s problem after the contract is signed.

This is not a moral critique. It is a structural observation. The vendor’s incentives are not aligned with your outcomes. Understanding that is the first and most important step toward protecting yourself in the process.