Endute opens up: 45 guides and a public roadmap

A budgeting app asks for a lot on day one. Connect your bank, it says, before you know whether the thing deserves it. We think trust like that is earned by writing things down: how the product works, why it works that way, what we are building next, and what changed while you were away. This week we shipped the two biggest pieces of that: a Help Centre and a public roadmap.

A Help Centre with the reasoning included

The Help Centre holds 45 guides across twelve categories: getting started, bank connections, transactions, transfers, multi-currency, budgeting, reports, investments and FIRE, debt, the mobile apps, the API, and your account. Every part of Endute is covered. Not just the steps, though the steps are all there, but the reasoning behind them: why imported transactions ask for a minute of your attention, why the cash flow forecast widens the further out it looks, why a transfer between your own accounts should never count as spending.

Two good places to start. Your first week with Endute walks through setup in the order that works best, and why Endute asks you to review transactions makes the case for the product's most deliberate design choice. And if you have ever wondered when your bank data actually refreshes, how bank syncing works finally answers it properly, cooldowns and all.

Why written guides replaced the videos

Some of you will remember our old video guides. Retiring them was not a hard call. A video cannot be checked against the product, and it cannot be patched; the moment a button moves, the recording quietly becomes a small museum. Text can be corrected the same afternoon something changes. The old guide links redirect to the new material, which covers far more ground.

Checked against the source code

Documentation has a well-known failure mode: it describes the product the team remembers building rather than the one that exists. We tried to close that gap the blunt way. Before publishing, every claim in every guide was verified against Endute's source code, down to button labels, default settings and the exact wording of warnings. Writing documentation this way is slower. It is also the only kind we would rely on ourselves.

A roadmap you can push on

The public roadmap shows what we are exploring, what is in build, and what has shipped, in rising order of commitment. Every card takes a vote, up or down, and we read every one. There is a feature request form for the ideas we have not thought of yet.

A roadmap is a promise about attention, not about delivery dates, so you will not find deadlines on it. What you will find is an answer to the question every product this size should be able to answer in public: is anyone still working on this? Yes. Visibly.

The ledger behind both

Behind the roadmap sits What's New, the dated record of everything that changes in Endute, large and small. The roadmap's shipped lane is the curated highlight reel; What's New is the full ledger. Between the three surfaces, there is no longer a version of "what is Endute doing?" that goes unanswered.

None of this is glamorous work. A guide to CSV imports will never trend anywhere, and a card in an exploring lane is not a feature. But a finance app holds your attention in the same place it holds your bank data, and both deserve better than a shrug when you ask how something works. Go read the guides, even the retirement planning one if that feels far away. Then visit the roadmap and tell us what to build next.