What should version one be?
First user, must-work flow, non-goals, platform and release condition become one written boundary.
Choose a focused two-day review when one launch problem needs a decision. Choose the full audit when scope, platform, release and budget need to be resolved together.
A bounded read for an existing app, MVP, release candidate or development quote. It is designed to answer one question: what is actually stopping the next safe move?
Use the larger audit when several decisions interact and a build quote would otherwise price uncertainty as implementation.
First user, must-work flow, non-goals, platform and release condition become one written boundary.
Release, data, admin, privacy, AI review, support and handoff concerns are ranked before build spend.
A decision memo, MVP boundary, risk plan, recommended route and a quote-ready next step.
Each gate can end the work if the evidence says a larger spend is not justified.
No credentials or customer data in the first message.
The useful core and the hardest unknown are separated.
Proceed only when the next spend has a clear acceptance proof.
No automatic lock-in after either review.
Send the current state. The first reply will recommend the €490 review, full audit, another route or no engagement.