← Back
A phone showing the chatbot’s welcome screen, lit by a beam of light

Fortune Cookies Inc. · UX Research Intern · Mar – Apr 2025

An AI finance chatbot that earns trust before it asks

A financial AI that proves its value before asking what’s in your bank account.

RoleUX research
Qualitative research, concept design, usability testing
TimelineMar – Apr 2025
2 months
PlatformMobile / web app
TeamLeqi Huang
Isabelle Tang
Tyler Jan
Sky
★

My impact

My research shaped a response template and four entry-point flows. The template and prototype passed the product team’s design review, showing how stored context could lead to an explained recommendation and a practical monthly budget.

01

Overview

Made financial guidance feel safe from the very first question.

theAI.Money began as a follow-up to We FIRE, our team’s earlier financial planning platform. We FIRE gave users dashboards and manual data entry: useful, but demanding for someone with little financial experience.

The team wanted to lower that barrier. Instead of asking users to organize their finances first, theAI.Money uses AI conversation as the way in: ask a question, get guidance, no setup required.

Product

theAI.Money

A conversational financial assistant, from the team behind We FIRE.

Audience

Beginners, 20–35

New to AI tools and new to personal finance.

Core value

Value before data

Guidance first; financial details only when they clearly improve the answer.

The solution at a glance

Four ways in, one outcome

However much the user has shared, the assistant answers first, asks only for what would change the guidance, and confirms before using anything.

02

Problem

People were already asking AI about money. They just didn’t trust it with their numbers.

By 2024 the pattern was visible. Many Americans were using AI to help manage their finances, yet far fewer trusted it as much as a human advisor. People were willing to ask AI about money, but handing over specific financial details raised real concerns about privacy and how that data might be used.

Use AI for their finances37%

of Americans, rising to 61% among Gen Z.

Gen Z using gen-AI for money67%

and 62% of Millennials.

Trust it like a human advisor38%

Most still prefer a person.

Sources: BMO Real Financial Progress Index (Ipsos, Jul 2024, n=2,501); Experian (Atomik Research, Oct 2024, n=2,011).

For the chatbot, this trust gap showed up at a critical moment: getting started. The product needed personal context to give relevant guidance, but asking for financial details too early could make users hesitate. We needed to understand what people were comfortable sharing, what they expected in return, and what would help them feel in control.

So the challenge wasn’t building smarter AI. It was making people comfortable enough to use it.

03

Research

Ran three research streams to learn what makes newcomers willing to share.

Research questionHow do financial newcomers seek guidance today, and what shapes their willingness to share personal financial details with an AI tool?
5Semi-structured interviews
newcomers aged 20–35
12AI tools tested
in financial scenarios
6Competitor heuristic evaluations
Cleo, Kiro, Bright Money, Empower…

What we learned from the interviews

01

Users wanted a reason to share

They hesitated when tools asked for financial details before showing how that information would improve the guidance.

02

More tools still left the work to users

They pieced together banking apps, spreadsheets and memory to understand their situation.

03

Knowing what to do wasn’t enough to start

They knew they should budget, save or repay debt, but struggled to pick the first step.

04

Personalization meant relevance

They wanted guidance on their current question without explaining their entire financial situation.

User journey: where engagement breaks down

Concerned → hopeful → overwhelmed → discouraged. The drop after the first answers is where the opportunity sits.

User journey: initial concern, testing the value, growing uncertainty, delayed action, with the opportunity marked on the falling curve
!

The first AI response decided whether users continued

Asking AI a financial question and sharing personal details were separate decisions. Participants wanted relevant guidance, a manageable next step, and a clear reason to provide more context. That led me to the tools themselves: how did existing assistants give initial value, request information and help users move forward?

Evaluating existing AI tools

How did existing assistants handle requests for more context?

I evaluated 12 AI tools across seven financial scenarios (51 model responses), focusing on how they used available context, requested more information, and guided users toward a next step.

What the AI-tool review showed

Three takeaways
Learned 01

Use the context already available

Check what the user has shared before making assumptions or asking them to repeat it.

Learned 02

Offer an initial answer

Give useful guidance within the limits of the context, then explain what more information could improve.

Learned 03

Give each follow-up a purpose

Tie extra questions to the current decision, and say why the answer matters.

From 12 responses to one template

I compared the 12 tools’ responses to the same car-loan payoff scenario, mapping how they framed the problem, used context, explained options and suggested a next step. The comparison became an ideal response template: understand the question, make the options clear, then suggest a manageable next step.

Response template diagram: excerpts from Claude, ChatGPT, Gemini, Perplexity, Grok and DeepSeek mapped onto empathy, problem analysis, solutions, prevention, conclusion and follow-up blocks
Click to zoom · car-loan payoff responses mapped onto the template

Evaluating existing finance products

Does the pattern hold beyond AI responses?

I evaluated six personal finance products against Nielsen’s 10 usability heuristics. The same trust gap appeared in products already on the market.

What the product review showed

Three implications for the design
Implication 01

Let users explore before connecting finance info

Make bank linking optional, and offer a way to begin without a full financial profile.

Implication 02

Explain the information request

Show why a detail is needed and how it supports the current task before asking for it.

Implication 03

Keep the conversation flexible

Let users skip setup, leave a flow, and type their own questions instead of only preset replies.

04

Synthesis

Found the problem wasn’t a lack of financial advice.

Financial newcomers needed a first step that felt safe enough to try, clear enough to evaluate, and concrete enough to act on.

What each research stream contributed to the design

User interviews

A relevant first response and a clear reason to share more.

AI-tool evaluation

Guidance that uses available context and explains the next step.

Product evaluation

Ways to explore, skip requests, and choose how to continue.

HMWHow might we help users build enough trust to share, understand their options, and take the next financial step with confidence?
05

Ideation

Mapped how one response template adapts to every way a user could arrive.

The interaction map covers entry, optional onboarding and four account conditions. Each path adapts the conversation to the context already available, while following the same principle: provide value first, explain every request, and leave the user in control.

Entry & optional onboardingUsers can ask a question immediately; sign-up and onboarding appear only when useful.
Entry & optional onboarding interaction map
Guest · no stored dataOffers an initial answer without requiring sign-up or personal financial information.
Guest · no stored data interaction map
Signed in · no financial dataLets the user begin without completing a financial profile.
Signed in · no financial data interaction map
Signed in · partial dataUses available context and asks only for the missing information that would change the guidance.
Signed in · partial data interaction map
Returning · relevant data storedShows what’s already stored and asks users to confirm or update it before giving guidance. Nothing is reused without their approval.
Returning · relevant data stored interaction map
06

Design

Designed four starting points that converge on one shared outcome.

Each path collects or confirms context differently, then arrives at the same personalized guidance once the required information is available. Three decisions carry the trust-first idea across all four paths.

Review what will be shared: card balance and purchase APR requested, transactions not requested
Decision 01 · Path B

Preview what will be shared, before connecting

Before a card is connected, the assistant lists exactly what it will read. Card balance and purchase APR are marked Requested; transaction history is Not requested. Entering details by hand stays one tap away.

From researchUsers hesitated when a tool asked for financial details before showing how they would improve the guidance.

Card snapshot: two details available, one still needed; asks for a comfortable monthly payment
Decision 02 · Path D

Ask only for the one detail that’s missing

Balance and APR are already known, so the assistant asks for the monthly budget alone and says what it will be used for. Keep it general is always offered, so sharing never becomes a gate.

From researchThe strongest AI responses used the context already available and gave every follow-up question a purpose.

Ready to check: each detail, its value and what it is used for, with Use these details and Change a detail
Decision 03 · Paths A, B, D

Show how each detail will be used, then confirm

Before guidance is calculated, a table pairs every input with its purpose: balance sets the starting debt, APR the interest cost, budget the payment pace. Users confirm or change a detail. Nothing is reused without their approval.

From researchProduct reviews showed users need to see why information is requested, and stay free to change course.

All four paths, screen by screen

34 screens across guest, signed-in, returning and partial-data users. Click a screen to zoom.

A · Guest, no stored data

10 screens

Answer first → choose how to share → enter details step by step → confirm.

  1. A · Guest, no stored data, screen 1
    01
  2. A · Guest, no stored data, screen 2
    02
  3. A · Guest, no stored data, screen 3
    03
  4. A · Guest, no stored data, screen 4
    04
  5. A · Guest, no stored data, screen 5
    05
  6. A · Guest, no stored data, screen 6
    06
  7. A · Guest, no stored data, screen 7
    07
  8. A · Guest, no stored data, screen 8
    08
  9. A · Guest, no stored data, screen 9
    09
  10. A · Guest, no stored data, screen 10
    10

B · Signed in, no financial data

12 screens

A permissions preview before connecting: balance and APR “Requested”, transaction history “Not requested”.

  1. B · Signed in, no financial data, screen 1
    01
  2. B · Signed in, no financial data, screen 2
    02
  3. B · Signed in, no financial data, screen 3
    03
  4. B · Signed in, no financial data, screen 4
    04
  5. B · Signed in, no financial data, screen 5
    05
  6. B · Signed in, no financial data, screen 6
    06
  7. B · Signed in, no financial data, screen 7
    07
  8. B · Signed in, no financial data, screen 8
    08
  9. B · Signed in, no financial data, screen 9
    09
  10. B · Signed in, no financial data, screen 10
    10
  11. B · Signed in, no financial data, screen 11
    11
  12. B · Signed in, no financial data, screen 12
    12

C · Returning, data stored

5 screens

“Welcome back. Are these details still right?” Confirm, then receive guidance.

  1. C · Returning, data stored, screen 1
    01
  2. C · Returning, data stored, screen 2
    02
  3. C · Returning, data stored, screen 3
    03
  4. C · Returning, data stored, screen 4
    04
  5. C · Returning, data stored, screen 5
    05

D · Signed in, partial data

7 screens

“Just one detail to go”: two of three items are already covered, so it asks only for the missing budget.

  1. D · Signed in, partial data, screen 1
    01
  2. D · Signed in, partial data, screen 2
    02
  3. D · Signed in, partial data, screen 3
    03
  4. D · Signed in, partial data, screen 4
    04
  5. D · Signed in, partial data, screen 5
    05
  6. D · Signed in, partial data, screen 6
    06
  7. D · Signed in, partial data, screen 7
    07

One path, end to end

We took the returning-user path deeper

The four flows showed how the conversation adapts to different levels of context. To test the template through a complete financial decision, I developed the returning-user path into a clickable rent-planning prototype. Using stored information, it confirms what is still accurate, explains an income-based rent range, and turns the recommendation into a practical monthly budget.

  1. Reuse stored context
  2. Confirm details
  3. Explain the rent range
  4. Build a monthly budget
07

Reflection

Learned that trust has to come before the ask.

01

Trust before the ask

We FIRE asked users to organize their finances first and lost anyone who didn’t already understand them. theAI.Money exists to put trust before the ask.

02

Prove value before asking for numbers

Users weren’t refusing AI. They were refusing to hand over numbers before a tool proved it deserved them.

03

Show the reasoning, not just the answer

I added an income-based benchmark and a population chart so users could see the reasoning, not just the conclusion.

04 · Next

Test the other three paths

I focused on the returning-user path. The other three entry points share the template but weren’t tested as rigorously. That’s next.

Users weren’t refusing AI. They were waiting for it to earn their numbers.

Next On