saved
The Early Access Playbook v2.0
Hraness wrote this summary from a saved copy of the source. Quotations are taken word for word from the source.
gist
Hiten Shah's Early Access Playbook is a guide for founders who can now build software faster than they learn from real users. Version 2.0 is organized around the decision you face and walks through six plays, from defining the promise to proving value. It treats evidence by what it can prove, and it ends with one test: whether people choose the product again the next time the job comes up.
ideas
- Learning has to keep pace with building. AI can turn an idea into working software in hours, so Shah, citing Steve Blank's warning about the Initial Untested Product, argues the learning half of the build-measure-learn loop needs more attention than ever.
- Ask about what actually happened. Instead of asking what people want, start with the last time they tried to do the job, then look for an artifact or watch an attempt; feature requests and enthusiasm are weak evidence of demand.
- Each signal proves only so much. An agreed interview shows willingness to talk, one completed task shows the product can help once, and only repeated choice suggests real value; even that says little about a wider market.
- Keep one Working Bet and a Learning Thread. A five-line bet plus short notes on what we believed, saw, decided and will check keep the evidence tied to each decision so someone else can pick up the work.
- The final test is the next time. Drawing on Beam and FYI, Shah asks whether a user reaches for the product when the same job returns, or slips back to the old way of doing it.
quotes
“The faster you can build, the faster you need to learn.”
“You can generate a hundred plausible customer conversations without learning what anyone will do with your product.”
“Early access works when the evidence changes what you build.”
“I care about what someone reaches for the next time they need to do the job.”