Assess · Assess & Decide · Analysis & Finance
Startup lifecycle stage exit readiness
The founder gets a structured readiness assessment that scores their startup against the named exit criteria for their current stage (Idea/MVP/Launch/Scale), surfacing which gates are met with evidence and which are blocking, so the stage-transition decision is reasoned rather than an act of faith.
You receive: A JSON object: { stage: enum(idea|mvp|launch|scale), assessedOn: date, gates: [ { gateId, gateName, stageStandard, status: enum(met|partial|not_met), evidenceType: enum(qualitative|quantitative|none), evidenceSummary, blockingReason } ], gatesMet: int, gatesTotal: int, overallVerdict: enum(ready_to_exit|not_ready), blockers: [gateId...] }
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:
- Blockers
- Blocking Reason
- Evidence Summary
- Evidence Type
- Gate Id
- Gate Name
- Gates
- Gates Met
- Gates Total
- Overall Verdict
- Stage
- Stage Standard
- Status
Some fields carry set values, drawn from:
idea, mvp, launch, scale
met, partial, not_met
qualitative, quantitative, none
ready_to_exit, not_ready
yes, true, y
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies that the register is structurally complete, internally consistent (counts match statuses, verdict matches the threshold), and that every claimed gate carries the required evidence field. STUD does NOT judge whether the cited evidence is true, sufficient in the real world, or whether the startup will actually succeed after exiting the stage. The met/not-met status reflects what the performer recorded, not an independent audit of the company.
Get early access to STUD the day it goes live.