October 13, 2026

One Bertha on every desk
We decided to rebuild Bertha as one core for every desktop. What stands today, and what is still to come.
We decided to rebuild Bertha so that one program runs on every desktop a firm uses. This post says what that means for a firm, what is already built, and what is not.
Why
Firms do not all use the same computers. Whichever computers a firm chooses, it should get the same Bertha. The first version of Bertha was written for one operating system only, which is a fine way to learn and a poor way to serve a profession.
The question we asked was whether one app could be native on every desktop system. One codebase compiled for each desktop system: yes. One interface made from each system's own controls: no, nothing does that well. So we chose one core for everything that decides anything, and one interface on top. The look of Bertha is our own drawing already, so little is lost.
What it means in practice
Everything that decides something lives in the core: the reminders, the write-off policy, the approvals, the receipts, the record of every connection. The same core, tested the same way, runs on each system. The interface only shows what the core returns. It never decides.
The earlier version stays as the reference for what Bertha does and how it looks. It gets no new features, and it makes no live changes to anyone's books.
What is built today
All of this runs on demo data, on one development machine:
- the approval and receipt machinery, tested,
- sealed storage for practice data, safe across a crash,
- the front page, in English and Dutch,
- Today, the Inbox of who has sent what, and Clients,
- reminders in the client's own language,
- the write-off policy for open items,
- a record of every connection Bertha may make and every one it refused.
A signed build for the pilot firm's computers is still the biggest unknown, because there the key that protects the data is tied to the developer's signature.
What is next
The order is decided, and it follows the one job we sell, chasing documents. In short: a signed build, people and roles, the firm's client list imported from an export file, sending from the firm's own mailbox, reading arrivals from the mailbox, then a restore drill on a clean machine and a dry run beside the pilot firm's current way of working.
The other desktop systems come after that. We would rather say so than show a screenshot of something that does not run yet.
Phones and tablets are later still, and they hold no client data. They are a window onto the machine in the office.
What this does not change
Client data stays on the firm's own machine. Anything that leaves, such as a mail or a booking, is a proposal that a person approves. Those two rules do not depend on the operating system, which is the other reason to have one core.
Sources. Bertha's rebuild plan, one core for every desktop (build status as of mid-October 2026).