Bespoke software: cost, timelines and when it is worth it
Bespoke software is written around your own business rules instead of making you adopt a vendor’s. This guide covers when that pays off, what it costs in the UK and what the contract should say. If you are ready to commission one, the service is on the bespoke software development page.
By Soulaimane Echemmali, updated
The short answer
- Bespoke makes sense when the process sets you apart from competitors, or when no packaged product covers it without workarounds. For accounts, payroll or email, buy a standard product.
- A first production release costs £11,000 to £34,000, with a median near £25,000, across 12 UK estimates from one London firm; a production web platform runs £25,000 to £60,000 (Magora, 2026).
- A first production release takes 6 to 14 weeks in the figures below. A fully bespoke ERP takes 9 to 18 months.
- After delivery, maintenance is a yearly cost: one London firm publishes a retainer from £1,000 a month, and a bespoke ERP costs 15 to 25% of its build price each year.
What is bespoke software?
It is software built for one company, from that company’s rules: how prices are worked out, who signs off what, how the shop floor is scheduled, how jobs are tracked. Off-the-shelf software is the opposite: one product sold to thousands of customers and adjusted through settings.
In a manufacturing or distribution SME it is rarely one big system. It is a set of focused tools: bespoke software that replaces a shared spreadsheet, a customer portal, a quoting tool, a bespoke CRM. They plug into the ERP you already run instead of replacing it.
Heavy customisation of a packaged product is not the same thing. If the vendor can drop your change in the next release, you do not own it. You depend on it.
Bespoke vs off-the-shelf software
The question is not which is better, but for which process.
| Situation | Off-the-shelf | Bespoke |
|---|---|---|
| Accounts, payroll, invoicing, email | The right choice: the rules are the same for everyone and the vendor tracks the regulations. | Avoid: you would pay for every change in the law. |
| A process that sets you apart (quoting, product configuration, scheduling) | Forces you to work like your competitors, or to keep spreadsheets on the side. | The right choice: the tool follows the way you work. |
| Fewer than ten users, simple need | A subscription costs less than a build. Power Apps Premium is £15.40 per user per month ex VAT (Microsoft). | Rarely pays back. |
| Many outside users (customers, distributors) | Per-user licences push the bill up. | No cost per user. |
| The need is still unclear | Lets you learn cheaply. | Too early: settle the process first. |
| Tight link to an older ERP | Connectors limited to what the vendor planned. | Adapts to the format of your data. |
Bespoke software cost by size of project
Few UK firms publish prices. Magora, a London software house, publishes both its price bands and figures from 12 client estimates made between July and October 2026. They give a usable scale.
| Project | Price | Timeline | Source |
|---|---|---|---|
| Discovery before the build | £1,200 to £3,600 | Not stated | Magora, 12 estimates |
| First production release | £11,000 to £34,000, median about £25,000 | 6 to 8 weeks | Magora, 12 estimates |
| Production app or web platform | £25,000 to £60,000 | 3 to 6 months | Magora price bands |
| Regulated or integration-heavy product | £80,000 to £120,000 | 5 to 8 months | Magora price bands |
| Bespoke business application | From £13,000 ex VAT | 8 to 14 weeks | Vernline |
| Fully bespoke ERP for an SME | €150,000 to €800,000 (French market, in euros) | 9 to 18 months | Cegid, 2026, in French |
Day rates explain much of the spread. The median contract developer rate in the UK was £500 a day in the six months to 11 November 2026, from 3,484 quoted rates (IT Jobs Watch). Magora reports an effective £520 to £570 per developer-day once testing and product ownership are included.
What drives the price: the number of screens and roles, the calculation rules, the links to the ERP (reading data costs less than writing it) and the migration of existing data. If the starting point is a spreadsheet, see our guide on moving from Excel to a web app.
How long does it take?
- Six to fourteen weeks. For a first version that people use, as the table above shows: 6 to 8 weeks in Magora’s estimates, 8 to 14 when an audit and a specification are counted.
- Your availability sets the pace. The timeline depends less on the code than on access to ERP data, answers to questions about rules, and sign-off on each delivery.
- A delivery every two weeks. Ask for one on a test environment. A project cut that way shows a delay at the second delivery, not in month six.
- Budget in stages. Magora notes that a second phase usually adds 30 to 70% of the first release.
Who owns the code?
Whoever the contract names. Paying for the work does not by itself make the code yours: the contract has to say so. Ask for these four things in writing, and have your solicitor check the clause.
- A written assignment of the rights in the code, effective on payment.
- The code repository opened in your company’s name, with access from the start of the project.
- Hosting, domain and third-party service accounts in your name.
- Enough documentation for another supplier to take the software over.
Running costs after delivery
| Item | Typical cost | Source |
|---|---|---|
| Maintenance retainer, London software house | From £1,000 a month | Magora, 2026 |
| Maintenance of a bespoke ERP | 15 to 25% of the build cost a year | Cegid, 2026 |
| Second phase | 30 to 70% of the first release | Magora, 12 estimates |
| Changes | Quoted on request: set an annual budget | Agree in the contract |
Software with no maintenance keeps working, then ages: security updates, a new ERP version, new needs. Always compare a subscription and a bespoke build over three to five years, maintenance included.
Choosing a supplier and reducing the risks
Bespoke projects rarely fail on technology. They fail on scope, on dependence and on late surprises. The risks are known, and a well-written contract reduces each of them.
| Risk | What the contract should provide |
|---|---|
| Vague scope, budget overrun | A written specification before the build, then a fixed price per stage. |
| A delay discovered too late | Dated interim deliveries on a test environment. |
| Dependence on the supplier | Code, accounts and documentation in your name; maintenance with no lock-in. |
| Software delivered but unusable | Acceptance testing by your users before each payment, and a fixing period after go-live. |
| Exposed data | Hosting location stated in the contract and a data-processing agreement signed before any access to real data. |
To choose, ask to see a specification the supplier has already written, not only screenshots. Check who actually writes the code. And start small: an audit and a first module are a safer bet than a year-long commitment.
Frequently asked questions
How much does bespoke software cost in the UK?
A first production release costs £11,000 to £34,000, with a median near £25,000, according to 12 estimates published by Magora. A production web platform runs £25,000 to £60,000.
How long does bespoke software take to build?
Six to fourteen weeks for a first useful version in the figures above, and 9 to 18 months for a fully bespoke ERP according to Cegid. The pace depends mostly on access to your data and on how quickly your team signs off each delivery.
Will bespoke software work with our ERP or accounts package?
Yes, if the system offers an API, file exports or an accessible database. Check that first, before any quote.
Who owns the software once it is delivered?
Whoever the contract names. Ask for a written assignment of the rights in the code, effective on payment, and for the repository and all accounts in your name.
What happens if the supplier goes out of business?
If the code, the accounts and the documentation are in your name, another supplier can take the software over. That is the reason to insist on them from day one, and to prefer widely used technologies.
Bespoke or off-the-shelf: how do we decide?
Buy a standard product for what every company does the same way, and build bespoke for the process that sets you apart. If a packaged product covers 80% of the need without workarounds, it is the better choice.
Read next
- Service
Bespoke software
An internal tool in place of spreadsheets: production, costing, planning, quality. from £13,000 - Service
Web application development
An online application for your customers or partners, from the first version onwards. from £13,000 - Guide
From Excel to a web app
Many companies run at least one process on a spreadsheet that was never meant to carry it. - Service
Audit
A review of the website, the tools and the manual tasks, with a costed roadmap. fixed price £1,650
Start with a fixed-price audit
In one to two weeks you know what to build, in what order and in what price range. The audit fee is deducted from the first project we build for you.
£1,650 ex VAT 1 to 2 weeks See a sample report