None of them knew what they needed.
Every one started as an audit. Some stopped there. The ones that kept going sit right under the audit that started them, so you can follow the whole thing.
The audits
Three questions, one method. What a buyer needs before signing. What an owner needs before building. What the $995 version produces on its own.
A $3M business that looked clean everywhere else
Buyer under LOI. Financials fine, legal fine, CIM fine. We built the report from the broker’s deal file alone. No site visit, no seller involvement.
It found six figures of annual leakage and a contractor network that existed entirely in the departing owner’s head.
“I have no idea what you’d automate for us”
That’s how it started. That’s how most of them start.
A fitness studio with nothing visibly broken and everything slightly heavier than it should be. The biggest finding was an 18,000-contact list nobody had ever used.
This engagement is where the audit came from
Pen, paper, spreadsheets. Working out what to fix and in what order took months of email, and those exchanges became the questions.
So we ran the audit on his day-one answers. Same questions, same order, same reasoning. It just happens on a form in twenty minutes now.
What got built
Only after the audit said so. Two of these trace straight back to an audit you can read above.
Fifty years of file folders to a voice-controlled pipeline
No CRM, no digital forms, no file system. Six workflow stages living in one person’s head and a filing cabinet. Rebuilt in Zoho with Deluge flows off the estimate signature.
It runs through MCP now, so the system can be told in plain English to act on a specific record. Not an agent. A person aiming a tool.
The apps the audit said to build, in the order it said to build them
Two of the eleven findings needed software that didn’t exist for sale. So we built it, plus a migration plan for the rest of the sequence.
OSHA paperwork that stops living in a truck
QR sign-ins, daily forms filled on a phone at the site, incident reports that route themselves instead of surfacing three days later.
Thirteen forms replacing a system that wouldn’t have survived an inspection.
Three of the six things a report can end in.
Each of these started as a finding, not a feature request. What the audit turns up decides which of these you need, and sometimes the answer is to repair what you already own and buy nothing.
Websites
Most business sites are a few pages over a real system. Twenty years of building the system half is why we can tell whether a fix is actually buildable.
Amateur Trapshooting Association
shootata.com. Member portal, scoring system, club and state directories, membership processing, shoot programs and results.
See it →NAPHA
napha.org. Membership, a publication archive, a grant program, and a discount network across a dozen parks.
See it →Church Outlet
Built years before anyone mentioned automation. The same business now runs a Zoho pipeline behind it. The whole arc of this page, in one client.
See it →Built with AI, without the platform tax
onizukastudio.com
Static, fast, no CMS, no platform fee, with a knowledge base underneath. Built the way we’d build yours.
How we build sites →HomeschoolDesk.ai
Pages over a working application. It replaced three apps a family was paying for monthly.
See it →FESible
Built in a week to replace a spreadsheet that couldn’t keep up. 213 line items in three clicks.
See it →Somebody described a symptom. We went looking for the system underneath it.
You don’t need to know what to automate, what to build, or what to call any of it.