WealthBasket

Helping first-time investors put money into expert-built portfolios on Paytm Money, and making it easy to keep investing.

This case study is password protected

The work is under a confidentiality agreement. Enter the password to read it, or email me and I'll share it.

FintechCase study
WealthBasket on Paytm Money: a phone showing the WealthBasket logo, with the line: finding and investing in curated stock portfolios becomes a cakewalk

3

days of scoping workshops with Paytm Money in Mumbai

4

core journeys designed, from first launch to a monthly SIP

30+

screens designed across iOS, Android and the web

The team

  • Design lead, agency
  • UX researcher, agency
  • Paytm Money product team
  • and three back-end developers

I was a product designer at the UX agency Paytm Money brought in for WealthBasket, working with our design lead and researcher, the client's product team in Mumbai and their back-end developers.

Tools used

  • Adobe XD
  • Sketch
  • Asana

My role

As a Product designer, I helped scope the project with the client, mapped the user journeys, planned our sprints and took the core flows from wireframes to visual design, reviewing each one with the developers who would build it.

  • Scoping workshop
  • User journeys
  • Sprint planning
  • Wireframes
  • Visual design
  • Developer reviews

Timeline and platform

About 12 months, 2020–21 on iOS, Android and the web

Overview

WealthBasket lets anyone on Paytm Money invest in model portfolios of stocks, exchange-traded funds (ETFs) and real-estate investment trusts (REITs), each built and managed by professional advisers. Diversification lowers the risk, and investors can still adjust a basket to suit them.

What a basket is

A set of stocks or ETFs, weighted after careful research, that follows one investment idea, theme or strategy. People can use it for long-term wealth or shorter-term goals.

Who it's for

Anyone who wants a diversified, low-cost portfolio without picking every stock themselves, from first-time investors to people who invest every month.

My part

Scoping the project with the client, mapping the journeys, and designing onboarding, the first purchase, monthly SIPs and the web view.

The problem

A basket asks people to trust stocks they didn't choose, picked by an adviser they've never met. For a first-time investor that is a big step, and the app had to earn that trust before asking for any money.

At the same time, people who already invested wanted the opposite: fewer explanations and faster ways to add money. One design had to serve both without slowing either down.

Who we designed for

Contextual interviews showed a dilemma: new investors need control and transparency to feel safe, while everyday investors want convenience. I mapped a journey for each, which showed the moments that mattered most.

New to investing

The first-time investor

Has savings to put to work, but doesn't know which stocks to pick or whom to trust.

Needs

  • To see what's inside a basket, and why
  • A small, safe first investment
  • Plain language instead of jargon

Gets in the way

  • Terms like ETF, REIT and rebalancing
  • Forms before any payoff

Invests every month

The everyday investor

Already holds baskets, checks in often and wants to add money without thinking about it.

Needs

  • Top-ups and SIPs in a few taps
  • Returns at a glance
  • A clear heads-up when a basket changes

Gets in the way

  • Explanations they've already read
  • Long checkouts for a repeat purchase

What we learned

Before the project, the agency had mapped a long list of journeys through an ethnographic study. A three-day scoping workshop at the client's offices in Mumbai narrowed them down to the moments with the most impact on the business, and I tested the existing platform to see basket investing from the user's side.

Trust comes from transparency

New investors wanted to see inside a basket, its stocks, weights and the adviser behind it, before putting money in.

Control before commitment

First-timers wanted to try, review and change details before any money moved. A guided trial run did more than any explainer.

Regulars want speed

Once invested, people wanted to top up or start a SIP in a few taps, without the hand-holding.

Process

After the workshop, my team and I turned the discussions into a set of work packages and a recommended scope. From there the work ran as a series of sprints, with research and testing between them.

A line drawing of the project path: scoping workshop, exploratory user research, interaction design, UI design, UX patterns, presentation, concept sprint and user testing, with loops where work went back for another pass
The project's path: from the scoping workshop through research, design and concept sprints to user testing, with loops back wherever testing sent us.
  1. 01

    Scope

    A three-day workshop with the client to agree the scope, success criteria and guiding principles.

  2. 02

    Map

    A user journey for each kind of investor, marking the moments that needed the most care.

  3. 03

    Plan

    A simple sprint board so the bare minimum got built first.

  4. 04

    Wireframe

    Semi-low-fidelity wireframes, iterated through the year as features and feedback came in.

  5. 05

    Design

    Visual design, starting with onboarding, reviewed with the back-end developers at each step.

  6. 06

    Validate

    Internal critiques, user testing and technical checks, so each concept fit the existing platform.

Building the bare minimum first

I set up a deliberately simple board in Asana. Four columns were enough to keep a client team, developers and designers looking at the same week:

Tasks

Everything planned for the week.

Active sprint

What was being worked on that day.

Sprint backlog

Anything carried over from the previous sprint.

Done

Finished and reviewed.

A whiteboard covered in early flow sketches, screen boxes and notes from a working session
Early flows on the whiteboard. Wireframes showed quickly which layouts and components worked before anything went to visual design.

Key decisions

I sketched and prototyped several ideas for each flow, then refined them through internal critiques, user testing and technical checks. Three decisions shaped the product most.

If it needs a tooltip, it needs another look.

A rule I keep coming back to

A guided first run instead of a form

Onboarding introduces baskets through a friendly guide and a trial investment, game-like and step by step, so a first-timer understands what they're buying before being asked for anything.

  • Builds trust
  • Plain language
  • Learn by doing

Know the investor before suggesting a basket

A short risk profile and a clear choice of advisory plan come before the first purchase, so the baskets people see match how much risk they're comfortable with.

  • Better-fit baskets
  • Transparency
  • Fewer surprises

A monthly SIP in three steps

For everyday investors, a systematic investment plan takes an amount, a frequency and a start date on one screen, then a confirmation. Regular investing becomes a habit, not a chore.

  • Fewer taps
  • Repeat investing
  • Built for regulars

The flows, screen by screen

Onboarding came first. Once it worked, I walked the back-end developers through it to check it against the platform, then moved on to purchasing and SIPs.

Onboarding

A guided, game-like first run

Onboarding, part 1: a guide explains that anyone can invest in portfolios built by expert advisers, then offers a trial investment in a WealthBasket Onboarding, part 2: a confetti celebration after the trial, then confirmation screens saying the investor is up to date and invested Onboarding, part 3: an introduction to investing in WealthBaskets and the first basket's details

Buying a basket

The first purchase

First purchase, part 1: exploring a WealthBasket and entering personal details First purchase, part 2: reviewing details and completing a short risk profile First purchase, part 3: the risk result, choosing an advisory plan and confirming it with a one-time password First purchase, part 4: paying the advisory fee and the payment success screen

Monthly SIP

After the first purchase

SIP, part 1: the portfolio overview with returns, the list of WealthBaskets and a basket's detail page SIP, part 2: entering an amount, choosing a monthly frequency and picking a start date SIP, part 3: confirming the SIP and the payment success screen

On the web

The same flows carried over to Paytm Money on the web, so investors could check and manage their baskets from a browser after buying on their phone.

Web app

After purchase, in the browser

Web app: the portfolio overview with invested amount, current value and basket distribution Web app: the list of the investor's WealthBaskets Web app: a basket's detail page with performance and holdings Web app: entering how much to invest

Results

The flows went into the build with the client's team, and Paytm Money took WealthBasket to market. I wasn't able to test or measure the designs after handoff, so I can't share usage numbers; the screens above are the work as delivered.

Looking back

As an early fintech enthusiast, this was a chance to learn investing products first-hand. I'm grateful for it, and there are things I'd do differently now.

Investing is cultural

The client taught me how differently people approach high and low investment, and it still shapes how I design fintech products.

Agree how to measure, early

The project's scale and the stakeholders' priorities didn't line up for post-launch testing. Next time I'd agree success measures before the build starts.

Process is a skill too

With what I know now, I'd bring testing earlier and keep the scope tighter. That's what the project was for: learning.

Paytm Money's WealthBasket campaign artwork: an illustrated investment expert surrounded by money bags
Paytm Money's launch artwork for WealthBasket.

Some details are left out because the work is confidential. My role was to help frame the product's long-term direction, run the research and make sure the design held up. If you'd like to know more, email me and we can talk it through on a call.

Next project Atlas Design System

This case study is password protected

Enter the password to read this case study. Don't have one? Email [email protected] and I'll share it.