You own your data. I own the engines. 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.
Who owns what.
The single fastest way to lose an owner's trust is to be vague about this, so here it is in one line: you own your data, your configuration and everything the system produces, with a perpetual licence to your instance; I own the engines and the parts that aren't specific to you. Partners hold a resale licence.
What's yours
Your data, your configuration and everything the system produces: every lead, record, draft, report and decision. You hold a perpetual licence to your instance, and your data exports at any time in a format another tool can read.
What's mine
The engines, and the parts that aren't specific to you. That is what lets a product be priced monthly and improved for everyone on it, and what Run and Evolve keeps working. Clients who signed before October 2026 keep the terms they signed: the code and the documentation were handed over.
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 for your instance, and your team gets trained to run it. Nothing you need day to day lives only in my head.
No lock-in
Every plan has a first run long enough to judge it, three months for the products and the Care Plans, six for Run and Evolve, and then it is month to month. Your data and configuration leave with you and the hosting transfers on request. 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.