Ledgr
Leading the end-to-end product design of a personal finance app that helps people plan around their real payday, log every rupee, and turn a pile of transactions into one clear next decision.
- Role
- Lead Product Designer
- Scope
- Flows → features → wireframes → UI → design system
- Platform
- Web (mobile-first)
- Status
- Design in progress
01 · Context
Most money apps record the past. Ledgr is designed to help people understand it.
Bank apps tell you what cleared, and most budgeting apps stop at a neat monthly chart. But real money doesn't move in calendar months — salary lands on the 27th, spending is split across UPI, cards and cash, and small daily payments quietly add up. On Ledgr I own the product design end to end: mapping user flows, deciding which features earn a place, shaping the UX, moving from lo-fi wireframes to hi-fi screens, and building the design system from scratch. The goal is a calm, behaviour-first workspace — track money by behaviour, not guilt — where every entry teaches you a little more about where the money actually goes.
The problem space
- Budgets reset on the 1st, while people actually live payday to payday.
- Tiny payments and mixed payment modes (UPI, cards, cash, transfers) get lost in bank statements.
- Existing apps show more charts, but rarely answer "so what should I do next?"
- Logging feels like a chore, so people stop before the picture becomes useful.
What I'm designing
- Salary-cycle budgeting that treats each payday as the start of a new cycle, with carry-over of leftover budget.
- A 50 / 30 / 20 framework (needs, wants, savings) that turns salary into simple monthly guardrails.
- A 0–10 money score that makes the month readable at a glance, with the detail one tap away.
- An "amount first, everything else optional" logging flow and an AI assistant grounded only in the user's own data.
02 · The problem
Logging has to be faster than forgetting
If adding an entry takes more than a few seconds, people stop. The add flow is designed around one rule — amount first, everything else optional — with keyboard shortcuts on desktop and shake-to-open on phones to get straight into the Ledger.
One signal, without hiding the detail
People want a quick answer to "am I okay this month?" but also need to trust it. The 0–10 score gives that single signal, and the dashboard, category breakdown, calendar and daily trend let them open it up and see exactly what moved it.
Designing AI people can actually trust with money
The "Ask about your money" assistant only reads safe, read-only summaries of the user's own data. The UX had to make that boundary clear, suggest good starter questions, and remind people to verify important figures — useful, but never pretending to be financial advice.
The core idea
Plan. Log. See. Decide. — turn every transaction into one clear next decision.
03 · The screens
04 · Impact
100%
Design ownership
Owning every stage — user flows, feature decisions, UX, wireframes, UI and the design system.
1
Design system
Built from scratch to keep the Dashboard, Ledger, Analysis, Calendar and Settings consistent.
0–10
Money score
Designed a single, readable signal that summarises the month against the user's plan.
50/30/20
Budget framework
Turned a known budgeting rule into guided setup and live guardrails for needs, wants and savings.
05 · Learning
Clarity beats another spending chart.
Designing Ledgr end to end has pushed me to make product decisions, not just screens — deciding what not to build is as important as what goes in. Starting from user flows and feature priorities before touching UI kept the product focused on one question: what should I do next with my money? This case study is being updated as the design moves from wireframes to final screens.