Most people who try to track a personal budget do it in Excel. It works, technically. The math is correct, the formulas run, the categories add up. But somewhere around month three, the spreadsheet stops getting opened. The numbers keep happening in real life, just not in the sheet.
That was the exact situation a recent Fiverr client was in. She had a working Excel budget. She’d built it herself. She’d maintained it for over a year. And she was tired of it.
When she reached out, she sent two files with the first message: her current Excel file, and a rough PNG sketch of what she wished her budget looked like. The sketch had dark cards, round charts, and progress bars. She’d seen dashboards like it online and wanted to know if Notion could build the same thing for her personal finances.
This is how that build came together, what we decided along the way, and what made the final system something she actually uses.
The Requirements
She was specific about what she needed:
- Track expenses by category (education, food, subscriptions, and others)
- Compare actual spending against budget each month
- See yearly trends at a glance
She was equally specific about her concerns. She worried that any new system would add friction, and she’d drift back to Excel within weeks. She wanted the dashboard to feel clean, not colorful, and motivating to open each month. She described the feeling she was after as “almost gamified.”
One more detail shaped the entire build. She uses a dedicated virtual credit card for each spending category. That meant her actual data entry is one or two transactions per category per month, not dozens. The system didn’t need to handle high-volume input. It needed to handle low-volume input beautifully.
The Scoping Process
Before any Notion work started, I recorded two Loom walkthroughs and shared a Whimsical architecture diagram.
The first Loom covered the proposed structure. A central Transactions database would feed monthly dashboards. Each month would use the same pre-built template. The yearly view would calculate automatically from the transactions. The workspace would be structured one year at a time, then duplicated for the next year.
The Whimsical diagram made the structure visual. Every database, every connection, every view, laid out on a single map. She could see the whole system before it existed.
The second Loom confirmed the finalized scope. 16 expense categories and 4 income categories, 20 total. It walked through the exact chart types, the layout of each monthly dashboard, and how the yearly trend view would be organized. Only after this Loom was approved did database work begin.
Two Loom walkthroughs and a Whimsical diagram before writing a single formula. This is my standard process. Clients don’t get surprised by what I deliver because they’ve already seen it, twice, before it exists.
The Build
The final workspace contained:
A Transactions Database as the single source of truth. Every income and expense entry lives here once, tagged with a category, a date, and an amount. She never has to look at this database directly.
Category Databases for both expenses and income. Each category stores its own monthly budget and connects to all related transactions. These databases feed the per-category charts on the yearly view.
12 Monthly Dashboards, each built from the same template so every month looks identical. Headline metrics at the top (target income, spend on needs, spend on wants, total used, total saved). An income vs expenses line chart below. A category performance donut chart. Per-category progress cards showing actual vs budget as a filling progress bar.
A Yearly View with 20 category charts, one for each expense and income category, each comparing projected vs actual performance across all 12 months. This is the view she uses to make decisions about next year’s budget.
A Dark, Minimal Visual Design matching her request. One accent color for neutral progress, green for positive deltas, soft red for overspend. No rainbow category palette. The dashboard feels calm, not busy.
Why the Monthly Template Matters
Her original Excel file had a different layout in every month’s tab. She’d made small adjustments over the year, and by December the sheets didn’t match. That inconsistency was part of why she stopped opening the file. Every visit required re-orienting to a slightly different layout.
In the Notion build, every month uses the same template. January looks exactly like July. The same five headline numbers sit in the same place. The same chart is always in the same column. The same progress cards stack in the same order.
This is the quiet reason dashboards work. Muscle memory beats novelty. Once she knew where to look, checking her budget became a 20-second action instead of a 10-minute chore.
The Yearly View Did Something Excel Never Did
In her Excel file, she could calculate yearly totals. She couldn’t see yearly patterns.
The Notion yearly view stacks 20 category charts on one page. Each chart shows the projected budget and the actual spending month by month. Two seconds of scanning reveals which budgets were set too low all year, which were too high, and which categories she’d been quietly underestimating.
Within the first month of delivery, she already had clearer answers about her own spending than she’d built up in a full year of Excel tracking. Not because Notion is smarter, but because the visualization was designed to be scanned, not calculated.
The Gamification Question
Her request for the dashboard to feel “almost gamified” shaped three specific design choices.
Progress bars on every category card that fill throughout the month. Seeing “68% of grocery budget used by day 18” feels different from seeing the same data as a dollar amount.
A dark theme instead of light, because light mode reads as spreadsheet work. Dark mode reads as a product you want to open.
Green and soft red deltas on the headline metrics, so good months feel visibly good and bad months are obvious without being punishing.
None of this is genuine gamification. There are no points, no levels, no achievements. But the dashboard engages the same visual system a fitness tracker does, which is enough to change the relationship she has with it.
Manual Entry, Not Automation
I could have proposed a bank integration, a Zapier workflow, or an email parser to automate transaction logging. I didn’t, because she didn’t need it.
Her virtual-card-per-category system already simplifies her data entry to the point where manual input takes under a minute per month. Adding an automation layer would have introduced a failure point without meaningfully reducing her workload. Integrations break. APIs change. The first thing that dies in a Notion budget system is usually the automation layer, followed shortly after by the workspace itself.
This is a decision I make on most personal finance builds. Automation sounds impressive on a feature list. Manual entry, done in seconds per month, is more reliable.
Built to Replicate
The last structural decision was making the workspace fully duplicatable. At the end of the year, she duplicates the entire workspace, resets her budget targets for the new year, clears the transactions, and runs it again.
Year-over-year data gets archived. Nothing gets rebuilt. No formulas re-entered. This turns the workspace from a one-year project into a long-term system.
The Outcome
The full build was delivered with a walkthrough Loom showing where to enter data, how the automations work, and how to duplicate the workspace for the following year. She watched one video and was running it independently the next day.
The friction concern, the one she’d raised at the beginning, didn’t materialize. The dashboard takes less time to maintain than her Excel file did, and she reports opening it more often than she ever opened the spreadsheet. The shift wasn’t about better math. It was about a system built to be looked at.
Need Something Like This?
If you’re running a personal budget in a spreadsheet you’ve stopped opening, or trying to build a Notion budget system and getting stuck, this is exactly the kind of build I do. I’ve built 400+ custom Notion workspaces for clients across finance, operations, content, and personal productivity.