From financial dashboards to decisions

Reimagining mobile wealth planning around user goals, conversational guidance, and interactive what-if scenarios.

Fintech

Mobile AI

MVP in development

My Role

Led end-to-end product design and UX strategy

Methodology

Competitive Analysis, AI Prototyping, Usability Testing

Team

2 UX Designers,

1 PM, 1 Developer

Tools

Figma Make, v0, Magic Patterns

Problem

Financial tools help people track money. Few help them understand what to do next.

Advisor-grade platforms offer sophisticated planning but are complex and desktop-first. Consumer tools focus on short-term tracking, fragment budgeting, investing, and planning across apps, and offer limited support for understanding how financial decisions connect over time.

Discovery & Research

Identifying the gap between financial tracking and decision-making

I triangulated secondary research, a 12-product competitive audit, and primary research to understand how people approach financial planning, and where existing tools fail to support them.

Literature review

Users seek accessible, flexible planning

Mobile convenience and guidance matter, but they're cautious about AI making financial decisions for them.

Competitive audit · 12 apps

Most tools stop at tracking

Consumer apps cover short-term money management. Scenario modeling is fragmented, complex, or desktop-only.

Survey (n=52) + 2 interviews

Most people plan on their own

65% don't work with an advisor. Wealth managers showed how good advice connects goals, decisions and trade-offs.

Where the apps we audited sit. Each one either looks backward or assumes an expert at a desk.

Key insight

Planning is goal-driven and future-focused

People don't just want to know where their money is today. They want to explore what's possible, understand trade-offs, and decide with confidence.

Research synthesis → Product opportunity

From tracking money to modeling what's next

Bring advisor-grade planning to a mobile-first experience where people set goals, simulate scenarios, weigh trade-offs and act with confidence.

Goal-based planning

Scenario modeling with trade-offs

Advisor optional

From research to requirements

Mapping evidence to requirements

After early concepting, I turned each research finding into a requirement and mapped it to a feature. Priority came down to two questions: how many research sources backed the need, and could the MVP support it from a short onboarding profile?

Early concepts: paper sketches and annotated wireframes of projection settings, goal setup and dashboard widgets

Requirement · evidence

Feature

Priority

See how one decision changes the rest of the plan

Audit · Survey · Interviews

Shared trajectory

One projection that every tool updates in real time

MVP

Test a choice before committing to it

Audit · Survey · Interviews

What-if calculators

Debt, savings and investment scenarios

MVP

Plan around a goal, not a budget category

Survey · Interviews

Goal-based planning

Goal types decide which fields appear

MVP

Get started without financial expertise

Lit review · Survey

Financial profile

Entered once, pre-fills every calculator

MVP

Compare options and keep the final call

Lit review · Interviews

Side-by-side comparisons

Trade-offs in plain language; the user decides

MVP

Plan for long-horizon goals

Audit · Survey

Long-term planning

FIRE planner, retirement guide, ideal-scenario view

Phase 2

Run specialized analyses

Audit

Advanced analysis tools

Debt-ratio analyzer, student loan optimizer, insurance estimator

Cut

MVP: backed by two or more sources and buildable from a short profile. Phase 2: needs richer onboarding data. Cut: narrow use cases with weaker survey signal.

01

The dashboard concept lost to a conversation

V1 led with widgets. Internal testing showed the friction wasn't reading numbers. It was knowing which tool and which inputs answered a question. Conversation lowers the knowledge needed to begin, and interactive controls keep the precision needed to decide.

How I used AI

AI built the prototypes. The decisions stayed with the team.

A Magic Patterns proof of concept let us test the whole system in code before any high-fidelity work, and it exposed the input/output collision early. V2 moved to Figma Make so testers could drag real sliders.

What I took forwardThe goal wasn't to remove financial complexity. It was to reveal it at the right moment, and on mobile that means deciding what controls what before drawing a single screen.