Business Finance

insurance

Risk & Decision ScienceDifficulty: ★★☆☆☆

insurance (how much to charge to cover average claims?)

Your e-commerce platform ships 10,000 orders a month. About 5% arrive damaged - a 5% defect rate - and replacing each one costs $40. A product manager proposes adding a $2.99 optional "shipping protection" at checkout. The Expected Value of claims is $2.00 per order, so $2.99 looks profitable. But the people who buy protection aren't a random sample of your customers - they're the ones who expect problems. Does the math still work when your opt-in pool files claims at double the population rate?

TL;DR:

Insurance is a financial product where you charge a price that exceeds the Expected Value of claims you'll pay out. The difference is your per-policy Profit - but only if you price for the defect rate of the people who actually buy, not the population average. The Buyer has an Informational Advantage about their own risk, and that advantage will break your P&L if you ignore it.

What It Is

Insurance is a deal: one party pays a predictable fee now, and the other party absorbs unpredictable costs later. As an Operator, you encounter insurance from both sides:

  • Buying it: You pay a fixed fee to transfer risk off your P&L (property coverage, liability policies, cyber coverage).
  • Selling it: You charge customers a fee to cover their downside (warranties, protection plans, uptime guarantees with financial penalties).

Both sides use the same math. The price of insurance starts with the Expected Value of claims - the probability-weighted average payout. Then you add enough above that to generate Profit. That spread is what makes insurance a sustainable financial product instead of a transfer payment.

The formula:

Price = E[claims] + per-policy Profit

If E[claims] per customer is $2.00 and you charge $2.99, your per-policy Profit is $0.99. Multiply by volume and you have a business - if your estimate of E[claims] is accurate for the people who actually buy.

Why Operators Care

Insurance shows up on your P&L in three ways:

  1. 1)As a cost: Every business buys insurance - property, liability, errors & omissions. These are Fixed Obligations that hit your Cost Structure whether Revenue is up or down.
  1. 2)As a Revenue Line: Protection plans, extended warranties, and guaranteed-uptime contracts are insurance products you sell. They generate high-Profit Revenue because the price exceeds expected claims by design.
  1. 3)As a risk retention decision: When you skip buying coverage and absorb losses yourself, you're making a capital discipline call. You keep the fees you would have paid an insurer, but you eat the claims when they come. That's a bet on your own risk appetite and your ability to handle Variance.

The key insight for Operators: insurance is not just a line item you pay. It's a Unit Economics lever. Offering a protection plan at checkout can flip a Cost Center (customer support for damaged goods) into a Profit center - if you price it correctly.

How It Works

Pricing Step by Step

We'll use the hook scenario throughout. You ship 10,000 orders/month with a 5% defect rate and $40 replacement cost.

Step 1: Calculate Expected Value of claims.

E[claims] = P(claim) × cost per claim = 0.05 × $40 = $2.00 per order

This is your break-even floor. Charge less than this and you lose money on every policy.

Step 2: Price above break-even.

Your price must exceed E[claims] by enough to cover two things:

  • Variance in actual claims: At 10,000 orders/month, actual claims cluster near Expected Value. At 100 orders/month, a single bad week could produce twice the expected claims. The relationship is direct: as Pipeline Volume grows, the Standard Deviation of your per-policy cost shrinks relative to the mean. High volume makes results predictable. Low volume means you need a wider spread above break-even to survive the swings.
  • Operating costs: Someone processes claims and handles support. These are Fixed vs Variable Costs layered on top of claim payouts. (The first worked example below includes this calculation.)

Common practice for simple protection products: price 25-40% above E[claims]. So $2.00 × 1.30 = $2.60, rounded to $2.99 for a clean price point.

Step 3: Adjust for adverse selection.

This is the step most Operators skip, and it's the one that breaks the P&L.

When insurance is optional, the people who buy it are not a random sample of your customers. They're disproportionately the ones who *expect to file claims* - they've had damage before, they're shipping fragile items, or they're ordering to an address where packages get stolen. The Buyer has an Informational Advantage about their own risk that you don't have at the point of sale.

This means your opt-in pool's defect rate will be higher than the population average. If the population defect rate is 5%, expect the opt-in cohort to land between 8-12%. The exact number depends on how strongly the protection purchase correlates with risk.

The Pricing implication is concrete: if the opt-in cohort's real defect rate is 10% instead of 5%, E[claims] doubles to $4.00 per policy. At $2.99, you're losing $1.01 on every policy sold. The checkbox that looked like free Profit is now a Cost Center.

What to do about it:

  • Price for the opt-in pool's defect rate, not the population average. Start with a conservative estimate (1.5-2x the population rate) until you have cohort-specific data.
  • Use customer segmentation to measure: compare the claim rate of protection buyers vs. non-buyers over 2-3 months. That ratio is your adverse selection multiplier.
  • If adverse selection is severe, consider making protection a default (opt-out) or bundling it into the product price. When everyone is covered, the pool's defect rate converges back toward the population average.

Step 4: Monitor and gate.

This is the Feedback Loop that keeps the product solvent. Track claims monthly for the opt-in cohort specifically. The metric that matters: actual claims paid / policies sold. If that ratio consistently exceeds your priced-in E[claims], you have two levers:

  • Raise the price.
  • Tighten eligibility (decline coverage for high-risk customer segmentation tiers).

This gatekeeping function - deciding which risks to accept at which price, before you issue the policy - is Underwriting. It's a front-door decision, not back-office monitoring. You evaluate a specific risk, decide whether to accept it, and set the price accordingly.

When to Use It

Sell insurance (offer a protection product) when:

  • You have enough Pipeline Volume that Variance smooths out. A few hundred transactions per month is a reasonable floor.
  • The failure event is costly enough that customers feel the pain (damaged shipments, broken devices, downtime) but infrequent enough that the price stays small relative to the product price.
  • You can estimate the defect rate from your own data - Payment History, support tickets, return rates - and you can measure the opt-in cohort's rate separately.
  • The price is small relative to the purchase price. A $2.99 add-on on a $50 order feels reasonable to the Buyer. A $30 add-on on a $50 item signals the product is unreliable.

Buy insurance (transfer risk off your P&L) when:

  • A single event could cause an Income Shortfall large enough to threaten operations - a lawsuit, a warehouse fire, a data breach.
  • The fee is small relative to the potential claims. This is a straightforward Expected Value comparison: if annual cyber insurance costs $5,000 and a breach could cost $500,000 with a 2% annual probability (E[loss] = $10,000), buying makes sense.
  • You're early-stage and can't absorb Variance. Retaining risk requires liquid assets. If your Cash Flow can't handle a worst-case quarter, transfer the risk.

Retain the risk (absorb losses on your own P&L) when:

  • You have the liquid assets and risk appetite to absorb bad outcomes.
  • The expected losses are small and predictable.
  • The cost of buying insurance significantly exceeds E[claims] - you're paying too much of someone else's Profit spread.

Worked Examples (2)

Pricing a Shipping Protection Plan (with Adverse Selection)

Same scenario as the hook: 10,000 orders/month, 5% population defect rate, $40 replacement cost. Your support team costs $25/hr including salary, benefits, and workspace overhead - the total per-hour cost to your P&L. Each claim takes about 5 minutes of support time: $25 x (5/60) = $2.08 per claim in labor. You offer optional shipping protection at checkout.

  1. Calculate E[claims] per order at population defect rate: P(damage) x (replacement + labor) = 0.05 x ($40.00 + $2.08) = 0.05 x $42.08 = $2.10 per order.

  2. Price with 40% spread above break-even: $2.10 x 1.40 = $2.94. Round to $2.99.

  3. Estimate Revenue: 30% of customers opt in: 3,000 policies/month x $2.99 = $8,970/month.

  4. Estimate claims at population rate: 5% of 3,000 = 150 claims x $42.08 = $6,312/month. Projected Profit: $8,970 - $6,312 = $2,658/month. Looks like a $32K/year business.

  5. Now apply adverse selection. After two months you pull cohort data: protection buyers file damage claims at 9%, not 5%. Revised E[claims] = 0.09 x $42.08 = $3.79 per policy. Revised claims cost: 270 claims x $42.08 = $11,362/month. At $8,970 in Revenue, you're losing $2,392/month. The product that projected $32K/year in Profit is actually a $29K/year loss.

  6. Corrective action: Reprice to $3.79 x 1.35 = $5.12, rounded to $4.99. Alternatively, bundle protection into the base product price for all orders - this eliminates adverse selection by covering the full population at the 5% rate. Bundled cost: $2.10 x 1.35 = $2.84 per order across all 10,000 orders = $28,400/month, but the defect rate stays at the population average.

Insight: The population-average defect rate is not the defect rate of the people who buy your product. Adverse selection - the Buyer's Informational Advantage about their own risk - is the single biggest Pricing trap in optional insurance. Always measure the opt-in cohort's claims separately and reprice within 60-90 days of launch.

Buy vs. Retain Risk: Cyber Liability

You're a SaaS Operator. Annual cyber insurance quote: $12,000. Your estimate: 3% chance of a breach per year, average breach cost $250,000 (legal fees, notification, downtime, lost customers). Your company has $80,000 in liquid assets.

  1. Calculate E[loss] without insurance: 0.03 x $250,000 = $7,500/year.

  2. Compare to the insurance price: Insurance costs $12,000/year. You're paying $4,500/year above E[loss]. That $4,500 is the insurer's Profit spread.

  3. Assess Variance and survivability: A $250,000 hit against $80,000 in liquid assets is fatal - an Income Shortfall that triggers Bankruptcy. Even though E[loss] is less than the insurance price, the Tail Risk matters. One breach wipes you out.

  4. Decision rule: Buy the insurance. The $4,500 annual spread above Expected Value is the price of survival. You're not paying for the average outcome - you're paying to avoid the catastrophic one.

Insight: Expected Value alone doesn't settle the buy-vs-retain-risk question. Weigh Variance and Tail Risk against your liquid assets. When a single bad outcome causes Bankruptcy, you buy insurance even when the price exceeds E[claims]. This is rational risk aversion, not waste.

Key Takeaways

  • Insurance Pricing starts with E[claims] and adds a Profit spread. If your price doesn't exceed the Expected Value of payouts, you don't have a financial product - you have a subsidy.

  • Volume reduces Variance per policy. At 10,000 policies, actual claims cluster near Expected Value. At 100, a bad month can drain your liquid assets. Pipeline Volume is a prerequisite for predictable insurance economics.

  • Adverse selection inflates your opt-in pool's defect rate above the population average. The Buyer has an Informational Advantage about their own risk. Price for the cohort that actually buys, not the population, and measure the gap within 60-90 days of launch.

  • The buy-vs-retain-risk decision isn't just about Expected Value. It's about whether your Cash Flow and liquid assets can survive the Variance. Tail Risk kills companies that only plan for averages.

Common Mistakes

  • Pricing on the population defect rate for an opt-in product. This is the most common trap. If your population defect rate is 5%, your opt-in cohort's rate will be higher - often 8-12% - because the Buyers who expect claims are the ones who buy protection. Use customer segmentation to measure the opt-in cohort separately and reprice accordingly.

  • Pricing on gut feel instead of data. Operators who skip the E[claims] calculation and pick a round number either leave money on the table or run the program at a loss. Use your own defect rate and claims data - they're in your support tickets and return logs.

  • Ignoring Variance at low Pipeline Volume. At 200 orders/month with a 5% defect rate, you expect 10 claims - but might see 3 or 20 in any given month. If you priced for exactly 10 and get 20 two months running, your liquid assets are gone. Build a wider spread above break-even for low-volume programs.

Practice

easy

You run a device rental company. You rent out 500 tablets per month. Data shows 8% come back with cracked screens (repair cost: $120 each) and 2% are lost entirely (replacement cost: $350 each). What's the minimum monthly fee per rental you need to charge for a "damage protection" add-on to break even? What price would you actually set, and why?

Hint: Calculate E[claims] as the sum of each failure type: P(cracked) x repair cost + P(lost) x replacement cost. Then decide how much spread above break-even you need.

Show solution

E[claims] = (0.08 x $120) + (0.02 x $350) = $9.60 + $7.00 = $16.60 per rental. That's your break-even floor. Add 25-40% above break-even for Profit and Variance cushion: $20.75 to $23.24. A $21.99 price point works. Important caveat: because this is opt-in, your actual cracked/lost rates among protection buyers will likely exceed the population rates. Monitor the opt-in cohort's claims after the first month and be ready to reprice.

medium

Your SaaS platform offers an uptime guarantee: if uptime drops below 99.9% in a month, you refund 10% of that customer's monthly fee. You have 200 enterprise customers paying $2,000/month each. Historical data shows you miss the 99.9% target about 4 months per year, and when you miss it, all customers are affected. Should you build this cost into your existing Pricing, or charge a separate fee? What's the annual expected cost of this guarantee?

Hint: Calculate the annual E[claims]. Each miss triggers a 10% refund for all 200 customers. Then consider: if you charge separately, adverse selection changes who opts in.

Show solution

When you miss uptime, you refund 10% x $2,000 x 200 customers = $40,000 per miss. At 4 misses/year, E[claims] = 4 x $40,000 = $160,000/year. Your annual Revenue is 200 x $2,000 x 12 = $4,800,000. The guarantee costs $160,000 / $4,800,000 = 3.3% of Revenue. Two options: (1) Build it into the $2,000 price - you're retaining the risk at ~$67/customer/month. (2) Offer a separate guarantee tier at $100/month that includes the financial guarantee plus priority support. Option 2 turns a liability into a Revenue Line. But watch for adverse selection: customers most likely to buy the guarantee are the ones whose Operations are most sensitive to downtime - meaning they're the most likely to invoke it. If you go with option 2, price for a higher-than-average invocation rate in the opt-in cohort.

hard

A competitor offers the same shipping protection you sell for $2.99, but charges $1.49. Your E[claims] for your opt-in cohort (after measuring adverse selection) is $3.79. Assuming similar Cost Structures, what are the possible explanations for their price - and what's your decision rule for whether to match it?

Hint: Either their E[claims] is genuinely lower (lower defect rate, different customer mix), they're subsidizing the program from other Revenue, or they haven't measured their opt-in cohort's actual defect rate yet. Think about what data you'd need.

Show solution

Three possibilities: (1) Their defect rate is genuinely lower - better packaging or a less fragile product mix means their opt-in cohort's E[claims] might be $1.00, making $1.49 profitable. (2) They're running the protection program at a loss to boost Close Rate on the core product, subsidizing from other Revenue. (3) They priced on the population defect rate and haven't discovered their opt-in cohort's adverse selection yet - they're losing money and don't know it. Decision rule: Don't match the price if it puts you below your cohort-specific E[claims]. At $1.49 against $3.79 in expected claims, you lose $2.30 per policy. Instead, investigate whether you can reduce E[claims] through Cost Reduction - better packaging, carrier changes, or product-mix restrictions on what qualifies for protection. If the cost to cut your defect rate from 9% to 4% is less than the per-policy Profit you'd recover, that's the right move. Competing on price below your own E[claims] guarantees negative Unit Economics.

Connections

Insurance depends on Expected Value (the Pricing floor) and claims (the payout variable). It connects forward to Underwriting (which risks to accept at which price), Risk Tolerance (your threshold for absorbing Variance before transferring risk), and Tail Risk (catastrophic outcomes that justify buying coverage above E[claims]). It connects laterally to Unit Economics and customer segmentation (critical for detecting adverse selection in opt-in pools), and upward to capital discipline (the buy-vs-retain-risk decision on your Operating Statement and Balance Sheet).

Disclaimer: This content is for educational and informational purposes only and does not constitute financial, investment, tax, or legal advice. It is not a recommendation to buy, sell, or hold any security or financial product. You should consult a qualified financial advisor, tax professional, or attorney before making financial decisions. Past performance is not indicative of future results. The author is not a registered investment advisor, broker-dealer, or financial planner.