Sit down. Dream. Build. Own.
This is how an engagement actually runs, start to finish. It isn't a framework invented for a pitch deck — it's the shape of real work with real clients, and it's flexible on purpose. Every job is different.
The sit-down.
60% listening, 40% talking. You tell us everything you wish existed — not just the loudest problem, the whole list. We leave with your dreams written down in your words, and you leave with zero obligation.
The quote.
We scope the first phase and put it on one page: price, timeline, what's included — and 14 days of post-launch tweaks, standard. Future ideas get named, not billed. The price is a project, never a subscription.
The build.
AI does the heavy lifting; you get plain, dependable software — web pages, scripts, spreadsheets that work the same way tomorrow as they did today. You see a working demo early and react to something real. Longer builds get a weekly check-in: demo, tweak, next.
You watch it happen on a private build page: every milestone as it moves, the money in plain numbers, and a box for notes. See a sample build page →
The handoff.
"You own it" is a checklist, not a phrase:
- Every account in your name — never ours.
- A register of what exists, where it lives, who has access.
- A plain-English "State of the System" document.
- A real walkthrough — training, not a link dump.
- 14 days of included tweaks after handoff.
Handoff day.
“You own it” is a checklist, not a phrase. Three things move from our side to yours — watch them go.
Nothing left on our side.
The return visit.
Something breaks, or a small fix or tweak comes up? We come back, sort it for a flat $150–250, and then it's done again. Not a retainer. Not a subscription. Not an expectation. A whole new build — another tool, another site, a major addition — is its own quote, not a return visit. Because you own the code, anyone can maintain it — us, another developer, or your own team. Or skip the phone call entirely: an optional Care plan carries hosting, upkeep, and fixes for you, month to month — cancel anytime, everything keeps working.
Held loosely on purpose. A church database, a contractor's estimator, and a shop's website don't run on the same rails — so the cycle bends to the job, not the other way around. The two things that never bend: the consult is free, and you own what we build.
Who maintains this when you’re gone?
—Fair question. It’s what sinks a lot of fast-built software. A tool gets built quick — often with AI — it works, the business starts leaning on it, and then the person who built it moves on. No notes. No logins. Nobody who can safely change a line. The tool didn’t break. It got orphaned.
Given is one person, so every build has to outlive the builder. Here’s how, and all of it is in writing: