Banking · Case Study · Growth under constraint
How I turned a stalled growth target into roughly 3,000 extra bookings a day — not with new technology or a bigger budget, but by finding the customer the business had misjudged.
Overview
Leaders rarely need more screens. They need a number to move. This project is a clean example of how I work: start from the business outcome, question the assumptions standing in its way, and prove the answer before scaling it.
Grow daily Fixed Deposit bookings in the bank's mobile app from 5,000 to 10,000.
The backend was completely off-limits. Every gain had to come from the experience layer alone.
When the first redesign failed, I went back to real customer behaviour and found the business was designing for the wrong people.
Daily bookings rose to nearly 8,000 in three months — about 60% growth, with no backend change.
Challenge
With the backend untouchable, every decision had to happen in the interface. Stakeholder discussions pointed to one logical audience — customers aged 35 to 50 — and we built the landing page, key screens and messaging around them. The redesign failed in testing.
Insight
Instead of polishing a broken assumption, I studied real behaviour and data from people actually using the banking app. The pattern that emerged had nothing to do with the age group the business had in mind.
The customers most likely to book a Fixed Deposit weren't 35 to 50 — they were 25 to 30. Nothing like we'd assumed.
Turning a failed test into a better question — rather than defending the original plan — is the decision that unlocked everything that followed.
Approach
A 25-to-30-year-old booking a Fixed Deposit has different motivations, different trust signals and a different pace than the audience we had assumed. So the journey had to be rebuilt around them, not retrofitted.
Treated the failed test as information, not a setback, and traced behaviour and data to find who was really booking.
Mapped what the real audience needed — motivation, trust signals and pacing — and chose the direction around them.
Redesigned the landing page and every key screen in the booking flow, all within the experience layer.
Tested the new experience with a small group of customers before rollout, so scale came with evidence.
The final booking flow — pick an amount and tenure, review what you’ll get, and book in one clear step.
Results
Within three months of the redesign, the app was booking close to 8,000 Fixed Deposits a day, up from 5,000. That is roughly 60% growth, delivered entirely through a better understanding of the customer.
How I work
The Fixed Deposit story is one example of a habit I apply to every business problem. If you lead a team, a product or a budget, this is what you can expect from me.
The most expensive mistakes are the ones everyone agrees on. I find the belief that hasn't been tested and test it first.
Locked systems, fixed budgets and tight timelines are the starting point, not an excuse. Constraints often produce the clearest thinking.
A short test with real customers costs far less than a failed launch, and it gives leadership evidence instead of opinion.
I connect design to a business number and share it as it is, including what fell short, so you can decide with confidence.
This applies when growth has stalled, when a product is live but unused, when a costly rebuild is on the table, or when a capable team is building confidently for the wrong user. If any of that sounds familiar, write to me at pranjal.productmind@gmail.com.
Go deeper on the thinking: Data-driven design · UX-led growth · Business-driven design