Thinking in forecasts

Most budgeting apps are built around a question you can only ask in the past tense: how much did I spend? You log purchases, label them by category, compare to a monthly limit, and at the end of the month you find out whether you stayed inside the lines. The information is real. The problem is timing — you're measuring decisions that were made weeks ago, and there's nothing left to do except feel good or bad about them.

OutBudget starts with a different question: where am I going?

Before a single transaction is logged, you describe what you expect your money to do — not what it has done, but what you expect it to do over the next one to five years. That description becomes the forecast. Transactions come later, not as the point of the exercise, but as the evidence that tests the plan.

Why a long horizon changes behavior

Consider the difference between these two questions:

Did I overspend €300 on dining this month?

If I keep spending €300 above forecast on dining, does it push my house deposit date back — and by how long?

The first question is answerable with any basic tracking app. The second requires a forecast. And the second is the one that changes behavior. When you can see the consequence in real time — the deposit date moves from March 2027 to September 2027 — the overspend has weight that a category bar turning red never quite captures.

This is why OutBudget is built around a multi-year horizon. Most decisions that matter financially don't resolve in a single month. A rent increase that seems manageable today looks different compounded over three years. A planned career break needs to be accounted for years in advance, not the month before it happens. A relocation — new country, new currency, one-off moving costs, a period without income — is a cluster of assumptions that interact with each other across a timeline only a forecast can hold.

Assumptions are the engine

In most budgeting apps, the unit is a category: groceries, dining, transport. You track actual spend against a monthly limit.

In OutBudget, the unit is an assumption: a description of something that is expected to happen. Your salary is an assumption. Your rent is an assumption. The insurance that renews once a year in March is an assumption. Unlike a static category limit, an assumption has a type — it can be fixed, grow at a rate, recur every X months, or spike in a particular season — because real financial life is not static. Salaries get raised. Rents increase on renewal. If a forecast ignores this, it isn't a forecast. It's a snapshot of today projected forward unchanged, which is almost certainly wrong.

Categories still exist in OutBudget — they group assumptions and transactions for analytics. But they are not the engine. The assumptions are.

Variance is feedback, not failure

Once you have a forecast and you're logging real transactions, OutBudget shows you variance: the gap between what you planned and what actually happened.

There's a mental shift required here. Variance is not a report card. It's information. A month where you spent €200 more than planned on travel isn't a moral failing — it's a data point. The question is what it means.

Sometimes variance means you should adjust your behavior: the plan was right, you drifted. Sometimes it means you should update the plan: reality is telling you the assumption was wrong. And sometimes it means nothing — it was a one-off, and next month the line returns to forecast.

OutBudget doesn't tell you which is true. That's a judgment only you can make. What it does is surface the information clearly enough that you can make it.

If you're coming from envelope budgeting

If you've used a zero-based or envelope-style budgeting tool before, this approach will feel different in a specific way.

In envelope budgeting, you allocate income to fixed pots at the start of each month. Every euro gets a job. The budget resets monthly. The question you're answering is: am I living within my means this month?

In OutBudget, there are no pots to fill and no monthly reset. There's a continuous projection of flows over time, and actual transactions are layered on top to show drift. The question you're answering is: am I on track for what I actually want to achieve over the next few years?

These are genuinely different questions. Neither approach is better — they solve different problems. If the problem you're solving is monthly cash discipline, envelope budgeting is a good tool for it. If the problem is multi-year trajectory — knowing whether your current behavior gets you where you want to go — that's what OutBudget is for.

Common questions

What if my forecast numbers are just guesses? They are, at first — and that's fine. The value isn't in the precision of the forecast; it's in the comparison between forecast and actual. Even a rough plan, maintained honestly, tells you more than a perfect one you stopped updating.

I earn in USD and spend in EUR. How does the forecast handle that? Each assumption is in its own currency — your USD salary stays in USD, your EUR rent stays in EUR. The forecast converts to your base currency using the FX rates you set, so you see a consolidated picture without losing the underlying numbers. When the rate moves, you update it and the projection updates automatically.

How long before this actually feels useful? For most users, it clicks after the first full month of real data. Over time, it gains momentum — allowing you to easily spot seasonal variance and unexpected annual spikes, making both your baseline and your projections highly accurate.