Process, stack choices, AI-native workflows, and the trade-offs we make to ship a real MVP in two weeks. No think-pieces, no thought-leadership — just the things we wish someone had told us.
A walk-through of our actual sprint — day by day — from a locked spec on day zero to deploy and handover on day seven. Where AI compresses time, where humans still have to do the work, and the three things that always blow up the timeline if you let them.
Read the post →The pattern we keep seeing in discovery — founders booking a 7-day MVP when a 3-day landing page would tell them more. What our Landing Page & Waitlist sprint actually ships, and when it's the better first move.
The opinionated default that lets us hit day seven without spending half the sprint on infrastructure decisions. And the rare cases we deviate.
Boilerplate, scaffolding, tests, docs: real wins. Architecture, debugging novel state bugs, naming things: still on humans.
What goes into the locked spec, why we charge for discovery, and the questions we always end up asking — even when founders think they've answered them.
The shape of a webhook bug we've seen more than once, what to ship to fix it, and the change we now make to every sprint template so it never happens again.
The five-item checklist we wish every founder had on day zero — and the two items most don't.
Distributed systems for a 7-day spec is almost always a mistake. The shape of "monolith first" we run, and when it bends.
Field notes from inside the sprint — usually short, occasionally long, never thought-leadership. Unsubscribe any time.
