A $1B company can run well on either tier, and the choice moves the budget more than any other decision in the program. Published tier 2 mid-market ranges and single-region tier 1 ranges overlap between $500,000 and $3M, so revenue alone cannot pick the tier (SysGenPro). At the same company size, a tier 1 product costs about 3x to 10x as much to implement as a tier 2 product. Five conditions decide which tier is right: the number of legal entities, the number of countries with their own statutory reporting, transaction and user volume, the five-year growth path, and industry fit. Revenue is not on that list.
Revenue puts a company in the overlap, it does not pick the tier
Between about $500M and $5B in revenue, both tiers quote real numbers and both can deliver. The published segment ranges prove it. A mid-market tier 2 program for 200 to 1,000 users runs $300,000 to $3M, and a single-region tier 1 program for 1,000 to 3,000 users runs $500,000 to $5M or more (SysGenPro). Those two rows overlap across a wide band. A $1B company sits inside both.
The gap inside that overlap is large. Implementation-only ranges by product, published by ERP Research, put SAP S/4HANA Private Cloud at $500,000 to $5M and Oracle Fusion Cloud ERP at $300,000 to $3M, against Infor CloudSuite at $100,000 to $1M and Epicor Kinetic at $75,000 to $500,000. At the same scope, the tier 1 figure is roughly 3x to 10x the tier 2 figure. The reasons are structural: more configuration surface, higher SI rates, and longer programs, since the SI is 40 to 60% of the bill.
All of these are confidence C ranges from research sites and SIs, not audited program accounts. The full breakdown of what sits inside them lives in the cost pillar; this article takes apart the one decision it leaves open, what an ERP program costs at a company our size. Use the ranges as the outer walls, then let the five conditions below place you.
Five conditions decide the tier, and none of them is revenue
The deciders are structural facts about how the company is organized and where it is going. A CFO can answer all five in an afternoon, and the answers point to a tier more reliably than the revenue line does.
| Condition | Pushes toward tier 1 | Pushes toward tier 2 |
|---|---|---|
| Legal entities on one ledger | More than a handful, consolidating monthly | One or a few, simple consolidation |
| Countries with their own statutory reporting | Several, each with local tax and payroll | One country, or a few with light local rules |
| Transaction and user volume | Will outgrow a tier 2 product within five years | Comfortably inside tier 2 limits for five years |
| Five-year growth path | Acquisitions, new regions, a plan to pass $2B to $5B | Organic growth inside the current footprint |
| Industry fit | Thin, so custom code climbs above 15% | Deep, so custom code stays under 10% |
Industry fit is the condition buyers underweight. Custom code is the single largest cost lever a buyer controls: holding it under 10 to 15% of requirements saves 20 to 40% of implementation cost (ERP Research). A tier 2 product built for your industry meets more requirements out of the box, which keeps custom code low. A general tier 1 suite in a specialized industry can push custom code the other way, which is where a tier 2 program's cost advantage can disappear.
The legal-entity count carries real money too. CRM Layers, an advisory blog, estimates 10 to 20% of implementation cost for each additional legal entity (CRM Layers). It is a weak source, so treat the figure as a direction rather than a rate. The direction is clear: entities and countries multiply the work regardless of tier, and they do it faster on a product that was not built to consolidate many books.
Tier 1 is the right answer for a $1B company in three cases
Tier 1 earns its higher price when the company's structure or trajectory outruns what a tier 2 product was built to carry. Three cases name themselves.
The first is multi-country statutory reporting. A company operating in several countries, each with its own tax rules, local chart of accounts, and payroll, needs a product that treats localizations as standard content rather than custom code. SAP S/4HANA and Oracle Fusion both carry wide localization coverage, which is why global finance tends to land on one of them.
The second is one ledger across more than a handful of legal entities. When a monthly close consolidates many books into one set of numbers, the value is in a single data model rather than a chain of interfaces. Workday Financials fits this case for services firms where finance and HR share one model. Dynamics 365 Finance and Supply Chain fits companies that already run Microsoft across the business and want finance on the same platform.
The third is volume that will outgrow a tier 2 product within the five-year window. A company growing 15% a year passes roughly 2x its current size in five years, and acquisitions move it faster. If current transaction and user volume already sits near a tier 2 product's comfortable ceiling, the program is buying a system it will replace before it has paid for itself.
Which tier 1 product wins among S/4HANA, Oracle Fusion, Dynamics 365, and Workday is a separate decision with its own deciders. The head-to-head sits in the tier 1 comparison (S7), not here. The point for the tier decision is narrower: if any of these three cases holds for a $1B company, the extra cost of tier 1 is buying something the company will use.
Tier 2 is the right answer more often than a $1B company expects
The default assumption that a billion dollars in revenue requires tier 1 is wrong often enough to cost real money. Tier 2 is the right answer when three conditions hold together.
The company operates in one country, or a few with light local rules. The industry fit is deep enough that custom code stays under 10% of requirements, which is where the 20 to 40% saving lives. And the finance team is small, so a product tuned to the industry serves it better than a configurable suite that assumes a large team to run it.
Where those hold, the tier 2 shortlist is strong. IFS Cloud fits asset-heavy companies and utilities, which it treats as a core market. Infor CloudSuite, Epicor Kinetic, and QAD Adaptive ERP fit mid-market manufacturers, each with its own manufacturing-mode strengths. NetSuite, Acumatica, and Sage Intacct fit multi-entity companies where consolidation matters more than a plant floor. Sage X3 fits mid-market process manufacturers and distributors. The choice among them is the tier 2 comparison (S8) and, for manufacturers, the manufacturing fit (E21); this article stops at the tier line.
A $1B single-country company with deep industry fit that buys tier 1 pays 3x to 10x the implementation cost and 15 to 25% of that larger number every year to run it, for scope it does not use. That is the more common mistake at this size, not the reverse.
The year-three failure mode tells you which mistake you made
Both wrong choices look fine at go-live. Both show their cost in year three, and the two failure modes are opposite.
Pick tier 2 when the company needed tier 1, and the system runs out of room. Suppose a $1B distributor picks a tier 2 product, saves $2M against the tier 1 quote, and goes live cleanly. Then it acquires two companies abroad. Now it needs local statutory reporting in three countries and one consolidated ledger across five entities, and the product it chose was built for one country and simple consolidation. Custom code climbs to bridge the gap, integrations multiply at $10,000 to $50,000 each, and by year three the company is scoping a replacement. The $2M saved at go-live is spent several times over, and a program rescue runs 30 to 50% of the original budget on its own (Deliberate Directions, writing about NetSuite rescues).
Pick tier 1 when tier 2 would have served, and the system is too big for the company. Suppose a $1B single-country manufacturer buys a tier 1 suite for a $6M implementation when a tier 2 product would have cost $2M. It uses perhaps 30% of the configuration surface. The run cost, at 15 to 25% of implementation, is $900,000 to $1.5M a year against $300,000 to $500,000 for the tier 2 program it passed over (Ecosire). By year three the gap in run cost alone has matched the original overspend, and it keeps compounding every year the system runs.
The run cost is why the tier 1 overspend is the quieter, more expensive mistake. The outgrow case announces itself with a replacement program. The overkill case never announces itself; it just bills a larger number every year for capability no one uses.