Austin, Texas
You're the integration layer between five systems and six people.
I build custom internal operating systems for small businesses — the tools that take coordination work off the person currently doing it in their head.
Six years in operations before this, two of them running a dealership parts department. I architect the system and direct AI coding agents to build it, which is why it ships in weeks instead of a quarter.
01 — The problem
Where the week actually goes
None of this is a people problem. Nobody's slacking. It's that the work is manual, and manual work fails quietly. The examples are a parts department, because that's where I did this job by hand for two years — yours might be a clinic, a studio, a shop, or an events business. The shape is the same.
Reconciliation that waits for month end
Invoices get matched against receiving by eye, one line at a time. The mismatch that happened on the 3rd doesn't surface until the 30th — twelve steps removed from whatever caused it.
Orders chased by hand
Someone has to remember which vendor hasn't confirmed, which backorder moved, and which part was promised for a job that's already on the lift.
Follow-up that depends on memory
Declined work, open repair orders, and callbacks live in somebody's head or a sticky note. The ones that get followed up are the ones somebody happened to remember.
The same data, three times
It goes into the DMS, then the vendor portal, then a spreadsheet built by an employee who left in 2019. Three chances to fat-finger a number nobody catches until close.
02 — What I build
Not chatbots. Not an AI strategy deck.
Specific automations that remove specific hours from specific jobs.
- Invoice & inventory reconciliation
- The system reads the invoice, compares it against what was actually received, and flags only the lines that disagree. Your team reviews exceptions instead of reviewing everything.
- Vendor & purchase order tracking
- Open orders track themselves. Missing confirmations, late backorders, and price changes surface on their own instead of when someone thinks to check.
- Repair order & customer follow-up
- Declined work, service reminders, and status updates go out on schedule without anyone remembering. Declined jobs stop evaporating.
- Month-end reporting
- The numbers you rebuild by hand every month get assembled before you sit down. You review a report instead of constructing one.
Built on Zapier, self-hosted n8n, and Claude. Every engagement starts by watching the actual workflow — not by picking a tool.
03 — Why me
You won't explain your operation three times.
Off-the-shelf software makes you fit its idea of your business. Custom development has historically meant a quarter of discovery and a price that only makes sense above a certain size — which is why small operations end up running on a person instead of a system.
I architect the system and direct AI coding agents to build it. That collapses the timeline enough that a genuinely custom internal tool becomes worth building for an operation with fifteen people instead of five hundred.
And I spent six years in operations, two of them running a parts department. I know which "small" manual step is quietly costing a day a week, because I was the one doing it.
Most technical consultants have never run an operation. I did this job by hand before I automated it.
Doing something twelve times a week that a machine should do once?
Twenty minutes, no pitch. Tell me what the work looks like and I'll tell you straight whether it's worth automating — including when the answer is no.