I Built My Own Budgeting App. Here's the Finance Professional's Problem with Every Existing One.
I Built My Own Budgeting App. Here's the Finance Professional's Problem with Every Existing One.
I've spent over twenty years working with financial data professionally — budgets, forecasts, management reporting, payroll reconciliations. How financial data is handled, stored, and protected is something I think about constantly in a professional context. So when I went looking for a personal budgeting app, I expected to find something that worked. What I found was a set of trade-offs I couldn't get comfortable with.
Eventually I stopped looking and started building. The result is the PFL Budget App. But this post isn't a product announcement — it's about what I found wrong with the existing options, why those problems matter more than most people realise, and what a finance professional's checklist for any financial tool actually looks like.
The Bank Connection Problem
Almost every modern budgeting app leads with the same feature: connect your bank accounts and we'll automatically import your transactions. It's framed as convenience, and it genuinely is convenient. But the moment I started reading what that connection actually involves, I hit a wall.
The issue isn't the bank connection itself. The issue is what happens to your transaction data once it's inside the app's ecosystem. Your bank transactions — every coffee, every transfer, every direct debit — are being stored on a third-party server. That company now holds a detailed picture of your financial behaviour. And while most of these companies have reasonable security practices, "reasonable" and "in your control" are not the same thing.
What will that data be used for? What happens if the company is acquired? What does their privacy policy say today, and what will it say after the next update? These aren't paranoid questions — they're the same questions I'd ask in a professional due diligence context. And as someone who works with organisations' financial data every day, I wasn't willing to drop that standard for the sake of automated transaction imports.
The Complexity Problem — From a Finance Expert's Perspective
The data concern was the first problem. The second was simpler but equally frustrating: most budgeting apps are too complicated, and not in a way that adds value.
This probably sounds odd coming from someone who works in finance. But there's a difference between complexity that reflects genuine analytical depth and complexity that accumulates because someone thought more features meant more value. Most consumer budgeting apps fall into the second category — investment tracking, net worth calculators, savings goals, credit score monitoring, all layered on top of what should be a simple task. The core function gets buried.
From a finance professional's perspective, good financial tools do one thing clearly and do it well. The best management reporting frameworks I've worked with aren't the most feature-rich — they're the ones where the relevant information is immediately visible and the noise is removed. What I actually wanted was straightforward: set a budget by category, enter what I spend, see where I stand. No credit score widget. No "insights" about coffee spend. Just a clean, honest view of whether I'm on track.
What I Built — and the One Decision That Shaped Everything
When I decided to build something myself, the architecture decision came first, before any feature decision. Where does the data go?
The answer I landed on: your financial data is not stored in a PFL-operated database or persistent server storage. It is processed transiently through serverless infrastructure and saved directly to your own Google Drive. Your data lives in your Google account, under your control. If you delete it from your Drive, it's gone — not archived somewhere on our end.
This isn't just a privacy feature — it's a structural commitment. PFL doesn't accumulate user financial data over time. The privacy promise isn't dependent solely on our security practices; it's built into where the data lives. Google Sign-In only, handled by a specialist identity platform. No separate account creation, no new password, small attack surface.
What It Actually Does
The free tier is designed around that "one thing clearly" principle. Set budgets by category — up to twelve — choose your cycle (monthly, quarterly, biannual, or annual), and enter transactions as you go. The envelope budgeting approach carries unused budget forward, which is how most people actually think about their money across months.
✅ Free Tier — Live at apps.professionalfinancelink.com.au
- Manual transaction entry — fast, by category, no bank connection required
- Category budgets — up to 12 categories with custom amounts
- Flexible budget cycles — Monthly, Quarterly, Biannual, or Annual
- Envelope budgeting — unused budget rolls forward automatically
- 4-tab dashboard — Overview, Add, History, Settings
- Overview dashboard — 4 widgets:
- Monthly Spend — actual vs budget line chart
- YTD Tracking — cumulative actual vs budget opened, so you can see at a glance whether you're tracking ahead or behind across the full year
- Top 5 This Month — highest spend categories for the current month
- Budget Health — % of categories on track, at risk, or over, plus your overall YTD spend rate vs budget
- Per-category breakdown — current period progress plus YTD position for every budget category
- Auto-save to your Google Drive — every entry, immediately, no PFL server storage
- No ads. No subscription. Completely free.
A paid tier with CSV import for the major Australian banks is in development for users who want transaction import without the third-party data storage trade-off. The same architecture applies: your data goes to your Drive, not ours.
The Questions You Should Be Asking Any Financial Tool
Whether you use this app or not, the due diligence questions are worth having. I'd apply these to any tool that handles financial data — personal or professional.
📋 Finance Professional's Checklist for Financial Tools
- Where is my data stored? On the vendor's servers, or somewhere I control? Who has access to it?
- What is the business model? If the product is free, how does the company make money — and does that involve your data?
- What happens in an acquisition? If this company is bought, what does their privacy policy say about data transfer to a new owner?
- What happens in a breach? What data would be exposed, and what is their disclosed incident response process?
- Can I export and delete my data? Do I have genuine control, or is my data effectively theirs once I've entered it?
- Does the complexity match the task? Or has the product accumulated features that obscure rather than inform?
These questions don't have to be adversarial. Most legitimate tools can answer them clearly. The ones that can't — or that bury the answers in thirty pages of privacy policy — are telling you something worth listening to.
The Australian Consumer Data Right framework has improved data access standards for bank-connected apps under ACCC oversight. But CDR governs data access — not what happens to your data once it's inside an app's ecosystem. That question is still yours to ask.
Why This Is a Finance Mindset, Not Just a Privacy One
What surprised me building this was how naturally finance professional instincts apply to personal tool design. In a professional context, we ask hard questions about data governance and control. We don't accept "trust us, we're secure" from vendors managing sensitive information. Most people don't apply that same rigour to tools managing their personal finances — partly because the UX is friendly, partly because the data feels less consequential. But your transaction history, your spending patterns, your income and savings behaviour — that's genuinely sensitive information, and it deserves the same question: where does it go, and who controls it?
That's the insight I'd leave with you, regardless of what tool you use. Treat your personal financial data with the same governance instinct you'd apply professionally. Ask the questions. Read enough of the privacy policy to understand the business model. If the answers don't satisfy you, look for a different trade-off.
The PFL Budget App is free. Sign in with Google and your data stays in your Drive — not ours. If you want to see how we've approached the architecture, the app speaks for itself.
Try the PFL Budget App → Learn about PFL →
Comments
Post a Comment