Seven Tech E&O Buying Mistakes SaaS Companies Make Before Signing Enterprise Deals
An enterprise customer asks for a limit, but your E&O policy has to stand up against the whole contract, not one number. Here are seven mistakes SaaS teams make before signing, and what to fix first.
The Insurance Schedule Is a Liability Negotiation, Not a Formality
Late in an enterprise deal, procurement sends the contract with an insurance schedule attached. It asks for $10 million in technology errors and omissions insurance, $10 million in cyber, a certificate within five business days and the customer named as additional insured. Sales wants it signed this quarter, so someone forwards the schedule to the broker and asks for a quote.
That's usually where things go wrong. The insurance schedule is one part of how the contract allocates risk. It only makes sense when you read it next to the limitation of liability clause, the indemnities, the data-protection addendum and the governing-law clause. If you buy insurance against the schedule alone, you can pay for a limit that doesn't match your real exposure. Or you can sign obligations your policy will never cover.
The seven mistakes below are common at SaaS companies of every size. They show up at 30-person startups selling to banks and at mid-market vendors with customers across Europe, India and the Gulf. Each one comes with what to fix before procurement signs off.
Buying the Limit the Customer Asks For Without Checking the Liability Cap
Customers often copy their insurance requirements from a template written for a much larger vendor. A $10 million E&O requirement on a $150,000 annual contract tells you about the customer's template. It doesn't tell you much about your exposure.
What to do instead: work out your realistic maximum contractual exposure first, then size the limit to fit it. Start with the limitation of liability clause. Many SaaS contracts cap general liability at around 12 months of fees. They then add super-caps or uncapped carve-outs for data breaches, confidentiality, IP infringement and gross negligence. Those carve-outs are what drive your exposure.
Hypothetical example: a 60-person SaaS company signs a $400,000-per-year deal. The general cap is 12 months of fees ($400,000). A data-breach super-cap is set at three times fees ($1.2 million), and IP indemnity is uncapped. A $10 million E&O limit looks generous for the capped items. The real problems are the uncapped IP indemnity and the fact that 40 customers share this one aggregate limit. The better move is to negotiate the IP indemnity down to a super-cap. Then buy a limit sized to your worst plausible year across all customers. Here that might be $5 million rather than $10 million.
Decision rule: if the requested limit is more than about five times the contract's highest negotiated cap, push back on the requirement before you buy more insurance. Customers often accept a lower limit once you show them the cap math, especially on mid-sized contracts.
Missing the Contractual Liability Exclusion
Almost every E&O and cyber policy has some form of contractual liability exclusion. It removes cover for liability you take on under a contract, except liability you would have had anyway without that contract. For SaaS vendors, it bites in three places:
- Broad indemnities, such as a promise to indemnify the customer for "any and all losses arising from" your service, whether or not you were negligent.
- Service credits, refunds and fee rebates, which many policies exclude outright as return of fees.
- Liquidated damages and fixed penalties for missed SLAs or breach-notification deadlines.
What to do instead: before redlines go back to the customer, have your broker read the indemnity and SLA clauses against your actual policy wording. Look for a carve-back that keeps cover for contractual indemnities tied to a covered wrongful act. Some insurers include it as standard, and others add it by endorsement. If you can't get cover, narrow the indemnity to third-party claims caused by your negligence or breach. Treat service credits as an uninsured cost and price them into the deal.
Regulatory fines need separate attention. Fines can arise under the GDPR, the UK GDPR, India's DPDP Act, Brazil's LGPD and similar laws. Whether they can be insured depends on local law, and in some jurisdictions the answer is unclear or no. Don't agree to reimburse a customer's regulatory fines on the assumption that your policy will pay.
Getting the Retroactive Date Wrong
Tech E&O is almost always written on a claims-made basis. The policy covers claims made during the policy period, but only for errors that happened after the retroactive date. If the code or services behind a claim predate your retro date, you have no cover. That's true even if the policy is in force when the claim arrives.
Retro dates get reset more often than buyers realize. Common triggers include:
- switching carriers without negotiating full prior-acts cover
- buying E&O or cyber for the first time years after the company started
- acquiring a product whose code was written before your policy began
What to do instead:
- Confirm the retro date separately for each coverage part, because combined tech/cyber policies sometimes carry different dates.
- When you change insurers, make keeping your existing retro date a condition of the move.
- For acquisitions, check whether the seller bought run-off (extended reporting) cover. Ask your insurer to cover the acquired entity's prior acts.
- If a contract requires cover "for the term plus three years," budget for one of two things. Either buy an extended reporting period, or commit to keeping claims-made cover in force after the contract ends.
Ignoring Where the Policy Actually Applies
A policy labeled "worldwide" may not be worldwide in practice. Two clauses matter here:
- Territory is where the wrongful act or loss happens.
- Jurisdiction is where a claim can be brought.
Some wordings, often from UK, European and Asian markets, give worldwide territory but exclude suits filed in the US or Canada, or cover them only for extra premium. Others cover broad jurisdiction but limit territory.
Admitted insurance is a separate issue. Some countries restrict non-admitted cover for local risks, and the rules vary in strictness. Brazil, India and China are frequently cited examples. A customer in one of these markets may require a policy from a locally licensed insurer instead of a global policy written abroad. Enterprise buyers in the UAE, Saudi Arabia and parts of Southeast Asia sometimes ask for local paper as well.
What to do instead: list your customers by governing law and claim venue. Then check the policy's territory and jurisdiction clauses against that list. If you earn significant revenue in countries with admitted-insurance rules, ask your broker about a controlled multinational program. In that setup, a master policy sits above local policies. Expect it to add cost and lead time, and plan in weeks, not days.
Treating Tech E&O and Cyber as One Shared Pot
Many SaaS companies buy a combined tech E&O and cyber policy with a single aggregate limit. It's simple and usually cheaper. The catch is that your own breach-response costs come out of the same limit that protects you against customer claims. Those costs include forensics, notification, restoration and ransomware negotiation. A single serious incident can use up most of the limit before the lawsuits arrive.
Read the sublimits too. Ransomware, regulatory defense, PCI assessments and social-engineering fraud are often capped well below the headline limit. A customer that requires "$10 million cyber" may not accept a $10 million policy with a $1 million regulatory sublimit as compliant.
What to do instead: if your contracts include data-breach super-caps, check whether your aggregate is shared or split. Where it's shared, consider structuring excess layers so third-party liability has its own capacity. Before you confirm compliance in writing, check the sublimit schedule against each enterprise contract's insurance requirements.
| Limit purchased (tech E&O + cyber) | Indicative annual premium, SaaS with roughly $5M–$30M revenue |
|---|---|
| $1M primary | $4,000–$15,000 |
| $3M primary | $10,000–$35,000 |
| $5M (primary plus excess) | $18,000–$60,000 |
| $10M (primary plus excess) | $35,000–$110,000 |
These are typical 2026 market ranges, and they vary widely. Premiums depend on your contracts, security controls, claims history, data volume and region. Rates in London, continental Europe, Singapore and India can differ significantly from North American pricing, so confirm figures with brokers and insurers. Excess layers generally cost less per million than the primary layer. That's why going from $5 million to $10 million rarely doubles the premium.
Promising Certificate Terms the Policy Can't Deliver
A certificate of insurance shows that a policy exists. It doesn't change what the policy covers. In the US it's commonly an ACORD form. In the UK, Europe and much of Asia it's more often a broker's letter of insurance.
Enterprise insurance requirements often ask for terms a certificate can't create by itself:
- additional insured status
- waiver of subrogation
- primary and non-contributory wording
- 30 days' notice of cancellation
On a professional liability policy, additional insured status is often unavailable or of little practical value. The customer usually isn't the one at risk of being sued for your professional errors. If you agree to it and can't deliver, you're in breach of contract from day one.
| Common customer request | Typical position for tech E&O | What to do |
|---|---|---|
| Additional insured | Rarely available; more common on general liability | Offer it on general liability only; strike it for E&O |
| Waiver of subrogation | Sometimes available by endorsement | Confirm with your broker before agreeing |
| 30-day cancellation notice to customer | Insurers often won't commit to it | Agree that you, not the insurer, will give notice |
| Occurrence-based cover | Not standard; E&O is claims-made | Offer claims-made with a tail commitment |
| Insurer rated A- or better | Usually achievable | Check your carrier's current rating |
Bringing the Broker In After Procurement Has Signed
This last mistake causes most of the others. If the broker first sees the contract after it's signed, every gap turns into either an expensive mid-term endorsement or an uninsured obligation. Underwriters also need time. Raising limits or adding US jurisdiction mid-term brings new questions about MFA, backups, secure development practices and incident history. Answering them can take several weeks.
What to do instead: make insurance review part of the deal desk before final redlines. Keep a one-page insurance position sheet that sales and legal can share with customers early. It should list:
- current limits and how the aggregate is structured
- your retro date
- territory and jurisdiction
- notable sublimits
- the certificate terms you can and can't give
Set an escalation threshold that sends a contract to your broker before it goes back to the customer. Good triggers are any requested limit above your current insurance tower and any uncapped indemnity.
Policy wordings and local insurance law vary, so have a licensed broker or coverage counsel confirm how your policy would respond before you commit to contract terms. For a next step, pull your three largest pending enterprise contracts. Line up their liability caps, indemnities and insurance schedules next to your current policy declarations, and send that comparison to your broker this week.
Questions buyers ask
How much tech E&O limit does a SaaS company need for enterprise deals?
Enterprise insurance schedules commonly ask for somewhere between $2 million and $10 million, but one customer's template shouldn't set your limit. Base it on three things: your negotiated liability caps, your super-caps and uncapped carve-outs, and your total exposure across all the customers who share the aggregate. Map your largest contractual exposures first, then size the limit with your broker.
Can a customer be named as additional insured on a tech E&O policy?
Usually not, and when it's possible it adds little practical value. Additional insured status is standard on general liability policies but uncommon on professional liability, because the customer typically isn't exposed to claims for your professional errors. Offer it on general liability and negotiate it out of the E&O requirement.
Does tech E&O cover service credits or refunds owed under an SLA?
Generally not. Most wordings exclude return of fees, service credits and liability taken on purely by contract. Some insurers offer limited carve-backs, so have your broker check your specific wording. Otherwise, treat service credits as a business cost and price them into the deal.
What happens to my retroactive date if I switch tech E&O insurers?
It depends on what you negotiate. If the new insurer sets a fresh retro date, errors made before that date may not be covered, even when the claim arrives during the new policy. Make keeping your existing retro date a condition of moving, and confirm it in writing for each coverage part before the old policy lapses.
Written by the Auditvault Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.