The CFO across the table
A former Oracle NetSuite customer posted this on r/ERP in May 2025:
“4 year anniversary since we got royally screwed by oracle NS during their year end ‘discounts’. 85% off the software and our ’ free’ implementation… Well 250k with NS later and a reimplementation of 130k to our new ERP later I am here to tell you. Don’t DO IT. NOTHING IS FOR FREE. […] You don’t own your data — migration to our new ERP sucked. […] they lock you in for 5 years so be prepared for a heavy lawsuit if you want out.”
Username Jaded_Strategy_3585. Posted at the four-year anniversary of the original NS signing. The ”… Well 250k” punctuation is the original poster’s; the bracketed […] marks two short repetitions we elided. The quote otherwise verbatim — archived for permanence at the Wayback Machine if you want to confirm.
$380,000 of damage on one vendor decision. Real customer, real numbers, public warning. Lowercase k preserved.
We’ve never met Jaded_Strategy_3585. We’ve watched the same situation dozens of times across decades of ERP transformations at top-tier consulting companies. The pattern is consistent enough that we can usually predict which category of cost has surfaced before the CFO names it. Data ownership constraints. Year-end discount math that doesn’t survive past the implementation. Multi-year lock-in clauses that make exit cost a multiple of the original deal. The 4-year-anniversary post is the documented version of what shows up in CFO offices regularly — and what very few buyers ask about during selection.
This piece is about what those CFOs discover in Year 3. Not the salesperson’s fault. Not the implementation partner’s fault, exactly. A structural pattern. Three cost categories that surface predictably, plus one contract clause that activates continuously, plus an economic model that explains why none of them get quoted upfront.
Three categories you’ll pay for that weren’t quoted
The proposal is honest about one thing: the cost of installing the software you bought.
License fees through Year 1. Implementation services scoped to a specific Statement of Work. Maybe a discount applied to the first-year subscription. The numbers add up cleanly. The implementation partner’s project plan even has a Gantt chart.
What the disclosed cost does not cover, but what running the system actually requires:
Master data cleanup
Customer records in the legacy system carry inconsistencies from years of operational practice. Address formats that vary across regions. Payment terms that map awkwardly to the new system’s options. Vendor records duplicated when staff turnover left naming conventions inconsistent. The implementation partner scopes data migration (moving the records) but not data cleanup (making them usable in the new system). Cleanup is the buyer’s responsibility by convention. The buyer’s team usually doesn’t know what good data hygiene looks like in the new system, which is why master data cleanup typically extends six months past go-live and consumes finance-team capacity nobody planned for.
Integration-layer rebuild
Year 1, you connect the ERP to Salesforce. The implementation partner scopes “standard Salesforce integration”: the vendor’s documented connector, configured per documentation. Year 2, you bring on a new billing platform. The standard connector doesn’t handle it. The implementation partner proposes scoping the additional integration work as a change order, sized to data volume and the destination platform. Year 3, you swap your subscription billing platform for a different one because the first one’s pricing tripled at renewal. Another scope. By the time the dust settles, you’ve rebuilt the integration layer two or three times. The system that was supposed to be the system-of-record has become one of several systems-of-record that need orchestration.
Intercompany rules
Year 2, you acquire a small competitor. Congratulations. Now you have two entities, different fiscal calendars, different chart-of-accounts conventions, different revenue-recognition policies. The implementation partner who built your Year-1 system did not scope multi-entity. The COA you set up was single-entity. Now you remap. Now you build intercompany elimination rules. Now you decide whether to consolidate at the GL level or at the management-reporting layer. The implementation partner returns with a proposal to extend the original SOW. The amount on the extension often approaches the original SOW’s headline number, or exceeds it. The implementation cost in Year 2 turns out to be larger than the implementation cost in Year 1.
The supplemental hourly rate
Section 14 of the contract. Maybe section 19, depending on the vendor. Specifies what happens when the buyer’s needs exceed the disclosed monthly plan. The supplemental rate isn’t hidden. It’s printed. What’s harder to anticipate is the surface area for “out-of-scope” once your team is actively using the system. Three categories of supplemental work typically: out-of-scope configuration, custom development, and training-session-beyond-included-onboarding. Each at a different rate. Each adding to a category of cost the disclosed monthly plan didn’t surface. Year 1 the team draws on supplemental hours occasionally — onboarding consumes most of the included capacity. Year 3 the surface area of “out-of-scope” has compounded across integration boundaries, intercompany rules, and the periodic reconfiguration that growth requires. The hours category by Year 3 is qualitatively different from Year 1.
Year 1
Quoted in proposal
- License fees
- Implementation SOW
- Supplemental rate (in fine print)
Not quoted
- (Most cost categories surface later)
Year 2
Quoted in proposal
- License (recurring)
Not quoted
- Master data cleanup
- Integration scope add
- Supplemental hours begin to draw
Year 3
Quoted in proposal
- License (recurring)
Not quoted
- Integration-layer rebuild
- Intercompany rules at multi-entity
- Multi-entity COA remap
- Supplemental hours compound
Why nobody on the sell side quotes Year 3
Nobody on the sell side gets paid for telling you the Year-3 truth.
The salesperson is compensated on Year-1 ACV. Their performance review next quarter is about deal velocity, not deal accuracy. They are not lying to you. They are presenting the most favorable accurate view of what you’ll pay, which is the cost of the proposal you saw.
Disclosing Year 3 is competitive suicide.
The implementation partner is compensated on the Year-1 Statement of Work. Their margin comes from billing the SOW as scoped, completing on time, and getting the next SOW. Telling you upfront that you’ll need a second SOW in Year 2 for multi-entity and a third SOW in Year 3 for the integration rebuild costs them the deal — because the comparison shop is presenting Year-1-only cost too. Nobody discloses Year 3. Disclosing Year 3 is competitive suicide.
The analyst tier — Gartner, Forrester, IDC — publishes vendor capability assessments. The economic model is partially vendor-paid (vendors engage analysts in advisory relationships that influence Magic Quadrant placement) and partially buyer-paid (Gartner research subscription tiers run $20K-$25K entry, $40K-$50K adviser-tier, $80K-$100K top-tier — 2026 figures). The buyer-side subscription doesn’t surface Year-3 implementation cost reality because the analyst’s value to the subscribing buyer is benchmark and scale, not specific-deal-economics. Year-3 truth isn’t on the analyst’s surface to disclose.
The peer-review tier — G2, which acquired Capterra, Software Advice, and GetApp from Gartner in Q1 2026 for approximately $110 million — surfaces customer reviews that occasionally name implementation cost overruns. The 1-2 star reviews are sometimes specific. The 4-5 star reviews almost never are. Review velocity is driven by vendor-side customer-outreach campaigns. The customers who agree to be referenced are not, statistically, the ones whose Year-3 reality went sideways.
So nobody quotes Year 3. The proposal is honest about what it claims to be honest about. The buyer who reads it carefully and asks “what about Year 3?” learns by signing.
Four questions that surface Year-3 reality at the proposal stage
These work whether you’re talking to a Tier-1 vendor or a small implementation boutique.
1
"Walk me through what your last three customers in my profile paid in Years 1, 2, and 3 — not just Year 1."
The implementation partner who can answer this with specifics — a representative customer paid X in Year 1, Y in Year 2 because of master-data cleanup and an integration scope add, Z in Year 3 in supplemental hours plus a multi-entity SOW — is the partner worth working with. The partner who says "every customer is different, we can't predict your specific costs" is the partner whose Year-3 reality will be a surprise.
2
"Will you put a Year-3 total-cost-of-ownership estimate in writing — with your specific assumptions about my data volume, my integration scope, and my entity structure — as an attachment to the proposal?"
This is an impolite question. It is also the diagnostic question. The implementation partner who refuses is signaling that they don't want to be measured against the estimate. The partner who agrees and provides specific assumptions has just given you the document to revisit at end of Year 1 and Year 2 — both sides accountable.
3
"Show me your supplemental hourly rate clauses. All of them. And tell me what percentage of your last three customers' total spend ended up at the supplemental rate."
The rate is in the contract. The percentage of spend at that rate is in the implementation partner's CRM. They can pull it. Whether they will is the question.
4
"What's your scope-change process? Specifically — how many days from change-request to revised SOW, and what's the typical change-order pricing band relative to the original SOW size?"
Change orders happen. The question is whether your implementation partner has a documented, fair, fast process or an opaque one that compounds the Year-3 problem.
If the implementation partner or vendor declines to answer the four questions, that itself is the answer.
If you’re staring at a proposal right now
The Year-3 question is already partly answered by what’s in the document. The proposal that surfaces multi-year cost ranges, names supplemental rates explicitly, and references comparable-customer engagement history is a different document than the one that lists Year-1 disclosed pricing only.
If the proposal doesn’t surface those things, the four questions above surface them.
If the implementation partner or vendor declines to answer the four questions, that itself is the answer.
What this piece doesn’t cover: the specific decision frameworks for choosing between Traditional ERP and AI-native ERP — that’s the two-level decision framework piece when it publishes. The vendor-specific reads on NetSuite, Sage Intacct, Acumatica, Microsoft D365, SAP, Oracle, Workday, and the AI-native cohort — those live in Pillar D technology category analysis as they publish. The structural three-pole analyst-tier framing — that’s the cornerstone three-pole authority gap piece when it publishes June 30.
This piece is one specific cost-economics window. A small piece of a body of work. The structural answer Unconventional is building — independent senior practitioner authority, methodology published, buyer-aligned, no vendor revenue, no implementation-partner recommendations — is a longer arc. This Year-3 cost piece is one of the lenses through which the arc becomes visible.
If you’ve sat across from someone two years into a wrong ERP decision asking how to fix it — or you’re trying to avoid being that person — the conversation is open.