First we sketch. Then we build. Then it gets better.
Every system we’ve built started the same way: a few people around a table, drawing how the work really gets done. Here’s what happens after that, what you get at each step, and what we’ll need from you.
The sketch.
We sit down with you and the person who knows the work best. We follow real examples from start to finish, including the messy ones, and draw the process as it actually runs, not as the manual says it runs.
Then we tell you honestly what we see: build it, wait, or don’t bother. Sometimes the answer is a better spreadsheet, and we’ll say so.
You walk away with
- A drawn map of your process, beginning, messy middle and end
- A first draft of your playbook: the rules, the exceptions, the “except when…”
- A plain recommendation, and a scoped plan if it’s worth building
The build.
We build the first working version from your real work, with your expert checking as we go. It starts with training wheels: it works next to your team, someone reviews every answer, and nothing goes out on its own.
When your team trusts what it produces, you flip the switch. Not before.
You walk away with
- A working system, doing real work
- Your playbook, written down in plain language
- A dashboard of what it did, what it cost, and what it wasn’t sure about
- One switch that puts people back in control at any time
The run.
Real work throws up cases nobody thought of. When your team corrects the system, the correction becomes a new page in the playbook, so it gets sharper instead of repeating itself. We keep watch, tune what drifts, and add to it as your business changes.
You get
- Corrections that stick, with the reason written down
- Alerts when something breaks or starts to drift
- A partner for the next process worth sketching
What we’ll need from you.
Your expert’s time
The person who knows every exception. Mostly early on, for the sketch and the first weeks of the build.
Real examples
The messy ones especially. A system built on tidy examples breaks on the first real Tuesday.
Room to be wrong early
The training-wheels phase is where it learns. Mistakes there are cheap, and they’re the point.
One owner
Someone on your side who decides when the switch goes on, and who we call when something looks off.
A few promises.
- HonestyIf AI isn’t the answer, we’ll tell you before you spend anything on building.
- OwnershipYour playbook and your data are yours. Always.
- ControlNothing reaches your customers on its own until you decide it should.
Do we need to be technical?
No. You need to know your work. We handle the technology, and the playbook is written in plain language so anyone on your team can read and correct it.
Our process is a mess. Is that a problem?
That’s usually why people call. The sketch exists to untangle it, and some of the most valuable rules come from the messiest corners.
Creative work or operations?
Both. A quote and a newsletter each have a tricky middle, so the method doesn’t change. You can see both tracks in the case studies.
How long does it take, and what does it cost?
It depends on the process, which is exactly what the sketch tells us. Every build is scoped after the sketch, so you know the size of it before you commit.
What happens to the people doing the work today?
In our experience they become the system’s editors. The tedious part goes away, and their judgment is what keeps it right.
Bring us the process that never quite runs on its own.
Tell us what comes in, what’s tricky in the middle, and what should come out. We’ll take it from there.