What about support in five years?

For custom, whoever holds the source can support it — that is why the source, the documentation and the decision log are contractual deliverables rather than favours. For packaged, support is the vendor's, on their terms and their timetable.

Frequently the right answer. Keep the packaged system for finance and statutory reporting where standardisation genuinely helps, and build custom where the process is differentiating. The integration layer between them is then the engagement.

Comparison

Custom ERP or SAP: which one your process can actually live with

A packaged ERP asks your business to work its way. A custom one encodes how you already work. Which is right depends less on budget than on whether your process is a competitive advantage or an accident.

Talk it through How we engage

The short answer

Choose SAP when your processes are standard and you want the vendor's ecosystem, certified consultants and an upgrade path you do not maintain. Choose a custom ERP when your process is the competitive advantage, when packaged software has already been tried and abandoned, or when the integration surface is the real problem.

Side by side

Custom ERP against SAP or similar.

	Custom ERP	SAP or similar
Fit to your process	Built around how you work today.	Your process moves to the product's model, or you pay to customise it.
Time to first release	4–7 months, phased.	9–18 months for a mid-size rollout.
Licence cost	None. You own it.	Perpetual or subscription, per seat, forever.
Upgrade burden	Yours to schedule. Nothing forces your hand.	Vendor-driven. Customisations are what make upgrades expensive.
Talent availability	Anyone competent in the stack.	Certified consultants, priced accordingly.
Exit	You already hold the source.	Migration off is a programme of its own.
Risk profile	Delivery risk sits with the build.	Delivery risk sits with the fit.

Custom trades licence cost for build cost. The crossover depends on seat count and lifespan: a hundred-seat system running ten years usually favours custom, twenty seats over three years usually does not.

How to decide

When each is the right answer.

Each line below is a condition, not a preference. The matrix above scores the same choice on every axis a buyer weighs.

Choose custom erp when

A packaged ERP has been tried here before and was abandoned or heavily worked around.
The way you plan, cost or fulfil is genuinely different from your competitors — and that difference earns money.
Most of the pain is integration with systems that are staying.
You want the licence line off the P&L permanently.

Choose sap or similar when

Your processes are close to standard and you have no strong reason to keep them bespoke.
You need statutory localisation across many countries out of the box.
Your board wants a name it recognises behind the system, and that is a real constraint.
You have no appetite to own software long-term, even with a partner operating it.

Follow-ups

The risk moves rather than disappearing. With SAP the risk is fit — the expensive failures are customisations and workarounds bolted on to close the gap. With custom the risk is delivery, which is manageable with phased releases and exit points at each phase. Neither is inherently safer; they fail differently.

Other comparisons

Next step

Bring us the problem. We will bring the architecture.

A discovery call takes forty-five minutes. You leave with our read on the problem, the shape of the system we would propose, and a straight answer on whether we are the right team for it.

Book a discovery call Send a brief instead

No sales deck
An engineer on the call, not an account manager
NDA before you share anything