An ERP system is the software your business runs on — the single place where stock, orders, jobs, invoicing, purchasing and reporting all agree with each other. Custom ERP development means building that around your actual processes instead of changing your processes to fit a product.
It is the most valuable software most mid-size businesses ever commission, and the most likely to go badly.
The Panorama Consulting 2026 report, surveying 170 organisations between January 2025 and January 2026, found roughly 30% of ERP projects finished over budget and 22.3% exceeded their planned schedule. Gartner projects that more than 70% of recently implemented ERP initiatives will fail to fully meet their original business-case goals by 2027.
We build custom ERP systems — and we build them because, for operations-heavy UK businesses, a system shaped around how you actually work beats one you bend your business to fit. The failure data above is not an argument against building. It is an argument for building properly.
Should you build or buy?
Answer this honestly before anything else. It is the decision that determines whether the project succeeds.
Buy an off-the-shelf ERP if…
- Your processes are reasonably standard for your sector
- You are willing to change how you work to match the software
- You want to be live in months rather than a year
- You can live with licence costs that scale with headcount
- Nobody internally has the capacity to own a build
Odoo, NetSuite, Sage, Dynamics 365 and Microsoft Business Central all exist for good reasons and solve real problems well. For a large share of UK businesses they are the correct answer.
Build custom if…
- The thing that makes you competitive is a process no product supports
- You have tried to configure a product and ended up with a mess of workarounds, spreadsheets and manual steps around it
- Licence costs for a product you only half use have become indefensible
- You need to own the system because it is genuinely strategic
- You have a named internal owner and a decision-maker who can say yes
The hybrid almost nobody offers you
In practice the best outcome is often neither extreme: keep the accounting package you already run, and build only the operational layer that does not exist.
Most businesses that think they need a full ERP actually need three integrations and one custom module. That costs a quarter of a full build and carries a fraction of the risk. We will tell you when that is your situation, and it is more often than the industry admits.
Why ERP projects go over budget
The Panorama 2026 data names the causes, and they are not technical.
| Cause | Share of over-budget projects |
|---|---|
| Additional technology needed, discovered after the project began | 54.9% |
| Scope grew beyond the original plan | 51% |
Read that first line again. The single biggest cause of ERP overruns is discovering mid-project that something else needs buying or building. That is a discovery failure, and it is preventable.
Beyond the survey data, the failure modes we see repeatedly:
Data migration was treated as a task, not a project. Moving 40,000 clean records is a day. Moving 40,000 records where the same customer exists four times under three spellings is weeks. This is routinely underestimated by an order of magnitude.
The old process was automated instead of improved. If a process is broken, encoding it in software makes it permanently broken and expensive to change. ERP projects are the right moment to fix the process — but only if someone has authority to change it.
Nobody owned it. ERP touches every department, so it belongs to none of them. Without a single named owner with authority, decisions stall and the timeline doubles.
Training was the last line of the budget. The best system in the world fails if the warehouse carries on using the spreadsheet. Adoption is the deliverable, not go-live.
Go-live was a single event. Switching everything over on one weekend concentrates all the risk into 48 hours. Phased cutover costs more and fails less.
Source: Panorama Consulting 2026 ERP report (170 organisations, January 2025 – January 2026), reported via secondary sources; Gartner projection on ERP business-case goals through 2027. Figures measure different things and we cite them as directional rather than as a single comparable failure rate.
Signs you have outgrown your current setup
Not a sales list. These are the specific symptoms that indicate the problem is now structural.
- The same number lives in three systems and they disagree. Somebody reconciles them manually, and everyone quietly distrusts all three.
- One spreadsheet runs a critical process and one person understands it. When they are on leave, the process stops.
- Your month-end takes more than a few days. Usually because data is being assembled by hand.
- You cannot answer a simple question quickly. “What is our actual margin on this product line?” should take seconds, not a day.
- Staff retype data between systems. Every retype is an error waiting to be found three weeks later.
- Growth means hiring administrators, not makers. Headcount rising faster than output is a systems failure, not a staffing one.
Two of these is a sign. Four is a business case.
What we build
Full operational ERP — stock, purchasing, production, orders, fulfilment, job costing and reporting in one system, built around how you actually work.
The operational layer on top of existing accounting — the hybrid above. You keep Xero, Sage or QuickBooks; we build what sits over it and integrate properly. The most common thing we actually ship.
Replacing the spreadsheet estate — turning the critical spreadsheets into a system with proper permissions, history and validation, without losing the flexibility people liked about the spreadsheets.
Integration between systems you already run — making existing software agree with itself. Frequently the highest return per pound of any work on this page.
Customer and supplier portals — self-service for order status, documents and stock, taking volume off the phone.
Reporting that people trust — one source of truth, with the calculation visible so nobody has to take a number on faith.
What custom ERP costs in the UK
| Scope | Typical range | Duration |
|---|---|---|
| Discovery & process mapping | £6,000 – £15,000 | 2–4 weeks |
| Operational layer over existing accounting | £25,000 – £60,000 | 8–16 weeks |
| Mid-size custom ERP | £60,000 – £150,000 | 20–36 weeks |
| Large / multi-site ERP | £150,000 – £400,000+ | 9 months+ |
| Data migration | £5,000 – £30,000 | Quoted separately, always |
| Support retainer | From £1,200/month | Ongoing |
Data migration is quoted separately and deliberately. Bundling it into a project price means guessing, and guessing wrong on migration is how projects go 50% over. We quote it once we have seen the actual data, not before.
What drives the number
UK contract rates set the floor. ITJobsWatch reports a median advertised day rate of £525 for UK software developers in the six months to 1 October 2026, with London 15–30% higher. Divide any ERP quote by its weeks, then by five, and you will see what day rate it implies and how many people it assumes.
Beyond rates, three things move an ERP price more than the feature list: how many external systems must be integrated, how clean the data is, and how many people must approve decisions.
How we work on ERP
Stage 1 — Process mapping (2–4 weeks). We document how the business actually runs, not how the org chart says it runs. This stage regularly uncovers processes nobody had written down, and occasionally two departments solving the same problem differently.
Stage 2 — Build or buy recommendation. A written recommendation, including the option of not hiring us. If a configured product fits, we say so and name it.
Stage 3 — Phase one build. The highest-pain area first, live and in use, before anything else starts. You get value in months rather than at the end.
Stage 4 — Data migration, run repeatedly. Migration is rehearsed multiple times against real data with reconciliation reports you can check, not performed once on go-live weekend.
Stage 5 — Parallel running. The new system runs alongside the old one until the numbers match. Nobody switches off anything on faith.
Stage 6 — Phased cutover and training. Department by department. Training built into the rollout, not appended to it.
Handover. Source code, documentation, migration scripts and infrastructure in your accounts. All IP assigns to you on final payment.
Risks, named
Migration runs long. Mitigated by quoting it separately after inspecting the data, and rehearsing it repeatedly.
Scope grows — 51% of over-budget projects in the Panorama data. Mitigated with phase-one boundaries agreed in writing and a change process that prices every addition before it starts.
Something unexpected needs buying — 54.9% of over-budget projects. Mitigated by testing every integration during discovery rather than assuming the API works.
Adoption fails. Mitigated by involving the people who will use it during process mapping, and treating training as a deliverable.
Key-person dependency on your side. Mitigated by documenting processes as we map them, which has value even if the project never proceeds.
Supplier dependency. You hold the source, the documentation and the migration scripts. The system runs in your accounts. Ask every ERP supplier you speak to whether that is true of their offer — for many it is not.
What you get at handover
Specified, because ERP is the system your business runs on and dependency here is expensive.
- Source code, in a repository you own, from week one
- Documentation — architecture, deployment, configuration, integration specifications
- Migration scripts, so the work is repeatable and documented
- Reconciliation reports from every migration rehearsal
- Infrastructure in your accounts, on your billing, on your keys
- Training materials produced during rollout, not after
- All IP, assigning on final payment
Ask every ERP supplier whether that is true of their offer. For many it is not — a common and entirely legal arrangement is that the supplier owns the system and licences it to you, which means leaving means replacing.
Who we build ERP for
Good fit: UK organisations roughly 10–250 staff with physical operations — stock, production steps, multi-step fulfilment, or document-heavy compliance. A named internal owner, a decision-maker who can say yes, and a budget from £25,000 for an operational layer.
Sectors where custom ERP most reliably beats configuration:
- Manufacturing — batch traceability, bills of materials with versions and substitutions, yield and wastage through production steps
- Wholesale and distribution — multi-location stock with real allocation rules, customer-specific and contract pricing, EDI with large customers
- Construction and trades — job costing, subcontractor management, certificate and compliance tracking
- Logistics — delivery reconciliation, exception handling, customer-facing status
Sector detail, including the UK-specific requirements →
Frequently asked questions
What is ERP software development?
Building a system that unifies the core operational functions of a business — stock, orders, purchasing, production, invoicing and reporting — so there is one place where the numbers agree. Custom development means building it around your processes rather than configuring a product and adapting to it.
How much does a custom ERP cost in the UK?
An operational layer over existing accounting runs £25,000–£60,000. A mid-size custom ERP runs £60,000–£150,000. Large multi-site systems run £150,000–£400,000 and up. Data migration is quoted separately after we have seen the data.
How long does an ERP implementation take?
An operational layer takes eight to sixteen weeks. A mid-size custom ERP takes twenty to thirty-six weeks. Large multi-site builds take nine months or more. Anyone quoting a full ERP in six weeks is describing a configuration, not a build.
Is custom ERP better than Odoo, NetSuite or SAP?
Not inherently, and often not. Off-the-shelf ERP is faster, cheaper up front and already tested at scale. Custom is better when the process that makes you competitive is one no product supports, or when you have ended up with a product surrounded by workarounds. We give a written build-or-buy recommendation before any build is proposed.
Why do ERP projects fail so often?
The Panorama 2026 data points at scoping: 54.9% of over-budget projects needed technology discovered after the start, and 51% saw scope grow. The rest are usually migration underestimated, adoption neglected, or no single owner with authority.
What about data migration?
Quoted separately after inspection, rehearsed multiple times with reconciliation reports, and run in parallel before anything is switched off. It is the most underestimated line in every ERP project.
Can we keep Xero or Sage?
Usually yes, and often you should. Building the operational layer on top of accounting you already run is the most common and lowest-risk thing we ship.
Do we own the ERP system?
Yes. All IP assigns on final payment, including source code, documentation and migration scripts, with everything running in your accounts.
What happens if we grow or change?
You hold the code, so changes do not require our permission. Most clients take a retainer for ongoing changes; some take it in-house. The documentation is written so the second option is realistic.
Do you work with manufacturing and wholesale?
Yes — operations-heavy sectors with physical stock, production steps and multi-step fulfilment are where custom ERP most often beats configuration.
The first phase
Whatever the eventual scope, phase one should be narrow, live and in use within months.
Pick the highest-pain area, not the most complete one. Usually that is stock accuracy, goods-in reconciliation, or whatever the critical spreadsheet does. Ship it, use it, then expand.
Why this matters more than it sounds: a project delivering value at month four behaves completely differently from one delivering at month fourteen. People engage with software they are using. Requirements get sharper because they are informed by something real rather than imagined. And if the project has to stop for commercial reasons, you have a working system rather than a half-finished one.
It also contains the risk. 51% of over-budget ERP projects saw scope grow. A phase with a written boundary is the mechanism that stops that, because additions land in the next phase rather than the current one.
Next step
A 45-minute call. We will ask what breaks most often, what month-end costs you, and whether a product would fit. If the honest answer is Odoo or Business Central, you will hear that.
Written by Jas Singh, Founder. Last updated 8 October 2026.
Figures from the Panorama Consulting 2026 ERP report (170 organisations, January 2025 – January 2026) as reported by secondary sources, Gartner projections on ERP business-case outcomes through 2027, and ITJobsWatch UK contract data for the six months to 1 October 2026.
