A small AI workflow studio
One workflow at a time.
Built by hand, then automated.
We start with the interview — ten operators, the workflow that's eating your hours, end to end. Then we run that workflow by hand for two or three weeks, alongside your team, before any code exists, and only then automate.
Keep exploringMethodWorkshop pricingFor plumbersFor electriciansScope my shop
A handwritten clipboard showing seven weekly trade-workflow items, three completed and crossed off, two in flight, two yet to start.
What we are noticing
Most AI agencies sell a tool. We sell the time back first.
We refuse to ship a tool before the workflow has been run by hand against your real jobs for two or three weeks. The manual pass is the proof; automation is the byproduct.
- 10
- operators interviewed per engagement
- 2–3
- weeks of manual delivery before code
- 1
- workflow, end to end — not seven
The method
Four steps, in a fixed order.
We do not start with a demo of a tool you don’t have yet. We start with the workflow you already have and prove, in writing, where the hours go.
- A SaaS dashboard you log into once a week
- A generic AI agent you could subscribe to tomorrow
- A Zapier chain someone on your team built in an afternoon
- STEP 01
Sit in the truck for a morning
We ride along, watch the lead come in, watch the quote go out, watch the change order get lost between two inboxes. The workflow lives on paper, on the whiteboard, in someone’s head. We name it together.
- STEP 02
Run it by hand, alongside your team
For two or three weeks we do it ourselves — the re-quoting, the chasing, the spreadsheet logging, the reminder sends. Same tools, same headaches, real customers.
- STEP 03
Tabulate the time saved, in minutes
By week three we know, to the quarter hour, what the workflow cost before we touched it and what it costs after. That number — not vibes — is what justifies building.
- STEP 04
Only then automate, against a stable baseline
If the number justifies a build, we scope the agent or the Make / n8n flow against the manual pass. If it doesn’t, the engagement still paid for itself in time saved — and we leave you with the receipts.
Workflows we know
The ones that quietly cost you ten hours a week.
We don’t do everything. We pick one per engagement — and we have opinions about which ones are worth the time. Bring us your own; we’ll start from the same list.
- ARe-quoting inbound leads within the hourafter the measure
- BChasing change orders through the officerough-in to invoice
- CLogging completed jobs to the bookkeeper’s spreadsheetFriday evening
- DSending appointment reminders the morning of the visitbefore the truck rolls
- EFollowing up on outstanding invoices at 30 / 60 / 90 dayswithout nagging
- FReply-drafting the shared inbox after hoursin your voice, signed off
For your trade
Built for trades where one evening a week is the whole margin.
Most AI tools are built for venture-backed offices with standing desks. These are built for shop owners who run jobs from a paper notepad or a shared inbox, and whose CRM gets updated when they remember.
You are the quoting engine, the dispatcher, and the after-hours reply crew.
Two of you spend Monday mornings rebuilding what Friday’s jobs forgot.
You have a CRM. The CRM has stale leads and the owner still keeps the list in his head.
Workshop pricing
A fixed fee. Then a small retainer once it runs.
We split the cost into two halves so neither side is paying for a bet. The first half is for time you’ll get back before any code exists. The second half is for the automation, sized to what it actually carries.
Final numbers depend on the workflow. We scope after the workshop, not before.
Week 1
Workshop & ride-along
We interview the people who actually run the workflow. Fixed scope; quoted after this week.
Weeks 2–3
Manual delivery, audited
We do the workflow by hand, alongside your team, and tabulate the time saved in minutes.
Week 4
The decision point
We present the numbers. If they’re worth automating, you pay the build. If not, we keep what we proved.
After the build
Small monthly retainer
The agent or flow runs on a retainer sized to its load and to the people on your team who maintain it.
First-10 pilot
We are picking the first ten shops.
One workshop, the workflow you name, the manual pass, then the build. The first ten get the fixed engagement fee at the rate we quoted before the books closed — and a direct line to whoever is in your truck that week.
- Five weeks, two halves: weeks one to four are fixed; the build is only after the manual pass proves it.
- One workflow per shop. We will tell you, by week three, whether yours is the one we would pick.
- Reply within two business days, in your voice, with a real shop-visit window.
Questions
The ones we get, in plain English.
If yours isn’t on the list, ask us directly — we answer on email, not through a form.
Bring us the workflow
The one that costs you the most hours. We will do it by hand first.
A thirty-second form is enough to start. We will tell you within two business days whether it is the workflow we would pick.