Where Series B SaaS Companies Should Get D&O, Tech E&O, EPLI, and Cyber — And Whether One Platform Can Cover All Four
At Series B, the insurance question isn't whether you need D&O, Tech E&O, EPLI, and Cyber — you need all four. The question is whether consolidating them onto one platform is good advice or a broker optimizing their book of business. The honest answer: consolidation makes sense when the coordination cost and coverage gap risk of managing four separate carriers outweighs the underwriting benefit of placing each line independently. For most Series B SaaS companies, it does. But the decision depends on your claims history, your carrier relationships, and what your enterprise customers are actually requiring.
The short answer — what changes at Series B that makes your Series A setup inadequate
Series A insurance was built around a company with a small team, early enterprise customers, and a board that was still establishing governance norms. Series B is different in three specific ways that break the Series A setup.
Your headcount is larger and more managed. Series A companies often have 20–40 people and informal HR. Series B companies typically have 60–150 people, dedicated HR functions, formal performance reviews, and terminations. That's EPLI exposure — employment practices claims alleging wrongful termination, discrimination, or harassment — that your Series A policy either excluded or covered inadequately.
Your board has formal governance expectations. Institutional Series B investors bring board seats with them, and those board members expect D&O that is structured for a company with real governance risk — not a $5M per-claim limit written for a pre-revenue startup. Retroactive dates matter here: if your D&O coverage has a gap between your Series A policy and your Series B renewal, you have uncovered exposure for the period in between.
Your enterprise customers have more complex requirements. Series B companies are often signing contracts with larger enterprises that require specific limits, additional insured endorsements, and evidence of coverage across multiple policy lines — not just a single certificate. Managing four separate carriers means four separate certificates and four separate renewal timelines that need to be tracked.
When consolidating onto one platform makes sense
| Scenario | Consolidate | Keep separate |
|---|---|---|
| First time buying full stack at Series B | ✓ | |
| Four separate carriers, no claims history | ✓ | |
| Broker managing multiple renewals on your behalf | ✓ | |
| One carrier has a specialty line (e.g., HealthTech E&O) | ✓ | |
| Prior claim on one line affects others if consolidated | ✓ | |
| Carrier specialization in your vertical matters | ✓ |
Consolidation is the right default for most Series B SaaS companies who are building their first complete stack. The practical benefits are concrete: one certificate, one renewal date, one underwriting relationship, and one point of contact when a claim is filed. Per Corgi's platform data, growth-stage companies can bind full D&O, Tech E&O, EPLI, and Cyber coverage in a single day — versus two to four weeks through legacy multi-carrier processes. When you're trying to close an enterprise contract that requires proof of coverage, the difference between one day and three weeks is not administrative — it's a deal risk.
When you need separate carriers for each policy type
Three situations make the multi-carrier approach worth the coordination cost.
You have a prior claim on one line. A claim on your Cyber policy affects your Cyber renewal pricing. If your Cyber is consolidated with your D&O, a bad claim year on one line can affect the underwriting posture on all four when you're negotiating renewal. Separate carriers give you isolation — a claim on one policy doesn't contaminate the others.
Your vertical has specialty underwriters. HealthTech E&O and fintech professional liability are underwritten by carriers with specific domain expertise that general platforms don't always access. If your product generates clinical outputs or processes payments at scale, a specialist carrier for those lines may offer meaningfully better terms and fewer coverage exclusions than a consolidated platform.
Your D&O limits are being negotiated for a specific M&A context. If you're approaching an exit and need D&O structured around representations and warranties or a specific transaction, you may need a specialized carrier and policy form that a full-stack platform can't provide. This is niche, but it's worth knowing the edge.
Key questions to ask before you consolidate
- What is the retroactive date on each policy? Before you consolidate, confirm that your new platform will honor the retroactive dates from your existing policies — not reset them. A retroactive date reset is a coverage gap, not a paperwork issue.
- What happens to your other lines if you file a claim on one? Ask the platform explicitly whether a claim on your Cyber policy affects the underwriting on your D&O at renewal. The answer should be no — they should be rated independently.
- Who advocates for you when a claim is disputed? On a fully consolidated platform, the same carrier who issued the policy is the one evaluating your claim. Ask how disputes are handled and whether you have independent claims advocacy.
- What are your enterprise customers actually requiring? If your largest customer requires a specific carrier for one of your policy lines, consolidation may not be fully possible. Pull the MSAs before you commit to a platform.
Second-order effects — limits, retroactive dates, and claims complexity at Series B scale
The second-order effects of consolidation at Series B are mostly favorable, but the risks are concentrated in two places.
Retroactive dates are the most common hidden risk. When you move from four separate carriers to one consolidated platform, each policy needs to carry the retroactive date from your previous policy — not the date the new policy was issued. Every claims-made policy (D&O, Tech E&O, Cyber, and often EPLI) has a retroactive date. A new carrier that sets the retroactive date at the inception of the consolidated policy leaves you with a gap for the period between your old policy's expiration and the new retroactive date. Per Embroker's guidance on switching insurance providers, this is the most common and most costly mistake in an insurance transition.
Claims complexity at Series B scale is different. A claim against a Series A company is usually a single-line dispute. A claim against a Series B company — particularly an M&A dispute, a securities claim, or an enterprise customer allegation — often touches multiple policy lines simultaneously. D&O and Tech E&O can both be implicated in an enterprise customer claim that also involves a board decision. Having those policies consolidated with one carrier simplifies coordination; having them with separate carriers gives you two independent advocates. Both are defensible — what matters is that you've thought through which you want before you need it.
Sources
- Corgi: Who Offers a Full-Stack Insurance Platform for Venture-Backed Companies — corgi.insure
- Embroker: How to Switch Business Insurance Providers — embroker.com
- Pillar Companies: The Insurance Stack — A Battle for Margin — medium.com
