Bespoke ERP Software UK: Who Builds It Without User Fees?
What does bespoke ERP software really cost a UK business? Explore build prices, ongoing costs, software ownership and off-the-shelf alternatives, with practical examples for wholesalers, manufacturers and growing SMEs. Understand what to include in your brief before requesting a quote.
If you would rather buy a packaged product, Microsoft Dynamics 365 Business Central charges per user (from £61.50 a user a month, paid yearly), while ERPNext is open source and can be self-hosted, with its own cloud hosting priced per site rather than per user. Bespoke suits businesses whose stock, order or production rules do not fit a package; a packaged ERP suits businesses whose processes match standard patterns and who want a vendor roadmap.
Bespoke ERP software UK projects start with a simple idea: instead of adapting your operation to a packaged product, you commission a system built around your own orders, stock, production and finance handoffs. Done well, it gives one set of records that matches how the business actually runs. Done badly, it gives an expensive application that only its original developer understands.
The practical problem is that most of the risk sits outside the code. Unclear scope, an ownership clause nobody read, hosting that sits in the supplier’s account and a support arrangement that was never priced can all turn a sensible build into a dependency. This guide covers the commissioning decisions a UK business should settle before work starts: when bespoke fits, how to scope it, who owns what, where it runs, how it is supported, how to phase delivery and how to model the total cost. If you are still deciding who should build it, start with our bespoke software development UK guide on supplier types, quotes and the checks to make before you sign.
Scoping a bespoke ERP starts with the real workflows, exceptions and handoffs. Illustrative photograph, not an OpsMavix project.
Image credit: Daria Nepriakhina, Unsplash License. No edits.
Who Builds Bespoke ERP Without Per-User Fees? Facts Compared
Every fact below was checked on the supplier’s own page on 30 October 2026. A dash means the page did not state it, so check it directly before you rely on it.
| Option | Type | Price from | User or seat fees | Build or setup time | Code and data ownership | Integrations named |
|---|---|---|---|---|---|---|
| OpsMavix (checked 30 Oct 2026) | Bespoke build, fixed price in writing | One area from £4,950; each further area from £2,500; whole operation from £25,000 | No per-seat fees | Live in 30 days per area | “You own the code, data and hosting” | Shopify, Xero, QuickBooks, Stripe, WooCommerce, Sage |
| Elsio (checked 30 Oct 2026) | Bespoke ERP, fixed price after discovery | No price list published | “No per-user licence fees” | 20 to 30 weeks for core ERP; 9 to 18 months for full enterprise ERP | “Full data ownership and portability”; its custom software page states full ownership of code, data and IP | Xero, Sage, QuickBooks |
| Dynamics 365 Business Central (checked 30 Oct 2026) | Packaged ERP subscription | Essentials £61.50, Premium £84.60, Team Members £6.20 per user a month, paid yearly, ex VAT | Per user | - | - | - |
| ERPNext (checked 30 Oct 2026) | Open-source packaged ERP (GPL-3.0) | Free to self-host; Frappe Cloud hosting from $5 a month per site; implementation extra | “Not per user” | - | Open-source code you can host yourself | - |
What the table means for a 20-person business
Licence fees are where the models split. As a hypothetical illustration using only Microsoft’s list prices above: 20 users on Business Central Essentials cost 20 x £61.50 x 12 = £14,760 a year, or £73,800 over five years before VAT, implementation or partner support. On Premium the same five years cost £101,520. A bespoke build or self-hosted ERPNext has no per-user line, but you pay for the build or implementation, hosting and support instead, so model both on the same five-year basis (section 7 below shows how).
Where OpsMavix Fits
OpsMavix builds owned operations systems and bespoke ERP for UK product businesses: wholesale, distribution, ecommerce and manufacturing. These facts are taken from the OpsMavix homepage as it stood on 30 October 2026:
- Fixed price in writing before the build. Start with one area from £4,950 (inventory, orders, production, marketplace sync, purchasing or finance), add each next area from £2,500, or build the whole operation, up to a full ERP, from £25,000.
- Pay half to start, half only when it’s working.
- Live in 30 days per area, built in checkpoints you sign off.
- You own it outright: the code, data and hosting, with documentation and exports in a handover pack. No lock-in and no per-seat fees.
- Works with the tools you have: Shopify, Xero, QuickBooks, Stripe, WooCommerce and Sage are listed, and exactly what connects is mapped on a free 30-minute call before anything is promised.
Where it does not fit: if your processes already match a packaged ERP and you want a vendor roadmap and a large partner market, Business Central or a similar product is the more natural choice. If you have in-house technical skills and want the lowest licence cost, self-hosted ERPNext is free to run, although Frappe says it does not provide implementation itself. For the stock side specifically, see our inventory automation system page.
Key Takeaways
- Bespoke ERP fits when essential workflows are poorly served by configured packaged software, not simply because a business feels unusual.
- A written first-release scope with acceptance tests matters more than a long feature list.
- Under UK copyright law, a contractor usually owns the code it writes unless rights are assigned in a signed written agreement.
- Hosting accounts, repositories, domains and data exports should be in your name or fully accessible to you.
- Support, maintenance and exit terms need a price and a named owner before the build starts.
- Compare bespoke and packaged options on the same five-year cost model and the same test scenarios.
In this guide:
- 1. Decide Whether Bespoke ERP Fits Your Business
- 2. Write a Scope Before You Ask for Quotes
- 3. Deliver in Phases With Acceptance Tests
- 4. Choose Hosting and Protect Your Data
- 5. Settle IP and Source Code Ownership
- 6. Agree Support Maintenance and Exit Terms
- 7. Model the Total Cost Over Five Years
- 8. Compare Suppliers on the Same Brief
- Frequently Asked Questions
- How OpsMavix Can Help
1. Decide Whether Bespoke ERP Fits Your Business
Start from the gap, not the label
ERP connects business processes and their records across functions such as sales, purchasing, stock, production and finance. Bespoke describes how the software is made, not how much it covers. A bespoke build can be a focused order and stock application or a full ERP that replaces several systems.
Packaged ERP deserves a fair hearing first. Microsoft, for example, positions Dynamics 365 Business Central for small and midsize businesses, with industry solutions for areas including wholesale distribution, manufacturing and construction. Products like this bring established finance, supply chain and reporting functions, a vendor roadmap and a partner market. For many UK SMEs, configuring one well is the right answer.
Bespoke becomes more compelling when the work that matters most to your margin or service level remains a workaround after configuration: unusual allocation rules, complex unit conversions, job-specific costing or customer commitments that the packaged process cannot represent cleanly.
Compare the realistic approaches
| Approach | When it tends to fit | Main limitation | What to check |
|---|---|---|---|
| Configure current tools | The control you need already exists but is not switched on or used | Limited by the product and edition you already pay for | Settings, permissions and training gaps |
| Integrate existing systems | Each tool works but handoffs fail between them | Two or more systems still need maintaining | Record ownership, error handling, monitoring |
| Packaged ERP | Your processes broadly match established patterns | Changes follow the vendor roadmap and extension rules | Fit on your hardest scenarios, licence model, partner capacity |
| Focused custom application | One valuable workflow has clear boundaries | Covers only the agreed area | Integration with finance and future expansion |
| Full bespoke ERP | Core workflows are distinctive and central to the business | You carry responsibility for maintenance and change | Ownership, support, documentation and continuity |
Signs bespoke is worth investigating
- Staff re-key the same order, stock or job data into two or more systems every day.
- A packaged demo handles the normal case but not your three most common exceptions.
- Essential rules live in one person’s head or a spreadsheet that only they maintain.
- Licence costs grow with headcount for users who only need one or two screens.
- Reporting is assembled by hand because no single system holds the full picture.
If you are still deciding whether you need ERP at all, our guide to spreadsheets vs OpsMavix vs ERP compares the middle options.
2. Write a Scope Before You Ask for Quotes
Describe outcomes and exceptions
Suppliers can only price what you describe. “A complete ERP” means different things to different people, so quotes for it are not comparable. A useful scope describes the business events the system must handle, the people who act on them and the exceptions that cause rework today.
Write each requirement so someone can test it. “Better stock visibility” is a goal. “When a sales order is confirmed, available stock is reserved by location and any shortage appears on the purchasing list with the order reference” is a requirement.
Scope checklist
- Processes in scope: the workflows the first release must run end to end.
- Processes out of scope: what stays in current systems for now.
- Records and owners: which system creates customers, products, orders, invoices and stock movements.
- Business rules: pricing, approvals, allocation, units of measure and credit holds.
- Exceptions: partial deliveries, cancellations, returns, substitutions and corrections.
- Integrations: accounting, ecommerce, carriers, EDI or payroll, with direction and timing.
- Data migration: which open and historical records move, and who cleans them.
- Users and roles: who can view, create, approve and correct each record.
- Reporting: the decisions each report supports and its definitions.
- Non-functional needs: availability, backup, response times and audit history.
Separate discovery from build
A short paid discovery phase can turn a rough brief into a priced scope, process maps and a delivery plan. Ask whether the discovery outputs belong to you and could be given to another supplier. That keeps the build decision open rather than tying you in at the first meeting.
3. Deliver in Phases With Acceptance Tests
Make each phase usable on its own
Phased delivery limits the initial commitment and lets you check value before spending more. The rule is that each phase must run a complete workflow, not deliver half of several. A first phase that handles order entry, allocation and dispatch for one site is useful. One that delivers screens for every module without a working process is not.
| Phase | Hypothetical scope | Acceptance evidence | Decision at the end |
|---|---|---|---|
| Discovery | Process maps, scope, data review, delivery plan | Signed scope and test scenarios | Proceed, change scope or stop |
| Phase 1 | Orders, allocation, picking and dispatch for one site | Real orders run end to end with exceptions | Go live, fix or pause |
| Phase 2 | Purchasing, goods receipt and accounting integration | Receipts and invoices reconcile to finance | Expand to further sites |
| Phase 3 | Production jobs, reporting and further sites | Job costs trace to orders and receipts | Plan ongoing change budget |
Write acceptance tests before the build
Agree the scenarios that prove a phase works before development starts. Include normal cases and hard ones: a short delivery, an order changed after picking starts, a credit note and a failed transfer to accounting. Name the person who signs off each scenario.
Ask how you will see working software during the build, for example through a test environment you can use every few weeks. Reviewing real screens early is cheaper than discovering a misunderstanding at go-live. For the UK-specific timing of go-live around VAT periods and payroll, see our ERP implementation UK guide.
Phase checklist
- Each phase has a written scope, test scenarios and a named approver.
- Shared records such as customers and products are designed once for all phases.
- Data migration for the phase is rehearsed and reconciled before go-live.
- Users are trained on their real daily tasks, not a general tour.
- A rollback or fallback plan exists for the first days after go-live.
- Lessons from each phase feed into the scope of the next.
4. Choose Hosting and Protect Your Data
Decide whose account it runs in
A bespoke ERP can run in a public cloud, a managed hosting service or on your own servers. The technical choice matters less than control. If the application runs in the supplier’s cloud account, you depend on them for access, backups and continuity. If it runs in an account your business owns, with the supplier given delegated access, you can change supplier without moving infrastructure.
| Hosting arrangement | Who controls the account | Main benefit | Main risk |
|---|---|---|---|
| Your own cloud account | Your business | Full control and easier supplier change | You must manage billing and access rights |
| Supplier-managed in your account | Your business, supplier administers | Expert operation with your ownership | Access rules must be clear and reviewed |
| Supplier’s own account | Supplier | Simple to start | Continuity and exit depend on the supplier |
| On-premises servers | Your business | Physical control | Hardware, patching and backup are your job |
Use recognised security questions
The NCSC publishes 14 cloud security principles, covering areas such as data in transit protection, separation between customers, secure development, supply chain security and identity and authentication. They give a practical structure for questioning both the hosting provider and the developer.
Treat the developer as a processor
If the developer or hosting provider handles customer, supplier or employee personal data on your behalf, it is likely to act as a processor under UK GDPR. The ICO lists what a controller and processor contract must include, including processing only on documented instructions, appropriate security, rules on sub-processors, and deleting or returning data at the end of the contract.
Hosting and data checklist
- The cloud account, domain and DNS are registered to your business.
- Backups run automatically, and a restore has been tested.
- You can export all data in a documented, readable format.
- Sub-processors and data storage locations are listed in the contract.
- Administrator access is personal, logged and removed when people leave.
Owning the source code is only useful if you can access, build and hand it to another developer. Illustrative photograph, not OpsMavix code.
Image credit: Chris Ried, Unsplash License. No edits.
5. Settle IP and Source Code Ownership
Know the default position in UK law
Paying for software does not by itself make you the owner of the copyright in it. Under the Copyright, Designs and Patents Act 1988, a computer program is protected as a literary work. The author is the first owner of copyright, and an employer owns work made by an employee in the course of employment, subject to any agreement to the contrary.
An external development company is not your employee, so code it writes for you will usually belong to it unless the rights are transferred. The Act says an assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor. Take legal advice on your contract; the points below are questions to raise, not legal advice.
Assignment or licence
| Option | What you get | When it can work | What to check |
|---|---|---|---|
| Full assignment of bespoke code | Ownership of the code written for you | You want freedom to maintain and change it with anyone | Signed written assignment, timing tied to payment |
| Exclusive licence | Sole right to use and modify | Supplier retains a reusable framework | Scope of use, modification rights, term |
| Non-exclusive licence | Right to use, others may use similar code | Supplier builds on a shared product | Exit rights, continuity, price changes |
| Third-party and open-source components | Use under each component’s own licence | Almost every modern application | List of components and their licence terms |
Most suppliers reuse their own libraries or tools across clients. That is normal and can lower cost. What matters is that you know which parts are assigned, which are licensed, and that the licence lets you keep running and changing the system if the relationship ends.
Ownership checklist
- The contract states who owns bespoke code, designs and documentation, and when rights transfer.
- Pre-existing supplier components are listed with a perpetual licence for your use.
- The source code repository is in your account or mirrored to it.
- You hold administrator access to hosting, domains and third-party services.
- Build and deployment instructions are documented so another developer can follow them.
- Open-source components and their licences are listed.
6. Agree Support Maintenance and Exit Terms
Price the years after go-live
Owned software still needs work. Operating system and framework updates, security patches, integration changes when a connected service updates its API, bug fixes and small improvements all continue after launch. A build price without a support arrangement is only half a quote.
| Support element | What to define | Typical question |
|---|---|---|
| Incident response | Severity levels and response times | What happens if order entry stops on a Monday morning? |
| Maintenance | Updates, patches and dependency upgrades | How often are dependencies reviewed and updated? |
| Monitoring | Integration failures and system health | Who sees a failed accounting transfer first? |
| Change requests | How new work is estimated and approved | Is there a day rate or a monthly allowance? |
| Documentation | What is updated after each change | Is the handover pack kept current? |
Plan the exit on day one
An exit plan is not a sign of distrust. It protects both sides and makes the system easier to support. Agree what a handover to another developer would include: repository access, environment details, credentials transferred securely, a data model description and a reasonable notice period.
Some businesses also consider a source code escrow arrangement where the code is held by a third party. If the code is already in your own repository and hosting is in your account, escrow may add little.
7. Model the Total Cost Over Five Years
Hypothetical worked example
The figures below are hypothetical and exist only to show the method. They are not OpsMavix prices, vendor prices or market averages. They exclude VAT. Assume a business with 20 users comparing a phased bespoke build with a packaged ERP over five years, with internal time costed at £250 a day.
| Hypothetical bespoke cost line | Basis | Five-year amount |
|---|---|---|
| Phase 1 build | Fixed quote | £40,000 |
| Phase 2 build in year 2 | Fixed quote | £25,000 |
| Hosting | £150 a month x 60 months | £9,000 |
| Support and maintenance | £600 a month x 60 months | £36,000 |
| Internal time, year 1 | 40 days x £250 | £10,000 |
| Internal time, year 2 | 15 days x £250 | £3,750 |
| Change budget, years 3 to 5 | £6,000 a year x 3 | £18,000 |
| Total | £141,750 |
| Hypothetical packaged cost line | Basis | Five-year amount |
|---|---|---|
| Subscriptions | 20 users x £70 a month x 60 months | £84,000 |
| Implementation partner | Fixed quote | £30,000 |
| Integrations and extensions | Fixed quote | £12,000 |
| Internal time | 50 days x £250 | £12,500 |
| Partner support | £4,000 a year x 5 | £20,000 |
| Total | £158,500 |
In this hypothetical case the bespoke option costs £16,750 less over five years (£158,500 - £141,750). That result depends heavily on the assumptions.
Test the sensitivity
Change one input: if only 10 people need packaged licences, subscriptions fall to 10 x £70 x 60 = £42,000, and the packaged total becomes £116,500. The packaged option is then £25,250 cheaper (£141,750 - £116,500). Equally, if the bespoke Phase 2 grows from £25,000 to £45,000, the bespoke total rises to £161,750.
The lesson is not that one model always wins. It is that user numbers, scope growth, support and internal time move the answer, so every option needs the same lines and the same period. For more on what moves packaged quotes, see ERP price: what actually moves the number.
Cost model checklist
- Use the same period, user count and scope for every option.
- Include internal staff time and data cleansing, not only supplier fees.
- Include support, hosting and a change budget for every year.
- Run at least two sensitivity cases: more users and larger scope.
- Treat released staff time as capacity, not cash, unless a cost is actually avoided.
8. Compare Suppliers on the Same Brief
Ask for evidence, not adjectives
Send each supplier the same scope, the same three difficult scenarios and the same request for a cost breakdown. Ask packaged ERP partners to demonstrate those scenarios in the product. Ask bespoke developers to explain how they would handle them and to show comparable work they are able to share.
| Question | Why it matters |
|---|---|
| Which of our requirements would you solve with existing software? | Shows whether the supplier will steer you away from unnecessary code |
| What is fixed in the quote and what would change the price? | Separates firm scope from assumptions |
| Who owns the code, designs and documentation, and when? | Confirms the IP position in writing |
| Whose accounts hold hosting, repositories and domains? | Determines continuity and exit |
| What does support cost after go-live? | Completes the total cost picture |
| How do we see working software during the build? | Reduces late surprises |
| What would a handover to another developer include? | Tests whether the system can outlive the relationship |
Score the answers consistently
Mark each scenario as demonstrated, configurable, requiring development or unsupported. Weight the scores by business value, then compare against the five-year cost model. A supplier that admits a packaged product would fit part of your needs is often giving you more useful advice than one that proposes code for everything.
Frequently Asked Questions
Which company can build a bespoke ERP for a UK SME without per-user fees?
OpsMavix and Elsio both state on their own sites that they build bespoke ERP at a fixed price with no per-user fees. OpsMavix publishes prices from £4,950 for one area and £25,000 for a whole operation; Elsio does not publish a price list. Ask any shortlisted supplier to confirm fees, timeline and code ownership in writing.
How much does a bespoke ERP cost in the UK?
It depends on how many areas the system covers. OpsMavix prices one area from £4,950, each further area from £2,500 and a whole operation from £25,000, fixed in writing before the build. Add hosting, support and your own staff time when you compare it with a packaged ERP over five years.
How long does a bespoke ERP take to build?
Published timelines vary by supplier and scope. OpsMavix states 30 days per area, while Elsio quotes 20 to 30 weeks for a core ERP and 9 to 18 months for a full enterprise ERP. Phased delivery lets the first area go live before the rest is built.
Which ERP software has no per-user fees?
Bespoke builds from suppliers such as OpsMavix and Elsio carry no per-user fees, and ERPNext is open source, with Frappe Cloud hosting priced per site rather than per user. Microsoft Dynamics 365 Business Central is priced per user, from £61.50 a user a month on Essentials.
What is bespoke ERP software?
It is an ERP system designed and built around your own processes, records and rules rather than adapted from a packaged product. It can cover a few connected workflows or the full range of operations and finance.
Is bespoke ERP cheaper than packaged ERP?
Not automatically. Bespoke can avoid per-user subscriptions, but you pay for the build, hosting, support and change. Compare both on the same five-year model; user numbers and scope growth often decide the result.
Do we automatically own the source code we pay for?
No. Under UK copyright law the author is usually the first owner, and an external developer is not your employee. Ownership transfers through a signed written assignment, or you receive rights through a licence. Check the contract and take legal advice.
Should the system be hosted in our own cloud account?
Usually that gives the most control, because you can change developer without moving infrastructure. The developer can still operate it through delegated access. Make sure backups, billing and administrator access are clearly assigned.
Can a bespoke ERP be delivered in phases?
Yes. Each phase should run a complete workflow and have its own acceptance tests. Design shared records such as customers and products early so later phases build on them.
What happens if our developer stops supporting the system?
That is why exit terms matter. If you hold the repository, hosting accounts and documentation, another competent developer can take over. Agree what a handover includes before the build starts.
Can we keep our accounting software?
Often, yes. Many bespoke systems run operations and pass invoices or journals to an existing accounting package. Define which system owns each record and how failed transfers are spotted and corrected.
Can OpsMavix build a bespoke ERP?
Yes. OpsMavix can build focused applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can map how orders, stock, production, purchasing and finance records move through your business, then help decide which parts need a bespoke system and which are better served by configuration, integration or packaged software.
That may mean a wholesale order management system, an inventory automation system, manufacturing production tracking, ecommerce inventory automation, invoice approval workflow automation or a project operations dashboard, or a full custom ERP built in phases where that fits.
Contact OpsMavix with one recent order or job that went wrong, the records behind it and the handoff that creates the most rework. We can use that evidence to define requirements and a practical pilot.
Keep reading
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.