You own everything. No lock-in. No hype.
Most owners have been burned once, by a vendor who held their systems hostage, or one who oversold what “AI” could really do. So here's the standard I hold myself to, in plain terms, before you ever book a call.
You keep what I build.
The single fastest way to lose an owner's trust is to make them feel rented to. Everything I build to order is yours to keep, run, and walk away with. The monthly Lead System is the one thing that is installed, not sold.
The code is yours
Every automation, workflow, and line of custom code, plus the n8n and Make flows, is handed over. The IP vests to you when you pay for it. The one exception is the monthly Lead System: it is installed and run for a fee, not sold, and it says so on its page.
Your name on what matters
Your domain stays in your name and your data lives in your own tools. I host the sites and apps I build on a Care Plan, and hand the hosting over on request. Nothing important runs on a black box only I can log into.
Documented and trained
You get the runbooks, and your team gets trained to run it. The system never lives only in my head.
No lock-in
End the engagement whenever you like. The code and the runbooks are yours, the hosting transfers on request, and the Care Plans are month to month with thirty days notice. If keeping me on isn't earning its place, you shouldn't be trapped.
Straight about what AI can, and can't, do.
The category is loud with promises that quietly fall apart in production. I'd rather under-claim and over-deliver. Here's how you'll know you're not being sold a wrapper.
Human-in-the-loop by design
No "fully autonomous" promises. AI drafts, routes, and flags, a person stays in control of anything that actually matters.
I name the tools
Claude, OpenAI, n8n, Make, Supabase, Next.js, real, specific, chosen for the job. Not the word "AI" repeated fourteen times.
ROI before you commit
I project the hours and dollars a build should return before you sign anything. If the math doesn't work, I'll tell you it doesn't.
I push back on scope
If something won't pay off, I say so. You're hiring judgement, not a yes-man who builds whatever gets asked.
Careful with what's yours.
Your job data, your customer lists, your numbers, treated the way you'd want them treated.
Least-access by default
I take the minimum access needed to build, and it's revoked the moment the work is done.
Your data stays yours
It lives in your systems. It's never used to train anything, and it's never shared.
Clear retention
Anything I hold during a build is documented and removed on request. You always know where your data sits.
From snapshot to “it runs without me.”
Four steps, and a definition of done you can actually verify.
- 01
30-minute call
A free 30 minutes. We find the constraint costing you the most, no pitch, no homework.
- 02
Day-1 measurement
Before I build anything, we measure the baseline, so the result is provable, not a feeling.
- 03
Built, tested, shipped
The system goes into production on your stack, documented, with your team trained to run it.
- 04
Definition of done
"Done" means it runs without me and the numbers moved. Because the deliverable is software, that's verifiable, not a promise.
See the standard applied to your operation.
No pitch. Thirty minutes on the thing costing you the most, and how I'd build the fix.