How Much Insurance Does a FinTech, HealthTech, and Vertical SaaS Company Actually Need? A Limits Framework
When a customer's legal team requires $5M in Tech E&O, it usually isn't based on a real assessment of their exposure — it's a number someone inserted into their MSA template three years ago and nobody has updated since. That doesn't mean you should ignore it. It means you need a framework for deciding when the number is legitimate, when it's negotiable, and when paying for higher limits is the right business decision versus a cost you're absorbing to close a deal faster.
The short answer — and why "what the customer requires" is not the same as "what you need"
Your customer's MSA requirement and your actual risk exposure are two different questions. Most enterprise procurement teams insert insurance minimums that were set when the company last updated its vendor policy — which may have been five years ago, for a different risk profile entirely. The right limits for your company are a function of your product's role in the customer's workflow, the size of the losses your failure could plausibly cause, and your own balance sheet's ability to absorb a claim before insurance kicks in.
If your software sits in a high-stakes workflow — processing payments, generating health-related outputs, automating lending decisions — a $5M requirement isn't boilerplate. It reflects real exposure. If your product is a reporting layer or an operations dashboard where your failure causes inconvenience rather than financial loss, $1M/$2M is usually adequate and the $5M ask is worth pushing back on.
When $1M/$2M limits are sufficient
Most vertical SaaS companies at $3M–$10M ARR selling to SMBs are adequately covered by a $1M per-claim / $2M aggregate Tech E&O policy. The test is whether your product's failure could plausibly cause a customer loss large enough to generate a $2M claim. For most operational SaaS — scheduling, field service management, property management workflows — the answer is no. A bug in your scheduling software costs your customer time and maybe a customer complaint. It does not generate a seven-figure loss.
Standard $1M/$2M limits are appropriate when:
- Your customers are SMBs with aggregate annual contracts under $100K
- Your software is an operational layer, not a transaction or decision engine
- Your contractual liability cap in the MSA is already limited to fees paid in the prior 12 months
- Your customer base is distributed — no single customer represents more than 10–15% of revenue
According to SVB's startup insurance guide, most early-stage B2B SaaS companies start with $1M Tech E&O limits and increase only when enterprise contract requirements demand it.
When you need to go to $5M or higher
Three situations make $5M limits legitimate rather than just a procurement ask.
You process payments or enable financial transactions. If your platform sits between money moving between parties — embedded payments, lending origination, insurance premium collection — your failure can cause direct, traceable financial loss at scale. A payment processing error doesn't cost one customer one month of inconvenience. It can affect thousands of their end customers at once. FinTech platforms and vertical SaaS with embedded payments should default to $5M and evaluate from there.
Your outputs have clinical or regulatory consequences. HealthTech platforms generating care recommendations, medication alerts, or billing outputs that affect reimbursement face a structurally different claims environment. A single adverse outcome traced to your software can generate a claim that exceeds $2M before legal fees. The EPLI and professional liability markets treat HealthTech as a distinct risk category for this reason.
You're signing enterprise contracts with Fortune 1000 customers. At this level, the procurement requirement is often real — legal teams at large enterprises set minimums based on their self-insurance thresholds, not templates. If your customer's legal team can articulate why they need $5M, take the requirement at face value.
Key questions before you increase limits
Before paying for higher limits, get answers to four things:
- Is the requirement in the MSA or in an exhibit? Insurance requirements buried in exhibits are more negotiable than those in the body of the agreement. Ask procurement which section it's in.
- What is their actual self-insured retention? If the customer carries a $500K SIR on their own policies, a $5M requirement from you is partially redundant. That's negotiating leverage.
- What is your contractual liability cap? If your MSA already limits your liability to fees paid in the prior 12 months and that's $50K, no insurance restructuring changes your actual exposure — it changes the customer's perception of your risk profile.
- Will they accept a 30-day cure window? Many customers will accept a clause that gives you 30 days to obtain higher limits after contract signing rather than requiring coverage before signature. This lets you evaluate the real requirement before you pay.
Second-order effects — what higher limits change in your MSA negotiations and renewal pricing
Increasing your limits doesn't just affect your premium. It changes the negotiating dynamic on your MSA. When you carry $5M in Tech E&O, insurance is removed as a procurement blocker and it signals maturity to enterprise buyers. That's worth something independent of the coverage itself.
The renewal effect runs the other direction. Per Corgi's cost-by-stage data, growth-stage companies should expect annual premiums of $10,000–$25,000 or more across the full stack. Limits increases at renewal are underwritten based on claims history and revenue growth — a clean record makes the increase less expensive than founders expect. But starting with higher limits than you need inflates your base, which compounds at every renewal.
Buy the limits your actual risk profile requires. Negotiate the MSA requirement where you can. Increase when enterprise contracts make the math work.
Sources
- SVB Startup Insurance Guide for Founders — svb.com
- Corgi: Who Offers a Full-Stack Insurance Platform for Venture-Backed Companies — corgi.insure
- Founder Shield: Cyber Liability Insurance for Startups — foundershield.com
