DEV Community

Naveed Malik
Naveed Malik

Posted on AI-assisted

Freelance developer? Here's the business insurance clients will actually ask you for

Sooner or later a client contract arrives with an "Insurance" clause: Professional liability, $1,000,000 per claim. Certificate of insurance before kickoff. Name us as additional insured. If you just want to write code, it's easy to sign without knowing what any of that means.

If you freelance or contract as a developer, you'll hit this sooner or later, usually with bigger clients, agencies and anything enterprise. Here's a plain-English map of what those clauses mean, which policies developers usually need, and what they typically cost. It's meant as a starting point, not the final word.

Disclosure: I run InsuranceByTrade, a free, independent site that explains small-business insurance by trade. It sells nothing and isn't an insurance agency. I'm not a licensed insurance professional, so treat this as orientation, not advice. This post was drafted with AI assistance and checked by me.

The short version

Policy What it covers for a developer Median cost (Insureon 2026)
Professional liability (tech E&O) Claims that your work caused a client a financial loss: a bug, a missed deadline, a feature that didn't do what was promised $88/month all businesses (about $1,056/year)
Cyber insurance Data breaches and cyber incidents: notification costs, recovery, related claims $129/month all businesses (about $1,548/year)
General liability Bodily injury or property damage to other people, e.g. you knock over a client's monitor on site $30/month for technology businesses
Business owner's policy (BOP) General liability plus coverage for your own business property $46/month for technology businesses

Insureon's 2026 medians come from 100,000 small-business customers, mostly businesses with 1–4 employees. Your price depends on revenue, the kind of work, the limits you choose, your deductible and your claims history.

Professional liability (E&O) is the one that matters

For most developers, the realistic risk isn't someone tripping over a cable. It's a client saying your work cost them money. For example (illustrative):

  • An e-commerce checkout you built has a bug that silently drops orders over a weekend, and the client claims lost revenue.
  • A migration script you wrote corrupts customer records, and the client pays to restore them.
  • You miss a launch deadline written into the contract, and the client says it cost them a partnership.

Even if you did nothing wrong, defending a claim costs money. Professional liability (often called errors and omissions, or tech E&O for software work) covers claims of negligence, mistakes or failing to deliver a professional service, including legal defense.

General liability does not cover professional mistakes. It's an easy thing to get wrong.

Decoding the contract clause

"$1,000,000 per claim / $2,000,000 aggregate": the most the policy pays for one claim, and the most it pays in total during the policy year. $1M per occurrence and $2M aggregate is the most common general liability limit.

"Certificate of insurance (COI)": a one-page document from your insurer proving you have coverage. Clients, agencies and venues ask for it before you start. Your insurer issues it once you have a policy.

"Additional insured": the client wants to be added to your policy so it also protects them if they're pulled into a claim about your work. It's a common ask; your insurer adds it with an endorsement.

"Claims-made" vs "occurrence": E&O policies are often claims-made. They cover claims filed while the policy is active. If you cancel the policy and a client sues next year about old work, you may have no cover unless you bought tail coverage. Occurrence policies (typical for general liability) cover incidents that happened during the policy period, whenever the claim is filed.

Do you actually need it?

Usually no law requires a solo developer to carry business insurance. In practice the requirement comes from clients: larger companies, agencies and government contracts often won't sign without a COI.

A rough guide:

  • Solo, small clients, low-risk work: often no requirement, but E&O is still worth pricing.
  • Agency or enterprise contracts: expect a professional liability requirement, usually $1M.
  • You handle client data, payments or health info: add cyber insurance to the list.
  • You hire employees: most states require workers' compensation once you have employees. The thresholds vary a lot by state; here's a state-by-state table.

Ways to keep the cost down

  • Write a clear contract: scope, acceptance criteria and a limitation-of-liability clause reduce both risk and premium.
  • Choose limits that match your contracts, not the biggest number on the form.
  • Bundle general liability and property into a BOP if you need both.
  • Pay annually if the insurer discounts it.
  • Keep your claims history clean: version control, backups and written change requests are also good evidence if a dispute ever happens.

Further reading

If you've been through an insurance clause negotiation with a client, I'd love to hear how it went in the comments. What did they ask for, and what did you push back on?

Top comments (0)