Buy back the hours you lose to repeat work
Lees dit in het NederlandsThis is diagnosis-led automation: I find the work that keeps repeating inside your business, size what it costs you in hours a year, and build one specific fix that keeps running after I hand it over. It is for owners and operators whose team spends every week retyping, waiting, chasing, repeating, checking and reporting the same things.
If you can already name the task that eats your week, start the conversation and I will tell you whether it is worth automating.
Who it is for
Businesses that already run on digital rails, where hours are a visible cost and the owner is reachable. Roughly ten to fifty people, though that is a shape rather than a rule. The work has to repeat: the same task, the same way, many times a week. If a process never repeats, or if off-the-shelf software already solves it well, I will say so on the call instead of selling you a build.
How it works
It starts with a conversation. You send an email, we get on a call, and I go looking for six gaps in how work moves through your business.
- Retyping. Data moved by hand from one system into another.
- Waiting. Work that stalls until a person passes it on.
- Gathering. Chasing information together.
- Repeating. The same mail, the same answer, again and again.
- Checking. Manual checks.
- Reporting. The same list rebuilt every week.
Then we put a number on it. How often it happens, times the minutes it takes, times your hourly rate, times 52 weeks. That number is either the case for building the fix or the reason to leave it alone. I come back with one specific proposal, not a menu.
What you get
A built system that runs without me. Human checkpoints wherever the work needs judgment, logging that fails loud instead of failing quietly, and documentation your team can work from. Built, documented, monitored, handed over.
The specialty is SOP automation. You hand me the written procedure and I turn it into an automation or an agent that carries it out, with a person kept in the loop at the points that need one. The Answer Report runs this way end to end: an audit procedure that executes, reports and re-checks without a person in the delivery path. Where a step needs judgment, the system prepares and a person approves.
What it is not
Not a tool subscription, and not a rebuild of software you already pay for. If an off-the-shelf product solves your problem well, that is my answer. I do not automate work that never repeats, and I do not build anything only I can run. A system you need me for is a system that failed.
Proof
Four builds where the whole point was that they keep running after the person steps away.
- The Answer Report. A deterministic engine that scores a site out of 100, an editorial layer that publishes those scores, and the rails that keep the whole thing running with nobody standing next to it.
- Doomscrollers. A checkout that provisions a member the moment their payment confirms, private links that carry onboarding and every check-in, and a lifecycle of emails that fire off real events.
- Remesa. A reservation platform I designed and built from the ground up for independent restaurants, from the availability engine to the AI briefings.
- The Tea Sack. Real stock sits underneath the whole room, which is why a piece that sells does not quietly disappear.
Frequently asked questions
How do you decide which task to automate first?
By size, not by noise. I look for six gaps in how work moves: retyping, waiting, gathering, repeating, checking and reporting. Then I multiply how often the task happens by the minutes it takes, by your hourly rate, by 52 weeks. The task with the biggest yearly number and the clearest rules goes first.
What is SOP automation?
SOP automation takes a written standard operating procedure and turns it into a system that carries it out. The steps with clear rules become an automation or an agent, the steps that need judgment become human checkpoints, and the whole thing logs what it did, so a failure is loud instead of silent. The procedure stops living in one person's head.
Will I have to replace the software I already use?
Usually not. Most of what I build connects the systems you already pay for and moves the work between them. If an off-the-shelf product already solves your problem well, that is the answer you get from me, and I will not build around it.
What happens after it is built?
You own it and you run it. Every build is handed over documented and monitored, so your team can operate it, change it, and see when something breaks. The measure of a good system here is that it keeps working after I step away.