Many clients, separate books, one place to work

The thing that makes multi-client bookkeeping painful is not the volume. It is that most tools were built for one business, and running twenty through them means twenty logins, twenty billing relationships, and no way to see the whole practice at once.

One book per client, actually separate

Each book is its own ledger on its own machine. Not a tenant row in a shared database with a client_id column — a separate machine, which is a different and stronger claim, and the one that matters when a client asks you what would happen if another client’s data leaked.

Roles that survive a handover

A client can have read access to their own book without touching anyone else’s. An accountant can have export access without edit rights. When a client leaves, they leave with their ledger — it is a git repository and it was always theirs — and you are not the person who has to explain that their history is trapped in a product they no longer pay for.

That last part is worth being blunt about: it makes you easier to leave. It also makes you much easier to hire, and we think that trade is obviously the right way round.

Where the audit trail earns its keep

Every change is a commit with a timestamp and a diff. When a client asks why their software spend jumped in March, the answer is not reconstructed from memory — it is a list of the exact entries, when they were written, and by what.

What it does not do

No payroll, no filing, no practice-management layer — no time tracking, no client billing, no workflow board. Countbean is the ledger and the agent that keeps it. If you need a practice management suite, this sits underneath one rather than replacing it.