Banking apps show what happened, but rarely what it means or what to do next. Customers see balances and transaction lists, then do the math in their heads or in a spreadsheet.

• • Statements show numbers, not meaning. 
• A mid-month total says little until it is compared like for like.
• 
  
• • Budget tools feel like homework. 
• Categories and limits need setup before they give anything back.
• 
  
• • Purchase calculators ignore real life. 
• They don’t know the customer’s income, bills or savings goals.

The opportunity: use the data the bank already holds to answer everyday money questions in plain language, and let people try a decision before committing to it.

The design follows one customer from confusion to a plan they can keep. The persona is Jordan M., 31: salaried, renting downtown, saving about $1,239 a month and weighing a car purchase. Jordan's line: 

“I don't need a lecture. I need to know if I can do this.”

The journey runs in eight stages across three phases:

1. 1. Discover (AI Hub): “Where is my money actually going?”
2. 
   
3. 2. Understand (Spending Story): “Dining crept up again.”
4. 
   
5. 3. Anticipate (Financial Forecast): “Will I be OK until payday?”
6. 
   
7. 4. Ask (Ask About My Money): “Just tell me straight.”
8. 
   
9. 5. Explore (What-if Simulator): “Could I afford a Tesla?”
10. 
    
11. 6. Decide (simulation result): “Not affordable… what if I put more down?”
12. 
    
13. 7. Commit (Make this a plan): “Okay, let's make it real.”
14. 
    
15. 8. Follow through (notifications): “It's got my back.”

The emotional low point is stage 6, the “reality check.” The design bets that a clear “not affordable” is trusted when the levers to fix it sit right beside it.

Design principles

• • Plain language first, numbers always visible
• • Every insight leads to an action
• • Name exactly what the person asked about
• • The person stays in control: adjust, compare, undo