The work, written up honestly.
A case study here isn’t a testimonial. It’s the whole record: what was actually happening before, what we built, what the build cost, and what the business can do now that it couldn’t. Client systems appear on this page only once the client has read the write-up and agreed to it — so it opens with a system we built for ourselves, which we can describe down to the last file.
What every write-up here contains
Four parts, in this order, whether the system is ours or a client’s. A write-up missing one of them isn’t published, because the missing one is always the part a reader needed.
| The part | What it answers |
|---|---|
| The situation | What was actually happening before. Who the bottleneck was, and what stopped moving whenever that person got busy. |
| What we built | The components by name, and the tools they run on — usually Claude Code, n8n, or both. |
| The honest cost | What the build took, and what the system asks of the team every week afterwards. No system is free to run; a write-up that implies otherwise is an advertisement. |
| What changed | What the business can do now that it couldn’t. Measured where there’s something to measure, described where there isn’t — and we say which of the two we’re doing. |
One rule sits above the format and outranks it: we never invent a number. If something can’t be measured honestly, it gets described in words and labelled as a description. A percentage nobody can reproduce is worth less than a sentence that’s true, and it costs more when someone checks.
Rather see one of these built on your business?
Tell us what stops moving when you get busy. We’ll tell you what we’d build, what it would take, and whether it’s worth building at all.
Start a Conversation