How much does custom software cost for a UK small business?
Honest price shapes for bespoke software in the UK: what drives the cost, what each budget band typically buys, and how to get a fixed price instead of an hourly estimate.
By the Wovekit team · · 7 min read
Ask three studios how much a piece of software costs and you will get three numbers that bear no relation to each other. That is not because anyone is lying. It is because 'software' covers everything from a two-week automation to a two-year platform, and most quotes are produced before anyone has understood the process the software is meant to replace.
This article sets out how we think about cost at Wovekit, what the budget bands we publish actually mean, and how to arrive at a fixed price rather than an open-ended estimate.
What actually drives the cost
Four things move the number more than anything else.
- The number of distinct journeys. A tool that lets customers book, pay and reschedule has three journeys. Add staff views, reports and reminders and it has six. Each one needs design, build and testing.
- Integrations. Every external system (accounting software, a CRM, a payment provider, a calendar) adds work, and old systems with poor APIs add the most.
- Exceptions. The happy path is cheap. The deposit that was partly refunded, the booking moved twice, the customer with two accounts: handling these well is where the real engineering sits, and it is why off-the-shelf automation tools eventually break.
- How finished it has to be on day one. A tool for ten staff who can be trained in an afternoon costs far less than one that thousands of customers must understand without help.
Notice what is not on the list: the technology. Whether something is built in one framework or another changes the cost far less than the four factors above. Be wary of anyone who leads with the stack.
The budget bands and what they typically buy
We ask visitors to our planner to pick a band rather than a number: under £5k, £5k to £15k, £15k to £40k, and £40k and above. They are bands, not quotes, but in our experience each one tends to buy a recognisable shape of work.
Under £5k
A structured discovery: two to three weeks that end with a written brief, a clickable prototype and a phased plan with a fixed price on phase one. Or a very small, well-defined automation, for example a single intake form that creates records, sends confirmations and reminds people, where the process is already clear.
£5k to £15k
The first real process. This is the band where a spreadsheet and an inbox become a system: booking or intake, a calendar, status tracking, automatic reminders and a simple report, for one team. Three to eight weeks of work, released weekly so you are using it before it is finished.
£15k to £40k
A customer-facing product: a portal where customers sign in and do things for themselves, a web app with accounts and payments, or a mobile app for one platform-neutral codebase with the backend behind it. Typically four to twelve weeks for the web, eight to sixteen to reach both app stores.
£40k and above
Several connected journeys, more than one type of user, serious integrations or data volume, and the operational layer (admin consoles, audit trails, reporting) that lets a business run on the software rather than beside it. These are always phased; nobody should sign up to the whole thing at once.
Fixed price or hourly?
Hourly billing puts all the risk on you and rewards slowness. Fixed-price-for-everything puts all the risk on the studio and rewards cutting corners. The sensible middle is a fixed price per phase, agreed after a discovery that is itself fixed price. You know exactly what the next eight weeks cost; the studio knows exactly what it has promised; and both sides can change direction at a phase boundary without a dispute.
The costs people forget
- Running costs. Hosting, email delivery, text messages, map and AI usage. For a small-business tool these are usually tens of pounds a month, but they should be written down.
- Your own time. Someone on your side needs an hour or two a week to review releases and answer questions. Projects stall when nobody owns them.
- Change. The first month of real use always produces a list. Budget for it rather than being surprised by it.
- The cost of not building. Hours spent rekeying, chasing and apologising have a price too. Measured honestly, it is often the biggest number on the page.
How to get a number you can trust
- 1.Describe the process, not the product. 'Customers book, we confirm, we chase deposits' is far more useful than 'a booking app'.
- 2.Write down the exceptions. What goes wrong today, and how often.
- 3.Pick a band. It tells the studio which shape to propose.
- 4.Ask for a phased plan with a fixed price on phase one and running costs listed.
- 5.Make sure the code and accounts end up in your name.
Our planner at /plan walks through exactly these questions and turns the answers into a short brief. Send it, or bring it to a discovery call, and the first number you hear from us will be one we are prepared to stand behind.
Short answers.
Can you give a price without a call?
Not an honest one. We publish budget bands and the shape of each engagement, and quote the first phase at a fixed price after a short discovery. Anyone who quotes before understanding the process is guessing.
Why are quotes from different studios so far apart?
Because they are pricing different things. One includes design, hosting and a year of support; another is code only. A written brief makes quotes comparable, which is the point of discovery.
What does it cost to run afterwards?
Hosting for a small-business tool on Vercel and Railway is usually tens of pounds a month, not hundreds. Email, SMS and AI usage are metered on top. We put the running costs in the plan so there are no surprises.