Custom Software Development in the UK: Costs, Contracts and Choosing a Partner
A UK buyer's guide to custom software: cost drivers, contracts and IP, VAT on overseas suppliers, R&D relief limits, data transfers and choosing a partner.
What should a UK business know before commissioning custom software?
Custom software is worth it when off-the-shelf or configurable products cannot fit a process that differentiates your business or connects many systems. Before you commission it, fund a short discovery phase to set scope and assumptions; compare suppliers on the same assumptions and on the total cost of ownership; and settle the UK-specific points in the contract: written IP assignment, data protection terms (including international transfers if any of the team is abroad), VAT treatment, and whether R&D relief is realistic for the way the work is delivered. Cost depends on scope, integrations, data, security and the team; there is no honest single figure.
This guide is for founders, operations directors and IT leads at UK SMEs and mid-market companies. It is general information as at October 2026, not legal, tax or financial advice.
Key takeaways
- Start with discovery; fixed quotes without it are guesses.
- Compare quotes on the same scope, assumptions and three-year cost.
- Get IP assigned in writing and signed.
- Plan data protection terms before anyone sees production data.
- Expect the reverse charge on overseas services, not UK VAT on the invoice.
- Do not assume R&D relief on overseas-delivered work.
Buy, configure, build or combine?
Most organisations need less custom software than they think. Use SaaS for standard functions such as accounting, payroll and email; configure platforms where the process is common but needs adjustments; build where the process is distinctive, where several systems must work together, or where licensing costs at your scale exceed the cost of owning software. Many good solutions combine bought products with a custom layer that connects them. See low-code vs custom software and, if you are replacing spreadsheets, replacing spreadsheets with custom software.
What drives the cost?
The table lists the factors that move budgets most. Use them to challenge estimates and to decide what to leave out of the first release.
| Driver | Why it moves the budget | How to control it |
|---|---|---|
| Scope and workflows | Each role, screen, rule and exception adds design, build and testing | Prioritise the workflows that create value; defer edge cases |
| Integrations | Accounting (Xero, Sage, QuickBooks), CRM, ERP, payments, HMRC or bank APIs each need mapping, error handling and testing | Integrate the essential systems first; use existing connectors where reliable |
| Data migration | Cleaning and mapping old data often takes longer than expected | Profile data early; migrate only what is needed |
| Security and compliance | UK GDPR, sector rules, audit logs, penetration testing, accessibility | Set requirements in discovery; build them in rather than retrofitting |
| Platforms | Web, iOS and Android, offline support and admin tools each add work | Start with the platform users need most |
| Team and delivery model | Seniority, location, overlap with your hours and management overhead | Compare on outcomes and total cost, not day rates alone |
| Running and changing | Hosting, monitoring, support, upgrades and new features after launch | Budget for ownership from the start; see software maintenance contracts |
A total cost of ownership worksheet
Ask every supplier to fill in the same worksheet, with assumptions written down. Leave cells blank rather than guessing, and compare over the same period.
| Line | Year 1 | Years 2–3 | Notes |
|---|---|---|---|
| Discovery and design | Fixed price is common | ||
| Build and testing | By release or phase | ||
| Integrations and data migration | Per system | ||
| Hosting, tooling and third-party licences | Often in US dollars | ||
| Support, monitoring and upgrades | Response times and hours | ||
| Planned enhancements | Agreed capacity per month | ||
| Your internal time | Product owner, testing, training | ||
| Contingency | For known unknowns |
UK contract essentials
| Topic | What to check |
|---|---|
| IP ownership | Copyright generally belongs to the author or their employer unless assigned; an assignment must be in writing and signed by the assignor (CDPA 1988 s.90). Assign custom code, list open-source and pre-existing components with their licences |
| Data protection | A UK GDPR Article 28 processor agreement; security measures; sub-processors; breach notification; international transfer safeguards |
| Pricing model | Fixed price per phase, time and materials with a cap, or a monthly team; change control either way |
| Acceptance | Written acceptance criteria and a testing window per release |
| Warranty and support | Defect fixing period, response times, hours of cover and costs after warranty |
| Handover and exit | Access to repositories, infrastructure accounts, documentation and credentials in your name; see software vendor handover checklist |
| Governing law | Usually the law of England and Wales or Scotland; disputes and jurisdiction clauses |
VAT, R&D relief and other tax points
VAT. For most business-to-business services, the place of supply is where the customer belongs. A UK VAT-registered business buying services from an overseas supplier normally accounts for VAT through the reverse charge rather than paying it on the invoice (VAT Notice 741A). For a fully taxable business, this usually nets off, but it must be declared.
R&D tax relief. Some custom software projects involve qualifying R&D, but the rules changed. For accounting periods beginning on or after 1 April 2024, payments to subcontractors for R&D carried out outside the UK, and to externally provided workers not subject to UK PAYE, generally do not qualify. A narrow exception applies where conditions needed for the R&D are not present in the UK and it would be wholly unreasonable to replicate them; cost and availability of staff are excluded (HMRC). If relief matters to your business case, take advice before choosing a delivery model.
Worth noting
Do not build a business case on a grant or tax relief until an adviser has checked current eligibility for your company and project.
Data protection when part of the team is overseas
Under UK GDPR, giving people outside the UK access to personal data, even remote access to a database, can be a restricted transfer. Where the destination has no UK adequacy regulations (we found none for India as at October 2026), organisations typically rely on the ICO's International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses, supported by a transfer risk assessment, which the Data (Use and Access) Act 2025 frames as a data protection test (ICO international transfers guidance).
The best control is minimisation: developers rarely need real personal data. Use synthetic or anonymised test data, keep production access with named UK-approved staff or tightly controlled roles, and log access. See privacy by design in software development for the engineering patterns.
Choosing a development partner: a checklist
- Relevant work you can inspect: live products, code samples or architecture write-ups, not only screenshots.
- Discovery approach: what they produce before quoting a build (scope, risks, architecture, plan).
- Team: who actually does the work, seniority, continuity, and overlap with your working hours.
- Engineering practice: code review, automated testing, CI/CD, environments, security testing.
- Communication: demos, written updates, a named lead, how decisions and changes are recorded.
- Security and data handling: access controls, device policies, how they handle production data; any certifications you require, such as Cyber Essentials, verified rather than assumed.
- Ownership and exit: IP assignment, repositories and accounts in your name, documentation.
- References: speak to clients with similar projects where possible.
UK, nearshore or offshore delivery?
Location changes cost, communication and compliance work rather than quality on its own.
| Model | Strengths | Watch-outs |
|---|---|---|
| UK-based team | Same hours, on-site workshops, familiarity with UK sector norms, no international transfer for team access | Usually higher rates; availability |
| Nearshore (Europe) | Close time zones, frequent travel possible | Transfer safeguards depend on the country; varying rates |
| Offshore (for example India) | Larger talent pools; often lower day rates | Transfer safeguards; R&D relief restriction; working-hour overlap (India is 4.5 hours ahead of the UK in summer, 5.5 in winter); management discipline |
| Hybrid | UK product ownership with distributed engineering | Clear roles and documentation |
Hypothetical example: a distributor's order portal
This example is hypothetical. A UK wholesale distributor takes trade orders by email and spreadsheet and re-keys them into Sage. It commissions a four-week discovery that maps ordering, pricing tiers and the Sage integration, produces a release plan and a written set of assumptions, and asks three suppliers to price the first release on that basis. The chosen supplier's contract assigns IP in writing, includes a processor agreement with an IDTA because part of the team works abroad, and defines acceptance tests. The finance director confirms the VAT reverse charge treatment and decides not to rely on R&D relief.
Common mistakes
- Choosing on day rate or build price alone.
- No written IP assignment.
- Developers working on copies of production personal data.
- Assuming R&D relief or grants without advice.
- Repositories and cloud accounts in the supplier's name.
- No budget for running and changing the system after launch.
Sources
Tax: HMRC VAT Notice 741A: place of supply of services; HMRC: clarifying the scope of the R&D overseas restriction; GOV.UK: R&D tax relief reform.
Law and data: Copyright, Designs and Patents Act 1988, s.90; ICO: international transfers; NCSC: Cyber Essentials.
Accessed 10 October 2026. Tax and data rules change; check current guidance and take professional advice.
Conclusion
Commissioning custom software in the UK goes well when discovery sets the scope, suppliers are compared on the same assumptions and total cost, and the contract settles IP, data protection, acceptance and exit. If any of the team is overseas, plan transfer safeguards and do not assume R&D relief. For the delivery process in more depth, the Australian custom software guide covers discovery, architecture, testing and maintenance in detail; the delivery practices apply in the UK, though its legal and tax sections are Australian. Public bodies buying software should also read UK public sector software procurement.
Want a scoped estimate with every assumption written down?
ZSpace Labs is a remote-first technology studio that works with clients globally on custom web applications and integrations, mobile apps and automation. We have no UK office; we work remotely and can align with UK hours for workshops and reviews. If useful, we can talk through your project and the questions above.
Common questions.
It depends on scope, integrations, data migration, security and compliance needs, the delivery team and how long you will run and change the system. Reliable estimates come from a discovery phase that defines scope and assumptions, not from market averages. Compare quotes on the same assumptions and on the first two or three years of ownership, not the build price alone.