Fintech · Tier 2/3 · Insurance

Inclusive access to capital in India's Tier 2/3 cities

Turning a confusing health-insurance purchase into a self-service flow that works for first-time digital users on slow connections.

Role
Design Lead
Team
PM, 3 eng, 1 researcher
Timeline
~4 months
Surface
Mobile web + app
0
increase in policy purchase completion
0
of purchases completed without agent help
0
drop in support calls during purchase
The stakes

A market everyone designs past

Tier 2/3 users in India are not edge cases. They're the majority of the next hundred million people coming online. But insurance flows are built for confident, high-bandwidth, English-first users. The result: people who needed coverage most abandoned the purchase, or depended entirely on an agent who may not have their interest at heart.

Designing for the hard edges of the audience is where the real product lives.
The problem

Where people dropped off

  • Dense insurance jargon with no plain-language explanation.
  • Forms that assumed fast connections and frequent app use.
  • No way to compare plans without already understanding the terms.
  • Trust gap: users weren't sure the digital flow was safe or real.
Purchase funnel · Tier 2/3 users · Before redesign
Landing page
100% 4,800 sessions
Plan comparison
71% 3,408 reached −29% jargon confusion
Plan selected
44% 2,112 selected −27% no-compare drop
Form fill
28% 1,344 reached −16% form complexity
Payment
18% 864 attempted −10% trust gap
Policy issued
11% 528 completed baseline conversion
Biggest single drop
Plan comparison → selection (−27%)
Primary cause
No plain-language plan explanation
Agent escalations
73% of completions required agent
What I owned

My role

I led the redesign of the end-to-end purchase, partnered with research to get into the field with actual Tier 2/3 users, and made the call to rebuild around plain language and progressive disclosure rather than feature parity with the desktop flow.

  • Field research with low-digital-fluency users on real devices and networks.
  • Rewrote the flow around questions people could answer, not insurance terms.
  • Designed for intermittent connectivity and small screens first.
  • Built trust cues into every step so the digital path felt as safe as an agent.
The approach

Self-service that earns trust

We replaced the comparison table full of jargon with a guided conversation: a few questions in plain language, then a recommendation the user could actually understand. Every screen was designed to load and function on a weak connection. And we treated trust as a design material — clear pricing, no hidden steps, and obvious ways to get human help if needed.

Plan selection · Before vs. After
Before
Feature
Silver
Gold
Platinum
Sum insured
₹2L
₹5L
₹10L
Pre-existing
36m
24m
12m
Sub-limit
Yes
Yes
No
Co-payment
20%
10%
0%
No-claim bonus
10%
25%
Dense jargon. No guidance on which plan fits. User must already understand "sub-limit" and "co-payment" to decide.
After
How many people will this policy cover?
Just me
Me and my spouse
My whole family
Recommended for you
Gold Plan · ₹5L cover
Covers hospitalisation up to ₹5 lakh. No out-of-pocket for most treatments. ₹4,200/year.
Plain questions, one recommendation. User never needs to know what "co-payment" means.
Selection rate
44% → 86% (+42pp)
Avg. time on step
4m 12s → 58s
"Help me choose" taps
67% → 9%
The outcome

More people, finishing on their own

Completion more than doubled, and most purchases now happen without an agent — which means lower cost to serve and, more importantly, users in control of their own coverage decision.

  • 2.4x increase in completed purchases.
  • 61% of purchases completed fully self-service.
  • 40% fewer support calls during the purchase flow.
What I took from it

The leadership lesson

Inclusive design isn't charity, it's market access. The business case and the user case were the same case: make it usable for the people everyone else designed past, and you unlock the segment everyone else is fighting over. Getting leadership to see those as one argument was the win.

Executive Summary

Executive Summary

The problem in one line

India's digital health insurer had product-market fit with urban, high-literacy users. The Tier 2/3 segment, 3x the size, churned at the plan-selection step because the product spoke a language most users had never learned.

The answer in one line

Replaced a comparison table requiring insurance literacy with a guided conversation requiring none. Shipped in 14 weeks across mobile web and app, serving 2G connections and first-time smartphone users.

What changed, at a glance
Phase 1
Discovery
Field visits, 18 users across 3 cities
Phase 2
Architecture
Rebuilt purchase flow from scratch
Phase 3
Design + Test
3 rounds usability testing on-device
Outcome
2.4x completion lift
61% fully self-service at launch
Success Metrics

Success Metrics

Primary KPIs
Purchase completion rate
Target: 2x baseline
2.4x
Achieved
Self-service rate
Target: 50% no-agent
61%
Achieved
Support call reduction
Target: 30% drop
40%
Achieved
Secondary KPIs
Time to plan selection
Was 4m 12s
58s
−77%
Plan selection rate
Was 44%
86%
+42pp
CSAT (Tier 2/3 cohort)
Was 3.1/5
4.4
+1.3 pts
Before vs. After · Funnel health
Purchase complete
11% → 26%
Plan selected
44% → 86%
No agent needed
27% → 61%
Before
After
Stakeholder Map

Stakeholder Map

Influence × Interest matrix
Influence
Low interest
High interest
Keep satisfied
CFO / Finance
Cost-to-serve reduction
Compliance / Legal
Disclosure requirements
Manage closely
Product VP
Growth + Tier 2/3 funnel owner
Insurance Partners
Plan data, pricing accuracy
Engineering Lead
Low-bandwidth constraints
Monitor
Marketing
Acquisition messaging alignment
Customer Support
Call volume impact
Keep informed
Field Research Lead
User insights, Tier 2/3 context
Agent Network
In-field trust signals
End Users
Primary design audience
← Low influence
High influence →
Research Plan

Research Plan

Research questions
Where exactly do users lose confidence in the purchase flow?
What mental model do first-time buyers use to judge whether a plan is "right"?
What signals make a digital purchase feel safe vs. risky on a slow connection?
When and why do users call an agent instead of completing themselves?
Methods
Field study
18 participants · Pune, Nagpur, Surat
Observed on their own device, own network
Think-aloud usability
12 sessions · existing flow
Task: "buy a plan for your family"
Funnel analytics
30-day session data, Tier 2/3 cohort
Drop-off events, agent escalation triggers
Agent interviews
6 agents · 3 geographies
What questions do callers ask most?
Timeline · 4-week research sprint
Week 1
Screener + recruit
24 screened, 18 selected
Week 2
Field visits
Pune, Nagpur, Surat
Week 3
Synthesis
Affinity mapping, themes
Week 4
Readout
Insights → design brief
Research Insights

Research Insights

Insight 01 · Language
"Co-payment" was the single most-asked question to agents

14 of 18 participants could not define "co-payment" or "sub-limit" unprompted. All 14 abandoned or called for help at plan selection.

Insight 02 · Trust
The payment step felt "like giving money to a stranger"

No confirmation of who the insurer was, no human face, no receipt preview before paying. Users didn't know if the digital flow "counted" like an agent sale.

Insight 03 · Connectivity
Slow load at payment caused users to hit "pay" twice

On 2G/3G connections, payment confirmation took 6-14s. 8 of 12 usability participants tapped the button a second time, fearing the first didn't register.

Insight 04 · Decision model
Users chose plans by "what happens if I'm in hospital"

Not by sum insured or premium. The mental model was scenario-based: "Will I pay anything out of pocket if admitted?" That question wasn't answered anywhere in the existing UI.

"

I asked my neighbour. He said just pick the middle one. That's what I did. I don't know if it's right.

P-07 · 34, Nagpur · First smartphone, 2G data plan
JTBD

Jobs to Be Done

When · I want to · So I can
When
I'm worried about a family member's health costs
I want to
Understand exactly what will be covered without reading fine print
So I can
Feel confident I'm not wasting money on the wrong plan
When
I'm comparing plans and see unfamiliar words
I want to
Get a plain-language explanation without leaving the page
So I can
Make the decision myself instead of calling someone
When
I'm about to pay online for the first time
I want to
Know the transaction is secure and that a policy will actually arrive
So I can
Go through without calling an agent to "confirm it's real"
When
My internet drops mid-purchase
I want to
Pick up exactly where I stopped without re-entering everything
So I can
Finish on my own time, even on a weak connection
Opportunity Map

Opportunity Map

Unmet need → Design opportunity → Expected impact
Unmet need
Design opportunity
Impact
No way to understand plan terms without insurance background
Replace comparison table with guided Q&A + plain recommendation
High
No trust signals at payment — feels unsafe for first-time digital payers
Add insurer branding, policy preview, and real-time confirmation during payment
High
Forms break on slow connections; users lose progress and give up
Progressive-save pattern: every step auto-saved; resume link sent via SMS
High
No scenario-based explanation ("if I'm hospitalised, what do I pay?")
Add "what this means for you" plain-language summary card per plan
Med
Agent escalation creates dependency; users lose autonomy in decisions
Contextual "talk to a person" always visible but never the default CTA
Med
Design Principles

Design Principles

01
Speak the user's language
No jargon. Ever.

Every label, prompt, and error must make sense to someone who has never bought insurance. If it requires literacy in the product category, rewrite it as a question the user already knows how to answer.

02
Trust is a design material
Make safety visible at every step.

First-time digital buyers need explicit signals that the process is real, secure, and reversible. Insurer branding, policy previews, and receipt confirmations are not decoration. They are the product.

03
Design for the edge, not the average
2G, small screen, one hand.

Every interaction is designed for the lowest-bandwidth, smallest-screen, least-digital-literate user first. If it works there, it works everywhere. The reverse is not true.

04
Progressive disclosure
One decision at a time.

Show only what the user needs to act on right now. More detail is always available, but it is never the default. Complexity is revealed only when the user asks for it or the context requires it.

Workflow Architecture

Workflow Architecture

End-to-end system · 3 layers
User
layer
Landing
Entry / awareness
Guided Q&A
Needs assessment
Recommendation
1 plan, plain copy
Form fill
Progressive save
Payment + confirm
Policy issued
System
layer
Session state
Auto-save / resume
Plan engine
Rules → match
KYC / validation
Aadhaar / mobile
Payment gateway
UPI / netbanking
Policy API
Insurer issuance
Support
layer
Agent handoff (visible always, used rarely)
Contextual escalation
·
SMS resume link
Connectivity drop recovery
·
Policy delivery (SMS + PDF)
Offline-safe confirmation
User Flow

User Flow

Happy path · First-time self-service buyer
1
Land on product page
Arrives from paid search or organic. Sees hero with clear value prop: "Health cover from ₹200/month — no agent needed." Single CTA: "Check plans."
Entry point
2
Answer 4 questions
Who's covered? Any pre-existing conditions? Preferred hospital type? Budget range? One question per screen. No keyboard required — tap-to-select only.
Guided Q&A · ~58s avg
3
See one recommendation
Single recommended plan with plain summary: "If admitted to hospital, you pay ₹0 out of pocket up to ₹5 lakh." Price shown prominently. "Why this plan?" expander for more detail. "Compare all plans" available but not pushed.
Plan recommendation
4
Fill personal details
Name, DOB, phone, Aadhaar last 4. One field per screen on mobile. Progress bar always visible. "Saved — resume any time" shown after each step. Fields pre-filled where data already known.
Progressive form · auto-save every step
5
Review & pay
Summary screen: plan name, what it covers, final price. Insurer logo prominently visible. Payment via UPI or netbanking. Animated "processing" state prevents double-tap. Page stays functional offline if connection drops during load.
Trust-first payment step
Policy confirmed
Full-screen success state with policy number, insurer helpline, and download link. SMS confirmation with resume-safe copy also sent. PDF policy dispatched within 4 hours.
Done · no agent required
Escape route · available at all steps
Persistent "Talk to someone" link available on every screen — opens click-to-call or WhatsApp. Agent receives full session context so the user doesn't repeat anything.
IA

Information Architecture

Content hierarchy · purchase surface
Health Insurance Purchase
Needs assessment
Who's covered
Health conditions
Hospital preference
Budget range
Plan selection
Recommended plan
Plain summary card
Why this plan?
Compare all (secondary)
Application form
Personal details
Health declaration
Nominee details
Document upload
Confirm + Pay
Order review
Payment (UPI / NB)
Success + policy no.
SMS + PDF delivery
Persistent across all steps →
Progress indicator
Auto-save status
Talk to someone
Back navigation
Concept Exploration

Concept Exploration

Three directions explored · plan selection step
Direction A
Filtered table
Improve the existing pattern
[Filter chips: Family / Solo / Senior]
─────────────────
Plan name | Price | Cover
Silver | ₹2.1k | ₹2L
Gold ● | ₹4.2k | ₹5L
Platinum | ₹7.8k | ₹10L
─────────────────
[View details] [Buy now]
Rejected: still requires users to interpret plan attributes. Filter chips reduce scope but don't solve literacy gap.
Direction B · Selected
Guided Q&A + single rec
Replace the table entirely
"Who's covered?"
[ Just me ] [ Me + spouse ]
[ Full family ]
──────────────
"Any existing conditions?"
[ No ] [ Yes, tell us ]
──────────────
★ Recommended: Gold Plan
₹4,200/yr · ₹0 out of pocket
Chosen: no insurance literacy needed. Single clear output. Fastest path to decision. Tested best with Tier 2/3 cohort.
Direction C
Scenario cards
Pick your worry, see your plan
"What worries you most?"
[🏥 Big hospital bills]
[💊 Ongoing medicines]
[👨‍👩‍👧 Protecting my family]
──────────────
→ Based on your answer,
here's what we suggest...
Parked: emotionally resonant but took longer to complete. Better fit for re-engagement than first-time purchase. Revisit in V2.
Wireframes

Wireframes

Key screens · annotated low-fi
Screen 1 · Q&A step
9:41▮▮▮
Step 1 of 4
Who will this policy cover?
● Just me
○ Me and my spouse
○ My whole family
Continue →
Talk to someone instead
A
Progress bar: always visible. Gives users a sense of completion.
B
Tap-only selection. No keyboard required on any question.
C
Help link always visible but never the primary CTA.
Screen 2 · Recommendation
9:41▮▮▮
✦ Recommended for you
Gold Plan
₹4,200 / year
If you're admitted to hospital, you pay ₹0 out of pocket — up to ₹5 lakh per year.
Why this plan? ↓
Select this plan →
Compare all plans
A
Single recommended plan. No decision fatigue.
B
Summary in plain language: ₹0 out of pocket, not "nil co-payment".
C
"Compare all" is available but deprioritised — below the CTA.
Screen 3 · Payment
9:41▮▮▮
🏦
Star Health Insurance
IRDAI licensed · Secured payment
You're buying
Gold Plan · ₹5L cover
₹4,200 per year
● Pay via UPI
○ Net banking
Pay ₹4,200 →
🔒 256-bit SSL · Policy sent instantly
A
Insurer logo + IRDAI status visible before any payment action.
B
Full price shown — no surprise fees after tap.
C
Button disables on tap to prevent double-payment on slow connections.
Design System

Design System

Color tokens
--blue
#5B8CFF
Primary CTA, links
--violet
#9B6BFF
Gradient pair, accents
--green
#3FE08A
Success, completion
--orange
#FF8A3D
Warnings, friction points
--yellow
#FFD23F
Neutral callouts
--bg-3
Surface
Cards, inputs, rows
Type scale
Display
₹4,200/yr
Clash Display · 28px · 700 · Plan price, hero stat
H2
Who will this policy cover?
16–18px · 600 · Questions, plan names
Body
If admitted to hospital, you pay ₹0 up to ₹5 lakh.
14px · 400 · Plain-language summaries
Label
Step 1 of 4
Mono · 11px · 400 · Progress, metadata
Core components
Option tile · unselected / selected
Just me
Me and my spouse
Plan card · recommended state
✦ Recommended
Gold Plan
₹4,200/yr
₹0 out of pocket up to ₹5L
Progress bar + save state
Step 2 of 4 · Saved ✓
44px min touch target
Final Design

Final Design

Screen layout · final production UI · descriptive
Screen A · Guided question
Zone 1 · Header (fixed, 56px)
Logo left · Step progress bar center · Back arrow right. Always stays at top on scroll.
Zone 2 · Question (auto-height)
Kicker label ("Step 1 of 4") above. H2 question in 18px semi-bold. Left-aligned. Max 2 lines. No icons — text only for clarity at small sizes.
Zone 3 · Option tiles (scroll)
Full-width tap tiles, 44px min height, 8px gap. Selected state: blue border + light fill + filled radio dot. Unselected: neutral border. No checkbox — radio for single-select clarity.
Zone 4 · Actions (fixed bottom, 88px)
Primary CTA full-width gradient button. "Talk to someone" as text link below, 14px. Safe area padding for notch phones. Saves session on every tap.
Screen B · Plan recommendation
Zone 1 · Contextual header
Green "Recommended for you" eyebrow in mono caps. Signals result state, not a step. No back button — user should review before going back.
Zone 2 · Recommendation card
Green-bordered card fills top 40% of content area. Plan name 18px bold. Price 28px Display font. Plain summary below: "₹0 out of pocket up to ₹5 lakh." Single sentence. No bullet lists.
Zone 3 · Progressive detail
"Why this plan?" accordion below card. Collapsed by default. Expands to show 3 plain-language benefits. "Compare all plans" text link below accordion — available but passive.
Zone 4 · Fixed CTA
Full-width "Select this plan" gradient button. Below it: agent link. Price repeated in button label to reduce anxiety ("Select · ₹4,200/yr").
Screen C · Progressive form
Zone 1 · Save status banner
Slim top banner: "Progress saved. You can resume any time." Green checkmark. Fades after 3s. Reappears on each successful save. Reduces abandonment anxiety on slow networks.
Zone 2 · One field, full screen
One input field per screen. Label above in 12px. Input large 18px text, full-width. Helper text below in 12px ink-faint. Error state: orange border + inline message. No scrolling required on any step.
Zone 3 · Keyboard behaviour
CTA stays above keyboard on focus (not hidden behind it). Numeric fields open numeric keypad. No autocomplete suppression — browser autofill enabled to reduce effort.
Screen D · Trust-first payment
Zone 1 · Trust header (highest priority)
Insurer logo prominent top-left. "IRDAI Registered" badge. SSL lock icon. Appears before any payment UI — trust must land before the ask.
Zone 2 · Order summary (no surprises)
Plan name, what it covers, annual premium — all visible before user taps pay. Inline "Policy number will arrive within 4 hours" sets expectation for the post-payment wait.
Zone 3 · Payment method
UPI pre-selected (most common in Tier 2/3). Net banking secondary. Card tertiary. Each method uses a full-width radio tile. No nested menus.
Zone 4 · Pay CTA + loading state
Button disables immediately on tap. Spinner replaces label. Text: "Processing — do not press back." Prevents double-payment. On success: full-screen green confirmation, not a small toast.
Usability Testing

Usability Testing

Round 1 · Concept validation
6 participants · Prototype A vs B
Tested guided Q&A against filtered table. 5/6 completed Q&A without help. 1/6 completed table. Direction B confirmed.
Key fix: question 3 ("pre-existing") was confusing. Reworded to "Any ongoing health conditions?"
Round 2 · Flow validation
8 participants · Full prototype on device
Tested on participants' own phones, own SIM cards. Simulated 2G throttling. 7/8 reached payment. 6/8 paid without help.
Key fix: payment button allowed double-tap. Added disable-on-tap + spinner to prevent duplicate attempts.
Round 3 · Pre-launch
10 participants · High-fidelity, live backend
Real UPI payments. 9/10 completed end-to-end. Average time: 6m 20s. 0 unsolicited agent requests.
No critical issues. Minor: progress bar text too small at 10px — bumped to 12px.
Critical findings · what we changed
Observation
Design change
Round
Users paused on "pre-existing disease waiting period"
Replaced with "Any ongoing health conditions (diabetes, BP, etc.)?"
R1
3 participants tapped "Pay" twice on slow connection
Button disables on first tap; spinner + "Processing" message shown
R2
Users unsure if policy was "real" — asked to see a document before paying
Added "Policy preview" PDF sample on the review screen
R2
Progress bar label (10px) unreadable without glasses (3 participants 45+)
Bumped progress label to 12px; added step fraction ("2 of 4") in text
R3
One participant dropped network mid-form; couldn't find resume
Added SMS resume link sent automatically after step 2
R2
What I'd Do Next

What I'd Do Next

Near term · 0–3 months
Renewal flow redesign

The purchase flow is fixed, but first-year renewal is a cliff. Users who bought without an agent often call an agent to renew — recreating the dependency we broke. The renewal experience needs the same plain-language treatment, but with the added challenge of building on a prior year's relationship.

Near term · 0–3 months
Scenario card concept (Direction C)

We parked the "what worries you most?" model after Round 1 because it slowed completion. But it tested extremely well emotionally. I'd run it as a standalone A/B for re-engagement and upsell flows, where users have more time and lower urgency.

Medium term · 3–9 months
Voice-first alternative

A subset of our Tier 2/3 users are low-literacy but highly comfortable with voice (WhatsApp voice notes, calling). A conversational IVR or WhatsApp-bot path that mirrors the guided Q&A in spoken Hindi/Marathi could unlock a segment the current flow still can't serve.

Medium term · 3–9 months
Claim experience parity

We redesigned the buy. But the first time a user actually needs the product, they hit the claim flow — which is still agent-dependent, opaque, and paper-heavy. Trust earned at purchase will evaporate if the claim experience doesn't match. That's the next high-stakes surface.

The measurement I'd set up now

Track 12-month retention and claim CSAT by acquisition channel and flow type. Conversion is the right metric for the purchase redesign. But long-term, the business only wins if the users who now buy themselves also stay, trust the product, and successfully file claims. Those are the metrics that tell you whether inclusive design actually changed the relationship, not just the funnel.

Future-State AI Vision

Future-State AI Vision

What becomes possible when AI is a first-class design material
Adaptive language
The interface speaks the user's language, literally

An LLM layer detects preferred language from device locale and interaction patterns, switching the entire purchase flow to Hindi, Marathi, Tamil, or Bengali without a language-select step. Jargon is auto-translated not just linguistically but conceptually — "co-payment" becomes "your share of the hospital bill."

Conversational recovery
Drop-offs trigger a conversation, not a re-marketing email

When a user abandons at payment, an AI-powered WhatsApp message asks: "Had a question before you paid? I can help." The bot handles the top 10 objections (refund, document need, trust) without an agent — and hands off with full context if it can't resolve.

Dynamic plan explanation
Plan summaries generated from the user's own answers

Instead of a static copy block, the plan summary is generated dynamically: "Since you have diabetes, your waiting period is 2 years — but after that, all treatment is covered at ₹0." Personalised to their inputs, not averaged to a persona.

Claim assistant
Filing a claim becomes as simple as buying was

A guided AI claim assistant walks the user through hospitalisation documents, takes photos via camera, auto-fills form fields from OCR, and tracks claim status in plain language. "Your discharge summary is uploaded. Claim is with the insurer. Expected: 7 working days." No PDF email chains, no call centres.

Design principle for AI features
AI should reduce the burden of knowing, not add a layer to navigate

Every AI capability gets the same filter applied to the existing product: does this make it easier for someone with no insurance literacy to act confidently? A chatbot that answers questions but requires the user to know what to ask is not progress. The bar is: can a first-generation smartphone user complete this without a phone call to a relative?

A note on responsible deployment

AI in financial products carries real risk when it confidently misguides. Every AI-generated explanation in this vision needs a disclosure, a human review layer for edge cases, and a clear path to a licensed advisor. The design system includes a "AI-assisted" label on dynamically generated summaries. Trust in the product depends on users knowing what a human wrote and what a machine inferred.

NOTE — placeholder metrics: the numbers on this page are illustrative. Replace with your real results before sharing.
More high-stakes work

Building something where the wrong call gets expensive?

Start a conversation