Bespoke software development in the UK: costs, timelines and how to choose

Bespoke software development in the UK means a supplier designing and building software around how your business actually works, under UK contract law and UK GDPR. Published price guides span such a wide range that they tell a buyer very little, which is why we don't publish one: the number depends on your scope, your integrations and your data. Three things decide a British project in particular: what drives the quote, the fixed-price versus day-rate choice, and the contract terms around ownership and data. This page covers those. For how a build is shaped and scoped, the bespoke software buyer's guide is the pillar to read alongside it.

What drives a UK quote

Most of a UK quote is labour: the time of the people who design, build, test and manage the work. Three factors move it more than the choice of technology. The first is the seniority mix. A lead architect costs more per day, but their judgement on how the system scales and stays secure prevents the rework that costs most. The second is how settled the scope is, because every change after the build starts is paid for in time. The third is integrations and data: each system the software has to talk to, and each messy dataset that has to be migrated, adds build and testing time. An agency also covers design, QA, project management and the cost of keeping a team together.

London suppliers charge more than most of the UK. If budget is tight, a UK lead paired with a nearshore delivery team is the usual way to cut the number without the rework a purely offshore arrangement invites on a loose brief. The blended model works because the expensive judgement stays local while the volume work does not.

Timelines you can hold a supplier to

The timelines are our own working figures for a competent team, not sales promises. The single thing that blows them apart is requirements that keep moving after the build starts, which is why the contract shape below matters as much as the estimate.

Fixed price or day rate

This is the choice that decides who carries the risk. Fixed price means the supplier commits to a number for an agreed scope, so an overrun is their problem, not yours. It suits most UK SMEs, especially those without an internal technical lead, but it only works if a detailed specification is agreed before anyone writes code. Day rate means you pay for time and keep the flexibility to change direction, which suits work where the requirements are genuinely unclear or expected to evolve. The honest rule of thumb: if you can specify it, fix the price; if you truly cannot, day rate with a tight feedback loop and a spending cap.

Watch for the quote that offers fixed-price certainty without asking for any discovery. A firm number handed over without a proper scoping conversation is a guess wearing a suit, and the difference tends to appear as change requests three weeks in.

Ownership, data and the terms UK buyers forget

British projects carry a few settle-early items that are cheap to agree at the start and expensive to argue at the end. Confirm that you own the intellectual property and receive the source code on completion. Confirm GDPR-compliant data handling and where your data will physically sit. Agree the maintenance arrangement, because UK agency guides, Red Eagle Tech's and Softomate's among them, budget 15% to 25% of the build cost every year for upkeep, and you want to know whether the people who built it will be the ones supporting it. Put all of that in the contract rather than trusting it to a friendly conversation.

The discipline that keeps a build honest is the same discipline we apply to our own operations: map the work, watch the risky steps, and let a person sign off anything that matters. The notes on running a publishing operation with no content team show that principle in a different setting, and our software engineering page shows how it shapes a build.

Check a UK software development company before you sign

Two public checks take ten minutes and tell you things no sales call will. Both are free, and both work the same whether the agency is in London or Leeds.

Companies House. The register makes all of the public data we hold on companies available free of charge, in Companies House's own words (Companies House). Look up the supplier and read three things. The filing history: are the accounts and confirmation statements on time, or overdue? The officers: who the directors are, how long they've been in post, and whether any appear among the disqualified directors. And the charges and insolvency entries. A firm that's three months from trouble is a poor home for code you'll depend on for years. If the contract names a different company from the one on the website, ask why.

Cyber Essentials. This is the government-backed baseline for an organisation's own security, and it assesses five technical controls: firewalls and internet gateways, secure configuration, access control, malware protection and security updates. Central government has asked for it on higher-risk contracts, including systems that hold official data, under a procurement note in force since 24 February 2025 (Cabinet Office: PPN 014). It covers the supplier's own machines and accounts, not the software it writes for you. Still, a firm that will hold your data and your source code and can't show the baseline certificate is telling you something.

How to choose, in five questions

• Who is on the team, by seniority, and is the mix right for the work or priced for one person?
• Is there a written specification, and is this fixed price or day rate?
• Who owns the code and the IP, and when is the source handed over?
• Where does our data sit, and is the handling GDPR-compliant?
• What does year-one maintenance cost, and who provides it?

A supplier who answers those plainly and in writing is a different proposition to one who deflects. If you want to compare a build against staying on a subscription tool, the custom CRM case study works through that maths with real numbers.

Common questions

If you have a project in mind, start with an informal scoping chat. Tell us what the software needs to do and which systems it touches, and we'll come back with a price range. Our how we work page walks through the process, or send the project through contact.