Discover → Define → Ideate → Design → Test
Fintech · Mobile App · 2026Concept Project

Budgeting that
builds itself

A case study on designing Cairn — a budgeting and expense-tracking app that turns transaction data into a visible trail of financial progress, built for a 2026 landscape of AI-assisted, trust-first money management.

Role

Lead Product Designer

Timeline

10 weeks, end‑to‑end

Platform

iOS & Android

Tools

Figma · FigJam · Maze

Try the clickable prototype ↓
9:41●●● 5G 100%
Milestones
Emergency fund
9:41●●● 5G 100%
This week
Tue, Jul 28 — your trail so far
Left to spend this week
₹6,140
Groceries
Dining
Transport

What is Cairn?

Cairn is a budgeting and expense-tracking app that automatically organizes a user's spending into flexible categories and visualizes long-term progress as a personal trail — with savings and debt-payoff milestones marked as stacked stones, or "cairns," instead of spreadsheets and shame-toned alerts.

The Problem

Most budgeting apps still ask people to behave like accountants: log every purchase, force spending into rigid monthly categories, and absorb red, judgmental warnings when life doesn't cooperate. Research into 2026 fintech behavior shows users don't quit budgeting apps because they don't care about money — they quit because the apps make caring feel like homework, and because AI-driven "insights" often feel surveilled rather than supportive.

The Goal

Design a budgeting experience that removes manual tracking as the default, explains every AI decision in plain language, adapts to irregular income, and replaces punitive spending alerts with a motivating, opt-in narrative of progress — while giving users precise control over how much automation and personalization they want.

Why now (2026 context)

Three shifts define fintech UX this year: explainable AI is now expected, not a differentiator; users will only link real accounts once trust is earned before KYC; and financial wellness — not transaction speed — is what keeps people coming back. Cairn was designed directly against these three shifts.

Explain, don't assume
Consent before automation
Progress over perfection
Calm over gamified

Design Process

A five-stage double-diamond process, run end-to-end with weekly syncs alongside one PM and two engineers.

Discover

Research & competitive analysis

Define

Personas & journey mapping

Ideate

HMWs, IA & user flows

Design

Wireframes to hi-fi UI

Test

Usability testing & iteration

W1–2Research & interviews
W2Competitive analysis
W3Personas & journeys
W4HMWs & IA
W4–5User flows
W5–6Low‑fi wireframes
W7Style guide
W7–8Hi‑fi UI
W9Prototype
W10Usability testing

Design Strategy

Four opportunities emerged for differentiating Cairn against the current budgeting app landscape.

01

Automatic, editable categorization

Categorize spending by default; let users correct in one tap instead of building every category from scratch.

02

Explainable, consent-based AI

Every AI suggestion states its confidence and reasoning, and personalization is adjustable, never assumed.

03

Income-flexible budgeting

Rolling budget periods and income-smoothing for freelance and gig-economy earners, not just fixed salaries.

04

Progress as narrative, not punishment

A visual trail of milestones replaces red over-budget banners with empathetic, judgment-free language.

Phase 01

Discovery Phase

Understanding why budgeting apps fail to retain users, and what trust actually looks like in an AI-assisted financial product.

Qualitative Research

1:1 moderated interviews to surface the emotional and behavioral reasons behind budgeting-app abandonment.

  • Objective: uncover trust barriers, effort tolerance, and what "progress" should feel like
  • Method: remote 1:1 interviews, 40 minutes each
  • Sample: 14 participants — salaried employees, freelancers, and gig workers, ages 23–41

Quantitative Research

A follow-up survey validated interview themes at scale.

  • Objective: quantify friction points and AI comfort levels
  • Method: online survey, 12 questions
  • Sample: 112 respondents across income types
What stops you from sticking with a budgeting app long-term?
Too much manual entry
46%
Categories don't fit real life
28%
Lost motivation over time
18%
Privacy / data concerns
8%
How comfortable are you letting AI auto-categorize and flag your spending?
Comfortable, if I can review
61%
Only for basic categorization
24%
Not comfortable at all
15%
What would keep you engaged with a budgeting app long-term?
Visible progress toward goals
52%
Personalized, plain-language tips
31%
Gamified rewards / streaks
17%

Competitive Analysis

A structured review of three category-leading budgeting products to map strengths, gaps, and openings for differentiation.

YBYNAB
MMMonarch Money
RMRocket Money
DescriptionManual, zero-based budgeting method for intentional spendersNet-worth & investment tracking with household collaborationBill negotiation and subscription cancellation, budgeting as add-on
StrengthsDeep methodology, strong community and financial educationPolished net-worth visuals, great for shared household financesEffortless setup, genuinely useful subscription and bill tools
WeaknessesSteep learning curve, entirely manual entry, no free tierPremium-only, overwhelming for budgeting beginnersUpsell-heavy UI, budgeting feels secondary to monetization features
AI & PersonalizationMinimal — philosophy is manual controlModerate — automated insights, limited explainabilityModerate — spend alerts, limited category flexibility

Conclusion

The gap in the market isn't another budgeting method — it's an app that combines YNAB's intentionality, Monarch's visual clarity, and Rocket Money's low-effort setup, without their respective weaknesses: manual burden, beginner overwhelm, and upsell fatigue. Cairn's opportunity is automatic categorization the user can trust, explained in plain language, wrapped in a progress narrative that feels earned rather than gamified.

Phase 02

Define Phase

Synthesizing research into shared patterns, then into two personas that anchored every design decision.

Affinity Mapping

Frustrations

Manual entry feels like a second job
Red "over budget" alerts feel like being scolded
Fixed categories don't match real spending

Needs & Wants

Automatic categorization I can still edit
Plain-language reasons behind AI suggestions
Budgets that flex with irregular income

Behaviors

Check the app in short bursts, several times a week
Abandon the app after one "bad spending month"
Rarely open budgeting apps for more than 30 seconds

Motivations

Wants to see visible progress toward a named goal
Wants control over how much AI does automatically
Wants reassurance the bank link is secure

User Personas

AR

Aditi Rao

26 · Freelance Content Strategist · Mumbai

"I don't need another app telling me I failed this month."

Pain Points
  • Fixed budgets break down with variable freelance income
  • Feels judged by red "you overspent" banners
  • Doesn't trust AI suggestions she can't understand
Goals
  • A budget that adapts to income swings automatically
  • Clear, plain-language reasoning behind every AI flag
  • A way to see progress without feeling scolded
RM

Rohan Mehta

34 · Software Engineer · Bengaluru

"If I have to set it up like a spreadsheet, I've already uninstalled it."

Pain Points
  • No time for manual entry or building categories
  • Abandoned three apps within a month each
  • Uneasy linking a real bank account without proof of security
Goals
  • Automatic tracking with almost no setup
  • Visible, concrete security signals before linking a bank
  • A 30-second weekly check-in, not daily nagging

Journey Mapping

Scenario: Rohan sets up Cairn and reaches his first savings milestone.

PhaseAwarenessDemo PreviewAccount LinkFirst WeekMilestone Reached
ActionSees Cairn recommended in a finance newsletterExplores the app with sample data, no account requiredLinks his bank once he sees the security explanationReviews auto-categorized transactions in under a minuteGets a quiet, tasteful notification: a stone added to his goal
Feeling🙂 Curious🙂 Reassured😌 Confident😊 Relieved🎉 Proud
OpportunityLead with outcomes, not features, in marketingLet value be felt before any personal data is requiredExplain exactly what is accessed and why, in plain languageDefault to automatic categorization with one-tap correctionCelebrate without gamified noise — no confetti overload
Phase 03

Ideate Phase

Reframing research insights as "How Might We" questions, then structuring the product around them.

Trust

How might we help users trust AI categorization without feeling surveilled?

Persistent "why we flagged this" explainability tags, visible confidence scores, one-tap confirm or correct.

Tone

How might we make budgeting feel like progress, not punishment?

Replace red over-budget banners with a trail-and-cairn metaphor and empathetic copy ("15% over on dining" instead of "You overspent").

Onboarding

How might we build trust before we ask for a bank login?

A demo-data preview mode lets users feel the product's value before any account is linked.

Flexibility

How might we support users with irregular income?

Rolling budget periods and income-smoothing suggestions instead of fixed calendar months.

Effort

How might we make a 30-second check-in feel worthwhile?

A single "this week" home card with one clear, prioritized next action.

Control

How might we give users granular control over personalization?

A settings panel that lets users dial automation from Manual to Assisted to Automatic.

Information Architecture

Cairn — Bottom Navigation
Home
  • Weekly trail summary
  • Next best action
  • Recent transactions
Budgets
  • Category stones
  • Rolling period view
  • Edit / merge categories
Insights
  • Spend trends
  • AI flags & explanations
  • Confidence & feedback
Milestones
  • Savings & debt goals
  • Cairn progress view
  • Milestone history
Profile
  • Linked accounts
  • Privacy & AI controls
  • Security center

User Flows

Flow 1 · Reviewing an AI-flagged transaction

User opens Insights tab
Sees transaction flagged with confidence badge and plain-language reason
Does the category look right?
Yes
Taps "Confirm" — category locked in
No
Taps "Edit" and picks correct category
Cairn learns preference for future transactions. End.

Flow 2 · Setting a savings milestone

User opens Milestones tab
Taps "New milestone" and names a goal (e.g. Emergency fund)
Is income steady or variable?
Steady
Fixed monthly contribution suggested
Variable
Rolling, income-smoothed contribution suggested
Goal confirmed — first stone placed on the trail. End.
Phase 04

Design Phase

From low-fidelity structure to a visual language built around trust, calm, and quiet celebration.

From Sketch to System

Low-fidelity
Mid-fidelity
Hi-fidelity
Left to spend this week
₹6,140
Groceries
Dining

A Direction We Explored, Then Cut

Not every idea survived contact with users. The gamified home screen below is the clearest example — and the reasoning behind cutting it shaped Cairn's tone more than almost any other decision.

Cut after testing
9:41●●● 5G 100%
🔥 12-day streak
Rank #4 among friends this month
M
T
W
T
F
S
S

Don't break the streak — log a transaction today!

🏅
🎯
💰
🔒
🔒
🔒
🔒
🔒
Sketch 2, Week 6 — streaks, ranks, and a locked badge wall.

Why it looked right on paper

31% of survey respondents said gamified rewards would keep them engaged, and Revolut's savings-challenge streaks were a clear competitor benchmark. A daily streak plus a badge wall tested well in isolation for "delight."

Why it was cut

  • In moderated testing, 3 of 4 participants matching Aditi's profile said a broken streak felt like "one more way to fail" — the exact shame spiral the whole project set out to remove.
  • Ranking users against friends assumes a stable, comparable income — it actively punished the irregular-income persona the app was designed to support.
  • It optimized for daily open rate, not financial health — engagement that isn't tied to an actual goal is the wrong metric for a budgeting app.

What replaced it

The cairn milestone system kept the "visible progress" insight that made streaks appealing, but tied it to a user-chosen goal instead of daily login pressure — progress that can pause without ever resetting to zero.

Visual Style Guide

Display — Fraunces
Reach the next stone
Body — Inter
You're 15% over your dining budget this month.
Data — JetBrains Mono
₹4,280.00
Color System

Pine

#1F3A2E

Ochre

#C6862F

Stone

#8C8570

Paper

#F1EFE7

Rust

#A85A3E

Iconography

Deep pine and warm ochre replace the typical blue-and-white fintech palette to feel grounded rather than corporate; the rust accent is reserved only for genuine warnings, never routine spending alerts, so it keeps its meaning. Icons use rounded strokes to match Fraunces' soft serif terminals.

Key Screens

High-fidelity screens from the final prototype, each tied to a research insight above.

9:41●●● 5G 100%
This week
Tue, Jul 28 — your trail so far
Left to spend this week
₹6,140
Groceries
Dining
Transport
Home — a single weekly summary replaces a cluttered dashboard.
9:41●●● 5G 100%
Budgets
Rolling 30-day period · flexes with income
Dining₹8,420
92% match Confirm
Groceries₹6,110
Auto-categorized
Subscriptions₹1,240
98% match Confirm
Budgets — categories behave like adjustable stones, not fixed boxes.
9:41●●● 5G 100%
Why we flagged this
Swiggy · Jul 26 · ₹640
CategoryDining

Flagged because it matches 14 similar food-delivery purchases this month. Confidence: 92%.

Auto-confirm matches above 90%
Notify me for new merchants
Transaction detail — every AI decision is explained, never assumed.
9:41●●● 5G 100%
Milestone reached
Emergency fund · Stone 3 of 8

You've placed your third stone. ₹15,000 saved — five more to go.

Milestones — quiet celebration, no gamified noise or streak pressure.
9:41●●● 5G 100%
Privacy & AI
Choose how much Cairn does for you
Manual — I categorize everything
Assisted — suggest, I confirm
Automatic — act on high confidence
Settings — personalization is a dial the user sets, not a default.

Anatomy of the Home Screen

Every element on the flagship screen traces back to a specific research finding.

9:41●●● 5G 100%
This week
Tue, Jul 28 — your trail so far
Left to spend this week
₹6,140
Groceries
Dining
Transport
1
2
3
4
5
1

Weekly frame, not monthly

Matches the 30-second check-in habit found in interviews — nothing to parse a full month of data for.

2

Stone progress, not a percentage

Replaces a bare completion percentage with a visual trail so progress feels tangible rather than abstract.

3

Category order follows real spend

Highest-activity categories surface first, so the one thing worth reviewing this week is never buried.

4

Ochre used only where attention is earned

The one category running hot uses the accent color — color signals a decision point, not decoration.

5

Bottom nav sits in the thumb zone

All five destinations are reachable one-handed — see the reachability study below.

Inclusive Design

Accessibility & Trust Cues

2026 fintech UX is judged as much on who it excludes as on what it enables. Three checks ran alongside every screen.

Color contrast

Aa
Pine on PaperAAA9.1 : 1 — body text & headings
Aa
White on PineAAA9.6 : 1 — primary buttons & nav
Aa
Ochre — icons & large text onlyAA3.4 : 1 — never used for small body copy

Dynamic type support

100% — default
You're 15% over your dining budget this month.
150% — accessibility size
You're 15% over your dining budget this month.
Hard reach
Stretch
Easy reach

One-handed reachability

Primary actions, the weekly summary card, and the bottom navigation all sit in the bottom two-thirds of the screen — the zone a thumb reaches without a grip shift.

Security is shown, not just claimed

Before linking a bank account, Cairn shows read-only scope, encryption standard, and a revoke-access control in the same screen — not buried in a settings menu three taps deep.

  Read-only access, bank-grade encryption
Click through it

Try the Prototype

This isn't a screenshot — it's a working slice of the actual flow tested in the study below. Tap the flagged transaction, then confirm or edit its category.

9:41●●● 5G 100%
Insights
3 new transactions this week
Swiggy₹640
92% match · Dining Review →
Amazon₹1,899
Auto-categorized
Why we flagged this
Swiggy · Jul 26 · ₹640
CategoryDining

Flagged because it matches 14 similar food-delivery purchases this month. Confidence: 92%.

Choose a category
Swiggy · Jul 26 · ₹640
🎉 Entertainment
👨‍👩‍👧 Family & shared
🍜 Dining (keep as is)
Got it

Noted for next time — future Swiggy orders will be categorized the same way automatically.

Updated

Cairn will remember this correction and apply it to similar Swiggy orders going forward.

↑ Live demo — tap to interact
1

Browse this week's insights

Transactions the AI wasn't fully certain about surface first, with a confidence score attached.

2

Review the reasoning

Tap in to see exactly why a category was suggested — never a black box.

3

Confirm or correct in one tap

Either path teaches the model your preference for next time — no settings menu required.

Phase 05

Usability Testing

Moderated testing to validate whether the explainability and control mechanisms actually worked in practice.

Method

8 participants (4 matching each persona), moderated remote sessions via Maze, testing four core tasks: exploring the demo-preview flow, correcting an AI-categorized transaction, setting up an income-flexible savings goal, and adjusting the personalization level in Settings.

Session recording · Task 2 — correcting an AI-categorized transaction

● Rec — Participant 0603:41 / 07:52
Participant 06 · reacting to the confidence badge, 03:41 "Wait — ninety-two percent? Sure of what, though... oh, okay, I see, it's comparing it to my other Swiggy orders. Huh. That's actually kind of nice, ninety-two, not just 'trust me bro.' [laughs] Yeah okay, I'd confirm that one."

This reaction — relief once the number was explained, paired with an instinct to distrust an unexplained label — showed up in 5 of 8 sessions and directly shaped Finding 03 below.

01

The explainability tooltip went unnoticed

6 of 8 participants didn't realize they could see why a transaction was flagged — the info icon only appeared on hover/long-press.

Made the confidence badge always visible, not hidden behind an interaction.
02

"Budgets" and "Milestones" were confused

Several participants expected savings goals to live inside Budgets, since both showed progress bars that looked identical.

Gave Milestones a distinct cairn icon and stacked-stone visual language, separate from budget bars.
03

Participants wanted proof, not just a promise, of confidence

Testers trusted "92% match" more than a plain "auto-categorized" label with no number attached.

Added a numeric confidence score to every AI-categorized transaction, not just a badge.

Goal-setup task success

Before iteration
63%
After iteration
91%

System Usability Scale (SUS)

Before iteration
68
After iteration
82
Results

Outcomes & Reflection

Validated through iterative usability testing ahead of a planned engineering handoff.

91%
Goal-setup task success, up from 63%
82
SUS score — "Excellent" range
100%
Testers trusted linking a real account after the demo preview
8/8
Participants correctly identified Milestones vs Budgets post-iteration

What I learned

Explainability is only useful if it's impossible to miss — hiding trust-building information behind a hover state defeats its purpose. I also learned how much tone matters in financial messaging: the same underlying alert reads as either supportive or judgmental depending entirely on word choice, and users notice the difference immediately.

What's next

Next steps include testing the rolling-budget model with a larger sample of gig-economy users, exploring a lightweight voice interface for quick balance checks, and partnering with engineering to validate the confidence-scoring model against real transaction data before launch.