Tech E&O Insurance: What Software Developers and IT Consultants Are Actually Covered For

Your code ships on a Friday. By Monday, your client's checkout page is down, their customers are furious, and your inbox holds a letter from their lawyer alleging your deployment cost them six figures in lost sales. Whether the outage was your bug, their misconfigured server, or a bit of both, you now have a legal bill to pay — and that is exactly the moment errors and omissions insurance exists for.

Errors and omissions (E&O) insurance, also called professional liability insurance, covers claims that your professional work caused a client financial harm. For software developers, IT consultants, MSPs, and SaaS founders, the specialized version is technology E&O: a policy written around the failures your kind of work actually produces — buggy releases, missed deadlines, botched migrations, and systems that never did what the statement of work promised.

What Tech E&O Actually Covers​

A standard tech E&O policy pays for two things: your legal defense, and the damages or settlements you owe if the claim succeeds. Defense costs are the part most developers underestimate. Even a meritless claim can cost tens of thousands of dollars to defeat, and without coverage that money comes straight out of your operating account.

Here are the claim triggers a tech E&O policy is designed to answer.

Coding errors and software failures​

The classic scenario: a bug in software you built causes data loss, downtime, or corrupted records at a client. Examples include a backup routine that silently stopped running so a crash wipes months of client data, an e-commerce integration that double-charges customers, or an update that takes a client's ordering system offline during their busiest week. The client sues for the cost of recovery plus the business they lost while down.

Missed deadlines and undelivered projects​

Late or incomplete delivery is one of the most common professional-liability triggers in software work. If your contract promised a launch date and you missed it by three months, the client can claim the delay cost them revenue, a funding milestone, or a seasonal sales window. E&O responds to the financial-loss portion of that claim — the part general liability never touches.

Failure to meet specifications​

Sometimes the software works but does not do what was promised: the platform cannot handle the transaction volume in the requirements doc, the report module omits the compliance export the client needed for their audit, or the migration drops historical records. "It runs" is not a defense when the statement of work says otherwise, and these scope-gap disputes are a staple of tech E&O claims.

Negligent advice and recommendations​

Consultants get sued for guidance, not just code. Recommending a platform that cannot scale to the client's needs, designing an architecture with a single point of failure you should have flagged, or advising a client to skip a backup strategy that later proves catastrophic — all of these are professional-negligence allegations that sit squarely inside E&O territory.

Breach of contract (the insurable part)​

Many tech E&O policies include some coverage for breach-of-contract claims arising from your professional services, such as failing to deliver what the contract described. Read this clause carefully: insurers typically cover the negligence-flavored breach (you performed poorly) but not a pure failure to show up or a deliberate walkaway.

What It Does Not Cover​

Knowing the exclusions matters as much as knowing the coverage, because the gaps are where developers get surprised.

• Bodily injury and property damage. If you trip over a client's server cable and break an ankle, or flood their office installing hardware, that is general liability, not E&O.
• Intentional wrongdoing and fraud. No policy covers work you knew was defective when you shipped it, backdoors you planted, or data you stole.
• Employment disputes. Claims from your own employees — wrongful termination, discrimination, wage disputes — belong to employment practices liability insurance.
• Known claims and prior knowledge. If you buy a policy after a client has already threatened to sue, that dispute is excluded. Insurers ask about known circumstances on every application; answer honestly, because a wrong answer can void the whole policy.
• Patent and some IP disputes. Many tech E&O policies include copyright and trademark infringement (you reused code you should not have), but patent infringement is often excluded or sublimited. If you ship novel algorithms, ask specifically.
• Your own first-party losses. E&O pays claims others bring against you. When ransomware locks up your own laptops, that is cyber liability or business interruption coverage, not E&O.

Tech E&O vs. Cyber Liability: Why Developers Often Need Both​

This is the most confused boundary in technology insurance, so here is the clean version: tech E&O responds when your product or service fails a client; cyber liability responds when data is breached or systems are attacked.

In practice the two overlap constantly. Suppose a coding error in your authentication module lets attackers exfiltrate your client's customer database. The client's lawsuit against you for negligent development is an E&O claim; the breach-notification costs, forensics, and regulatory fines are cyber-liability territory. Without both policies, each insurer can point at the other side of the loss.

Many carriers now sell a combined tech E&O plus cyber package aimed at small software firms and consultancies. Bundling is usually cheaper than two standalone policies and eliminates the finger-pointing between carriers. If you handle client data of any kind — and nearly every developer does — get a quote for the bundle before deciding you only need one half.

Claims-Made: The Clause That Decides Whether You Get Paid​

Almost all E&O policies are written on a claims-made basis, which works differently from the car or general-liability insurance you may be used to. A claims-made policy covers claims first made against you during the policy period — regardless of when the underlying work happened — as long as the work falls after your policy's retroactive date.

Three consequences follow, and each one has burned freelancers who did not understand it:

1. Lapses create permanent gaps. If you let coverage lapse for two months and a client sues over work from last year, the claim lands in an uninsured window. Continuous coverage is the whole game.
2. The retroactive date is the real start of your coverage. Keep it as far back as your first insured policy year and never let a new insurer move it forward without understanding you are abandoning coverage for older work.
3. Retirement and shutdowns need tail coverage. When you wind down a consultancy or retire, buy an extended reporting period ("tail") so claims filed after you close — over work you did while insured — still get answered. Most tails run one to five years.

When switching carriers, confirm in writing that the new policy honors your original retroactive date. A cheaper premium that resets the clock can be the most expensive policy you ever buy.

What It Costs in 2026​

Tech E&O is one of the more affordable business policies relative to the protection it buys. Market data from brokerages serving small technology firms clusters in a consistent range:

• Solo developers and freelancers typically pay $60 to $110 per month (roughly $700 to $1,300 per year) for a $1 million limit.
• Small IT consultancies generally land between $750 and $3,000 per year, while software product companies range from $1,000 to $5,000 per year depending on revenue and risk profile.
• The commonly quoted average across technology businesses sits near $800 per year, or about $65 to $90 per month.

Your actual premium moves with five levers: annual revenue, headcount, the limits and deductible you choose, your claims history, and what you build. Developers writing payment processing, health-care, or aviation software pay more than those building marketing sites, because the blast radius of a failure is larger. Raising your deductible from $1,000 to $5,000 or $10,000 is the simplest way to cut the premium — just make sure the deductible amount is cash you actually hold in reserve.

One cost note with a tax silver lining: E&O premiums are an ordinary and necessary business expense, deductible on Schedule C for freelancers or as an operating expense for S corps and LLCs. Track every premium payment under a dedicated insurance account in your books, separate from general liability and cyber, so you can see the true annual cost of each policy at renewal time.

How Clients Force the Issue​

Many developers buy E&O not because they chose to, but because a contract required it. Enterprise master services agreements routinely demand $1 million per occurrence and $2 million aggregate in professional liability, plus a certificate of insurance before work begins. Staffing firms and subcontracting arrangements often require you to name the client as an additional insured.

Three contract clauses deserve your attention before you sign:

• Limitation of liability. Push to cap your liability at the fees the client paid you (or a low multiple of them). Without a cap, a $20,000 project can generate a $500,000 claim.
• Mutual indemnification. Make sure indemnity runs both ways and is tied to negligence, not a blanket promise to cover everything that goes wrong on the client's side.
• Insurance requirements vs. reality. Never promise coverage limits you do not carry. If the contract demands $2 million and you carry $1 million, either raise your limits or renegotiate the clause — a breach of the insurance covenant is itself a contract breach.

Keep signed contracts, statements of work, change orders, and delivery-acceptance emails organized by client and year. If a claim ever arrives, your insurer's first request will be the paper trail, and a clean archive shortens the defense considerably. This is pure bookkeeping hygiene: the same discipline that keeps your revenue recognition straight keeps your legal defense cheap.

Common Mistakes When Buying Tech E&O​

• Buying general liability and assuming it covers professional mistakes. It does not. General liability covers slips, falls, and broken things — not bad code or late delivery. Roughly half of first-time buyers discover this gap only after a claim is denied.
• Underinsuring the limit to save a few hundred dollars. The price difference between $500,000 and $1 million in coverage is often under $20 a month. Enterprise clients expect $1 million minimums anyway.
• Hiding prior work or known disputes on the application. Material misrepresentation lets the insurer void the policy precisely when you need it.
• Ignoring the retroactive date when switching carriers. Covered above, worth repeating: confirm it in writing every time you move.
• Skipping the cyber bundle. If your work touches client data, quote E&O plus cyber together and compare against E&O alone before deciding.
• Forgetting prior-acts coverage for side projects. Code you wrote as a freelancer last year and now support through your new LLC may need explicit prior-acts scheduling on the new entity's policy.

A Practical Buying Checklist​

1. Gather last year's revenue, headcount (including contractors), and a one-paragraph description of your services.
2. Decide your limits: $1M/$2M is the small-business default and satisfies most client contracts.
3. Get at least three quotes — include one tech-specialist broker, since generalist agents often misclassify software work.
4. Compare the retroactive date, deductible, defense-costs treatment (inside or outside the limit), IP coverage, and subcontractor coverage on each quote, not just the premium.
5. Ask for a bundled E&O-plus-cyber quote alongside the standalone E&O price.
6. Calendar the renewal date, the retroactive date, and the premium in your accounting system so a lapse never happens by accident.

Keep Your Protection — and Your Books — Current​

Insurance only works when the paperwork behind it is accurate: revenue figures that match your tax return, contractor headcounts that match your 1099s, and premium payments recorded where you can find them at renewal. If your books cannot answer "what did we pay for E&O last year, and when does it renew?" in under a minute, that is a bookkeeping problem wearing an insurance costume.

Beancount.io offers plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.