· Vimal Hari · WordPress & Headless Migration · 7 min read
Custom Software UK: Protect Your IP, Escrow & Exit
A UK buyer's guide to IP ownership, source code escrow and exit planning for custom software — what to demand before you sign.
TL;DR: Custom software UK contracts default to contractor-owned IP unless you assign it in writing before work starts. Pair that with source code escrow and a written exit plan, and you turn a single-supplier dependency into a manageable business risk rather than an existential one.
Introduction
If your business runs on a piece of custom software UK developers built for you, ask yourself one question: what happens if that developer disappears tomorrow? UK IT company insolvencies rose 74% in the first half of 2022 compared with the same period in 2020, and 42% of small businesses reported a cyber breach in 2024. Neither statistic is abstract once you’re relying on a single supplier for the system that runs your orders, your payroll, or your customer data.
Most SME owners think about functionality, timeline and price when commissioning software. Far fewer think about who legally owns the code once it’s built, what happens if the supplier folds, or how they’d actually leave the relationship if service quality slips. These aren’t legal nitpicks — they’re the difference between a manageable supplier transition and a business continuity crisis. This guide sets out what good contractual protection looks like, what it costs, and the questions to ask before you sign anything.
Who Owns the IP in a Custom Software UK Contract?
In the UK, IP created by a contractor or freelancer belongs to the contractor by default — not the business that paid for it — unless a written contract assigns ownership before work begins. This catches out a surprising number of SMEs who assume payment equals ownership. UK copyright protects the actual code automatically, but it does not cover the underlying ideas, functionality, or business logic the software performs, which matters if a competitor builds something similar without copying your code line for line.
Gaps here aren’t just theoretical. Ambiguous or missing IP assignment clauses can prejudice acquisition deals, depress valuations and trigger expensive disputes, because investors scrutinise IP ownership closely during due diligence, according to Chambers. Get the assignment clause right at the outset — it’s far cheaper than fixing it later.
What Source Code Escrow Actually Costs — and What Drives the Price
Software escrow is a three-party arrangement: you, your supplier, and an independent escrow agent who holds the source code, associated data and deployment materials. If the supplier becomes insolvent or stops supporting the software, the agent releases those materials so you can keep the business running, as explained by LegalVision. It’s effectively an insurance policy against supplier failure, and for anything running core operations, it’s one of the cheapest forms of risk protection available.
Pricing varies by provider and scope, but the cost drivers are consistent:
| Factor | Why it affects price |
|---|---|
| Deposit frequency | One-off deposit vs. continuous/automated updates with every release |
| Verification level | Basic deposit check vs. full build verification (confirming the code actually compiles and runs) |
| Scope | Source code only vs. full SaaS environment, infrastructure-as-code and data |
| Number of parties | Single supplier vs. multi-vendor stacks needing separate agreements |
Escrow London notes that escrow protects not just against insolvency but also against a supplier simply refusing to hand over materials during a dispute — a scenario standard contracts rarely cover well. For cloud-delivered software, traditional source code escrow often isn’t enough on its own; SaaS escrow needs to extend to the full application environment and underlying data, because code without the infrastructure to run it is of limited use in a crisis. In 2026, escrow is also expanding to cover AI-specific assets — training data, model weights and configuration — as businesses demand the same operational resilience guarantees for AI-driven systems that they’ve long expected for conventional software, a shift documented by Talk Think Do.
Pro tip: Don’t just sign an escrow agreement and file it away. Ask your provider for annual verification evidence that the deposited code actually builds — an untested escrow deposit is a false sense of security.
When Should You Walk Away From a Supplier Without These Protections?
Not every custom software project needs the full package. A simple marketing site or a low-stakes internal tool with readily available alternatives may not justify escrow fees or lengthy legal negotiation. The calculation changes sharply once the software is business-critical — processing payments, holding customer data, or running operations your team can’t replicate manually within days.
Red flags worth treating as deal-breakers:
- A supplier who resists assigning IP in writing, or offers only a licence rather than full ownership
- No mention of source code access, deployment documentation or data export formats anywhere in the contract
- Vague or absent exit clauses — no defined handover timeframe, no named responsibilities
- Reluctance to discuss escrow at all when the software underpins core operations
What good looks like: a contract with an explicit IP assignment clause, a written exit plan reviewed at renewal, and — for anything mission-critical — an escrow agreement with periodic verification. Andrews Duffy makes the point that exit planning should happen before signing, not when the relationship is already breaking down, because that’s when you still have leverage to negotiate favourable terms. A good exit plan is a living document, updated as the service evolves, clearly defining roles, timeframes, milestones, data return formats and the transferability of any software licences.
If you’re migrating an existing platform rather than commissioning something new — for example, moving a WordPress site to a faster, more resilient architecture — the same ownership and exit questions apply. A WordPress to Astro migration should leave you with full control of the codebase and content, not a new form of lock-in.
Questions to Ask Any Software Provider Before You Sign
Use these as a pre-contract checklist, ideally with input from a solicitor for anything above a modest project value:
- Does the contract explicitly assign IP ownership to us, in writing, before work starts?
- Who owns any third-party libraries, frameworks or AI models used in the build?
- Is source code escrow included, and does it cover the full deployment environment, not just the code?
- How often is the escrow deposit updated and independently verified?
- What does the exit plan specify for data format, handover timeframe and licence transfer?
- What happens to our access and data if the supplier is acquired or becomes insolvent?
The NCSC’s Small Business Guide, updated in October 2024 with a dedicated section on third-party risk and software supply chain security, reinforces that these aren’t just legal questions — they’re cybersecurity and operational resilience questions too.
What This Means for WordPress & Headless Migration in 2026
Platform migrations are a natural moment to fix IP and ownership gaps that have quietly persisted for years. If you’re moving off WordPress to a headless or static architecture, insist on a contract that assigns you full ownership of the new codebase, build scripts and content exports — not just a working site. UKIPO fees for patents, trademarks and designs rose by an average of 25% from April 2026, which makes getting ownership right the first time considerably cheaper than correcting it later through legal channels.
This is also where location matters less than process. Whether you’re a logistics firm in Reading or a professional services practice seeking website development in Bracknell, the same contractual discipline applies: clear IP assignment, an exit plan agreed before go-live, and escrow where the stakes justify it.
Key Takeaways
- Insist on a written IP assignment clause before any work begins — UK default law favours the contractor, not you.
- Treat source code escrow as insurance, not bureaucracy, for any system your business couldn’t operate without for more than a few days.
- For SaaS or AI-driven tools, confirm escrow covers the full environment and data, not just the code repository.
- Negotiate your exit plan at contract signing, when you have leverage — not during a dispute, when you don’t.
- Revisit IP and escrow terms whenever you migrate platforms; it’s the cheapest moment to close old gaps.
Conclusion
Protecting a custom software UK investment isn’t about distrust — it’s about making sure a single supplier’s bad year doesn’t become your bad year. IP assignment, escrow and a written exit plan cost far less than the dispute, rebuild or valuation hit you’d face without them. If you’re weighing up a platform migration as part of this review, our Astro migration service is built around the same principle — you keep full ownership and editorial control, with none of the lock-in. Get in touch to scope what good protection looks like for your specific setup.
