16

Blog · November 10, 2026 · 8 min read

Insurance Renewal UX: Put Last Year's Price Next to This Year's

Renewal is the one moment every policyholder is guaranteed to look at your product. Claims are rare. Quotes happen once. Renewal arrives every six or twelve months, on schedule, with a number attached. For most carriers, MGAs, and insurtech startups, that number shows up inside a PDF, a vague email subject line, or a portal banner that says "Your documents are ready."

We think that is the most expensive design decision in insurance. A renewal screen that hides the change trains customers to shop. The policyholder who cannot tell what moved, by how much, and why will open a comparison site within the hour. Renewal is retention UX, and it deserves the same senior attention a team gives its quote flow.

This post covers how we design insurance renewal UX for regulated products: what the first screen must answer, how to explain a price change without hiding behind "market conditions," and the patterns we reject on sight.

The three questions the first screen must answer

Every renewal surface, whether it is an email, an app notification, or the portal, should answer three questions before the customer scrolls:

  1. What is this? A renewal for a named policy, a named vehicle or property, with an effective date.
  2. What changed? Premium, deductible, limits, discounts, and add-ons, each shown as old value and new value.
  3. What do I need to do? Nothing, pay by a date, confirm a detail, or choose between options.

If a customer has to download a document to answer any of these, the screen has failed. Policy documents exist for legal completeness. They are a terrible place to communicate a decision.

Show last year's price beside this year's price

The single most useful element on a renewal screen is a two-column comparison: what you paid last term, what you will pay this term, and the difference in dollars. We put it at the top, in plain numbers, with the difference stated outright.

Teams resist this because a visible increase feels like inviting churn. The opposite is true. Customers already know what they paid. They can find last year's bank statement. When the product makes them do that math themselves, it signals that the carrier hoped they would not notice. Reddit is full of policyholders who found a doubled premium through their mortgage escrow shortfall instead of through their insurer. Every one of those threads ends with the same sentence: "I canceled and switched."

UK regulators already require renewal communications to show last year's premium next to the new quote. U.S. requirements vary by state and line of business. We design to the stricter standard everywhere, because the product that explains itself clearly in one market does not need a separate flow for the next.

Explain the change in terms of this policy

"Rates have increased due to market conditions" is a sentence that applies to every customer and explains nothing to any of them. A renewal explanation earns trust when it points at something the customer recognizes:

  • A claim filed on this policy during the term, with its date.
  • A change to the insured vehicle, address, driver, or square footage.
  • A discount that expired, with the reason it expired.
  • A filed rate change for the state, with a plain sentence about what it covers.
  • Rebuild cost or vehicle value updates that raised the coverage limit.

Where several factors stack, we show them as a short itemized breakdown that sums to the total change. Customers do not need actuarial detail. They need to see that the number was built from facts about their situation, and that someone at the company can say what those facts are.

When the honest answer is "your rating territory went up and nothing about you changed," say that. A clear, unflattering reason keeps more customers than a vague, flattering one.

Give the customer real options on the same screen

A renewal notice with only a "Pay now" button tells the customer their only alternative is to leave. Good renewal UX puts the adjustment options next to the price:

  • Raise the deductible, with the new premium shown live.
  • Remove or keep each add-on that auto-renewed, as a separate choice.
  • Switch billing frequency or set up a payment plan.
  • Ask a licensed human a question, with a real response time.
  • Cancel, with the date coverage ends and any refund owed.

Each option should show its effect on price before the customer commits. A deductible slider that reveals the new premium only after a form submission is a quote flow wearing a renewal costume.

Make leaving as easy as staying

If renewal can be confirmed in one tap, cancellation should be reachable in one tap too. Symmetry matters for trust, and in more and more jurisdictions it matters for compliance. Click to cancel rules, consumer duty frameworks, and state cancellation requirements are all moving the same direction.

Easy cancellation also gives you a better retention moment. A customer who reaches a clear cancellation screen and sees "Before you go, here is a $180 lower option with a $1,000 deductible" is far more likely to stay than one who has to phone a retention line and argue.

Timing is part of the interface

A clear renewal screen that lands four days before the effective date still feels like an ambush. We map renewal communications as a sequence:

  1. Early heads up, well before the legal notice window, when a price change is likely.
  2. Full renewal notice, with the comparison, the reasons, and the options.
  3. Reminder if the customer has not opened or acted.
  4. Confirmation after renewal, restating the new price and effective date.

Every message in that sequence pulls from the same source of truth. The single fastest way to lose a policyholder is an email that says one number and a portal that shows another. When we audit renewal flows, mismatched amounts across channels are the most common defect we find, and the hardest for customers to forgive.

Design the renewal for agents and support too

Many renewals involve an agent, a broker, or a support rep. The customer often calls with the renewal screen open. If the rep sees a different view, or cannot see the itemized reasons, the call becomes a hunt through policy admin systems while the customer waits.

We design the internal renewal view at the same time as the customer view, with the same comparison and the same reasons, so both people are looking at one story. This is where working software beats a Figma file. A prototype wired to real policy data shows instantly whether the explanation model holds up for messy cases: mid term endorsements, multi car policies, bundled home and auto. Static mockups always show the clean case.

What we reject in renewal UX

These patterns show up in almost every renewal flow we review. We remove them first.

  • "Your documents are ready" as the subject line. It hides the only thing the customer cares about.
  • A new premium with no prior premium beside it. It forces customers to do the math and assume the worst.
  • "Market conditions" as the whole explanation. It reads as a refusal to explain.
  • Auto renewed add-ons bundled into one total. Each add-on is a decision and should be shown as one.
  • Options that only exist on the phone. If a deductible change is allowed, it belongs on the screen.
  • Cancellation buried behind a call or a chat queue. Asymmetric friction erodes trust and increasingly invites regulators.
  • Different numbers in email, app, and portal. One source of truth, or no trust at all.
  • Renewal notices timed to the legal minimum. Minimum notice feels like a trap even when it is compliant.
  • A PDF as the primary renewal surface. Documents are the record. The screen is the conversation.

Where AI fits, and where it does not

AI is useful in renewal work. It can draft plain language reason statements from rating factor data, flag accounts likely to churn at renewal, and summarize policy changes for a support rep before the call connects. We use AI native tooling to build and test these flows quickly.

Judgment stays with people. Which reasons are accurate, which comparisons a regulator will accept, and how candid to be about a territory rate increase are decisions for senior designers working alongside compliance and product leads. A model that writes a confident, wrong explanation of a premium change creates a complaint file. We keep a human on every customer facing reason template.

How to tell if your renewal UX is working

Track these signals for each renewal cohort:

  • Share of customers who open the renewal notice before the effective date.
  • Renewal rate for customers with a price increase, split by size of increase.
  • Calls and chats in the 14 days before renewal, and what they ask.
  • Share of customers who adjust coverage instead of canceling.
  • Complaints that mention renewal, notice, or price surprise.

If calls spike around renewal and most of them ask "why did my price go up," the screen is not doing its job. That call volume is the clearest business case for redesigning renewal.

Work with us on your renewal flow

We are a Bay Area boutique studio of senior designers who build working software for complex and regulated products, including insurance, fintech, and health. We can audit your current renewal sequence, map every channel against one source of truth, and ship a coded renewal experience your team can test with real policy data.

Book a discovery call or email us at ash@uxsignalstudio.com.

Let’s talk about your next step

Have a question or a project in mind?

Tell us where you are and what you want to figure out. We’ll review your message and reply within two business days.

Contact UX Signal Studio

We’ll use your details to respond to your inquiry. This form does not subscribe you to a mailing list. Privacy policy.

Prefer to talk? Book a discovery call

Get the next essay in your inbox

One practical piece on UX and product design, every week or two. No noise.