Over five years, the cost difference between a custom ERP module and a third-party add-on is decided less by the quote price than by what each option does to the upgrade path. The decision surfaces with a renewal estimate and a build quote on one screen.
Add-ons look cheap in year one and expensive by year four. Custom modules reverse the shape: heavy opening spend followed by a maintenance curve whose slope tracks the parent ERP's release cadence. Integration debt sits under both, and rarely appears on the first business case.
The Module Decision Is a Cost Curve, Not a Line Item
A module-level build-vs-buy call has four cost drivers that behave very differently over time. Subscription or licence fees scale with user count and feature tier. Implementation lands in year one. Maintenance stays roughly flat on a vendor-hosted add-on and climbs on custom code bolted to a parent ERP. Upgrade cost is the driver most frames miss, and the one that usually decides the five-year number.
Panorama Consulting's long-running work on ERP total cost of ownership puts the weight of these components well outside the software price itself. The sticker figure explains very little of what the next five years will cost, and treating modules as line items on a licence schedule is where most five-year models go wrong.
What Five Years of Add-Ons Actually Cost
The add-on path is mechanically simple: a per-vendor subscription, a smaller implementation fee, and a renewal bill every twelve months. Mid-market finance stacks rarely stop at one add-on. Tax engines, EDI, e-invoicing, consolidation, revenue recognition and planning each arrive with their own contract, their own support channel, and their own connector to the ledger.
Stacked over five years, the subscription line alone moves the TCO conversation. The curve bends further once seat growth, annual uplifts and connector tiers are counted. Add-ons that looked like small annual line items at signing start competing with the original ERP licence by year three, and often exceed it by year five once vendor consolidation discounts expire. That inflection is often missed on a module roadmap: the total cost of the ERP has drifted from the ledger into the add-on layer without a single board slide flagging it.
The Custom Module Maintenance Curve
Custom modules front-load the spend. The first version of an invoicing extension, a revenue allocation engine or a warehouse workflow lands in a single implementation budget, and the per-user cost after that is effectively zero. What is not zero is what happens on every upgrade of the parent ERP, which is where the module meets the version it was not written against. The maintenance curve starts flat and turns upward sharply at the first version bump, which is why the year-one number is a poor predictor of year five.
Industry research on ERP customisation treats this as the governing cost, meaning not the build itself but the share of engineering attention the custom code consumes for the rest of its life. Modules that looked cheap at year two routinely compound into the largest line on the IT budget by year five, and are the main reason custom fields become ERP debt faster than finance teams expect.

The Upgrade-Break Tax Nobody Prices In
Both options carry an upgrade-break tax, but the shape differs. SaaS add-ons are exposed to API deprecations on either side of the connector. When the parent ERP changes a schema or the add-on vendor forces a new major release, the glue has to be rewritten, retested and re-certified. The cost of that glue often shows up the following quarter, categorised as integration maintenance rather than add-on subscription, and therefore invisible to the module-level business case.
Custom modules are exposed on a longer cycle at a larger amplitude. An on-premise version upgrade routinely invalidates a fraction of existing customisations and forces a partial rebuild of the rest, which is where the maintenance curve turns sharply upward.
Neither option is upgrade-free. The question is whether the five-year model has priced the rebuild cycles honestly, and whether the parent ERP's release cadence is annual, biennial or indefinite. Teams still running on-premise builds already know how this interacts with the true cost of keeping your legacy ERP alive.
Integration Debt Sits Under Both Options
The frame breaks down if the integration layer is treated as free. Both paths generate integration work: an add-on needs a two-way connector; a custom module needs event hooks into the ledger and into every adjacent system that reads the same master data. That work does not appear in the vendor's licence schedule.
Benchmarks on enterprise connectivity show only 27% of applications connected on average, with more than a quarter of IT projects slipping their deadlines in the prior year. The practical implication is that integration debt is the default state, not the exception, and the five-year TCO frame has to assume a non-trivial rebuild of connectors mid-cycle.
Ongoing vendor maintenance fees land on top of all of that. Perpetual-licence contracts carry a yearly maintenance component that rarely moves far in negotiation, and the real cost is its compounding effect over five renewal cycles. An AI-native architecture built so that agents run on a deterministic ledger, the model behind the erp.io platform, reduces the connector surface by absorbing add-on functions into role-based agents rather than vendor silos.
A Module-Level Framework for the Next Decision
A defensible five-year frame for the next module call has five inputs, each stated explicitly before the business case leaves the finance team:
- Year-one implementation cost for both paths, including the connector or the module's event hooks.
- Annual subscription or maintenance line, with the published renewal uplift applied each year.
- Expected upgrade-break cost, expressed as a percentage of the original build or connector cost, applied on the parent ERP's known release cadence.
- Internal engineering absorption, measured as hours per month the finance-systems team spends keeping the module alive, costed at a fully loaded rate.
- Exit cost in year five, because every add-on vendor has one and every custom module has one, and both are routinely missed.
Scored this way, add-ons tend to win when the functional surface is wide and commoditised (tax, EDI, e-invoicing) and the parent ERP's release cadence is slow. Custom modules tend to win when the workflow is specific to the business, the integration surface is narrow, and the module can be isolated from the parent's upgrade cycle. Build-vs-buy decisions that weigh AI-native ERP designs against a traditional stack of add-ons usually turn on which side of this line the workflow actually falls.
What the Five-Year Frame Costs to Adopt
The trade-off this frame asks for is giving up the comfort of a single-number subscription line, and accepting that both options carry rebuild cycles that are not optional. The payoff is a five-year figure that holds up in front of an audit committee rather than one that assumes the upgrade tax away. Finance leaders who stop treating modules as line items on a licence schedule tend to make the next module decision once, and with a clearer view of which cost curve they have actually signed up for.
