Insurance requirements in contracts can feel like a minefield, especially for founders signing their first enterprise deal. The limits look high, the language is dense, and it's not always clear what you're actually agreeing to. But understanding contractual insurance obligations, and knowing when and how to push back, is one of the more practical skills a startup founder can develop.
This guide walks through why insurance requirements in contracts exist, what's commonly required, and how to negotiate terms that reflect your actual risk without overpaying.
Key Takeaways
- Insurance requirements in contracts exist to transfer risk, not to burden vendors. Understanding what each party is actually protecting against makes negotiation much more straightforward.
- The most common requirements in contracts are General Liability Insurance, Errors & Omissions (E&O) Insurance, Cyber Insurance, and Workers' Compensation. Additional insured and waiver of subrogation clauses are standard additions worth understanding before you sign.
- If limits don't match the actual exposure or the coverage type has no relevance to the work being performed, it's reasonable to negotiate.
- A Certificate of Insurance (COI) is a snapshot of your active coverage, not a guarantee of a claim being paid.
Why Do Contracts Include Insurance Requirements?
Contractual insurance obligations often catch founders off guard, especially when they're deep in a deal and suddenly staring at a wall of coverage requirements. Before pushing back or signing blindly, it helps to understand what these clauses are actually trying to accomplish and who they're designed to protect.
Risk Transfer and Liability Allocation
Insurance requirements in contracts aren't arbitrary. They exist because both parties need confidence that if something goes wrong, there's a funded mechanism to cover the loss.
When a company requires you to carry certain coverage, they're making sure that if something goes wrong, there's a funded mechanism to cover the loss. Rather than suing each other directly and hoping the other party can pay, both sides can rely on an insurance policy to make injured parties whole.
What Each Party Is Actually Protecting Itself From
The requiring party is typically protecting against two things: direct losses they might suffer because of your work, and third-party claims they could get pulled into because of their relationship with you.
A customer requiring E&O Insurance is making sure that if your software fails and causes them financial harm, there's coverage in place to respond. The limits are set based on the perceived level of risk, factoring in things like contract value, data sensitivity, physical exposure, and industry.
What Are the Most Common Insurance Requirements in Contracts?
Insurance requirements in B2B contracts follow a fairly predictable pattern, but the specific types and limits vary depending on the nature of the work, the data involved, and the size of the counterparty. Here's what shows up most often and what each one is actually protecting against.
Cyber Insurance
Any contract that involves data sharing, software access, or handling customer information will likely require Cyber coverage. Enterprise customers in particular specify minimum limits, often $1M to $5M depending on the sensitivity of the data involved. This is one of the requirements most worth having in place before contract negotiations begin, not after: Cyber and E&O show up in nearly 90% of contract-driven conversations in Vouch calls.
Professional Liability Insurance / E&O Insurance
Professional Liability Insurance, also called Errors and Omissions (E&O) Insurance, or Technology Errors & Omissions (Tech E&O) Insurance for software companies, covers claims that your work or product caused a customer financial harm. This is standard in B2B tech contracts and is often required alongside Cyber coverage.
General Liability Insurance
General Liability covers bodily injury and property damage caused to third parties. 3 out of 4 contract calls with Vouch are about GL, especially when any physical or legal presence exists. Typical required limits range from $1M to $2M per occurrence, sometimes with a $2M to $4M aggregate.
Workers' Compensation Insurance
If your team is performing work on-site at a client's location, Workers' Comp is almost always required. It's also mandated by most states regardless of contract requirements, so this one is rarely negotiable.
Additional Insured and Waiver of Subrogation Clauses
Additional insured requirements and waiver of subrogation clauses are two of the most misunderstood items in any vendor contract. They show up constantly in contracts and trip up a lot of founders.
An “additional insured” requirement means the other party wants to be named on your policy. If a claim arises from your work, they can be defended under your coverage directly, not just named in a lawsuit hoping you'll indemnify them. Most insurers can add additional insured status via endorsement, and a blanket additional insured endorsement covers all parties who require it contractually without needing individual endorsements for each.
A “waiver of subrogation” means your insurer agrees not to sue the other party to recover money it paid out on a claim. Without it, if your insurer pays a claim caused by the other party's negligence, they could theoretically pursue the other party for reimbursement. The waiver eliminates that exposure. Both are standard requests and worth confirming with your broker before a contract is signed.
How Do You Evaluate Whether a Contract's Insurance Requirements Are Reasonable?
Not every requirement in a vendor contract is calibrated to your actual engagement. Before accepting limits at face value, it's worth pressure-testing them against the real exposure involved. Negotiating insurance limits in vendor contracts is common practice. The key is knowing which requirements are reasonable and which ones are worth pushing back on.
Does the Limit Match Actual Exposure?
The most common red flag in contract insurance language is limits that don't reflect the actual risk involved. A Fortune 500 company might paste their standard vendor requirements into every contract, regardless of whether they're signing a $50,000 pilot or a $5M enterprise deal. If a startup is entering a small beta test, carrying the same limits required of a large enterprise vendor isn't proportionate.
The question to ask is: what is the realistic worst-case loss from this engagement? If the contract value is $100,000 and the required Cyber Insurance limit is $10M, that's worth a conversation.
Are You Being Asked for Coverage Irrelevant to the Work?
Another common issue is being required to carry coverage that has no bearing on the work being performed. General Liability Insurance makes sense if there's any chance of physical presence or in-person engagement. Commercial auto coverage doesn't make sense if no vehicles are involved. Workers' Comp may not be relevant for a fully remote software engagement.
Before agreeing to any requirement, ask whether the coverage type maps to actual exposure in this specific relationship. If it doesn't, it's a reasonable candidate for negotiation.
How Do You Negotiate Insurance Requirements in Contracts?
Knowing how to negotiate insurance requirements in a contract is one of the more underrated skills a founder can develop. The process is less confrontational than it sounds. Most counterparties are working from templates, and a well-reasoned redline goes a long way.
Step 1: Review and Redline
Start by reading the insurance section of the contract carefully. Mark anything that looks disproportionate, irrelevant, or unclear. Redlining is expected in commercial contract negotiations and signals that you've read the document and take the terms seriously.
Step 2: Understand Your Actual Risk with Your Advisor
Before you push back on anything, make sure you understand your real exposure. An insurance advisor can help you assess what coverage makes sense for your business and what limits are appropriate given your stage, industry, and the nature of the contract. Having coverage in place before negotiations begin also strengthens your position; you're not refusing requirements, you're proposing alternatives based on what you already carry.
Step 3: Calculate Opportunity Cost vs. Contract Value
If meeting the insurance requirements means significantly increasing your premiums, factor that into the contract economics. A $200,000 contract that requires $50,000 in additional annual premium is a different deal than it looks on the surface. If the numbers still work, proceed. If they don't, that's a legitimate negotiating point and one the other side can usually understand.
Step 4: Agree Only to Relevant Coverage
Don't sign off on requirements that don't apply to your work. If the contract requires coverage that has no connection to the services being performed, a simple explanation is usually enough: "We don't use vehicles in the performance of this work, so Commercial Auto isn't applicable here." Most procurement teams aren't trying to over-insure you; they're working from a template that may not have been tailored to your engagement.
Step 5: Don't Disclose Excess Coverage
When issuing proof of insurance, only show the limits required by the specific contract in front of you. If you carry $5M in Cyber coverage but a contract only requires $1M, issue a Certificate of Insurance (COI) showing $1M. You're not obligated to disclose your full program, and doing so can invite requests to increase required limits in future contracts or renewals.
Step 6: Provide Logical Rationale When Pushing Back
Negotiation goes better when you explain your reasoning rather than just rejecting requirements. A practical example: "We understand you require $5M in Cyber coverage for enterprise contracts. We currently carry $2M, which aligns with the scope and value of this engagement. We're happy to revisit limits as the relationship grows." That's a reasonable position, stated professionally, with an opening for future alignment.
What Is a Certificate of Insurance and How Does It Work?
When a customer or landlord asks for proof of coverage, what they're actually asking for is a Certificate of Insurance (COI). Understanding COI requirements in contracts, like what the document shows, what it doesn't guarantee, and how to issue one correctly, saves a lot of back-and-forth at the worst possible time.
What a COI Shows (and What It Doesn't Guarantee)
A (COI) is a one-page summary document that confirms your active coverage. It lists your insurer, policy types, limits, and effective dates. It's what most customers and landlords are asking for when they say "send us proof of insurance."
What a COI doesn't do: it doesn't guarantee coverage for a specific claim, and it doesn't create any contractual obligation on the insurer beyond what's in the underlying policy. If a claim arises after the policy lapses, the COI is irrelevant. It's a snapshot, not a guarantee.
How to Issue a COI with the Correct Limits and Endorsements
When a customer asks for a COI, they'll often specify what they need to see on it: coverage types, minimum limits, their company as additional insured, and sometimes a waiver of subrogation. Your insurer or broker issues the COI based on your active policy. If the required endorsements aren't already on your policy, they need to be added before the COI is issued. Most standard endorsements can be added quickly, but confirm timelines with your broker so you're not delaying a contract close.
What Should You Watch Out for in Contract Insurance Language?
The details buried in insurance language are where deals stall and surprises happen. A few specific patterns come up repeatedly in vendor contracts. Knowing them in advance puts you in a much stronger negotiating position.
Vague or Open-Ended Requirements
Watch for language like "adequate insurance" or "sufficient coverage" without specifying policy types or limits. These phrases are legally ambiguous and can be interpreted broadly after the fact. Push for specificity: named policy types, per-occurrence and aggregate limits, and clear endorsement requirements. Vague language benefits whoever is making the claim, not whoever signed the contract.
Limits That Exceed What Carriers Will Underwrite
Occasionally, contract requirements specify limits that are difficult or impossible to obtain in the current market at a reasonable price, or at all. This is especially common in contracts written by large enterprises for startup vendors. If a customer is requiring $20M in Tech E&O Insurance for a $75,000 engagement, that's worth flagging. It may reflect a template requirement rather than a deliberate position, and most procurement teams will adjust once the issue is raised.
Frequently Asked Questions
Why do contracts include insurance requirements?
They exist to ensure both parties have funded risk management in place. If something goes wrong during the engagement, insurance provides a mechanism to cover losses without either party having to pursue the other directly for damages.
What insurance is most commonly required in B2B contracts?
General Liability and Professional Liability (E&O) are the most universal. Cyber Insurance is standard in any contract involving data or software. Workers' Comp is required when personnel are performing on-site work.
What is an additional insured and why does it matter?
An additional insured is a party added to your policy who can be defended under your coverage if a claim arises from your work. It's a standard contract requirement and can usually be added via a blanket endorsement that covers all parties who require it contractually.
Do I have to disclose my full coverage limits to every customer?
No. Issue a certificate of insurance showing only the limits required by that specific contract. You're not obligated to share your full program, and doing so can create leverage for future limit increase requests.
What should I do if a contract requires coverage I can't get?
Raise it early. Some requirements reflect outdated templates rather than deliberate positions. Explain what you can obtain in the current market and propose an alternative that reflects your actual exposure. Most counterparties would rather adjust the requirement than lose the deal.
Vouch Specialty Insurance Services, LLC (CA License #6004944) is a licensed insurance producer in states where it conducts business. A complete list of state licenses is available at vouch.us/legal/licenses. Insurance products are underwritten by various insurance carriers, not by Vouch. This material is for informational purposes only and does not create a binding contract or alter policy terms. Coverage availability, terms, and conditions vary by state and are subject to underwriting review and approval.
.png)
