BudgetTree, Personal Finance App

Personal Finance App Case Study

Back to projects

I designed a calm gifting and budgeting journey that helps users create meaningful financial actions without complexity.

Scope of workMobile Consumer Finance
Timeline6 weeks
RoleProduct Designer
TeamFounder, 1 PM, 2 Engineers

About BudgetTree

BudgetTree is a personal finance app built around budgeting and goal-based gifting: money is set aside towards a specific gift or goal rather than an abstract category. This case study covers the setup and gifting journeys.

BudgetTree: Personal Finance App Case Study overview

The problem

BudgetTree asked users to construct a budget before it gave them anything back. The setup cost was paid up front and the reward arrived, if at all, several sessions later.

User pain

  • Users wanted quick gifting but faced too many setup steps.
  • Budget visibility was weak during gift creation.
  • Festival and event context was not built into workflow.

Business pain

  • Drop-offs reduced completed gifting transactions.
  • Users abandoned before adding payment method.
  • Repeat usage weakened after first attempt.

Product gap

  • No clear bridge between intent, amount, and execution.
  • Contextual templates were buried in navigation.
  • Budget feedback appeared too late to guide decisions.
BudgetTree user flow diagram

What I owned

Owned

  • Product strategy, user flows, and information architecture
  • Wireframes, interaction model, and high-fidelity UI
  • Validation synthesis and iteration decisions
  • Developer handoff with behavior states and edge cases

Collaborated

  • PM on scope, sequencing, and KPI alignment
  • Engineering on technical feasibility and state visibility
  • Stakeholders on domain constraints and rollout priorities

Out of scope

  • Backend implementation and infrastructure changes
  • Pricing, growth campaigns, and sales operations
  • Post-launch paid acquisition strategy

The results

+29%

gift creation completion

-35%

drop-off in setup flow

4.5/5

flow simplicity score

Users completed gifting tasks with less effort and more certainty. Critical setup flow became shorter and more intuitive. Improved completion supports repeat event-driven usage.

The approach

I designed the reward first and the structure around it, so the product earns the setup effort it asks for instead of assuming it.

01

Discover

Mapped user and business friction through interviews, workflow audits, and benchmark analysis.

02

Prioritize

Ranked opportunities by impact on activation, task success, and decision confidence.

03

Design

Built IA, interaction patterns, and high-fidelity solutions with clear state behavior.

04

Validate

Tested critical flows, measured drop-offs, and iterated before development handoff.

The decisions

The calls that shaped the product, with what each one cost. Anything crossed out here was a real option at the time.

Decision 1: Entry point

Users entered app but did not know first action.

Considered

  • Dashboard-first
  • Occasion-first
  • Template-first

Chose

Occasion-first with prefilled template journeys

Gave up

Reduced early access to advanced settings

On what evidence

Users picked occasions faster than financial categories

What happened

Completion improved by 29%

Decision 2: Budget guidance

Users overshot budgets during setup then abandoned.

Considered

  • Static budget limit
  • Live budget meter
  • Post-submit warning

Chose

Live budget meter with threshold nudges

Gave up

Added visual component in dense screen

On what evidence

Abandonment spikes followed payment review stage

What happened

Flow drop-off reduced by 35%

Decision 3: Confirmation path

Users needed emotional clarity plus transaction certainty.

Considered

  • Utility-only receipt
  • Celebratory confirmation
  • Silent completion

Chose

Celebratory confirmation with clear receipt states

Gave up

One extra visual layer

On what evidence

Users asked for reassurance after payment step

What happened

Higher trust and repeat intent

The work

A gift or goal can be created in a single pass, and the category structure builds itself out of that action rather than being demanded before anything useful happens.

Occasion setup: Start from user intent, not system complexity.

Occasion setup

Start from user intent, not system complexity.

Budget controls: Keep spending confidence visible through the flow.

Budget controls

Keep spending confidence visible through the flow.

Confirmation: Close with emotional and transactional clarity.

Confirmation

Close with emotional and transactional clarity.

Targets, set up front

Gift creation completion

Baseline 41%

Target 52%+

Result 53%

pilot batch

Flow drop-off

Baseline 40%

Target <30%

Result 26%

funnel check

Simplicity score

Baseline 3.6/5

Target 4.2+

Result 4.5/5

usability survey

Outcomes in detail

Completion41% → 53% · +29%

More successful gifting outcomes

Flow drop-off40% → 26% · -35%

Lower abandonment

Simplicity score3.6/5 → 4.5/5 · +0.9

Better user confidence

Reflection

What worked

Occasion-first flow aligned naturally with user mental models.

What to improve

Add collaborative gifting journeys for family groups.

Next experiment

Test predictive budget suggestions by event type.

Next projectPortfolio
Investock.ai
Investock.ai
Web and Mobile Fintech10 weeks
Softly lit reading nook with a grey lounge chair and ottoman

Vinit Chaudhary

Vinit Chaudhary

I'll personally review your brief and get back to you within two hours.

Product Designer

Contact

I usually respond to all digital enquiries within 2 business hours.

Vinit Chaudhary

Let's Work Together.

Reach out today and let's craft designs that elevate your brand to the next level.

© 2026 Vinit Chaudhary. All rights reserved.