Built in less time than the requirements doc.

What changed

For most of my career, the bottleneck on any idea was the distance between "we should build this" and "someone is using this." Requirements, estimates, sprints, handoffs. AI development collapsed that distance. Now the bottleneck is knowing what to build and whether it's right — which is exactly where founders and operators have the advantage.

Things I've actually shipped this way

• A curation pipeline that discovers, scores, and imports outdoor experiences into a live marketplace — with a human review UI and scheduled daily runs.
• An automated video studio — drop raw footage in a folder, get silence-trimmed, transcribed, publishable clips out.
• Data quality radar — checks that catch dead listings and missing availability across thousands of marketplace items before customers do.
• Landing pages and prototypes — including the first version of this site, built and deployed in an afternoon.

How I keep it honest

"Vibe coding" doesn't mean shipping slop. The vibe is speed; the discipline is verification: real data, real tests against live systems, and a human decision at every consequential step. AI writes most of the code. I own every outcome.

The teams that win won't be the ones with the biggest engineering budgets — they'll be the ones with the shortest path from idea to shipped.

Want this speed applied to your project? I consult at a daily rate — or browse the ideas I'm exploring to see how I think.