The build was fine. Their business still stopped.
Cover for software companies, agencies and independent developers — where the loss is a client’s money rather than anybody’s property, and the contract you signed decides how much of it is yours.
Tell us the situation.
A licensed human replies the same business day — not an auto-responder, and not five producers calling at once. We shop it across our carriers and tell you if the policy you already have is the right one.
We use this to quote and service your insurance, and we do not sell it or pass it to lead networks. Privacy policy.
What software developer businesses actually need.
Technology E&O
Claims that the software failed to perform, was late, or was wrongly implemented.
Without it — The defining claim in this trade and outside general liability entirely.
Cyber liability
A breach of your systems or of client data you hold.
Without it — Holding a client’s data makes their breach your incident.
Intellectual property
Infringement claims over code, libraries, licenses or a product name.
Without it — One incompatible open-source license can force a rewrite.
Contractual liability
The indemnities and liability caps in client master service agreements.
Without it — Enterprise contracts routinely require limits nobody checked before signing.
General liability and property
The ordinary business exposures, plus equipment.
Without it — Frequently the only policy a young software company holds.
What software developer operators ask us.
Our contracts cap our liability. Why buy cover?
Because a cap limits what you might ultimately pay and does nothing about getting there. Defense costs on a disputed project are frequently the entire loss, and they start immediately. Caps are also challenged, are unenforceable in some circumstances, and bind only the party who signed — not a third party harmed downstream. A cap and a policy do different jobs and enterprise clients increasingly require both.
Do we need cyber as well as E&O?
Usually yes, and most technology programs put them on one combined form so the two cannot argue. The split is simple: cyber answers a breach of DATA, E&O answers a failure of the SERVICE. A deployment that takes a client offline is E&O. Ransomware in your environment that exposes their records is cyber. An incident that does both — which is common — is much easier to claim when one insurer holds both.
We use AI models in the product. Does that change anything?
It is the live question in this class and worth raising rather than hoping. Underwriters are asking whether model output reaches an end user unreviewed, whether it informs decisions with legal or financial consequence, what training data was used, and what the terms say about accuracy. Some forms now carry AI-specific wording and a few carry exclusions. Describe how it is actually used — a drafting aid and an automated decision engine are not the same risk, and being vague reads as the worse one.
Not ready to talk? The guides answer the questions this page raises in more depth. Already insured with us and need a certificate or a policy change? Ask the service team rather than starting a quote — it is faster and it goes to the people whose job it is. We also write home and auto, which is usually cheaper alongside the business policy than apart from it.