Custom ERP vs SAP: Which Is Right for UK Businesses in 2026?

Most UK businesses that end up unhappy with SAP were never really unhappy with SAP. They were unhappy with having bought a system designed for an organisation ten times their size, and then having paid to reshape themselves around it.

That is the honest framing of this decision, and it is not an argument against SAP. It is an argument for being clear-eyed about which problem you actually have before you commit to a five-year programme.

What SAP Actually Is (And Isn't)

SAP S/4HANA — what's included and what's not

S/4HANA is SAP's flagship enterprise suite: finance, procurement, manufacturing, supply chain, sales, and a great deal more, built on SAP's in-memory HANA database and available as on-premise, private cloud or public cloud.

What it includes is genuinely enormous. Decades of accumulated process knowledge across dozens of industries, functionality most businesses will never touch, and a level of auditability and control that large regulated organisations depend on.

What it does not include is the part that catches businesses out. The licence gets you the software. It does not get you the configuration, the data migration, the integrations, the testing, the training or the process redesign — and in almost every implementation those cost several times the licence.

It also does not get you a system that matches how you currently work. S/4HANA embodies a view of how a business should operate, and adopting it means adopting that view. For large organisations with undisciplined processes, that is frequently the main benefit. For a business whose competitive advantage lies in doing something differently, it is the main risk.

SAP Business One for SMBs — the mid-market option

Business One is a genuinely different product that shares a brand. It was acquired rather than built, it targets smaller organisations, and it is sold and implemented almost entirely through partners.

For a UK SMB with fairly conventional processes — distribution, light manufacturing, wholesale — Business One is a reasonable and proven option. It handles finance, inventory, purchasing, sales and basic production, and implementations run in months rather than years.

The limitation is extensibility. Business One customises through add-ons and partner development, and businesses with genuinely unusual workflows tend to accumulate a layer of bolt-ons that becomes expensive to maintain and awkward to upgrade. Where you land depends heavily on how standard your operation is.

Who SAP is actually built for

SAP's core product is built for large, complex, multi-entity organisations — typically multi-country, multi-currency, with significant regulatory obligations, substantial internal IT capability, and enough scale that process standardisation is worth more than process flexibility.

For those organisations SAP is frequently the correct answer and the alternatives are worse. The difficulty is that the same sales motion reaches businesses at a fifth of that scale, where the arithmetic is quite different.

The Real Cost of SAP for UK Businesses

Licence costs

SAP pricing is negotiated rather than published, which makes comparison genuinely difficult and is itself a cost — you cannot easily benchmark what you are being offered.

Broadly, cloud ERP licensing is priced per named user per month with tiering by user type, plus module-based charges for specialised functionality. A mid-market UK deployment typically lands somewhere in the low hundreds of pounds per full user per month, with limited-access users considerably cheaper.

Two things reliably surprise buyers. First, indirect or digital access — systems and processes touching SAP data without a named user — has historically been chargeable, and while the licensing model has been reworked, it remains something to scrutinise carefully in any contract. Second, list price and negotiated price diverge substantially, and the gap depends largely on timing and on how well advised you are.

Implementation costs

This is where the real money goes, and it is consistently underestimated.

A common rule of thumb in the mid-market is that implementation costs somewhere between one and three times the first-year licence spend, and complex programmes exceed that comfortably. The work includes discovery and process mapping, configuration, data cleansing and migration, integration with everything else you run, testing cycles, user training, and a hypercare period afterwards.

For a UK business of £10–50m turnover, a realistic S/4HANA implementation through a partner is a six-figure programme before the licence, and frequently a substantial one. Business One implementations are materially smaller but still represent a serious investment.

Ongoing support, maintenance and upgrade costs

Cloud subscriptions bundle some support; on-premise deployments carry annual maintenance that has traditionally run around a fifth of licence value per year.

Beyond SAP's own charges, most businesses retain a partner on an ongoing basis, because SAP administration is a specialist skill and the internal market for it is tight and expensive. That retainer is a permanent line item, not a transitional one.

Upgrades deserve their own consideration. Heavily customised deployments are harder and costlier to upgrade, which creates a slow drift toward being stuck on an old version — the situation that drove much of the recent migration activity in the first place.

The hidden cost: business process change management

The largest cost in most SAP programmes does not appear on any invoice.

Adopting SAP means adopting SAP's process model, which means retraining people, rewriting procedures, and absorbing a period of reduced productivity while the organisation relearns its own operations. Programmes that fail rarely fail technically. They fail because the business could not absorb the change, or because the process the system enforced was worse for that particular company than the one it replaced.

This cost is real, it is large, and it is almost never in the business case.

What Custom ERP Can (and Cannot) Do

What you get with a purpose-built ERP

A system built around how your business actually works, containing only the functionality you use, with no licence renewal and no per-user charge.

For businesses whose operational model is their advantage — an unusual production process, a distinctive service delivery model, a pricing structure that does not fit standard templates — this is the decisive argument. The software adapts to the business rather than the reverse.

You also get ownership. The code is yours, the data model is yours, the roadmap is yours, and nobody can change the commercial terms underneath you.

What you do not get is decades of accumulated industry process knowledge, a global partner ecosystem, or a large pool of people who already know the system. Those are genuine losses and should be weighed honestly rather than dismissed.

Time to build vs time to configure SAP

The common assumption is that buying is fast and building is slow. In the mid-market this is frequently untrue.

A focused custom ERP covering finance, inventory, production and reporting for a single-entity UK business typically takes six to twelve months to reach production, delivered in stages, with usable functionality live well before the end.

A full S/4HANA implementation of comparable scope commonly runs twelve to twenty-four months, because configuration, data migration, testing and process change are not faster than development — they are simply a different kind of slow.

Where buying genuinely wins on time is at the simpler end: Business One or a comparable mid-market package for a conventional operation can be live in three to six months.

Long-term flexibility and ownership

The practical difference shows up in year three. A custom system absorbs a new business line, a new regulatory requirement or an acquisition as a development project — scoped, costed and delivered on your timetable.

The same change in a packaged system is a configuration exercise if you are lucky, a customisation project if you are not, and a licensing conversation either way. Businesses that change shape frequently tend to find the custom route considerably less frustrating over time.

Our custom ERP development work is built around this staged, ownership-first model.

When SAP Is the Right Answer

Large enterprise with global operations

Multi-country, multi-currency, multi-entity operations with statutory reporting obligations in several jurisdictions. SAP handles this genuinely well, and replicating it from scratch would be expensive and unwise.

Regulatory and compliance-heavy industries

Pharmaceuticals, aerospace, defence, food production and similar sectors where validated systems, complete audit trails and traceability are regulatory requirements rather than preferences. SAP arrives with this built in and with a track record auditors recognise.

Existing SAP ecosystem and integrations

If your parent company runs SAP, if your largest customers require SAP-compatible EDI, or if your industry's supply chain is built around it, the integration argument frequently outweighs everything else. Fighting a well-established ecosystem is rarely worth it.

When Custom ERP Is the Right Answer

UK SMBs with workflows SAP cannot accommodate

The most common case. A business with a genuinely distinctive operating model discovers during discovery that fitting it into the package requires either substantial customisation or substantial process change — and both are expensive, with the second frequently damaging the thing that made the business work.

Businesses where the SAP budget does not exist

Straightforward, and more common than vendors acknowledge. A business that cannot fund a full implementation properly should not start one, because an underfunded ERP programme is worse than no programme. A staged custom build that delivers the highest-value module first is a considerably safer use of a constrained budget.

Companies that want to own their technology

Businesses building toward a sale, or operating in a sector where their systems are part of their valuation, frequently prefer an owned asset to a licence. Increasingly this includes companies wanting control over how their operational data is stored, integrated and used — particularly where they intend to build their own analytics or automation on top of it.

Our custom CRM development work often sits alongside this for exactly that reason, and our broader software development practice covers the integration layer between the two.

Total Cost of Ownership: A Five-Year Comparison

The figures below are illustrative, and any real comparison needs your actual scope and numbers. They are included because the shape of the comparison matters more than the precision.

Scenario 1: £5m revenue manufacturer, 25 users

SAP Business One route. Licensing for twenty-five users across five years, partner implementation, data migration and training, plus an ongoing support arrangement and a mid-period upgrade. A realistic five-year total sits in the region of £180,000–£320,000, with most of it committed in the first eighteen months and the rest recurring indefinitely.

Custom route. A staged build covering production scheduling, inventory, purchasing and finance integration, delivered over roughly nine months, plus hosting and a support retainer thereafter, plus a reasonable allowance for enhancements each year. A comparable five-year total sits in the region of £150,000–£280,000, weighted heavily toward the first year and falling sharply afterwards.

The totals are closer than most people expect. The difference is in the shape: the packaged route has a lower peak and a permanent floor, the custom route a higher peak and a much lower floor. At year eight the gap widens considerably in favour of the custom build.

Scenario 2: £25m services business, 80 users

At this scale the arithmetic shifts. Eighty users on per-seat licensing is a substantial recurring commitment, and a full S/4HANA implementation is a major programme — plausibly £600,000 to well over £1m across five years.

A custom build for a services business — project delivery, resourcing, time capture, billing, finance integration and reporting — is a larger undertaking than the manufacturer's, but per-user cost does not scale with headcount. A five-year total in the £350,000–£700,000 range is realistic for a well-scoped programme.

The caveat is capability. At eighty users the organisation needs someone accountable for the system internally, and businesses unwilling to own that should weight the packaged option more heavily regardless of the arithmetic.

Making the Decision: A Framework for UK Business Leaders

Five questions, in order.

How standard is your operation, honestly? If an experienced implementer can map your processes onto a package without significant compromise, buy. If the mapping requires you to change something that matters commercially, that is a real cost and it belongs in the comparison.

What is your true budget, including change? Not the licence. The licence, the implementation, the internal time, the productivity dip and the ongoing support. If that number does not exist, a staged custom build delivering the highest-value module first is the safer path.

Who will own this in three years? Packaged systems need administration; custom systems need a development relationship. Both need someone internal who is accountable. Neither survives being nobody's job.

How fast does your business change? Frequent change favours ownership. Stability favours the package.

What are you optimising for? Lowest risk and fastest proven path points to buying. Lowest long-run cost and highest fit points to building. Both are legitimate answers, and the failure mode is choosing one while optimising for the other.

If you take one thing from this: the worst outcome is not choosing wrongly between two viable routes. It is starting either one without an honest view of the total cost and the organisational change involved.

FAQ

Is SAP too expensive for UK SMBs?

SAP's enterprise suite usually is, once implementation and change costs are included. Business One is priced for the mid-market and is a reasonable option for conventional operations. The question is less about the licence than about whether the total programme cost is proportionate to the business.

When should a business build a custom ERP instead of SAP?

When its operating model is genuinely distinctive and fitting it into a package would require compromising something commercially valuable, when the budget for a proper packaged implementation does not exist, or when owning the system matters for flexibility or valuation reasons.

How much does SAP cost compared with custom ERP?

At mid-market scale the five-year totals are often closer than expected, but the shape differs: packaged systems have a lower initial peak and a permanent recurring floor, while custom builds concentrate cost in the first year and fall sharply afterwards. The gap widens in favour of custom beyond year five.

Can custom ERP replace SAP functionality?

The functionality a given business actually uses, generally yes. The full breadth of SAP, no — and attempting it would be wasteful. Most mid-market businesses use a modest fraction of a packaged suite, which is precisely what makes a focused custom build viable.

How long does a custom ERP take to build compared with implementing SAP?

A focused custom ERP typically reaches production in six to twelve months, delivered in stages. A full S/4HANA implementation commonly runs twelve to twenty-four. Simpler packaged options such as Business One can be live in three to six, which is the one clear timing advantage buying holds.

What is the biggest hidden cost in an SAP implementation?

Business process change. Adopting the system means adopting its process model, which means retraining people, rewriting procedures and absorbing a productivity dip. It rarely appears in the business case and it is frequently the largest single cost.