Designing Budgets for Wealthstack: Bringing Monthly Cashflow into a Long-Term Planning Tool

The Challenge

Wealthstack is built for the slow money. Retirement goals, insurance, investments, net worth over decades. That's the work of a good financial advisor, and Wealthstack does it well.

But the money people actually feel is monthly. Salaries and expenses, debt, giving, what's left to save. That fast money is where budgeting lives, and it's the bridge between a client's day-to-day reality and the long-term plan an advisor is trying to build with them. Wealthstack wanted to add a Budgets feature to close that gap.

The idea was clear. The design was not, because a budgeting feature inside a planning tool has to solve several things at once.

• Two very different households. A salaried family and an incorporated business owner budget in completely different ways. One template couldn't serve both, and two disconnected ones would feel like two products.
• Data that already half-exists. Wealthstack already knows a lot about a client from their dashboard. Budgets had to feel like it was building on that, not asking advisors to re-enter everything from scratch.
• Budgets change over time. A single budget is a snapshot. The real value is comparing snapshots across periods to see where money is actually moving. That meant designing a history and a comparison view, not just one form.
• It had to feel native. Bolt a generic budgeting tool onto a considered planning product and clients feel the seam. Budgets had to read as Wealthstack.

You can't spec your way to confidence on something with this many moving states. You have to build it and use it.

The Approach: A Fully Interactive Prototype

Rather than design a stack of static screens and hope they added up to a coherent feature, we built the whole Budgets module as a working prototype. Both household templates, real capture, live totals, and a values-based framework underneath it all.

That let everyone judge the feature the way an advisor eventually would: by sitting down and capturing a real budget. Does the salaried flow map to how a family actually earns and spends? Does the corporate template handle revenue and salaries paid out without turning into a spreadsheet? Those questions only have honest answers when the prototype behaves.

Snapshots Over Time, Not a One-Off Form

A budget captured once is a photo. A budget captured every quarter is a story, and that story is exactly what an advisor and client should be looking at together.

So Budgets is built around snapshots. Each capture is dated and saved, and the module keeps the history. From there, a compare view shows how each allocation bucket has shifted across periods, so a conversation moves from "here's your budget" to "here's what's changed, and here's what we do about it."

The compare view (shown at the top of this page) takes that further, breaking each period down by category and surfacing the difference, so growth and drift are measurable rather than felt.

Designing Every State: The Scenario Switcher

A feature like this is really a collection of states. An empty account with no budgets yet. A first snapshot. A full quarterly history. A corporation on top of the personal side. Miss one and it shows up later as an awkward moment in front of a client.

So we built a scenario switcher into the prototype: a control to instantly seed any data state. Empty, a single salaried snapshot, four quarters of history, a corporation, or a full history with both. Instead of clicking through capture after capture to reach the state you wanted to evaluate, you jumped straight to it.

This made planning the feature genuinely tractable. Every state could be seen, compared, and signed off on purpose, instead of hoping the edge cases would sort themselves out once it was built.

A Values-Based Budget, Native to Wealthstack

Budgets isn't organized like a generic expense tracker. It's built around a Grow, Give, Live framework, sitting alongside Tax and Debt, so a budget reflects what a household is actually trying to do with its money rather than just where it went.

That framing is what makes the feature feel like Wealthstack rather than a spreadsheet. It connects the monthly cashflow a client feels to the long-term plan the advisor is building, using the patterns, structure, and data the product already has. The capture experience reuses what Wealthstack knows about a household, and the values framework ties budgeting back to goals, insurance, and investments already in the plan.

Because the prototype was fully built out, engineering got more than screens to interpret. They got a working reference for how every state should look and behave, and a defined system to build from. The interactive prototype became the specification.

What Made This Work

Extending the plan, not bolting on a tool. Budgets deepens what Wealthstack already does by connecting monthly cashflow to the long-term plan. The best new features pull a product's pieces closer together rather than adding a disconnected one.

Interactive from the start. A feature with two templates and a history of states can't be judged from static frames. Building it as a working prototype meant decisions were made on how capturing and comparing a real budget actually felt.

A tool for the job: the scenario switcher. Complex features have complex state. Building a switcher to seed every data state turned an overwhelming design problem into a reviewable checklist.

Built to hand off. The prototype plus a defined system gave engineering a resolved, buildable target, so development could start from certainty instead of guesswork.

Budgets Feature / Financial Planning

“Claude one shotted the budgets from Francois' designs”

Wealthstack Budgets is a clear example of prototype-first feature design paired with an AI-ready design system: build the whole experience as a working prototype, design every state deliberately, make it feel native, and hand engineering a resolved direction.

Adding a feature to a product your clients already rely on? Schedule a discovery call and let's prototype it before you build it.