The new Decision Engine: how Obolus turns tools into one financial flow

Obolus started as a set of strong standalone tools. That was useful, but it also created friction: users often got a result and then had to decide on their own what to do next.

The new Decision Engine changes that. Instead of showing isolated tools, each relevant page now follows the same product logic:

1. State: your current scenario stays visible.
2. Interpretation: the page tells you what the result actually means.
3. Action: one recommended next step moves the journey forward.

That turns separate calculators into one guided financial system.

Why we introduced it

Most people do not want more dashboards. They want clarity.

If you calculate your net income, the real question is not just "What is my net pay?" The real question is:

• How well does that income hold up in everyday life?
• How much disappears into rent?
• Would the same offer work better in another country?
• What plan can I actually build from it?

The Decision Engine is designed to answer exactly those questions in sequence.

The new flow across the product

The system now follows one clearer path:

Net pay -> Cost of living -> Housing pressure -> Tax comparison -> Budget -> Cockpit -> Invest

Each step has a distinct job:

• TaxApp sets your net baseline.
• Cost of Living shows what remains after rent and everyday costs.
• Rent vs Income isolates housing pressure.
• TaxCompare separates tax effects from day-to-day affordability.
• Budget turns the scenario into a monthly plan.
• Cockpit turns that plan into a living system.

From there, the final step is Invest, where free monthly cash can be tested as a long-term wealth path.

What changed in the interface

The biggest change is not a new feature. It is a new structure.

1. Scenario Bar

The compact scenario bar keeps the current case visible across the flow.

Examples:

• DE · EUR 53,000 -> EUR 33,928 net
• EUR 260 free / month

This makes the active scenario feel continuous instead of reset on every page.

2. Decision Layer

Above the fold, pages now focus on one key takeaway.

Instead of long tool intros or too many competing options, the page shows:

• your result
• what it means
• why it matters now

For example, a cost-of-living page should not just say that one country ranks higher. It should tell you which country gives you the stronger day-to-day buffer and by roughly how much.

3. One Recommended Next Step

This is the core of the new system.

Each step now tries to show one obvious next action instead of a broad menu.

Examples:

• after net pay: check cost of living
• after cost of living: build a financial plan
• after budget: save the plan in the cockpit
• after cockpit: start invest

That makes the product feel guided instead of scattered.

Why this matters

The Decision Engine is a UX change, but it is also a product identity change.

Before, Obolus could feel like:

• a tax calculator
• a comparison tool
• a budgeting app
• an invest simulator

Now it is much closer to one connected system for real financial decisions around work, location, and long-term planning.

That matters especially for:

• relocation decisions
• expat planning
• salary negotiations
• housing trade-offs
• savings and investing follow-through

The product principle behind it

The underlying principle is simple:

State -> interpretation -> next state

That means each page should do more than display data. It should help users decide what to do with that data.

We believe this is the more useful direction for modern finance products. Fewer menus. Fewer dead ends. More momentum.

What comes next

The current rollout introduced the system across the main journey pages. The next steps are about refinement:

• sharper copy per step
• better decision summaries
• more consistent handoff of scenario values
• stronger account-saving moments in Cockpit
• tighter links between Budget and Invest

Conclusion

The new Decision Engine is not a cosmetic layer. It is the connective tissue of the product.

Instead of asking users to navigate a collection of tools, Obolus now does more of the sequencing itself:

calculate the result, interpret it, and move to the next meaningful step.

That is the direction we want to keep building.