Most finance leaders budgeting for enterprise resource planning assume the sticker price tells the story. A licence agreement lands on the desk, the number looks reasonable compared to competitors, and the decision moves forward. Then implementation begins. Six months in, customisation costs have doubled the estimate. Eighteen months in, you’ve committed resources you didn’t anticipate. By year three, you’re locked into a vendor whose upgrade cycles demand ongoing customisation work just to maintain current functionality. The total cost of ownership comparison: SAP S/4HANA vs modern ERP platforms reveals why licence price alone is a dangerous metric for long-term planning.
The reality is this: licence fees represent only 15 to 25 percent of what you’ll actually spend over five years. Implementation, customisation, infrastructure, staffing, and training consume the bulk of the budget. Yet most comparisons stop at the licence number. This gap between advertised cost and operational reality is where budget overruns, vendor lock-in, and missed opportunities take root.
Why TCO matters more than licence price in ERP decisions
Enterprise resource planning decisions are often framed as technology choices. But they’re really financial commitments that span five, seven, or even ten years. Treating them as a software purchase rather than a total cost analysis is the first mistake.
When SAP S/4HANA quotes a licence fee, you’re seeing perhaps one-quarter of the real expense. The rest emerges across implementation, customisation, infrastructure, and ongoing operations. Implementation consulting typically runs 2 to 3 times the licence cost for large enterprises. A single year of customisation work—fixes to workflows, integrations with legacy systems, adjustments to match your specific operations—can exceed the original licence fee. Support contracts escalate annually. Database licensing, hosting infrastructure, security updates, and dedicated staff to manage the system all compound the cost.
Finance teams often discover this too late. They’ve already committed the initial budget and locked the organisation into a multi-year relationship. Switching costs become astronomical. Custom code written in ABAP has zero value outside SAP. Data migration to a different platform becomes a months-long project. The vendor, knowing you’re trapped, has less incentive to keep costs competitive during renewals.
Modern platforms reshape this equation by making costs visible and avoiding the hidden drivers that inflate SAP budgets. When you understand where money actually goes—and what doesn’t have to cost anything—the comparison becomes clear.
Breaking down SAP S/4HANA’s total cost structure
Specificity matters here. You need to know what you’re actually paying for, and where the surprises typically emerge.
Licence costs come in multiple flavours. SAP offers perpetual licensing (pay once, but annual support becomes mandatory) or subscription models. Per-user pricing, per-instance pricing, and module-based fees create complexity. The Safeguarding and Support contract—required to stay current—includes automatic annual escalation clauses. A 3 percent annual increase compounds into significant cost over five years.
Implementation is where hidden expenses multiply. Large SAP deployments run 18 to 36 months. External consulting firms staff these projects heavily. Junior consultants learn your business while senior consultants command premium rates. If your organisation has legacy systems, parallel running (operating both old and new systems simultaneously) extends timelines and costs. Data migration alone can consume months and thousands in labour.
Customisation consumes budget in ways that catch most teams off guard. SAP is built for standard manufacturing and finance workflows. Your specific operational needs—unique approval structures, custom reporting, integration with systems SAP doesn’t natively connect to—all demand customisation. ABAP developers are expensive and hard to retain. Each customisation creates technical debt that requires maintenance and re-testing when you upgrade.
Infrastructure varies by deployment model. On-premise SAP requires database licensing (Oracle or SQL Server), hardware investment, backup systems, disaster recovery infrastructure, and the team to manage it. Cloud deployments move some costs to SAP’s cloud fees, but you’re paying premium pricing for the privilege of outsourcing infrastructure. Either way, it’s a multi-year expense most initial budgets underestimate.
Ongoing operations lock in permanent headcount. You need dedicated SAP resources—not shared business analysts, but people whose primary job is keeping the system running, applying patches, managing security updates, and handling the customisation requests that never stop coming. A typical mid-market SAP environment requires 3 to 5 full-time staff just for operations.
What modern ERP platforms structure differently on cost
Alternative platforms like Onfinity approach the cost problem from the opposite direction. Rather than licensing as the primary revenue model, they optimise for transparent, consumption-based pricing and faster value delivery.
Consumption-based pricing removes licence escalation surprises. You pay for what you use, not for theoretical per-user seats or module bundles you might never deploy. There are no hidden tiers or support contracts that auto-renew at inflated rates. Pricing stays predictable across the planning horizon.
Implementation timelines compress dramatically. Where SAP deployments run 18 to 36 months, modern platforms designed for rapid configuration can go live in weeks to months. This isn’t because they do less—it’s because they avoid the customisation bottleneck. Workflows are designed to handle common operational patterns without coding. Configuration, not customisation, is the default path. Your internal team does more of the work, reducing dependency on expensive external consultants. You move from years of pre-revenue to weeks of value.
The customisation burden shrinks when the platform is built with workflow flexibility in mind. Instead of requiring ABAP developers for every adjustment, business analysts can configure workflows through the user interface. This keeps total cost lower and keeps knowledge inside your organisation rather than locked with specialist vendors.
Cloud-native architecture eliminates infrastructure capital expenditure. Hosting, security patches, disaster recovery, and system updates are vendor-managed. You pay operational expenses rather than tying capital to hardware. Your IT team spends time on strategy rather than infrastructure maintenance.
Perhaps most importantly, lower switching costs mean you’re not locked in for a decade. If a better platform emerges or your needs change, you have options. See how transparent ERP architecture reduces customisation burden and keeps implementation timelines short.
The real cost of customisation and system lock-in
Customisation starts innocently. A workflow doesn’t quite match your process. The consultant says, “We can adjust that with a small custom field and some logic.” Six months later, you have dozens of custom modifications, all requiring maintenance.
The problem compounds at upgrade time. SAP releases new versions regularly. Each upgrade requires your custom code to be re-tested and often rewritten. What took weeks to build initially now takes weeks to maintain. You’re running in place financially, spending budget just to stay current with the vendor’s roadmap.
Specialist ABAP developers are expensive and hard to keep long-term. They’re aware they’re valuable and command premium compensation. They’re also single points of failure—if they leave, knowledge walks out the door. Your organisation becomes dependent on retaining specific people just to keep the system functional.
The switching cost is the hidden expense nobody wants to calculate. If you decide to move away from SAP mid-lifecycle, all that custom code has zero value. You’re rebuilding workflows from scratch on a new platform. Data migration becomes a months-long project. Training staff on new interfaces and processes interrupts operations. The stranded investment in customisation—often millions—can’t be recovered.
Platforms designed with extensibility rather than customisation manage this risk differently. Standard workflows handle 80 percent of operations. Only high-value, competitive differentiators get custom work. This keeps technical debt manageable and keeps switching costs low if the business changes direction.
Building a realistic five-year TCO model for your business
Stop comparing licence prices. Instead, build a complete cost model that captures what you’ll actually spend.
Start with year-one capital: licence fees, implementation consulting, training, and initial infrastructure. Then add year-one operational costs: dedicated staff, support contracts, integration middleware. Repeat for years two through five, accounting for annual support escalations, staffing growth, and periodic retraining cycles.
Headcount is often the largest hidden cost. A typical SAP environment requires 3 to 5 full-time operations staff, plus shared time from business analysts and IT. At fully loaded cost (salary, benefits, overhead), each FTE runs $120,000 to $180,000 annually. Over five years, that’s $600,000 to $900,000 per person. Most budget discussions never quantify this.
Factor in training costs. Every major upgrade requires refresher training for power users. New staff joining the organisation need system training. Training per employee per year typically runs $1,000 to $3,000. For a 200-person organisation with 20 percent annual turnover, that’s meaningful budget.
Integration work extends implementation timelines and cost. SAP rarely exists in isolation. You need middleware or custom APIs to connect it to accounting systems, supply chain platforms, HR systems, and business intelligence tools. Budget $50,000 to $200,000 for integration depending on your system landscape.
Finally, model the exit cost. What would it cost to migrate to a different platform if this one isn’t delivering? Include data migration, retraining, parallel running, and lost productivity. Building this scenario into your budget—rather than assuming it will never happen—gives you realistic financial clarity.
How to evaluate ERP costs transparently before committing
When evaluating any platform, demand specificity. Generic roadmaps and feature lists obscure the real cost conversation.
Request detailed cost breakdowns from vendors. Ask for licence costs, implementation estimates, annual support tiers, infrastructure costs, and staffing recommendations broken across years one through five. If a vendor won’t provide this level of detail, that’s a signal they benefit from opacity.
Benchmark staffing requirements against reference customers. Ask the vendor: “What’s the typical post-implementation team size for an organisation like ours?” Then call those references and ask directly: “How many people are dedicated to SAP operations?” The variance between what vendors project and what customers actually maintain is usually significant.
Run a proof-of-concept with your actual workflows. Don’t test theoretical scenarios. Import real data, configure workflows that match your current process, and measure how long it takes. Use this as your implementation baseline, not optimistic vendor projections.
Clarify the vendor’s financial incentives. Does the vendor make more money from customisation work? That’s a red flag—their margin improves the longer implementation takes. Does the vendor benefit from faster deployment with less custom code? That’s aligned with your interests.
Build sensitivity analysis into your planning. What if implementation runs six months over? What if you need to hire an extra FTE for operations? What if you discover integration work you hadn’t anticipated? Add 20 to 30 percent contingency to your budget based on these scenarios.
Making the case to your board
Finance leaders and CFOs need ammunition when presenting ERP decisions to boards and executives. The conversation should never be about technology—it should be about total financial commitment and risk management.
Frame the decision as: “We’re committing $X over five years, with Y percent going to licence costs and Z percent going to operations and customisation. Here’s where we have flexibility to reduce cost, and here’s where we’re locked in.” This grounds the conversation in financial reality rather than feature comparison.
Present the switching-cost scenario. “If we choose platform A, the cost to switch away is $2M and takes 18 months. If we choose platform B, the switching cost is $400K and takes 6 months.” Lower switching costs reduce long-term risk. You’re not locked into a single vendor’s roadmap for a decade.
If your team is still evaluating ERP options based on licence price alone—or if you’re inheriting customisation debt from a previous system—there’s a clearer framework available. Request a cost comparison walkthrough tailored to your operational workflows to see how transparent pricing and faster implementation reshape your five-year budget.
The ERP decision is the most expensive technology commitment most organisations make. It deserves financial discipline equal to any capital project. Demand specificity, model conservatively, and choose a platform whose pricing and implementation approach reduce rather than inflate long-term cost.
Follow us on LinkedIn for ongoing ERP insights and operational workflows.