← App Prototypes
App Prototypes 2026-10-22

Cover Path

You got a non-renewal letter or a premium shock. Find your state's insurer of last resort, the home upgrades that still unlock a discount, and the order to do them in before your policy lapses.

Cover Path
Prototype

CoverPath

You got a non-renewal letter or a premium shock. Find your state's insurer of last resort, the home upgrades that still unlock a discount, and the order to do them in before your policy lapses.

Date: 2026-10-22 Form factor: web app Status: Prototype

What it is

CoverPath takes the three facts on a homeowner's notice — state, reason (non-renewal, a renewal at a much higher premium, or no insurer willing to quote), and the date coverage lapses — and turns them into a specific plan. It matches the home's existing upgrades against the state's documented mitigation credits, estimates a re-quote with that discount applied, and shows the premium range for the state's FAIR Plan or wind pool as a fallback. The output is an ordered checklist, not a lecture about insurance terminology.

Who it serves

A homeowner holding a letter they don't fully understand, with a deadline that's already started counting down. They know roughly what they paid last year and roughly when the current policy ends. They don't know what a "surplus lines" quote is, whether their new roof actually qualifies for anything, or whether the FAIR Plan everyone's talking about is even an option in their state. This isn't for someone insurance-shopping on a normal renewal — it's for someone who just found out their normal renewal isn't happening.

Why it could be profitable

The market driving this is large and getting worse, not better: NAIC's first nationwide review found company-initiated non-renewal rates up 96–216% by region since 2024, with Florida up 280%, and roughly 35.6 million properties — about one in four U.S. homes — now facing rising premiums or reduced availability (beinsure.com). California's FAIR Plan alone passed 675,000 policies in 2026, prompting a 29.1% rate hike that took effect October 15 (kqed.org).

The monetization path is a lead-gen referral fee to licensed agents and surplus-lines brokers who place hard-to-insure homes — the same model comparison sites like Policygenius use, paid per qualified introduction rather than charged to the homeowner. A secondary, thinner idea is a one-time paid "mitigation credit report" PDF a homeowner could hand to an agent. The honest caveat: this prototype doesn't validate either willingness-to-pay or that brokers would take the leads; it demonstrates the matching logic that would make the lead worth something. The real moat would be a verified, state-by-state broker network, which is operational work, not product work.

Form factor & scope

A single-page web app. This prototype covers ten states across the two biggest hazard categories — wildfire (CA, CO, OR, WA) and wind (FL, LA, TX, NC, SC, MA) — with each state's last-resort plan, premium range, and mitigation credit list hardcoded as sample data. A real version would pull current state program data and let an insurance-licensed partner review the credit list before it goes live, since getting a discount percentage wrong carries more consequence than a typical demo bug.

How to run it

  1. Open index.html in any modern browser. The sample data is embedded directly in the page (a <script type="application/json"> block) rather than fetched, so it works even when opened straight from the filesystem with no local server.
  2. Click one of the three "Try an example" buttons to see a filled-in scenario, or pick your own state, reason, premium, and lapse date and check off any home upgrades you already have.
  3. Click "Calculate my path" to see the countdown, the discount match, the last-resort plan comparison, and the action checklist.

What's in this prototype

  • An intake form: state, reason for the notice, last premium paid, and lapse date.
  • A hazard-specific mitigation checklist that changes based on the selected state (wildfire items for CA/CO/OR/WA, wind items for FL/LA/TX/NC/SC/MA).
  • A results view with a color-coded lapse countdown, the stacked discount the homeowner qualifies for, an estimated re-quote premium, the state's FAIR Plan or wind-pool premium range, and a recommended next move that changes based on urgency and how much of the discount is already claimed.
  • An ordered, printable action checklist generated from the homeowner's specific inputs.
  • A running list of five dated market signals (non-renewal rates, FAIR Plan enrollment, rate hikes) for context.
  • Sample data for ten states covering both major hazard categories.

Roadmap

  • Replace the hardcoded state data with a maintained feed from each state's Department of Insurance or FAIR Plan filings.
  • Add a licensed-broker intake form so a homeowner's results can actually generate a referral.
  • Expand past the ten sample states to full national coverage, including hail-specific and flood-specific programs.
  • Let a homeowner upload a PDF of their actual non-renewal letter and extract the reason and date automatically.
  • Add a renewal calendar that reminds the homeowner before the next hardening deadline or rate filing.

Sources

Requirements

CoverPath — Requirements

Goals

  • Turn a homeowner's non-renewal letter or premium-increase notice into a concrete, ordered plan within one form submission.
  • Make the state's insurer of last resort (FAIR Plan, wind pool, etc.) and its real cost visible instead of buried in a Google search.
  • Surface which home-hardening upgrades the homeowner already has versus which ones would unlock a bigger discount.
  • Communicate urgency clearly — the countdown to lapse should be impossible to miss.

Primary user

A homeowner who received a non-renewal notice, a renewal at a sharply higher premium, or a flat refusal to quote from every admitted carrier they called. They have a lapse date already on a letter, a rough sense of what they paid last year, and no insurance background. The job to be done: figure out, in under five minutes, whether they're about to be uninsured and what the fastest responsible next step is.

Functional requirements

  • FR1: The app must let the user select a U.S. state from a dropdown populated from sample data.
  • FR2: The app must let the user select a reason for their notice: non-renewal, premium increase, or no insurer willing to quote.
  • FR3: The app must let the user enter their last paid annual premium (optional) and their coverage lapse date (required).
  • FR4: The app must render a mitigation-credit checklist specific to the selected state's hazard type (wildfire or wind) with each item's discount percentage shown.
  • FR5: On submission, the app must calculate and display the number of days until lapse, color-coded by urgency (urgent: ≤20 days, warning: ≤45 days, ok: >45 days).
  • FR6: On submission, the app must sum the discount percentage for all checked mitigation items, capped at the state's maximum stacked discount.
  • FR7: If a premium was entered, the app must display an estimated re-quoted premium using the earned discount.
  • FR8: The app must display the state's insurer-of-last-resort name, premium range, and a coverage-scope note.
  • FR9: The app must list any mitigation items the user has not yet checked, so they can see what's still available.
  • FR10: The app must generate a recommendation (bridge policy now, document hardening and re-quote, or shop surplus-lines quotes) based on urgency, reason, and how much of the discount is already claimed.
  • FR11: The app must generate an ordered action checklist reflecting the user's specific state, reason, and missing credits.
  • FR12: The app must provide at least three one-click example scenarios that pre-fill the form and immediately show results.
  • FR13: The app must display a running list of dated market-context signals (non-renewal rates, enrollment, rate changes) independent of the user's own inputs.
  • FR14: The app must offer a print-friendly view of the results panel.
  • FR15: All sample data must load from an embedded JSON block so the page works when opened directly from the filesystem.

User stories

  • As a homeowner who just got a non-renewal letter, I want to see how many days I have left, so that I know whether I need to act today or this month.
  • As a homeowner with a new roof and defensible space already done, I want to see that reflected in my discount, so that I don't pay more than I should.
  • As a homeowner who doesn't know what a FAIR Plan is, I want a plain-language explanation of my state's program and its real cost, so that I'm not caught off guard by what it does and doesn't cover.
  • As a homeowner facing a lapse in under three weeks, I want to be told plainly to apply to the last-resort plan now, so that I'm not uninsured while I shop around.
  • As a homeowner who already qualifies for every available discount, I want to be told to compare quotes instead of assuming I'm stuck, so that I don't overpay for a plan that isn't actually my best option.
  • As a first-time visitor, I want example scenarios I can click through, so that I understand what the tool does before entering my own information.

Non-functional requirements

  • The page must run with no build step and no server — opening index.html directly must work in Chrome, Firefox, and Safari.
  • No personal data is transmitted anywhere; all calculation happens client-side in the browser.
  • The UI must be usable on a phone screen (one-column layout under 600px) since many users will open this from a mailed notice while standing at a mailbox.
  • Discount percentages and premium ranges are explicitly labeled as illustrative sample data, not live quotes, both in the UI footer and in the README.

Out of scope (for the prototype)

  • Real-time integration with any state Department of Insurance, FAIR Plan, or carrier API.
  • Actual broker or agent referral/lead delivery.
  • Document upload or OCR of an actual non-renewal letter.
  • Coverage for hazards other than wildfire and wind (flood, hail-only, earthquake).
  • Any account creation, saved history, or user data persistence.

Open questions

  • Would licensed brokers actually pay for leads generated this way, or does the hard-to-place segment have thinner margins than standard homeowners' policies?
  • How often would the state program data (premium ranges, discount percentages) need to be refreshed to stay trustworthy, and who signs off on accuracy?
  • Should the tool eventually recommend specific named brokers, or stay neutral and point to each state's licensed-agent lookup to avoid any appearance of insurance advice?

More from App Prototypes