What an ERP program really costs

An ERP program costs 1x to 3x your first-year software fee to implement, whichever vendor you pick, and 3x to 5x the software cost over five years before run cost is added. Those two ratios, from ERP Research, an independent research firm, turn a vendor quote into a program budget in two lines of arithmetic. Applied to published prices, they put a tier 2 program for a 200 to 1,000 user company at $300,000 to $3M and a tier 1 program for a global company with 10,000 or more employees at $20M to $50M or more. The ranges are wide because the biggest cost decisions (vendor tier, scope, custom code, number of sites) are yours, not the vendor's. This article shows the arithmetic so you can rebuild any number an SI puts in front of you.

The two ratios that build every ERP budget

Every ERP budget rests on two multiples. The first is implementation to first-year software: ERP Research puts services at 1x to 3x the first-year license or subscription. The second is five-year total to software: the same source puts it at 3x to 5x, counting software and implementation only.

If a vendor quotes $1M a year in subscription, expect $1M to $3M to get live. Do not expect $3M to $5M over five years, because five years of subscription alone is $5M. The 3x to 5x rule works against a one-time license fee, not a recurring subscription. Under a subscription the five-year total runs higher, and the arithmetic section shows by how much, before you add the internal costs the vendor never sees.

The multiples move for reasons you can name. A company that keeps standard processes, has clean data, and runs one country lands near 1x. A company with 10 integrations, five legal entities, three languages, and a plant floor lands near 3x. CRM Layers, an advisory blog, uses a flat 1:3 rule (three service dollars per software dollar) and warns that any quote with software above 60% of the total is underfunded on services. That warning holds. A low services number in a proposal is a sign the SI has not scoped the work, not a sign you found a bargain.

The table below collects the cost ratios used in this article. Each one is published by a research firm, an SI, or a cost benchmarking site, and each is marked with a confidence grade. B means two or more independent sources agree. C means one source, or sources that do not disclose their sample. None of these ratios comes from audited program accounts, so use them to test a quote, not to replace one.

The published ranges by segment and tier

The published ranges below come from four sources, none of which is a vendor. All four are advisory or research sites that do not disclose their sample, so every row is confidence C. Treat them as the outer walls of a budget, not the budget. The arithmetic section further down shows how to narrow a row to your own company using the quote in front of you.

Two things stand out. First, the mid-market tier 2 rows and the single-region tier 1 row overlap between $500,000 and $3M. A $1B company can land in either tier, which is why vendor tier is the first budget decision, not the last (we take that choice apart in E8).

Second, the top row and the bottom row differ by two orders of magnitude. Company size explains part of that gap. Scope explains more. A global tier 1 program carries multiple legal entities, local tax and payroll rules, dual-run across regions, and a PMO that runs for three years.

Tier 1 costs 3x to 10x as much as tier 2 to implement at the same size

The clearest evidence that tier matters comes from implementation-only ranges by product. ERP Research publishes a vendor table that excludes license and subscription fees. The tier 1 rows run far above the tier 2 rows, and the reasons are structural, not a sign that one set of vendors overcharges.

The Dynamics 365 row needs a caveat. ERP Research publishes $50,000 to $500,000 for Dynamics 365 without separating Dynamics 365 Finance and Supply Chain from Business Central. The $50,000 floor belongs to Business Central, which lists at $70 to $80 a user a month and competes with NetSuite and Acumatica.

The $500,000 ceiling understates a multi-country Dynamics 365 Finance and Supply Chain program. That product lists at about $180 a user a month and competes with S/4HANA and Oracle Fusion. Read that row as low confidence for tier 1. For a Dynamics 365 Finance and Supply Chain program at enterprise scale, the Oracle Fusion row is the nearer guide.

The structural reasons for the gap are four. Tier 1 products carry more configuration surface, so design takes longer. Tier 1 SIs usually charge more per hour, and the SI is 40 to 60% of the bill. Tier 1 buyers tend to be larger and more complex, which inflates the range even when the product is not the cause. And tier 1 programs run longer, so the PMO, the dual-run, and the internal team cost more months.

None of this makes tier 2 the right answer by default. A $2B process manufacturer with plants in eight countries will find the IFS Cloud or Infor CloudSuite ceiling in that table too low. It will pay tier 1 money for a tier 2 product. A $400M distributor that buys S/4HANA will pay for configuration surface it never uses.

The arithmetic a CFO can rebuild from a quote

The formula has three parts: annual software cost, the implementation multiple, and the run cost over the years after go-live. Written out for a five-year horizon, it is:

Five-year cost = 5S + mS + 4r(mS)

where S is the annual subscription or license plus maintenance, m is the implementation multiple (1 to 3), and r is the annual run cost as a share of implementation (0.15 to 0.25). The 4 covers years two through five, since support in the first weeks after go-live is usually inside the SI's implementation fee.

Here is a tier 2 example at published list prices. ERP Research lists Oracle NetSuite from about $999 a month plus $99 a user a month. For 300 users, that is 300 x $99 x 12 = $356,400, plus $11,988 base, or about $368,000 a year before discount.

Implementation at 1x to 3x is $368,000 to $1.1M. Five years of subscription is $1.84M. Run cost for years two through five is 4 x (15 to 25%) x implementation, or $221,000 to $1.1M. The five-year total is $2.4M to $4.1M, which is 6.6x to 11x the first-year fee.

That result is above the 3x to 5x rule for two reasons. Five years of subscription alone is 5x the first-year fee, so the rule only holds against a one-time license. And the rule counts software and implementation only; run cost adds another 0.6x to 3x of the first-year fee. Any five-year number an SI shows you that sits at 3x to 5x of a subscription fee has left out the people who keep the system running.

Here is a tier 1 example at list price. Dynamics 365 Finance lists at about $180 a user a month (ERP Research). For 1,500 full users that is 1,500 x $180 x 12 = $3.24M a year.

Implementation at 1x to 3x is $3.24M to $9.72M. Five years of subscription is $16.2M. Run cost for years two through five is 4 x (15 to 25%) x implementation, or $1.94M to $9.72M. The five-year total at list is $21.4M to $35.6M, which lands inside the published $20M to $50M global tier 1 range.

List is the ceiling. Tier 1 contracts mix full users with team and self-service users at a fraction of the full price. ERP Research notes that every figure it lists varies by edition, region, and negotiation. Because every line in the formula scales with S, a 40% discount on the subscription cuts the five-year total by about 40% as well, to $12.8M to $21.4M.

Three notes on using this. First, S/4HANA and Oracle Fusion do not publish a per-user list price; ERP Research shows S/4HANA as custom at roughly $150,000 a year and up. Use your actual quote.

Second, if you are on perpetual licenses with maintenance rather than subscription, S is the annual maintenance bill plus the amortized license. For SAP, maintenance is about 22% of license value, per ERP Research. Third, the formula leaves out your own people. The internal team, backfill for business leads, and change management typically add 15 to 30% on top of the external spend, per ERP Research's hidden-cost estimate. E7 lists those items one by one.

Six line items decide whether you land low or high in the range

The difference between the low and high ends of any row in the segment table comes from a short list of decisions. Six items account for most of the variance in the published sources, and five of them are decided before the SI contract is signed.

Custom code is the largest. ERP Research's finding that holding custom code under 10 to 15% of requirements saves 20 to 40% of implementation cost is consistent across tiers. Data cleanup is second. Costbench puts data migration and cleansing at 10 to 15% of the project budget, and the cleanup work usually falls on your staff, not the SI's.

Integrations are third, at $10,000 to $50,000 each per ERP Research, so a company with 12 interfaces adds $120,000 to $600,000 before any of them is tested. Dual-run is fourth: 12 to 24 months of paying for both the old and new systems, per Costbench. The external PMO is fifth, at $5,000 to $20,000 a month, which over a 36-month tier 1 program is $180,000 to $720,000. Program rescue is sixth and the one nobody budgets. Deliberate Directions, writing about NetSuite rescues, puts it at 30 to 50% of the original budget.

An illustration shows how fast one item moves the total. Suppose a $500M manufacturer with five plants budgets $9M for a tier 1 program and plans a six-month dual-run. During dual-run it pays three things at once. The new subscription, say $1M a year, is $83,000 a month. Maintenance on the old system, at SAP's 22% of license value on a $2M license base, is $440,000 a year or $37,000 a month. An external PMO at the top of ERP Research's range is $20,000 a month.

That is $140,000 a month, or $840,000 for six months, and it is in the budget. Now suppose cutover slips and dual-run runs 18 months instead of six. The same $140,000 a month becomes $2.52M. The overrun is $1.68M, or 19% of the $9M budget, before the SI has sent a single change order and before the internal team's extra year is counted.

Nothing in that example happened to any company. It is arithmetic on published figures, and it is why dual-run length deserves its own line in the approval paper.

E7 takes each of these six apart with ranges and a checklist. For the approval decision, the point is simpler. If your SI's number sits at the low end of the segment range, ask which of these six items it excludes.

Run cost adds 60 to 100% of the implementation figure over years two through five

Most published ranges stop at go-live. The run cost is where a CFO gets surprised in year two. Ecosire, an SI, puts ongoing cost at 15 to 22% of initial implementation a year in its text, and its own size table implies 20 to 40%. We use 15 to 25% as the working range. On a $3M implementation, that is $450,000 to $750,000 a year, or $1.8M to $3M over years two through five.

Some of that is the SI's support retainer, which Ecosire puts at $12,000 to $60,000 a year for a mid-market company. More of it is your own ERP team. An internal ERP administrator costs $60,000 to $120,000 a year in the same source. A tier 1 program at enterprise scale needs a team of them plus a functional lead for each major process.

Vendor upgrades are the third piece. Cloud ERP removes the big upgrade project. But Costbench notes that platform usage charges (SAP BTP is the example it uses) are metered with no cap in standard contracts, so the bill grows with use.

The five-year total matters more than the implementation number for one reason. The board remembers the implementation number and judges the program against it. If you present $3M at approval and the five-year cost is $8M, the program looks like it failed even if every invoice came in on budget. E11 gives the full five-year TCO model for the board; the arithmetic section above is enough to build the headline.

Timelines are a cost line, not a schedule

Every month of a program has a fixed cost: the PMO, the internal team, the dual-run, and the SI's core team. That makes the timeline a budget input. Published tier 1 timelines run 12 to 36 months (ERP Research's vendor table shows 12 to 24 months for S/4HANA Private Cloud and 8 to 18 months for Oracle Fusion). In programs we have advised, a tier 1 program needs 36 months from decision to go-live, counting selection, contracting, design, build, test, and cutover. The 12 month end of the published range belongs to a single site in one country with standard processes.

Tier 2 timelines are shorter. SysGenPro, an SI, puts mid-market tier 2 at 6 to 18 months. ERP Research's vendor table agrees: Epicor Kinetic at 4 to 12 months, Infor CloudSuite and IFS Cloud at 6 to 15 months, NetSuite at 3 to 6 months. Energy and utilities programs run 6 to 24 months per ERP Research, with the long end for investor-owned utilities that carry regulatory reporting and asset management scope.

Delay is common enough to budget. A survey reported by ERP Today found 31% of ERP implementations took longer than expected and 12% had significant delays. The monthly burn can be derived from the ranges above. A global tier 1 program at $20M to $50M over 36 months runs $0.56M to $1.4M a month ($20M / 36 and $50M / 36). A mid-market tier 2 program at $300,000 to $3M runs $50,000 a month at the low end ($300,000 over 6 months) and $170,000 a month at the high end ($3M over 18 months).

Not all of that continues through a slip; the SI's build team usually rolls off. What continues is the PMO ($5,000 to $20,000 a month), the dual-run, and the internal team. In the manufacturer illustration above those three came to about $140,000 a month, so a six-month slip is $840,000 before any SI fees. Put a schedule contingency in the budget, not just a cost contingency.

Where each tier is the right answer on cost

The tables above favor tier 2 on price at every size where both tiers compete. That does not make tier 2 the answer. The conditions matter, and both tiers earn their place.

Tier 1 is the right answer on cost in three cases. The company runs multiple countries with local statutory requirements. It needs one ledger across more than a handful of legal entities. Or its transaction and user volume will outgrow a tier 2 product within the five-year window.

In those cases a tier 2 program that saves $2M at go-live and needs replacing in year six costs more than the tier 1 program would have. S/4HANA and Oracle Fusion carry that scale. Dynamics 365 Finance and Supply Chain carries it for companies that already run Microsoft everywhere else, and Workday Financials carries it for services firms where HR and finance need one data model.

Tier 2 is the right answer on cost when the company is one country or a few, when the industry fit is deep enough that custom code stays under 10%, and when the finance team is small. IFS Cloud fits asset-heavy companies and utilities; ERP Today notes that IFS treats energy and utilities as a core market.

Infor CloudSuite Industrial, Epicor Kinetic, QAD Adaptive ERP, SYSPRO, Plex, and DELMIAWorks are the mid-market manufacturing shortlist, and Plex is built around the plant floor. NetSuite, Acumatica, and Sage Intacct fit multi-entity companies under about 500 users where consolidation matters more than manufacturing. Sage X3 fits mid-market process manufacturers and distributors. E21 and S8 cover those choices in detail.

The cost mistake to guard against is not picking the wrong tier. It is picking tier 1 for a company that will use 30% of it, then paying tier 1 implementation and run costs for five years on that 30%.