The software worked. The customer still lost money.
Professional liability for technology companies — claims that what you built, hosted or advised on failed to perform, where the loss is purely financial and no property was damaged.
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 technology errors and omissions businesses actually need.
Failure to perform
The product or service did not do what was promised, and the client lost money.
Without it — General liability answers injury and property damage, and a client’s lost revenue is neither.
Negligent advice or configuration
An implementation, migration or recommendation that caused loss.
Without it — The most common claim against an MSP or consultancy has no policy behind it.
Missed deadlines and cost overruns
Delay claims on fixed-scope work, which are the everyday disputes of this trade.
Without it — A disputed project becomes a self-funded legal argument.
Intellectual property infringement
A claim that code, content or a name infringes somebody else’s rights.
Without it — A library with the wrong license in it can end a product.
Combined with cyber
Most technology programs place E&O and cyber on one form, because a breach at a provider is both at once.
Without it — Two policies argue about which one responds while the client waits.
Where technology errors and omissions shows up.
- Software Developers
The defining claim in this trade and outside general liability entirely.
- Managed Service Providers
The routine claim against an MSP and not a cyber claim.
- Fintech
An outage during settlement is a financial loss to every user at once.
What technology errors and omissions operators ask us.
Do we need this as well as cyber liability?
They answer different halves of the same incident and technology companies generally need both — usually on one combined form. Cyber responds to a breach of data, including your clients’ data in your systems. Tech E&O responds to a failure of the service itself: the deployment that took the client offline, the integration that corrupted their records, the advice that did not work. An MSP whose error causes a client outage has an E&O claim, not a cyber one, and finds out which policy they bought at exactly the wrong moment.
Our contracts limit our liability. Is that enough?
It helps and it is not cover. Limitation clauses are routinely challenged, are unenforceable in some circumstances, and do nothing about defense costs — which in a disputed project are frequently the whole loss. They also do not bind a third party who was harmed but never signed anything. A good contract and a policy do different jobs.
Is this claims-made?
Almost always, and it changes how you buy it. Cover responds to claims MADE during the policy period rather than work done during it, so continuity matters more than the limit: let the policy lapse and the work you did last year stops being covered. Keep the retroactive date intact when you move insurer, and never let a gap open between policies.
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.