How much does bespoke software cost in the UK?

In the UK, bespoke software costs anything from a few thousand pounds for one focused tool to six figures for a full platform. Most agency guides put a small business's first build at £10,000 to £50,000. A single, well-understood job, such as a quoting tool, can cost much less: our builds start at £3,000, and quoting tools usually cost £3,000 to £6,000, excluding VAT.

The build is only part of the cost. You also pay to run it, and you should compare the total with what a subscription would cost over the same years. This guide covers all of that, with the sums shown, for owners and managers of UK businesses weighing a built tool against a product. If you just want our prices and what moves them, they are on our pricing page.

There is no official price list, so the best evidence is what UK developers publish. We read about a dozen UK agency pricing guides published in 2026 (checked 8 October 2026). Their ranges disagree, sometimes by a factor of three for the same kind of project, but the pattern is clear:

• One focused tool (a quoting tool, a document generator, a simple internal app): most guides say £10,000 to £35,000. A few publish prices from about £3,000 to £8,000 for a single module.
• A reporting dashboard or an integration between two systems, such as job data into Xero: £5,000 to £50,000.
• A bespoke CRM or job-management system: £35,000 to £100,000.
• A mid-sized web application with several user types: £30,000 to £90,000.
• Large or enterprise platforms: £100,000 to £600,000 or more.

The spread is wide because "bespoke software" covers everything from one screen that prices a job to a system that runs a whole company. Agencies also price differently: some quote a fixed price, some a day rate, and some include discovery, hosting and training while others bill them separately. Treat any range, including ours, as a starting point until someone has seen your process.

A worked example from construction. A quoting tool for a contractor or supplier holds the rate library, the uplifts and minimum charges, and the rules that turn quantities into a price. It produces the branded quote, records whether it was won, and hands won work on to Xero or the job system. Built around one way of pricing, that is the £3,000 to £6,000 range. It costs more if it has to handle several pricing methods, several roles with their own approvals, or years of old quotes brought in from spreadsheets. There is more on these builds on our construction page.

Day rates are the best way to sanity-check any quote, because every fixed price is built from an estimate of days. The median UK contract day rate for a software developer is £525, based on job adverts in the six months to 8 October 2026 (IT Jobs Watch). The 10th percentile was £365 and the 90th £612. Agency day rates published in 2026 pricing guides run from about £400 to £900.

So a £3,000 build buys roughly six days of a median contractor's time (£3,000 ÷ £525 ≈ 5.7). A £6,000 build buys about 11. That is enough for one well-defined workflow. It is not enough for a system with many moving parts, which is why quotes for those run into tens of thousands.

Fixed price or time and materials? A fixed price tells you the number before work starts, and puts the risk of underestimating on the developer. Time and materials (paying for days used) can suit work that genuinely can't be specified up front, but the total is open-ended. For a small business, a fixed price per stage is usually the safer buy. That is how we quote: in stages, each at a fixed price, so you can stop at any point.

Five things decide most of the price. They are the same five we use, set out in more detail on our pricing page:

1. How many workflows. Automating one job, such as producing a quote, sits at the bottom of the range. Quoting plus enquiry tracking plus document generation is three pieces of work.
2. How many systems it connects to. A tool that stands alone is simpler than one that reads and writes to your accounts, CRM and file storage.
3. Who uses it, and how differently. The cost comes from the number of rules, roles and approval steps, not the number of people.
4. Whether history comes with it. Starting fresh costs nothing extra. Cleaning up ten years of past quotes is its own piece of work.
5. How settled the process is. If the rules live in one person's head, some of the work is writing them down first.

The very large numbers in agency guides usually come from things a first build rarely needs: native mobile apps for iPhone and Android, regulated platforms, or replacing a whole company system in one go.

How to keep it small: pick the one job that costs you the most time, build that, and use it for a while before deciding what comes next. A first build that does one thing well is cheaper, quicker to get into use, and tells you more about the next step than a big specification written up front.

Every tool that runs on the web needs four things after it goes live: hosting, security updates, fixes, and small changes as your business changes. Some suppliers bill these separately; others bundle them into a monthly plan. Ask for the running cost in writing before you agree the build: over five years it can add up to more than the build itself.

Our running costs are care plans. Every build includes 30 days of support after go-live, and the plans are optional after that:

• Care, £250 a month: hosting, updates, backups and fixes, 2 hours of new development a month, and replies within 2 working days.
• Care Plus, £750 a month: the same, with 10 hours of new development a month and replies within 1 working day.
• Partner, £1,500 a month: the build is included and paid for through the monthly fee, with 16 hours of new development a month and replies within 4 working hours. The minimum term is 12 months.

All prices exclude VAT. Also budget for anything the tool pays other companies for: an AI model billed by use, a paid tier of another system's connection, or a mapping or email service. These are usually small for one tool, but they are real, and a good supplier lists them before you start.

Off-the-shelf software is a product built for many businesses and usually rented per user per month, such as Xero, Tradify or a CRM. Bespoke software (also called custom software; the two terms mean the same thing) is built for one business, around how that business already works.

The honest default is to buy. If a product does the job without workarounds, it will be cheaper, ready today, and maintained by someone else. A product stops being the cheap option when you keep a side spreadsheet to work out the number you then type into it, or when its idea of a quote, a job or a report isn't yours. Our guide to construction estimating software lists the signs in detail.

It is rarely all or nothing. A bespoke tool often sits alongside a product rather than replacing it. A quoting tool holds your rates and pricing rules, and the won job goes to Tradify or Xero as before. You keep the product for what it does well and build only the part it can't do. There is more on how that works on our custom software page.

It depends on your team size and how long you'll use it. Our estimating software guide compared five users over three years, and at that size the products were cheaper. Here is the same comparison extended to bigger teams and a five-year view, so you can see where the lines cross.

Users	Tradify 3 years	Tradify 5 years	Cheaper option
5	£6,660	£11,100	Tradify over both
8	£10,656	£17,760	Tradify over 3 years; level with a £3k build over 5
10	£13,320	£22,200	Between the two builds over 3 years; dearer than either over 5
15	£19,980	£33,300	Dearer than either build
20	£26,640	£44,400	Dearer than either build

Your version: (price per user per month) × (users) × (months), plus any setup fee. Compare it with the build price plus the running cost for the same months.

Where the lines cross. Over five years, the £3,000 build matches Tradify Pro at 8 users (£17,750 against £17,760), and the £6,000 build falls between 9 users (£19,980) and 10 users (£22,200). Over three years the crossover is later: about 9 users for the £3,000 build (£11,988) and 11 to 12 users for the £6,000 build (£14,652 at 11, £15,984 at 12). Below roughly 8 to 10 users over five years, the subscription is the cheaper way to pay.

Read the example with four caveats:

• Tradify does far more than quote. It schedules jobs, invoices and records time. If you would keep it for those, building a quoting tool adds to your costs rather than replacing a subscription. Then the question is whether the hours saved on quoting pay for the build.
• Unlimited-user plans don't cross over. Some products charge a flat monthly fee whatever your headcount, so the per-user argument doesn't apply.
• The care plan level matters. Care Plus at £750 a month is a different service, with five times the development hours, and changes the sums a lot.
• The biggest cost isn't on either invoice. It is the time each quote takes. Work out quotes a week × hours per quote × the hourly cost of the person quoting, and set that against both options.

In one way, yes. AI assistants and agents are only as useful as the business rules and data they can reach: your rates, uplifts, pricing rules and job history. Without them, they give generic answers.

Products are adding AI features of their own. If a product fits how you work, its AI will usually fit as well. If your pricing lives in workarounds and a side spreadsheet, neither the product's AI nor a general assistant can see it. A system built around your own rules holds them in one place, which gives an AI tool something reliable to work from.

Our guide to AI for business covers why AI gives generic answers about your business, and what it takes to connect it to your systems safely.

Paying for software doesn't make it yours. Under the Copyright, Designs and Patents Act 1988, the author of a work is the first owner of the copyright (section 11). Work by an employee belongs to the employer, but a developer or agency you hire isn't your employee. Unless the contract says otherwise, they own the code they write, and you may only have a right to use it. A transfer of copyright only counts if it is in writing and signed by the owner (section 90(3)). Without that, you could end up asking a court to decide what was implied.

So whoever you hire, get these in writing before work starts:

• Who owns the code, and who owns the data in it.
• Where it is hosted, and in whose name.
• What you get if you stop working together (code, data, hosting details), in what form, and how quickly.
• Whether it is built on a mainstream framework another developer could pick up, and whether it is documented.

Our answer to the third question: if you leave the care plan, we hand over the code, the data and the hosting.

Lock-in runs both ways. With a product, the vendor sets the price and decides what gets built next, so check you can export your data in a usable form. With a bespoke tool, you control what it does, but you need someone able to maintain it, so the handover questions above matter.

Overruns are the other fear, and they usually come from big, loosely specified projects. The protection is a written specification, a fixed price for each stage, and changes quoted before they are built, not billed after.

Often, but how depends on your business. This is general information, not tax advice.

• Capital allowances. HMRC treats computer software as plant (CA23410), so capital spending on a build can qualify for capital allowances, including the Annual Investment Allowance, which is £1 million (GOV.UK).
• Companies have an extra step. For companies, the intangible assets rules normally come first for software. Capital allowances apply only in certain cases, including where the company elects to use them (CA23410). Your accountant will know which route suits you.
• R&D relief usually doesn't apply. HMRC says routine adaptation of an existing product or process is not R&D (CIRD81960). A quoting tool built with standard technology around your pricing rules is the routine kind. Be wary of anyone who says R&D relief will pay for your build.
• Subscriptions are normally treated as a running cost of the business. Your accountant can confirm.

Check with your accountant before you count on any relief.

It is worth it when three things are true: a product makes you work around how you actually do the job, the job takes real hours every week, and you can describe how it should work. A quick test:

1. Try a product on an awkward job you did last month. If it handles it without a side spreadsheet, buy the product.
2. Work out the hours: jobs a week × hours per job × the hourly cost of the person doing it.
3. Compare a year of those hours with the build price plus a year of running costs. If the hours cost more, a build is worth pricing properly.

For one client, a UK specialist supplier, quoting went from about 1 to 2 hours to about 5 minutes per quote, and the whole team can now quote. That is one client's result; yours depends on how you price.

When bespoke is the wrong choice: your quotes are mostly price-list items and labour, you send a handful a week, or a product handled your awkward job in a trial. If you are still on a spreadsheet, tidying it may be enough for now. See what a pricing spreadsheet does well, and where it breaks.

To place yourself in the range, use the five factors on our pricing page. To get a rough number for your own job without a call, get a ballpark price by email: tell us what you want it to do and attach one recent example. To see it working first, get your free prototype: a short call, then we build a working first version on one of your real jobs (we build 4 a month). We'll tell you whether a product, a tidy-up or a build fits. If a product will do, we'll say so.

Frequently asked questions

How long does bespoke software take to build?

A single, well-understood workflow, such as a quoting tool, typically takes weeks rather than months. UK agency guides commonly quote 4 to 12 weeks for a small internal tool. Larger systems take months. Building in stages means you see the first part working early, on your own data.

Who owns the code when bespoke software is built?

Under UK law, the developer or agency that writes the code owns the copyright unless it is transferred to you in writing and signed. Paying for the work doesn't transfer it on its own. Whoever you hire, get ownership of the code and the data, and what happens at handover, written into the contract before work starts.

What's the difference between bespoke and custom software?

None. Both mean software built for one business around how it works, as opposed to off-the-shelf software, which is a product built for many businesses and usually rented per user per month.

Can I start small and add features later?

Yes, and it is usually the cheapest way to start. Build the one job that costs you the most time, use it, then decide what comes next. Ask for each stage to be priced separately so you can stop at any point.

Why do bespoke software quotes vary so much?

Because suppliers are often pricing different things. One includes discovery, hosting and training, another bills them separately. One quotes a fixed price, another a day rate. And a vague brief gets a cautious, high number. Give every supplier the same written description of the job, and ask what is included and what it costs to run afterwards.

What if a bespoke software project goes over budget?

On a fixed price, the supplier carries the risk of their own underestimate. On time and materials, you do. The best protection is a written specification, a fixed price for each stage, and any change quoted and agreed before it is built.

Should I use a UK developer or an offshore one?

Offshore day rates are lower on paper, but we found no reliable published comparison of what projects end up costing. Weigh the rate against time zones, how easily you can talk through how your business works, and the same ownership and handover questions you would ask any supplier.

Keep reading

AI for business: a practical guide for UK small businesses

Your team is probably already using AI. Here's how to bring it under control, which assistant suits a UK SME, what it costs, and why the answers depend on the systems behind it.

6 October 2026 Read →

Business process mapping: how to map a process in an afternoon (and spot what to automate)

A practical guide to business process mapping for UK SMEs: what it is, how to map a process in an afternoon, a worked example you can open as a flowchart, and how a clear map shows what to automate.

6 October 2026 Read →

Markup vs margin for contractors: the formulas, a quick conversion table, and how to stop getting it wrong on quotes

Markup is profit as a share of cost, and margin is profit as a share of the price. Here are the formulas, a conversion table and the Excel formulas, plus why the real margin leaks happen on the quote rather than in the arithmetic.

6 October 2026 Read →