Professional Indemnity Insurance for Freelance Web Developers (UK)
Reviewed by Apex Insurance Brokers · Last reviewed 2026-08-05
If you build websites or applications for clients as a sole trader or through a limited company, your biggest exposure is not a slip in the office — it is a claim that your code, design or advice cost a client money. Professional indemnity insurance exists for exactly that. This guide explains the specific risks freelance web developers face, when cover is genuinely required, sensible limits, and how Apex places it.
What PI actually covers for a web developer
PI responds to claims of professional negligence, error or omission in the service you provide. For a freelance developer, real-world triggers include:
- Defective code or bugs that break a client's site, checkout or booking flow and cause lost revenue.
- Missed deadlines or non-delivery that breach a project agreement or service level agreement (SLA).
- Negligent advice — recommending a platform, framework or hosting setup that proves unfit for the client's needs.
- Unintentional intellectual property infringement, such as using a code library, stock image or font outside its licence.
- Loss of client documents or data you were responsible for handling.
Crucially, PI typically covers your legal defence costs as well as damages or a settlement. Defending even a weak claim can cost more than the claim itself, so the defence element is where a freelancer often feels the value first.
Is PI insurance a legal requirement?
No. Unlike employers' liability insurance — which is compulsory under the Employers' Liability (Compulsory Insurance) Act 1969 if you have staff — there is no statute forcing a web developer to hold professional indemnity cover. Web development is also not a regulated profession with a mandatory-insurance regime (unlike solicitors or accountants).
In practice, though, PI is effectively required by your contracts, not by the law. This matters because a contractual obligation is often stricter than anything a regulator would impose.
Line up cover before you sign the contract — not after the dispute.
Get a PI quote →Client contracts, SLAs and PI clauses
Most professional clients — agencies you subcontract to, established businesses, and public-sector bodies — will not engage a freelance developer who cannot evidence PI. The requirement usually appears in one of three places:
- The insurance clause of your contract, naming a minimum limit of indemnity (commonly £1m, £2m or £5m) that you must hold and maintain for the duration of the engagement.
- Supplier onboarding or procurement, where you upload a certificate before work can start.
- Framework and tender requirements, particularly for public-sector or larger corporate work, where a specified PI limit is a condition of bidding.
Read the clause carefully. Two details catch freelancers out. First, the limit basis: "each and every claim" is stronger than "in the aggregate", and some contracts specify it. Second, the maintenance period: many contracts require you to keep PI in force for a number of years after the project ends. Because PI is almost always written on a claims-made basis — meaning the policy that responds is the one in force when the claim is made, not when the work was done — letting cover lapse after a project can leave you exposed to a later claim. If you stop trading, run-off cover fills that gap.
Send us the contract clause and we will confirm the exact limit and basis your policy needs to satisfy it.
Project and SLA liability: the freelancer's real risk
Service level agreements raise the stakes. If you commit to uptime, response times or delivery milestones, a failure can be framed as a breach that caused measurable loss — and that is precisely the kind of allegation PI is designed to answer.
Two practical points. Keep your scope of work and your SLA commitments realistic and written down; vague promises invite disputes. And be wary of contracts that ask you to accept unlimited liability or to indemnify a client for consequential or indirect losses — a PI policy responds up to its limit and within its terms, so an uncapped contractual promise can outrun the cover behind it. A sensible liability cap in the contract, aligned to your PI limit, protects both sides.
How PI and cyber cover overlap — and where they don't
Web developers sit at the exact point where professional risk and cyber risk meet, so it is worth being clear on the split.
| Scenario | Typically PI | Typically cyber |
|---|---|---|
| A bug in your code causes a client to lose sales | Yes | — |
| Negligent advice on platform choice | Yes | — |
| Your own systems are hacked and client data exposed | Possibly, in part | Yes |
| Ransomware, incident response, data restoration | — | Yes |
| Notification costs after a personal-data breach | — | Yes |
PI answers "your professional work was wrong." Cyber answers "a security event caused loss." A breach can trigger both — for example, if a client alleges your negligent build caused the breach. Because the line is blurry and UK data-protection obligations under the UK GDPR and the Data Protection Act 2018 sit behind any personal-data incident, many freelance developers hold both, ideally arranged so the two policies dovetail rather than dispute cover between themselves. Every submission Apex makes carries a named broker, and our page on how we place IT consultant professional indemnity sets out what that means in practice.
Choosing a limit of indemnity
The right limit is driven by your contracts and your clients' size, not by guesswork. As generic guidance:
- £1m — a common baseline for smaller business clients and much subcontracted agency work.
- £2m — frequently specified by larger commercial clients and some frameworks.
- £5m — typical where you handle high-value e-commerce, sensitive data, or public-sector contracts.
Set the limit to meet your most demanding current or expected contract, and check whether it must be per-claim or aggregate. If in doubt, it is usually cheaper to carry a slightly higher limit than to decline work or scramble to increase cover mid-tender.
How Apex places PI for freelance developers
Apex Insurance Brokers is an FCA-authorised broker (FRN 724952) based in Bristol. When we arrange PI for a freelance web developer, we:
- Review your actual client contracts and SLA wording so the limit, basis and any maintenance-period requirement are correctly met.
- Match you to insurers whose wordings suit technology and web work — including cover for IP infringement and, where relevant, dishonesty of the insured.
- Advise on aligning PI with a cyber policy so the two work together, not against each other.
- Explain the claims-made basis and arrange run-off cover if you wind down the business.
Because we are a broker, we act for you — not the insurer — and place cover across the market rather than from a single provider.
Common questions
Do I need PI if I work through my own limited company?
Yes — the company is the party contracting with clients and the party a claim would be brought against, so the policy is arranged in the company's name. Trading through a limited company does not remove the professional exposure.
I only build small sites for local businesses. Is PI overkill?
Not necessarily. Even a modest project can generate a claim larger than the fee if a fault causes lost sales or a client demands rework and compensation. Many small clients also now ask for evidence of cover before they engage you.
What happens to old projects if I cancel my policy?
Because PI is claims-made, a claim about past work is only covered if a policy is in force when the claim is made. If you stop trading, run-off cover keeps you protected against claims arising from work you have already delivered.
Apex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority (FRN 724952). This guide is general information, not advice on a specific policy or a substitute for your policy wording.