In 2007 the tier-one ERP vendors discovered the mid-market. SAP had packaged pre-configured versions of its suite for smaller buyers and, in September, launched Business ByDesign specifically for companies that would never sign an eight-figure licence. Oracle ran a parallel programme of fixed-scope, partner-delivered implementations aimed at the same segment. Both pitches rested on the same promise: buy the enterprise platform now, at a manageable entry price, and grow into it. A great many mid-market ERP selections were decided on that sentence. Most of the companies that believed it are still paying for the decision.
Why the Tier-One Pitch Was So Persuasive
The arguments were not dishonest, and they were hard to argue against in a boardroom. Nobody gets fired for buying the market leader. For a CFO signing the largest technology cheque of their tenure, vendor reputation is risk insurance. The functional depth was real. Tier-one products genuinely handled multi-entity consolidation, complex costing, international tax and regulated industry requirements that smaller products did not. Growth ambition is flattering. Every mid-market board believes it will be an enterprise within five years. Buying the enterprise system is an expression of that belief, and voting against it feels like voting against growth. Partners made the numbers work. Pre-configured industry templates and fixed-price implementations put a credible-looking figure on the first page of the proposal. The flaw was never in the software. It was in the fact that the entry price described the entry, and nothing else.
What Tier One Actually Cost a Mid-Sized Company
The licence was consistently the smallest line item over any realistic horizon.
- Implementation services typically ran one to three times the licence value, and considerably more where process redesign or data migration proved harder than scoped.
- Annual maintenance was calculated on list price rather than the discounted price paid, compounding for as long as the system ran.
- Specialist internal headcount was required permanently. Tier-one platforms do not administer themselves, and the skills command a premium in the labour market.
- Upgrade projects arrived every few years as substantial programmes rather than routine maintenance, particularly where the system had been modified.
- Modification debt was the quiet killer: every customisation made every subsequent upgrade more expensive and more fragile. A mid-market company with a forty-person finance function ended up carrying a cost structure designed for a multinational, without the transaction volume to spread it across.
The Utilisation Problem
The recurring finding in ERP research, then and now, is that organizations use a fraction of what they licence. Modules purchased in the original deal to secure a discount are never implemented. Capability that justified the vendor selection is switched off because the business cannot support the process discipline it assumes. This is the clearest signal of a right-sizing failure. If your justification for tier one rests on functionality your organization will not operate, you have purchased an option you will never exercise and will pay maintenance on indefinitely. The honest test is uncomfortable but simple: which specific tier-one capabilities will be in production use within eighteen months, operated by named people, and what is the cost of the alternative that does not include them?
2007's Real Signal Was Coming From Somewhere Else
While the enterprise vendors were packaging themselves downward, the structural answer to the mid-market problem was going public. NetSuite's December 2007 IPO raised roughly $161 million and valued the company at around $1.55 billion — a striking outcome for a business selling an integrated ERP, CRM and e-commerce suite entirely as a subscription service. Demand was strong enough that the expected price range was revised upward before pricing, and the shares traded sharply higher on debut. The significance was not the valuation. It was the proof that mid-sized companies would run their general ledger on infrastructure they did not own, administered by people they did not employ. That proposition had been considered unserious by enterprise buyers five years earlier. SAP's Business ByDesign, launched the same year, was aimed at the identical insight. It underperformed commercially for a decade, but the strategy was right: the mid-market needed a product designed for it, not a shrunken version of something else.
| Cost area | Include in the comparison |
|---|---|
| Access to software | Licence or subscription and renewal terms |
| Initial delivery | Implementation, process redesign and data migration |
| Operating capacity | Named internal specialists and ongoing support |
| Change over time | Upgrades, modifications and integrations |
| Exit | Extraction rights, documentation and portability |
Qualitative summary of this article's source text, not a measured outcome or performance estimate.
A Better Right-Sizing Framework
- Start from process complexity, not company size. A $40 million manufacturer with regulated batch traceability may genuinely need tier-one depth. A $400 million distributor with simple flows may not.
- Count your true differentiators. Most organizations have three to five processes that create competitive advantage. Everything else should run on standard functionality, unmodified.
- Model ten years, all-in. Licence or subscription, implementation, internal headcount, upgrades, integrations and the cost of the modifications you will inevitably request.
- Weight time-to-value heavily. A system delivering benefit in nine months materially outperforms a theoretically superior system delivering in thirty, and the shorter project is far more likely to finish at all.
- Assess your own absorption capacity honestly. Can your team sustain a two-year programme alongside their day jobs? The answer determines feasible scope more than any functional requirement.
- Plan the exit before signing. Data extraction rights, documentation ownership and integration portability are cheap to negotiate up front and impossible to obtain later.
Where Mid-Market Buyers Still Go Wrong
The vendors changed; the mistakes did not. Requirements are still gathered as feature checklists, which reward the product with the longest feature list rather than the best fit. Demos are still evaluated on polish rather than on how the vendor handles your three ugliest edge cases. Implementation partners are still selected on day rate rather than on named consultants with relevant deployments. And subscription pricing has made the entry cost lower while making the ten-year cost harder to see — uplifts, user-tier creep and module expansion do not appear in the first-year business case. The question that separates a good mid-market ERP selection from an expensive one has not changed since 2007: are we buying capability we will actually operate, or are we buying reassurance?
Common Questions
What is the difference between tier one and tier two ERP?
Tier one refers to the large enterprise suites with the broadest functional and international coverage. Tier two covers products designed for mid-sized organizations, with narrower scope, faster implementation and lower total cost. The boundary is commercial rather than technical, and it has blurred considerably with cloud delivery.
When is tier one the right choice for a mid-market company?
When genuine complexity demands it: multi-country statutory reporting, regulated industry requirements, complex manufacturing costing, or an acquisition strategy requiring rapid entity consolidation. Anticipated growth alone is not a sufficient reason.
How much ERP functionality do companies actually use?
Consistently less than they license. Modules bought for discount leverage frequently go unimplemented, and advanced capability is often disabled because the organization cannot sustain the process discipline it requires.
What is the most reliable predictor of ERP project success?
Not the product. Executive ownership, data quality, disciplined scope and a business-led project team predict outcomes far better than vendor selection does.
Mid-Market ERP Fit Review — Outpace assesses whether your process complexity actually justifies a tier-one platform, models ten-year total cost across shortlisted options, and tests your organization's capacity to deliver the implementation. Independent of any vendor or reseller.