← Portfolio / Luma Finance
Case Study

Reimagining Personal Finance through Behavioral Habits

Product Luma Finance
Role Founder & Lead PM
Focus 0→1, Behavioral UX, MVP Scoping
Status
Currently Building
Founder Behavioral Economics 0→1 Strategy Product Positioning MVP Scoping
Section 01

Strategic Objective / The Anxiety-Accounting Gap

Most finance apps treat money as a math problem. Track every transaction, categorise every purchase, surface a dashboard full of numbers. The logic is sound but the assumption is wrong. Users with money anxiety don't fail because they lack data. They fail because the apps make them feel judged.

Luma starts from a different premise entirely: money problems are behavioral, not mathematical. Fix the emotional relationship with money first, and the financial outcomes follow.

The Pattern
Users in the 25-40 "Independent Earner" segment have typically tried and abandoned 2-3 finance apps. High initial engagement, guilt when they miss a week, then full abandonment. The app becomes another thing they're failing at.

The strategic objective was to build a habit-first financial coach that prioritises emotional awareness and consistency over perfect ledger reconciliation. Not track every cent but build a healthier relationship with money over time.

Problem space diagram
Section 02

Product Positioning / From Surveillance to Support

The personal finance app market is saturated — but saturated in one direction. Every major player frames money management as a performance metric. Green means winning, red means failing. The entire category is built around urgency and accountability.

That created a clear white space: a product that leads with support, not surveillance.

"Money problems are behavioral, not mathematical."
Positioning Decision
Luma removes the success/failure binary entirely. No red states. No guilt-triggering alerts. No "you overspent" notifications. The entire UX language is non-judgmental by design.

The target persona is the Independent Earner — ages 25-40, has tried budgeting apps and quit, earns enough but feels anxious about money. Optimised for Reflection over Reaction and Consistency over Perfection.

What competitors optimise for
Accuracy, completeness, category tracking, performance dashboards.
What Luma optimises for
Emotional awareness, habit consistency, calm engagement, long-term retention.
Competitive positioning matrix
Section 03

Core Product Loop / Check-in → Reflect → Adjust

The central design challenge: how do you keep users engaged with their finances without triggering a stress response? The answer was to change the entry point entirely.

Unlike every other app, the entry point isn't a transaction list. It's an emotional check-in: "How did today feel financially?" This reframes the relationship from auditor to coach. The loop is designed to take under 2 minutes and feel like journaling, not accounting.

Habits as the Organising Layer
Instead of "you spent £200 on eating out," Luma surfaces habits like "Pause before online purchases." The focus shifts from "What did I spend?" to "How am I behaving?" — a fundamentally less anxiety-inducing frame.

The product is also explicitly designed for imperfection. Missing a day resets gently, not punitively. Partial tracking is supported by default. The all-or-nothing barrier that kills engagement in traditional apps is removed by design.

Core loop flow
Section 04

Identity & Privacy / Shared Intent, Not Shared Control

Shared finances are a minefield. Couples or accountability partners sharing financial data often creates pressure and judgment — the opposite of what Luma stands for. The challenge was to solve for social motivation without creating surveillance.

The Accountability Partner Model
A symmetrical role where partners see high-level habit progress — "Checked in 4 days this week" — but never see raw transactions, individual balances, or emotional check-in responses. Motivation without exposure.

The privacy logic is designed so that even a curious or controlling partner cannot extract meaningful financial data. What they see is aggregate signal — momentum, not money.

What partners see
Weekly check-in streaks. Habit completion rates. General momentum signals.
What partners never see
Transactions, balances, emotional responses, individual habit details.
Monetisation Decision
The Accountability Partner feature is the Pro tier unlock. Valuable enough to drive conversion, but not so essential that free users feel disadvantaged. That balance was deliberate — designed at the product spec stage, not retrofitted later.
Privacy model diagram
Section 05

MVP & Outcomes / Defined as Much by What Was Cut

The hardest PM skill is knowing what not to build. Luma's V1 is as much a story of restraint as it is of design.

The temptation with a finance app is to integrate with banks immediately — it feels like the "real" version of the product. But bank integrations in V1 would have shifted focus from habit-building to transaction-tracking. That's exactly the pattern Luma is trying to break. They're deferred to V2 deliberately — a product philosophy decision, not a resource constraint.

Monetisation Model
The core solo habit loop is fully functional on the free tier. Pro unlocks the Accountability Partner and advanced insights. Luma is genuinely useful before it asks for money — not artificially limited to force conversion.
What This Case Study Demonstrates
0→1 product thinking, behavioral economics applied to UX, ruthless scope discipline, a clear monetisation thesis, and a local-first technical architecture decision — all before a single line of code was written.