/mvp
Build the thing that answers something
Building is what you're here for, and nothing in here is about doing less of it. What changes is what each build is for: shipping something real, and settling a question you couldn't settle on a whiteboard. Same builds, scoped so the answer — whichever way it lands — is worth more than the artifact.
👋 Hey, builder! Got a minute to help us shape our roadmap?
Take builder's survey
Scope the smallest version worth building
The hardest part of an MVP isn't writing code — it's deciding what's actually in scope. The advisor works through your validated hypotheses and target persona to define the tightest version that would prove something real. If a feature doesn't test an assumption, it doesn't belong in v1.
Define winning before you start
An MVP without success criteria is just a product in progress. The advisor sets the specific, measurable signals that would tell you the thing is working — before the first line of code is written. Knowing what success looks like in advance is the only way to know when you've learned enough to move.
From validated plan to running code
Once the design is locked, the advisor scaffolds the codebase — structure, dependencies, boilerplate — matched to your stack, then deploys. The goal isn't to build the product for you. It's to get you past the blank-screen problem so your first commit is meaningful, not ceremonial.
startup superpowers