Professional Indemnity Insurance for New IT professionals — Your First Policy (2026)

Reviewed by Apex Insurance Brokers · Last reviewed 2026-08-05

1. Do you actually need PI as a new IT professional?

Let's start with the honest answer, because it isn't a simple yes. There is no statutory regulator for IT professionals in the UK and no law that says a software developer, IT consultant, systems integrator or managed-service provider must carry professional indemnity insurance. Unlike solicitors or accountants, you can legally trade on day one without it. Membership of a professional body such as BCS, The Chartered Institute for IT, is entirely voluntary and doesn't impose a compulsory insurance requirement either. A fuller description of a broker who places IT consultant PI every day sits on its own page.

So why does almost every working IT professional carry it? Because the real requirement doesn't come from a regulator — it comes from your clients. The moment you start bidding for serious work, you'll meet the contract clause that catches most first-timers off guard: the buyer requires you to hold professional indemnity insurance, often to a stated minimum limit, for the duration of the engagement and sometimes for a period afterwards. Public-sector frameworks, corporate procurement teams, agencies placing you on contract, and even mid-sized businesses will frequently make evidence of PI a condition of signing. No certificate, no contract.

Beyond the contractual box-ticking, there's the substance of what PI does. IT work carries a specific kind of risk: your deliverables are relied upon, and if something you built, advised or configured is blamed for a financial loss, you can be pursued for it. A migration that corrupts data, a bug that halts trading, advice that leads a client down an expensive dead end, an integration that fails at go-live — these are allegations of professional negligence, breach of duty or breach of contract, and they land on you personally if you're a sole trader, or on your company if you've incorporated. PI insurance is what stands between that allegation and your own bank account. It typically covers the legal cost of defending the claim as well as any damages or settlement, which matters because defence costs alone can be substantial even when you've done nothing wrong.

So the practical reality: you don't legally have to buy it, but you effectively can't win and keep good work without it, and one uninsured dispute could end a young business. For most new IT professionals, that settles the question.

2. When your cover needs to start — and why day one matters

Here's the single most important thing for a first-time buyer to understand: your cover should begin from your first client engagement, not from the day the money arrives or the project “properly” kicks off. Professional liability attaches to the work itself. The scoping call where you advise an approach, the discovery phase, the first lines of code, the recommendation you make before a contract is even signed — all of it can later be pointed to as the source of a problem. If you weren't insured when you did the work, the fact that you insured yourself a fortnight later won't help.

New professionals often treat insurance as an admin task to sort out “once things are up and running.” It's understandable, but it leaves a window of unprotected work at exactly the point when you're most likely to make an early-days mistake and least able to absorb a loss. The fix is simple and cheap: put cover in place before you take on your first paying client, so there's never a period of exposed work behind you. If you've already started trading, don't wait — get insured now and we can discuss how earlier work is treated.

3. How much cover does a new firm actually need?

The amount of cover is called your limit of indemnity — the most the insurer will pay out. Common options are structured in round figures such as £1m, £2m or £5m, and occasionally higher for larger contracts. As a first-timer, the honest starting point is: your limit is usually driven by what your clients demand, not by a formula you invent yourself.

Three things tend to set the figure:

• Client-mandated minimums. Read the insurance clause in your contracts. Many corporate and public-sector buyers specify a minimum PI limit — often £1m, frequently £2m, and sometimes £5m for larger or more sensitive engagements. Your policy needs to meet the highest figure any current contract requires.
• The scale of loss your work could cause. A developer building marketing microsites carries a different exposure to one integrating a client's core financial or trading systems. Ask yourself: if my deliverable failed at the worst possible moment, what's the realistic size of the loss? The bigger and more business-critical the systems you touch, the higher the limit you'll want.
• Who your clients are. Larger, better-resourced clients tend both to demand higher limits and to be more capable of mounting a substantial claim. If you're aiming at enterprise or public-sector work, plan for higher limits from the outset.

A sensible approach for a new firm is to start at the limit your immediate contracts require, with an eye on where you want to be trading in a year. It's straightforward to increase your limit later as you land bigger clients — you're not locked in. If you're genuinely unsure, that's exactly the kind of judgement a broker exists to help with; tell us what your contracts say and we'll size it with you.

4. What a first policy costs to think about — what underwriters look at

We won't quote a price here, because a fair one depends entirely on your specifics — and anyone giving you a number before understanding your work isn't doing you a favour. What's genuinely useful is knowing what an underwriter weighs up when pricing a new firm with no trading history. There are fewer factors than you might fear, and being a start-up is not the disadvantage people assume.

For a brand-new IT business, underwriters typically look at:

• Your estimated turnover. Since you've no accounts yet, a reasonable projection for your first year is fine. Turnover is a proxy for how much work you're doing and therefore how much risk you carry — a modest estimate reflects a modest exposure.
• What you actually do. The specific activities matter: bespoke software development, IT consultancy and advice, systems integration, hosting or managed services, reselling third-party products, hardware installation. Advisory and build work that clients rely on heavily sits differently to lower-touch services.
• Your background and qualifications. Relevant experience, certifications and a track record in the field — even from employment before you went independent — reassure an underwriter that you know your craft, new company or not.
• Your limit of indemnity. A higher limit means more potential exposure for the insurer, so it feeds into the price.
• The nature of your clients and contracts. The sectors you serve and the size of the engagements shape the risk picture.

Notice what's not on that list: years of accounts, a claims history, a portfolio of case studies. As a new firm you simply have less to provide, which is why first quotes are usually fast. You give a fair estimate and an honest description of your work, and the market prices from there. The golden rule is accuracy — describe your real activities and turnover honestly, because a policy priced on the wrong information may not respond properly when you need it.

5. “Claims-made” — the one bit of jargon that really matters

Professional indemnity is almost always written on a claims-made basis, and understanding this early will save you a nasty surprise later. It means the policy that responds to a claim is the one in force when the claim is made against you — not the one you held when you did the work.

An example makes it concrete. Say you build a system in 2026, and in 2028 the client alleges it caused them a loss. It's your 2028 policy that has to respond, even though the work was done two years earlier. This has two consequences every first-timer should absorb:

• Continuity is everything. You need to keep your PI running without gaps, year after year, for as long as anyone could still bring a claim about past work. Let the policy lapse and a claim arrives, and you may have no cover — even for work that was insured at the time you did it. Starting cover from day one and renewing it faithfully is what keeps you protected.
• The retroactive date. Policies carry a retroactive date — work done before it isn't covered. When you buy your first policy at the start of trading, your retroactive date should sit right at the beginning of your professional work, so there's no unprotected history behind you. This is another reason to insure before your first engagement rather than after.

The practical takeaway is reassuring: get on the ladder early, stay on it, and don't let a renewal slip. When you eventually wind down or retire, you can arrange “run-off” cover to keep protecting you against claims about past work — but that's a conversation for years from now, not day one.

6. How to buy your first policy — what you'll need

The good news for a new firm: the information you need to hand over is short. Have these ready and you can get a quote quickly:

• Your business name and structure (sole trader or limited company) and where you're based.
• A plain description of the services you provide — be specific about development, consultancy, integration, managed services, reselling and so on.
• Your estimated turnover for the first year.
• The limit of indemnity you need — check your contracts for any mandated minimum.
• Relevant experience and qualifications.
• Whether any contract requires cyber cover as well, so it can be arranged alongside.

That's largely it. Because you've no claims history or years of accounts to assemble, a first-time application is genuinely lighter than a renewal for an established firm. A broker takes this handful of details, matches you to insurers who understand IT risk, and comes back with options and a clear explanation of what each covers — including whether to pair PI with cyber insurance, which many IT professionals now hold together because the two address different risks. PI answers for allegations about your professional work; cyber responds to incidents like a breach, ransomware or a data compromise affecting your own or your clients' systems.

You can begin your quote online in a few minutes and we'll pick up anything that needs a human eye.

7. Common first-timer mistakes to avoid

• Leaving it until after the first job. Cover should predate your first engagement. Retro-fitting insurance around work you've already done leaves a gap.
• Buying the lowest limit without reading your contracts. If a client mandates £2m and you hold £1m, you're in breach and potentially under-protected. Match the highest figure your contracts demand.
• Assuming your limited company shields you personally. Incorporation helps, but claims of negligence against your work can still be costly and disruptive, and defence costs mount fast. PI is what actually funds the defence.
• Confusing PI with public liability or cyber. They cover different things. Public liability is about injury or physical damage; cyber is about breaches and system incidents; PI is about your professional work causing financial loss. You may want more than one.
• Letting cover lapse between contracts. Because PI is claims-made, a gap can leave past work exposed. Keep it continuous even during quiet spells.
• Under-describing what you do to save money. If your policy is based on an inaccurate picture of your activities, it may not respond when you claim. Be honest and complete.
• Sitting on a potential problem. If a client raises a complaint or you suspect a claim might follow, tell your insurer promptly. Notification rules matter, and early disclosure protects you.

8. About Apex

Apex Insurance Brokers Limited is an FCA-authorised insurance broker based in Bristol (FRN 724952). We arrange professional indemnity and cyber cover for IT professionals across the UK — from first-time contractors and freelance developers to growing consultancies and managed-service providers. Because we work with insurers who genuinely understand technology risk, we can usually turn a straightforward new-firm enquiry around fast, often with a quote the same day.

If this is your first policy, that's exactly the situation we enjoy helping with: no jargon, no pressure, just a clear explanation of what you need, why, and what it protects. Start online whenever suits you, or get in touch and we'll take it from there.

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.