What a 5-Year ERP Rollout Really Costs a 200-Seat Manufacturer
A mid-sized discrete manufacturer — 200 named users across the shop floor, planning, and finance — gets a licence quote of $180,000 for a new ERP platform. Compared to the incumbent system's renewal fee, it looks like a bargain. It isn't a complete number, and treating it as one is the single most common budgeting mistake in an ERP selection process.
The licence fee is one line in a total cost of ownership (TCO) model that has at least four components: the licence itself, implementation services, user training, and recurring annual maintenance across however many years you plan to run the system. Skip any of them and the number you take to your CFO will be wrong by a wide margin.
The four numbers that make up TCO
For this manufacturer, here's what a realistic quote package looks like once implementation partners have scoped the work:
| Cost component | Amount | Notes |
|---|---|---|
| Software licence | $180,000 | Perpetual licence for 200 named users, discrete manufacturing module set |
| Implementation | $340,000 | Data migration, process configuration, integrations to MES and payroll, testing, go-live support |
| Training | $45,000 | Role-based training for three shifts plus a train-the-trainer track |
| Annual maintenance | $96,000/yr | Support, patches, and upgrade rights — roughly 18% of licence value, typical for on-premises ERP |
Add the one-off costs to five years of maintenance and the picture changes considerably:
$180,000 + $340,000 + $45,000 + ($96,000 × 5) = $1,045,000 total cost of ownership, or $209,000 a year on average.
That's nearly six times the headline licence figure. None of the four numbers is padding — every one of them is a cost this manufacturer will actually pay, and every one of them is routinely left out of the first conversation a sales rep has with a prospect. You can run your own numbers with the ERP TCO calculator: swap in your own licence quote, implementation estimate, training budget, and maintenance rate to see your total.
Why implementation costs more than the software
Implementation running to nearly double the licence fee surprises first-time buyers, but it's normal for a manufacturing rollout. The line items usually break down as: data migration from the legacy system (bill of materials, routings, open orders, inventory balances), process configuration for each production line, integration work to the MES and any barcode/scanning hardware already on the floor, and a testing and cutover phase that has to happen without stopping production. A vendor that quotes implementation at less than half the licence price for a multi-shift manufacturer is usually underscoping the integration work, which shows up later as change orders.
Training is not a one-time cost
The $45,000 training line covers the initial rollout. It does not cover the training a manufacturer will need every time it hires a new machine operator, promotes someone into a planning role, or brings on a new shift supervisor. Build an ongoing training allowance — even a modest $8,000-$12,000 a year — into the maintenance side of your budget rather than assuming the initial session covers you for the life of the system.
Maintenance is where TCO actually lives
On a five-year horizon, maintenance ($480,000) is the single largest line in this model — larger than the licence and larger than implementation. That's the part most buyers underweight because it doesn't show up in the initial proposal as a big number; it shows up as a monthly or annual invoice that keeps arriving long after the go-live celebration. If you're comparing two vendors and one has a lower licence price but a higher maintenance percentage, run the five-year total before deciding — the cheaper quote is not always the cheaper system.
What changes at a different company size
Scale the seat count up or down and the licence and training lines move roughly proportionally, but implementation doesn't scale linearly — a 50-seat single-site manufacturer might implement for $120,000-$150,000 rather than a quarter of the 200-seat number, because a meaningful share of implementation cost is fixed project overhead (project management, core configuration, testing infrastructure) that doesn't shrink much with headcount. That's part of why smaller manufacturers often see a higher TCO per seat than larger ones, even with a proportionally smaller licence fee.
Using the model to negotiate
Once you have all four numbers, you have real leverage in vendor conversations. Ask every finalist for the same four figures in writing — licence, implementation, training, and annual maintenance rate — and build the same five-year total for each. A vendor whose implementation partner won't commit to a fixed-fee (or capped time-and-materials) implementation number is telling you something about how confident they are in their own scope. Push for it before you sign, not after the first change order arrives.
What the same model looks like at a 3-year horizon instead of 5
Not every manufacturer plans around a five-year system life. Run the identical inputs over 3 years instead: $180,000 + $340,000 + $45,000 + ($96,000 × 3) = $853,000, averaging $284,333 a year — a much higher average annual cost than the 5-year model's $209,000, because the fixed one-off costs (licence, implementation, training) get spread across fewer years. This is the single biggest reason two companies can look at the same vendor quote and reach different conclusions about affordability: the one planning a longer system life gets a lower effective annual cost from the identical proposal. Before comparing TCO figures between vendors, or between "buy" and "keep the old system" options, make sure everyone in the room is using the same horizon — a 3-year TCO and a 5-year TCO are not comparable numbers.
Common mistakes when building this model
A few errors show up repeatedly when manufacturers build their first TCO model:
- Using a maintenance percentage from a different deployment type. On-premises maintenance typically runs 18-22% of licence value annually; cloud/SaaS subscriptions bundle a different cost structure entirely. Don't apply an on-premises maintenance rate to a cloud proposal or vice versa — compare each deployment model's own realistic total.
- Treating the implementation quote as fixed. Implementation estimates are scoped against an assumed set of integrations and customizations. If your actual requirements turn out heavier during discovery — a second ERP-to-MES integration nobody mentioned in the first meeting, for instance — the number in your model needs to move too, before you present it as final.
- Forgetting to re-run the model after negotiation. Vendors will often move on the licence price during negotiation but hold firm on implementation and maintenance rates. A "10% off" headline can understate or overstate the real TCO impact depending on which line item the discount actually applies to — always re-run the full four-line calculation with the negotiated numbers, not just the discounted headline figure.
Presenting this number to a CFO
A CFO evaluating a $1,045,000 five-year commitment wants to see three things beyond the total: the average annual cost against the current budget for the system being replaced (is $209,000/year more or less than what's already being spent on the incumbent platform plus its own support costs?), a sensitivity check on the maintenance line specifically (since it compounds annually and is the largest single component over five years), and confirmation that the implementation number reflects a written, ideally capped-fee scope rather than an open-ended time-and-materials estimate. Bring the full four-line breakdown, not just the total — a single number invites the question "how did you get there," and having the answer ready is what turns a budget request into an approved one.
Frequently asked questions
Does cloud ERP need a TCO model too, or just on-premises?
Both. Cloud/SaaS pricing folds licence and much of the maintenance cost into a single subscription fee, but implementation and training are still separate, real costs on top of the subscription — a cloud quote of "$9,000/month" is not a complete TCO figure any more than an on-premises licence quote is. Add implementation and training to the multi-year subscription total the same way this guide adds them to the on-premises maintenance figure.
How much should implementation cost relative to the licence?
For a mid-sized manufacturer, implementation running 1.5x to 2x the licence price (as in this guide's example) is typical, not a red flag on its own. Implementation quoted well under the licence price for a multi-shift, multi-integration environment is more often a sign of underscoping than a genuine bargain.
Should maintenance cost be negotiated as a percentage or a fixed dollar amount?
Push for a fixed dollar figure with a capped annual increase (2-4% is a reasonable ask) rather than an open-ended percentage of "then-current licence value," which can drift upward if the vendor later raises list prices — a percentage-of-list-price maintenance clause effectively lets the vendor raise your costs without renegotiating the underlying contract.