Transformed Acko's new car insurance — from a 21% funnel to 65%

A 3× lift in entry-to-quote, achieved across three releases — and one screen killed at 1% before it could scale.

ACKO new car insurance journey
Summary

I led the design rebuild of Acko's new car insurance journey. The product was converting 21% of users to a quote and losing the rest — half the pipeline was researchers with delivery dates weeks away, and the other half was being actively pushed back by dealers at the showroom. The product had no answer to either.

I rebuilt the journey around a clear position against dealer misinformation, a structural fork based on purchase intent, and a graduated rollout that used 1% traffic as a live design experiment. Three releases over three months. E2Q stabilised at 65% — a 3× improvement on the baseline.

65%
E2Q at full rollout
Up from 21% baseline
Funnel improvement
Feb → May 2026
1
Screen killed at 1%
Cut before scaling
~5%
Q2S — held stable
Intent-driven, expected
The most important design decision on this project happened in production. The 1% rollout caught what no prototype could — and cutting that one screen was worth more than any other change.
Context
Why this project mattered

New car buyers are one of motor insurance's most valuable segments — clean history, brand-new vehicle, high renewal rate. Acko's pricing was genuinely better than dealer offers. None of that advantage was converting into policies.

Between booking a car and collecting it — typically two to six weeks — dealers have daily touchpoints with the buyer. Acko had zero. Dealers had financial incentive to push their own insurance partners, and they used every touchpoint to do it. When one internal user mentioned Acko while collecting his car, the dealer dropped his quote from ₹1 lakh to ₹35,000 on the spot. Not because Acko was overpriced — because the dealer was protecting their margin.

The product had no presence in any of those moments and no rebuttal once the user came back to it. Acko was losing a segment it should have owned.

The product wasn't losing on price or quality. It was losing because it wasn't in the room when the decision was being made — and had nothing to say when the user came back.
A funnel problem was actually a position problem

PRD said E2Q was 44% overall, 66% with misclicks removed. That looked like a funnel problem — too many steps, too much friction. The signals underneath pointed somewhere different.

The brief assumed
A funnel problem
Reduce steps, simplify the MMV selector, tighten the flow. Treat the journey as a series of friction points to remove. Optimise for completion.
The data showed
A position problem
Half the users had no urgency — delivery weeks away, no reason to commit. The other half were being talked out of it before they opened the app. The journey had no answer to either.

Two signals made this clear: Q2S: 11% same-day. 0.5% for "not sure". A 10× gap driven entirely by how close someone is to needing insurance. The funnel can't fix this. ~50% of quotes from far-delivery users — the biggest cohort, almost zero conversion. No early-buy hook meant no reason to commit before the showroom visit.

Build a journey that earns trust before the dealer gets there — and gives users who aren't ready a reason to come back.
Strategy

The product needed to do three things the old journey couldn't. Each became a structural decision — not a screen-level fix.

MOVE 01 — Position before design
The product needed to stand for something specific. Confident, fact-led, activist — not defensive. Named dealer claims, real settlement data, specific not generic.
MOVE 02 — Fork the journey at intent
A user who hasn't booked yet needs a different product than someone picking up tomorrow. Booking status modal, three flows not one, intent-driven routing.
MOVE 03 — Production as design tool
A prototype can't tell you 99% of users will ignore your landing page. 1% of real traffic can. Graduated rollout, hypothesis-driven release, cut what doesn't work.
How the journey forks

User enters new car insurance journey → booking status (booked / finalised but not booked / still deciding) → three paths:

Path What they get
Booked Direct to MMV + plans — get out of the way. Route them to purchase.
Finalised Lock-in incentive first — give them a reason to commit before the dealer visit.
Deciding Education + comparison — build intent. No pressure to buy.

The fork wasn't a feature. It was the structural argument that one product can't serve two users with completely different needs — and the booking status modal became the spine of the new journey.

The hard calls

Three decisions that shaped the journey. Each pushback changed something structural. The first set up the tone, the second set up the architecture, the third caught what would have scaled badly.

01

Pushed for activist copy, not defensive

Early drafts answered dealer claims politely — useless to a user being told the opposite by someone in front of them. Pushed for confident, fact-led, specific. Named garages near the user, real settlement numbers, direct rebuttals to specific claims. Approved through leadership review.

Activist tone shipped Template for dealer pressure
02

Forked the journey at booking status

A user who hasn't booked yet doesn't know their dealer or delivery date. A user picking up tomorrow does. Asking both groups the same questions created friction for the ready buyer and irrelevance for the researcher. The booking status modal became the structural spine — every screen downstream changed because of it.

Core architecture Every screen downstream redesigned
03

Killed the landing page at 1%

Built an activist landing page to address dealer myths. At 1% rollout, scroll data showed 99% of users ignored it — they hit the CTA at the top, the content below was invisible. Carrying it into a 50% rollout would have added friction for everyone and helped no one. Cut it.

E2Q 13% → 34% after cut Signal over vanity

E2Q went from 13% at 1% to 34% at 50% after removing the landing page. The most useful signal from the 1% phase wasn't what worked — it was what didn't, fast enough to fix.

The booking status fork is now the core architecture of the new car journey. Every screen downstream was redesigned around what the user told us about where they were.
Dealer rebuttals in the journey

Dealer rebuttals were integrated into the plans page itself, not a separate screen — specific named garages, real settlement data, direct answers to the claims dealers were making at the showroom.

Named dealer claims

Address what buyers actually hear in the room — not generic reassurance.

Real settlement data

Fact-led proof users can hold up against misinformation at the dealership.

Specific, not generic

Named garages near the user, numbers that land, direct rebuttals to specific claims.

The flow shifted from a single funnel for everyone to three forked paths based on intent — each one designed for what the user actually needed at that moment.
What shipped

Key surfaces from the new car insurance journey: booking status entry, forked flows, plans page, dealer selection pre-payment, and checkout.

What the rollout showed

Three releases over three months. Each one had a hypothesis and a decision point — not just a traffic split.

21%
Old baseline
Nov–Dec 2025
13%
1% rollout
Feb 2026 — signal caught
34%
50% rollout
March — recovered
65%
100% rollout
May — 3× baseline
E2Q went from 13% at 1% to 34% at 50% after removing the landing page. The most useful signal from the 1% phase wasn't what worked — it was what didn't, fast enough to fix.
What each stage taught us

1% — February 2026. E2Q at 13%, worse than baseline. Landing page had a 1% scroll rate. Plan naming confusion (1+3 vs 3+3 future scope leaked into UI). Killed the landing page, fixed the naming, did not scale until resolved.

50% — March 2026. E2Q at 34%, above baseline for the first time. Fork holding. Activist positioning landing. Dealer selection pre-payment working. Confidence to scale.

100% — April–May 2026. E2Q stabilised at 59–65% and continued improving. mweb — previously the weakest channel — consistent at ~55%. App at ~75–80%. 3× the baseline.

~5%
Q2S held stable
Across all stages — expected
E2Q vs baseline
At full rollout

Q2S held at ~5% across all stages — and that's expected. Quote-to-sale is downstream of when a user's car arrives, not how good the journey is. Knowing what design cannot fix is part of the work.

What I'd do differently

Three things I'd change if I ran this project again. Each would have moved us faster or taught us more.

01
Start with ten internal journeys, not one
One internal user's real journey told me more than the entire PRD. The dealer dropping ₹1L to ₹35K, the 106 ghost variants, the blank payment screen — none of that was in the funnel data. Finding it was luck. Next time I'd commission ten of those before opening Figma.
02
Push the fork to the very first screen
The booking status fork works — but it sits inside the funnel after MMV. Intent divergence happens before that. The product should know what user it's talking to from screen one, not three steps in.
03
Treat the 1% phase as a timed decision sprint
We had enough signal to cut the landing page in week two. We waited a month. At 1% the cost of delay is low — but the discipline of cutting fast is exactly what graduated rollout is for. I'd set a hard decision date: two weeks to call what stays.
Other key projects