It is almost never the work. It is everything around the work — and that is the whole of what I build.
Click the blocks that are yours. The diagram routes what you hand over — nothing here is claimed, it is counted.
Every line comes from a block you hand over. The page has no opinion until you give it one.
Nothing yet. Every line here comes from a block you hand over — the page has no opinion until you give it one.
The owner is the system. It works until they're out for a week. We start from scratch and build only what earns its place.
The tools exist and don't talk. The same work is re-entered by hand three times. I service, connect and extend what's there rather than replacing it.
A scheduling product for businesses whose storefront is a calendar — and for mobile vendors whose storefront is a pin on a map. Customers find who's open near them; operators go live in one tap.
Built end to end: the availability model, a real coordinate-to-map projection for radius search, calendar file export, and an admin side for live location.
A private operations system where a roster of specialist agents debate a decision, audit their own output and file the result — running across a hosting node and a compute node with local models.
The interesting part isn't the agents, it's the gate: an automated check rejects any figure an agent can't source. That is the difference between an AI system you can act on and one you have to double-check.
Cinematic site
Scroll hero
Shop sites
Product
None of these four is client work, and the page that carries them says so — every figure on it has a source you can check.
A working session and a walkthrough of how the job actually gets done — not how the org chart says it does.
We pick the one block worth automating first. Usually the one someone re-types by hand.
Short cycles, something running you can look at, no six-week silences.
It ships with the documentation and the access. You own it — including the option to never call me again.
Fixed scope, quoted in writing, and the same numbers for everyone. There is no hourly rate running in the background and no minimum term — the work is priced whole, and at the end of it you own the thing.
One week. I sit with the week as it actually runs, find where it leaks, and hand back a written plan with the options costed. If you go ahead with a build, it comes off the price.
The single worst block of the week, automated end to end, documented, and handed over running. Usually the one someone re-types by hand.
The loop, not one piece of it — several connected systems and you trained on all of them. Accounts, code and documentation are yours from the first day, not the last.
Monitoring, fixes, small changes, and a monthly check that it still does what it promised. Cancel any month — nothing here is a contract you have to escape.
The first three engagements signed by then take 20% off the build — that is $3,600 for One Block and $9,600 for The Week. The audit and the monthly stay where they are; they are already at the floor. What I want back is permission to say what I built and who I built it for. I have no case studies yet, and that is worth more to me than the difference.
You work with me directly. There's no account manager, no bench, and nothing gets handed to someone junior after the pitch — which is the honest trade for not being an agency: you get the person who builds it, and one at a time.
One conversation, no deck. If there's nothing worth automating I'll tell you that instead.
Sent. I have your message and will get back to you by phone or email.
That did not go through. Add your name and a phone number or email, or call the number above.
Before you write, look at four systems you can open right now — Lighthouse 89–91 on desktop, 444 pre-rendered frames, two shop sites whose smoke suites pass 68/68 and 48/48, every route of a booking product answering 200. None of the four is client work, and the page that carries them says so.