Shipped

Driving purchases through discount discovery and reducing checkout drop-off

Driving purchases through discount discovery and reducing checkout drop-off

Driving purchases through discount discovery and reducing checkout drop-off

I led the design of discount discovery- two features targeting different points in the funnel. Gives users a self-serve eligibility search tool, and a late-stage reminder to recover users without a discount applied.

COMPANY

Sonnet Insurance

Sonnet Insurance

TIMELINE

Q4 2024-Q2 2025

TIMELINE

Q1-Q2 2025

Q1-Q2 2025

MY ROLE

Lead Product Designer

Lead Product Designer

TEAM

PMs, Engineers, Copywriter, Stakeholders

PMs, Engineers, Copywriter, Stakeholders

Context

Sonnet offers member discounts to employees of 2,000+ partner organizations- employers, universities, and professional associations. Most eligible users had no way to discover it before starting a signup, and users who reached checkout without applying their discount were faced with a hard choice: abandon their progress and restart, or just pay full price.

Quick metrics:

56%

of users who saw the search tool clicked through to start sign up

2.9x

lift in auto checkout completion after late-stage discount was introduced

2.1x

lift in property checkout completion

Problem: Two separate drop-off points

Users with partner discounts weren't converting, partly because they didn't know they qualified, and because the system punished them for finding out too late.

TOP OF FUNNEL

Users had no way to check and verify eligibility before starting a signup.

Users who didn't know about the discount had no incentive to start.

BOTTOM OF FUNNEL

Users who skipped or missed the discount field early on couldn't add it later without restarting from scratch. The system was penalizing users for not completing something upfront.

Strategic goal: Grow the partner segments, a high-retention, high-value cohort through improving the clarity of discount eligibility at the top of funnel and removing friction of discovering your discount too late.

Strategic goal: Grow the partner segments, a high-retention, high-value cohort through improving the clarity of discount eligibility at the top of funnel and removing friction of discovering your discount too late.

part 01

Discount eligibility search on the marketing site

Discount eligibility search on the marketing site

Solution: Interactive search tool

A self-serve eligibility tool that gives users confidence before they commit to signup. No personal data required to find out if a discount is applicable.

Searches 2000+ partners

Provides instant confirmation

Research and discovery

I started with a cross-functional journey mapping workshop to identify where on the marketing site partner discounts were and weren't surfaced. We mapped user intent within the signup journey and marketing site, where confusion or drop-off was happening, and what a user needed to feel confident enough to start a signup.

Journey mapping workshop

Cross-functional session to map where partner discounts were surfaced (and not) on the marketing site. Focused on identifying pages with high partner-segment traffic but no eligibility signal.

Traffic & engagement analysis

Reviewed which landing pages partner-organization traffic hit most. Identified 4 high-traffic partner pages with no interactive discount component, but rather heavy text and a generic CTA.

Competitor review

Analyzed how comparable other platforms surface promotions and member eligibility. Looked for interaction patterns that reduced friction and felt familiar rather than insurance-specific.

Journey mapping workshop

Cross-functional session to map where partner discounts were surfaced (and not) on the marketing site. Focused on identifying pages with high partner-segment traffic but no eligibility signal.

Traffic & engagement analysis

Reviewed which landing pages partner-organization traffic hit most. Identified 4 high-traffic partner pages with no interactive discount component, but rather heavy text and a generic CTA.

Competitor review

Analyzed how comparable other platforms surface promotions and member eligibility. Looked for interaction patterns that reduced friction and felt familiar rather than insurance-specific.

Journey mapping workshop

Cross-functional session to map where partner discounts were surfaced (and not) on the marketing site. Focused on identifying pages with high partner-segment traffic but no eligibility signal.

Traffic & engagement analysis

Reviewed which landing pages partner-organization traffic hit most. Identified 4 high-traffic partner pages with no interactive discount component, but rather heavy text and a generic CTA.

Competitor review

Analyzed how comparable other platforms surface promotions and member eligibility. Looked for interaction patterns that reduced friction and felt familiar rather than insurance-specific.

What was built and what was cut

The clearest solution was an inline search widget — users type their organization name, confirm their eligibility, and are routed directly into signup. But we had two significant constraints: engineering timeline and the need to reuse existing search infrastructure.

Engineering constraint

Engineering constraint

We couldn't pass the organization name from the search widget into the signup flow in the MVP. This meant users would search on the landing page and need to re-enter their group in the next step- a known duplication.

It shipped anyway to get baseline data on whether the search tool drove signups at all.

Design challenges and ideation

To meet the launch window, I collaborated with engineering and product to navigate technical constraints that went against the initial UX vision. We adopted an MVP strategy, prioritizing the launch to ensure we could gather baseline data on conversion, user engagement, and plan for iterations.

Two approaches were explored and ruled out:

CONCEPTs EXPLORED -> REASON REJECTED

Second floating action button

A chat/support FAB already owned that position on mobile. Two competing FABs creates tap conflicts and unclear hierarchy.

Modal triggered by CTA

Interrupts reading flow and strips context. Users lose their place in the marketing content.

Inline search widget

Lives in the natural scroll flow. Supports marketing copy around it. Works within existing search infrastructure. Doesn't compete with other UI.

part 01

Results- one month post-launch

The widget shipped across 4 high-traffic partner landing pages. After 30 days of tracking:

56%

Of users who interacted with the search tool went on to start signup — strong signal that eligibility confirmation was the missing conversion lever.

4 pages

Initial rollout. The widget was designed to be CMS-embeddable, enabling expansion to additional partner pages without further engineering work.

What I'd do next

The biggest MVP cut was data passing. Users searching on the landing page had to re-enter their organization during signup. The next iteration is closing that loop: carry the search result into the signup flow as a pre-fill, reducing friction and improving conversion from search to completed signup.

part 02

Late-stage discount reminder at checkout

Late-stage discount reminder at checkout

Users were falling through a gap

There's an existing discount field near the beginning of the signup flow, but users were skipping it. Session recordings showed two patterns: users rage-clicking on an unintuitive "group category" selector, and users simply missing it entirely in the flow. By the time they reached the pre-checkout page and saw their price, the opportunity to apply a discount was gone. The only option was to restart.

Over 6,700 auto users and 4,400 property users passed through checkout monthly without a discount applied. Even with a modest recovery rate represented significant revenue.

AUTO

Driver's details page

24, 746 active users

-72.7% drop-off

Pre-checkout page

6, 763 active users | reminder shown here

26.7% quote to purchase

2.9x lift

PROPERTY

Confirm info page

9, 725 active users

-53.9% drop-off

Pre-checkout page

4, 487 active users | reminder shown here

35.7% quote to purchase

2.1x lift

Where to surface the reminder, and why it mattered

Placement was the most important decision. The reminder needed to appear at a moment of high purchase intent — late enough that users were committed, but early enough that the price re-calculation (triggered when a discount is applied) didn't feel jarring.

Anchor to price evaluation

We placed the reminder on the pre-checkout page — where users are already reviewing and adjusting their price. Applying a discount there feels natural; applying it one step before "confirm purchase" would feel like a last-minute system surprise.

Build once, ship across products

Auto and property signups are separate flows, but share the same pricing infrastructure. A consistent placement meant one technical implementation could serve both, important given the engineering constraints we were working within.

Conditional display only

The reminder only surfaces for users who haven't already applied a discount. Users who entered their organization earlier see a clean experience- no redundant prompts.

Anchor to price evaluation

We placed the reminder on the pre-checkout page — where users are already reviewing and adjusting their price. Applying a discount there feels natural; applying it one step before "confirm purchase" would feel like a last-minute system surprise.

Build once, ship across products

Auto and property signups are separate flows, but share the same pricing infrastructure. A consistent placement meant one technical implementation could serve both, important given the engineering constraints we were working within.

Conditional display only

The reminder only surfaces for users who haven't already applied a discount. Users who entered their organization earlier see a clean experience- no redundant prompts.

Anchor to price evaluation

We placed the reminder on the pre-checkout page — where users are already reviewing and adjusting their price. Applying a discount there feels natural; applying it one step before "confirm purchase" would feel like a last-minute system surprise.

Build once, ship across products

Auto and property signups are separate flows, but share the same pricing infrastructure. A consistent placement meant one technical implementation could serve both, important given the engineering constraints we were working within.

Conditional display only

The reminder only surfaces for users who haven't already applied a discount. Users who entered their organization earlier see a clean experience- no redundant prompts.

Design challenges and ideation

To meet the launch window, I collaborated with engineering and product to navigate technical constraints that went against the initial UX vision. We adopted an MVP strategy, prioritizing the launch to ensure we could gather baseline data on conversion, user engagement, and plan for iterations.

Part 02 results- one month post-launch

WHAT THE DATA SURFACED

Analytics showed significant drop-off earlier in the funnel. Many users who were already price-sensitive left before reaching the pre-checkout page where the reminder lives.

WHAT i'd do next

The current reminder is passive as it appears once on the configuration page. Testing earlier placement (or a secondary reminder closer to the final confirm step) could recover the users who drop before they ever reach it.

I'd also revisit the original discount field UX. The session data from research is clear that the category selector is the core friction point, and fixing that upstream would reduce reliance on the secondary reminder entirely.

Factors behind page placement

Where this discount reminder would surface was one of the highest important factors. In order to capture users who missed a discount earlier, we needed to surface the reminder during a moment of high purchase intent while respecting technical system limitations.

01

Balancing price logic and performance

Applying a discount late in the funnel triggers a price re-calculation. To ensure a fast, seamless experience and minimize backend load for engineering, we placed the reminder on the 'Customize Coverages' page—the natural point where users are already evaluating their final price and editing their policy.

02

Cross product scalability (Auto and Property)

While Auto and Property applications have different flows, they share the same pricing logic. By selecting a consistent page placement across both products, a predictable user experience and a unified technical implementation was easier to build and maintain.

Crystal Huang. Powered by Timmies steeped tea.

Crystal Huang. Powered by Timmies steeped tea.

Crystal Huang. Powered by Timmies steeped tea.