An independent workshop · est. 2026
Daedulus Labs is where I build the software I wanted to exist and couldn't buy — reporting tools, record-keeping, and the occasional thing made purely because it was interesting.
What this is
I run an accounting practice. Most of the software in that world is either enterprise machinery priced for a hundred-seat finance department, or a spreadsheet somebody's cousin built in 2011 and nobody dares touch. There is a wide gap in the middle, and I kept walking into it.
So this is the bench where the gap gets filled. Things get built here, tested against real work, and only then do they leave. Nothing ships from here because it demos well. It ships because I ran my own work through it and it held.
Some of what's here is professional — a financial reporting package that turns a trial balance into a full statement set. Some of it is not: a garden journal, a family football pool. Those aren't filler. They're where the awkward problems get solved first, on something where being wrong costs nothing.
How it's built
The reporting package reads your trial balance in the browser and makes no network calls at all. Not fewer than the competition — none. That is a property you can check in the page source and confirm in a network tab, rather than a sentence in a privacy policy you have to take on faith.
A cash flow statement that doesn't reconcile to the balance sheet is a rumour. Every statement here carries a check line that proves itself in front of you — and when a mapping is wrong, it shows the difference instead of quietly absorbing it somewhere plausible.
Every decision that isn't obvious is written down beside the code that made it, including the ones that were wrong first. In six months somebody has to change this, and that somebody is almost always me.
In the workshop