Insurance
Activation for a policy wallet, install to first tracked policy
An insurance broker is launching a policy wallet app. How do you design their activation journey from app install to policy tracking?
The problem
Policies sat behind a legacy PMS layer, so nothing was visible until the back end agreed to hand it over. Signup demanded full KYC before the user saw a single benefit, and the first screen after install was an empty list. The user had no reason to finish, and no reason to return if they did.
The solution
Flipped the order. Value first, verification later. Onboarding became conversational and progressive with four mandatory fields, KYC storage deferred to v2, and policy upload offered over WhatsApp for users who had the PDF but not the patience. Listing was rebuilt around the insured person rather than the policy number, with Active, Expiring, Expired and Needs attention as the primary cut, because a family buys for people and not for products. One stack-ranked action per surface, so no screen asks twice.
Shipped A PRD plus annotated wireframes for listing and detail, a WhatsApp-led upload path, and an event taxonomy that measures time to first tracked policy as the activation metric.
Education
A pre-school website that converts walk-ins, not just visits
A leading pre-school business wants to revamp their website to make more parents enrol their kids. How do you ensure the website gets more hits and more conversions?
The problem
Two separate problems wearing one brief. Traffic was weak because the site ranked for the brand name and nothing else, while parents search by locality and by age band. Conversion was weak because the only action on the page was a generic enquiry form that promised a callback nobody waits for.
The solution
For traffic, built pages around the queries parents actually type: pre-school in a named locality, playgroup admission age, daycare timings, fee structure. One indexable page per centre with its own address, photos, timings and staff, because a chain ranks locally or not at all. For conversion, replaced the enquiry form with a booked campus visit carrying a date, a slot and a confirmation, since the real conversion event is the parent standing in the building. Fees and timings go on the page rather than behind a callback, because hiding them filters out serious parents, not casual ones.
Shipped A centre-level page architecture, a search-intent content map, and a visit booking flow with slot visibility instead of an enquiry form.
Quick commerce
A grocery app losing half its installs before the second order
A grocery app was not getting repeat orders, and uninstalls per day were more than 50% of installs. How do you stop the churn and make customers stick?
The problem
An uninstall rate at half of installs is not a retention problem, it is an acquisition quality problem compounded by a weak first order. Discount-led installs brought people who came for the coupon and left with it. Those who stayed hit empty carts on the SKUs they actually buy weekly, and a delivery promise the app missed often enough to stop being a promise.
The solution
Split the cohort before fixing anything. Coupon-only installs were a spend decision, not a product one. For the rest, moved the first order to a basket the user recognises, seeded from their first search rather than from the merchandising calendar. Fixed availability on the weekly repeat SKUs ahead of the long tail, because a missing staple ends the relationship and a missing novelty does not. Built the repeat loop on reorder rather than on offers, since a grocery habit is a list, not a deal.
Shipped A cohort model separating paid from intent installs, a first-order basket flow, and a reorder surface on the home screen.
Wealth
Holding DAU through a red quarter
A mutual fund platform was seeing DAU fall because of a market crash and red portfolios that lasted a quarter. IPL was approaching, which gave an opportunity to engage users. How do you arrest the DAU de-growth and make the app stickier?
The problem
Portfolio value was the only reason to open the app, and the number was red. Every push notification was an invitation to feel worse. DAU was not falling because the product broke. It was falling because the product was working exactly as designed and the design assumed green.
The solution
Separated the reason to open from the reason to feel good. Gave the home screen a second job during a downturn: progress against goals and SIP discipline, which stay green while the portfolio is red. Used the IPL window as a scheduled reason to return rather than a theme, with a daily prediction built on the same behaviour investing needs, a repeated small call with a deferred payoff. Tied it to SIP streaks so the engagement left something behind once the tournament ended.
Shipped A downturn home-screen variant, a goal-progress surface, and an IPL engagement loop designed to convert into SIP continuity rather than vanity DAU.
Banking
Pulling a banking app's rating back from 4.2
A banking app was seeing its rating gradually fall, down to 4.2, which was a reputational loss. How do you increase ratings on the Play Store?
The problem
A rating does not slide on its own. Reading the one-star reviews, the complaints clustered in three places: login failures on specific device and OS combinations, a forced update that locked people out mid-transaction, and support that answered after the frustration had already been published. The rating was a lagging indicator of a reliability problem nobody owned.
The solution
Fixed the cause before touching the prompt. Instrumented login failure by device, OS and network so the engineering team had a cohort rather than an anecdote. Made updates optional until a security floor, so nobody is locked out mid-payment. Then moved the rating ask to the moment after a successful transaction instead of on app open, and routed unhappy users into support rather than into the store. Replied to existing one-star reviews with the actual fix, because Play Store replies are read by the next person deciding to install.
Shipped A failure-cohort dashboard, a revised update policy, a repositioned rating prompt, and a review response process owned by product rather than marketing.