Build · Create · Engineering
MVP scope boundary contract
The founder gets a structured scope contract that locks the MVP boundary in advance, so zero-friction scope creep is gated by a written evidence test for every excluded feature rather than founder enthusiasm.
You receive: A JSON object: { inScope: [{ featureId, statement }], outOfScope: [{ featureId, statement, amendmentEvidence }], amendmentRule: string, signedOff: bool, reviewDate: date }
Part of Choose Business Model
What you receive
The shape of your delivered file. Your result is generated for your inputs.
Your deliverable is a structured document carrying these fields:
- Amendment Evidence
- Amendment Rule
- Feature Id
- In Scope
- Out Of Scope
- Review Date
- Signed Off
- Statement
Some fields carry set values, drawn from:
yes, true, 1
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies the scope contract is structurally complete and self-consistent: both lists meet their minimums, every excluded feature carries an amendment-evidence test, IDs are unique, and nothing is simultaneously in and out of scope. STUD does NOT judge whether the chosen scope is the right MVP, whether the excluded features are correctly excluded, or whether the evidence tests are well-calibrated. It enforces that a written, evidence-gated boundary exists, not that it is strategically correct.
Get early access to STUD the day it goes live.