Most finance leaders can point to their SAP contract renewal and describe the sticker shock—but few can actually articulate where the money is going. The headline license fee is just the anchor. Implementation partners, annual maintenance, infrastructure scaling, customisation backlogs, and the opportunity cost of a 24-month deployment create a total cost of ownership that often doubles or triples what executives initially budgeted. When you evaluate a total cost of ownership comparison: SAP S/4HANA vs Onfinity ERP, the gap in how vendors structure their economics becomes visible—and it matters to your bottom line.
This article deconstructs the real cost drivers behind enterprise ERP systems, showing where traditional proprietary models break down and what a transparent pricing alternative looks like. If your team is rebuilding the business case for ERP investment, this framework will help you see the full picture.
The Hidden Costs of SAP S/4HANA Most Finance Teams Don’t Budget For
SAP’s licensing model starts with a number that looks manageable, then expands during implementation in ways that surprise even experienced procurement teams. Per-user licensing is the first multiplier. A mid-market organisation with 500 users doesn’t pay for 500 seats upfront—the implementation typically starts with a core group of 100–150 named users. But as you expand to finance, supply chain, HR, and operations teams, seat count grows. Each additional user license, even at volume discount rates, adds material cost. Many organisations discover halfway through rollout that they’ve already exceeded their original user tier.
Implementation partner fees are the second shock. Systems integrators, SAP’s preferred implementation partners, charge between $150–$300 per hour for senior consultants. A typical S/4HANA implementation consumes 5,000 to 15,000 hours of partner labour—often 2 to 3 times the initial software license cost. Timeline overruns are common. A 18-month project becomes 24 months. Each additional month means extended partner engagement, your internal team still diverted from operations, and deferred business benefits.
Annual maintenance and support fees run 17–22% of your total license cost every year, in perpetuity. For a $2 million license base, that’s $340,000–$440,000 annually just to keep the system running and receive updates. This compounds over 10 years. Organisations often accept higher support tiers than they use because vendors bundle them into maintenance contracts, and renegotiation is difficult once you’re locked in.
Customisation becomes a hidden cost factory. SAP promises “standard functionality” for finance and operations, but your company’s procurement workflows, approval hierarchies, and reporting rules rarely map cleanly to the out-of-the-box design. Custom code, bolt-on integrations, and modified business processes emerge during testing. Some organisations accumulate 30–50% custom code by year three. Each customisation increases the cost of upgrades, complicates support interactions, and creates technical debt that compounds annually.
Cloud versus on-premise deployment also shifts costs in ways that aren’t immediately transparent. On-premise SAP requires capital investment in servers, storage, and networking infrastructure, plus a dedicated team to manage it. SAP Cloud deployments avoid that capital expense but include licensing restrictions on how you can modify the system and where you can host it. Multi-year cloud contracts can lock you into pricing that doesn’t account for business growth or the emergence of cheaper hosting alternatives.
How Deployment Architecture Impacts Your Total Spend
The decision between on-premise, SAP Cloud, and third-party hosting isn’t purely technical—it’s a cost architecture decision that ripples through five to ten years of spend.
On-premise deployment requires upfront capital expenditure: servers, storage arrays, networking, and often a dedicated infrastructure team to manage patches, backups, and security. A mid-market organisation might invest $500K–$1.2M in infrastructure alone. That’s separate from software licensing. You also own the operational risk. Database performance degradation, disk failures, or network bottlenecks become your problem to solve. Many organisations underestimate the headcount required to keep SAP running reliably—often 2–4 full-time infrastructure and database specialists.
SAP Cloud deployments eliminate capital infrastructure costs but introduce contractual restrictions. SAP controls the hosting environment, patches, and upgrade cadence. If you want to customise the system or integrate it with legacy platforms in a way SAP doesn’t pre-design, you run into licensing restrictions or have to pay for premium integration services. You’ve traded capital expense for operational constraints and vendor control.
Data migration and system integration often appear as line items in implementation budgets, but the scope rarely matches what actually needs to happen. Extracting clean customer, vendor, and transaction data from legacy systems is labour-intensive. Testing data integrity across systems adds weeks. Post-go-live integration debugging—when real data flows and edge cases emerge—typically consumes 10–20% of total implementation effort and happens after go-live, when budgets are already exhausted. Many organisations absorb that cost as unbudgeted operations support.
Post-implementation stabilisation is another cost that rarely appears in the original business case. The first 60–90 days after go-live involve bug fixes, performance tuning, and business process refinements. Your team is still learning the system, users are discovering workarounds for missing functionality, and the ERP vendor’s support team is focused on preventing critical failures rather than proactively optimising your setup. This phase typically costs 10–15% of total implementation labour, spread across your internal team and the vendor.
Upgrade cycles also factor into long-term TCO. SAP moves to new versions roughly every 2–3 years. Staying on older versions creates risk: security patches stop, integrations break as third-party systems move forward, and recruitment becomes harder because consultants want experience on current versions. But upgrading S/4HANA isn’t a patch—it’s a significant undertaking that often requires re-testing custom code and re-validating integrations. Many organisations budget $500K–$1.5M per major upgrade cycle.
Licensing Models That Actually Fit Mid-Market Budgets
The structural difference between traditional proprietary licensing and modular, open-source approaches shows up clearly in how organisations can control their own growth and customisation.
SAP’s per-user model means cost scales with headcount. If you double your user base from 500 to 1,000, licensing costs roughly double. Subscription-based pricing can invert that logic: your cost scales with what you actually use—compute, storage, transaction volume—rather than a flat per-seat fee. For growing mid-market companies, that difference compounds. A 15% annual user growth on per-seat licensing adds material cost; the same growth on usage-based pricing may add only 5–8% because you’re only paying for incremental infrastructure consumption.
SAP bundles features into modules and forces you to buy entire packs even if you only need a subset. If you need advanced procurement functionality, you’re licensing the full supply chain module, which may include capabilities you don’t use for years. Modular systems allow you to activate features as your business demands them. Over ten years, true pay-for-use pricing can reduce software spend by 20–30% for organisations that don’t immediately need all functionality.
Customisation ownership is a long-term cost lever that most organisations overlook. SAP’s licensing typically restricts your ability to modify the source code or port customisations if you change vendors. You own the business logic you’ve built, but you can’t easily extract or re-use it. Open-source ERP systems give you full ownership of your code. If you invest in a custom procurement workflow, you own that code completely. That reduces long-term vendor lock-in risk and gives you genuine negotiation leverage during contract renewals.
Multi-tenancy versus single-tenant infrastructure is a vendor economics choice, not a technical necessity. SAP Cloud uses multi-tenant infrastructure—your data sits alongside other customers’ data in a shared environment. That efficiency benefits SAP’s margin more than it benefits you. Single-tenant deployments—where you control your own isolated environment—cost more but give you control over performance, security, and when upgrades happen. For organisations handling sensitive data or operating in regulated industries, single-tenant can actually reduce compliance and audit costs.
Vendor lock-in amplifies over time. If SAP knows switching costs are prohibitively high, they have less incentive to keep your renewal pricing competitive. Transparent data formats, unencumbered export capabilities, and contractual flexibility to modify or extend the system reduce your switching risk. That freedom, even if you never exercise it, typically results in better vendor negotiations and lower effective cost.
Implementation Timeline and Resource Cost: Where Budget Goes Wrong
The length of an ERP implementation creates its own cost category that few organisations quantify accurately.
SAP’s typical 18–36 month timeline creates opportunity cost that extends beyond software spend. Your finance controller, supply chain director, and operations manager are pulled into implementation governance, testing, and change management for two years. That’s two years they’re not driving process improvement in your existing business. Some organisations estimate that opportunity cost alone—the strategic work that doesn’t happen while leadership is focused on go-live—equals 20–30% of total implementation cost.
Internal team diversion is measurable. A mid-market finance team might dedicate 2–3 FTEs full-time to SAP implementation for 18 months. That’s not a pure cost—those people still exist on payroll—but it’s an operational cost: month-end closes take longer, reconciliations get backed up, and variance analysis happens less frequently because the people who do that work are in meetings. When you multiply that across finance, supply chain, and operations, you’re looking at 15–20 FTEs partially or fully diverted. Most organisations don’t budget for that productivity loss.
Training and change management costs are similarly underestimated. Each user needs training—sometimes 2–3 days per role. For 500 users across five roles, that’s 5,000–7,500 hours of training. Even using internal trainers, that cost is real. Plus, there’s a productivity dip post-launch. Users are learning the new system, finding workarounds, and working slower than they did before. Some research suggests productivity dips 15–25% for the first 60–90 days after go-live. For a 500-person finance and operations team, that’s significant.
Partner dependency creates another cost driver. Implementation partners are optimised for delivery, not knowledge transfer. When they leave at go-live, the knowledge goes with them. Many organisations have to re-hire consultants a year later when they need to execute process improvements or manage their first upgrade. Building a business case for faster implementation—12–18 months instead of 24–36 months—often reduces partner hours by 25–35%, which translates directly to cost savings.
Year-on-Year Operating Costs and the Maintenance Trap
Once you’re live, ERP costs don’t stabilise—they compound.
Annual support contracts include functionality you often don’t use. SAP offers three support tiers. Many organisations buy the highest tier because they’re uncertain about what they’ll need, then stick with it because renegotiating mid-contract is difficult. The reality: most mid-market organisations use Tier 1 (critical incident response) and Tier 2 (non-critical support). Tier 3 (dedicated architect and strategic guidance) is rarely used. If you’re paying $300K annually for support and only using 40–50% of it, that’s $150K–$180K in excess spend that compounds over a decade.
Mandatory upgrade cycles create a treadmill. SAP stops security patches after a system version reaches end-of-life. If you’re on a version from 2019, you may have only 2–3 years before patches stop. Staying unpatched creates audit and compliance risk, so you’re forced to upgrade. Each upgrade cycle costs $500K–$1.5M. That’s roughly every 2–3 years, or $200K–$500K annually when annualised. It’s a recurring cost that doesn’t go away.
Database and infrastructure scaling happens quietly but consistently. As your transaction volume grows—more purchase orders, more sales transactions, more journal entries—the database grows. Storage costs increase. Query performance degrades, and you add more database servers to maintain response times. A $10M revenue company might run SAP on a $500K infrastructure footprint. A $100M revenue company might need $3–$5M in infrastructure. Much of that scaling is driven by data volume, not capability expansion.
Patch management and stability become increasingly expensive with high-customisation systems. If 40–50% of your system is custom code, SAP’s patches sometimes break customisations. You have to test patches against all custom code before deploying them. Some organisations hire managed services partners just to handle patch testing and deployment. That’s another $50K–$150K annually.
Talent retention affects your long-term SAP costs. SAP specialists are expensive and in high demand. When they leave, you have to replace them quickly. A mid-market organisation might have 2–3 SAP specialists on staff. If one leaves and takes three months to replace, you’re paying interim consultants $200–$300 per hour to keep the system stable. A six-month cycle of one person leaving and being replaced can cost $100K–$200K in excess consulting fees.
Building Your TCO Model: What to Actually Measure
Rather than accepting a vendor’s implementation estimate or relying on peer benchmarks, build a TCO model specific to your organisation and constraints. Start with your current spending: software licenses, support contracts, infrastructure, internal labour, and consulting fees. Establish a baseline. If you’re currently on SAP, total what you’re actually spending annually. That baseline is your reference point.
Project costs across a 5–10 year horizon with realistic assumptions for user growth, transaction volume, and complexity. Most organisations grow 10–15% annually in users and 15–25% in transaction volume. Use your own growth trajectory, not industry averages. Model your upgrade cycles. If major upgrades happen every 2–3 years at $500K each, that’s $200K–$250K annually annualised. Include infrastructure scaling based on your growth.
Add hidden cost categories explicitly. Budget training at 30–40 hours per user for initial rollout. Budget post-implementation support at 20% of total implementation labour for the first year. Budget annual customisation and integration maintenance at 5–10% of total implementation cost. Budget for at least one major upgrade and one minor upgrade cycle over ten years. The organisations that control TCO best are the ones that budget for what typically