
A bespoke ERP can cost less than a licensed product over its working life, but that outcome is not automatic. For a UK SME, the useful comparison is the total cost of supporting the same business processes over the same period. A subscription price and a development quotation describe different parts of that investment.
Use five years as a planning horizon, then test how the result changes with growth, different support needs or an earlier replacement. The aim is to compare assumptions that you can check, rather than assume either buying or building must be cheaper.
Compare the same business scope
Give both suppliers the same example transactions, integrations, user groups and service requirements. Include exceptions such as partial deliveries, returns and approval limits. A standard package that already covers these needs may be the more practical choice, even when a custom interface looks attractive.
Microsoft's fit-to-standard and fit-gap guidance recommends examining standard capabilities before deciding which gaps justify custom work. A specialist module connected to an existing ERP may also resolve the problem without replacing the whole system.
Build a five-year cost worksheet
Separate initial work from recurring costs, and ask each supplier to state its assumptions:
- Initial work: discovery, configuration or development, integrations, data preparation, migration, testing, training and launch.
- Recurring costs: product subscriptions, third-party licences, hosting, backups, monitoring, support and maintenance.
- Business participation: time spent agreeing rules, cleaning data, testing workflows and supporting colleagues through the change.
- Later changes: additional users or sites, new integrations, upgrades and features outside the original scope.
- Exit: data export, documentation, handover and the work another supplier would need to take responsibility.
For a UK business, ask for consistent treatment of VAT, expenses and any charges in another currency. Show uncertain costs as assumptions or scenarios instead of hiding them inside a single total. Microsoft's cost modelling guidance is useful for identifying infrastructure, licensing and operational costs that can otherwise be overlooked.
Bespoke software still has ongoing costs
A custom application may avoid a per-user licence for the application itself, depending on the agreement. It can still depend on licensed databases, components, cloud services or external APIs. Check the actual technology choices and terms instead of treating “bespoke” as a promise of no licence costs.
It also needs maintenance, security updates, hosting and support. Building around an existing process does not eliminate training or organisational change: people still need to agree responsibilities, validate data and learn the new workflow. Include this work on both sides of the comparison.
Test the assumptions that could change the result
Model today's users and transaction volumes, then an agreed growth scenario. Check what happens if customisation grows, a supplier changes its pricing or a critical integration requires more work. A lower initial price can be outweighed by later obligations, while a larger build budget may never be recovered if the business does not need the custom capability.
Compare benefits separately from costs. Reduced re-entry or faster order handling should have a baseline and a way to measure improvement. Treat projected savings as estimates until the business can demonstrate them; they are not guaranteed simply because a new system has been delivered.
Check ownership and handover in the proposal
Paying for development does not by itself settle every ownership question. Ask the proposal to specify source-code access, intellectual-property arrangements, third-party dependencies, documentation and operational accounts. Confirm what another provider would receive and which licences would still apply. These details affect the practical ability to maintain or replace the system.
Turn the comparison into a scoped decision
Use our bespoke ERP versus off-the-shelf guide for UK SMEs to compare the approaches, then the UK ERP development cost guide to prepare a first-phase budget.
Worktechlabs can help assess bespoke ERP options and the integrations around them. Share the process you need to improve and the systems involved so the discussion can focus on a manageable scope, its ongoing responsibilities and the evidence needed to choose.
Related service: Custom ERP development.

