Who builds bespoke business software for UK SMEs at a fixed price?
A fixed price for bespoke software works when the project is scoped first and priced in phases, because nobody can honestly fix one price for something that hasn't been defined yet. This is how We UC does it, and what to ask any supplier.

A fixed price for bespoke business software is realistic when the work is scoped first and then priced one phase at a time, and a supplier who quotes a single fixed figure for a whole custom system before anything has been defined is guessing, however firmly they say it. We UC is a UK software company that builds custom apps, CRMs, internal tools, customer portals and integrations for small and medium-sized UK businesses this way: we scope the work, then build it in fixed-price phases, and you own the code. We don't publish a Build price, because it depends on what the software has to do, so you ask and we quote.
Why can't anyone give a fixed price for a whole custom system up front?
A fixed price for a whole custom system cannot be honest up front, because the price depends on decisions that haven't been made yet, such as which screens exist, which other systems it has to talk to, and what happens to the data on the day you switch over. A quote written before those answers exist has to either pad the price to cover the unknowns or leave the unknowns out and charge for them later as changes, and neither is the fixed price you thought you were buying.
The UK government's own digital teams handle this by splitting the work up. The GOV.UK Service Manual says of its first stage that there's no set time for a discovery, but around 4 to 8 weeks is typical, and that you shouldn't build anything during it. Its next stage is an alpha, which tends to last between 6 and 8 weeks, where you try out solutions and expect to throw away much of the code. That guidance is written for public services and a small business doesn't need the same ceremony, but the idea carries over: find out what the software has to do before you commit to the expensive part.
What does "scoped first, then fixed-price phases" mean in practice?
Scoped first, then fixed-price phases means the first piece of work is working out what the software has to do and writing that down, and each stage after that has its own written scope and its own price that doesn't move once you've agreed it. If a phase turns out to need something that wasn't in the scope, that is a conversation and a new quote, and it isn't an invoice that arrives afterwards.
For a new build, that gives you a point after each phase where you can see working software and decide whether to carry on. We think that's a better deal for a business owner than one large number, because the biggest risk in a custom build is money spent on the wrong thing, and short phases limit how much can go wrong before somebody notices. A supplier with a long track record on one kind of system may be able to price a bigger block sensibly, though that depends on the system.
What should a bespoke software quote include?
A quote you can hold someone to has these parts, and a missing one is worth asking about before you sign:
| Item | What to look for |
|---|---|
| Scope | A written list of what is built in this phase, in words you understand |
| Price | One figure per phase, stating whether VAT is included |
| What's excluded | Named items that would be quoted separately, such as data migration or training |
| Integrations | Which outside systems it connects to, for example Xero or Zoho |
| Testing | Who tests it before you see it, and how |
| Ownership | The code, the repository and the hosting accounts are in your name |
| Hand-over | Written documentation, so another developer could pick it up |
Who owns the code when it's finished?
You should own the code when bespoke software is finished, and the contract should say so in writing before work starts. Our approach is that your code, your repository and your accounts are yours to keep, which also means you aren't locked in: if you decide to work with someone else on the next phase, they can read what we built. Ask any supplier the same question, because a custom system you can't move is a long-term cost that doesn't appear on the quote.
Is it better to build custom software or buy something off the shelf?
Buy off the shelf if an existing product already does what you need, because it will almost always be cheaper to start and someone else maintains it. Custom software makes sense when your process is what makes the business work and no product fits it without awkward workarounds, or when several systems have to be joined so that people stop re-typing the same data. We run products from We UC, such as Scheduler, which books field appointments for UK Zoho CRM teams with drive times by postcode, so we have some sympathy for both sides of the question.
How do we work on a build?
The main engineering team is in Southampton, with some engineers offshore in Ukraine and Eastern Europe. We use AI heavily for speed, and engineers make the decisions: an engineer reviews every change before it ships, and two QA engineers test the work before it reaches you. We also run products from We UC in production, including Olatti, a UK business phone network, and Quenta, an app that posts receipts into Xero.
If your software already exists and is the problem, the start is different. A Rescue audit reads the code and hosting, changes nothing, and gives you a written report and a priced plan, and our piece on whether to fix or rebuild a vibe-coded app covers that decision. Once the software is live, Run is the monthly retainer that looks after it.
Common questions
How much does bespoke business software cost?
We don't publish a Build price, and we'd be wary of anyone who quotes one without asking what the software has to do. Scoping comes first, then each phase has its own fixed price.
How long does a custom build take?
How long a custom build takes depends on the scope, and we can't give a number before we've seen it. The GOV.UK figures above (4 to 8 weeks for discovery, 6 to 8 for an alpha) are for government services and are a reference point only.
Can you build integrations with Xero or Zoho?
Yes, integrations such as Xero and Zoho are part of what we build, and each one is listed in the scope of the phase it belongs to.
Do you only build new software?
No. We also fix software that has gone wrong, often apps built with Lovable, Bolt, Cursor or Replit. Whoever built those got further than most people do, and the Rescue audit is £2,500 + VAT, fixed, deducted from the first phase if you go ahead with us on the fix.
If you have a system in mind, you can talk to us about a build.