Screen · Assess & Decide · Analysis & Finance
Incubator and accelerator eligibility screen
A founder receives a structured eligibility screen showing, criterion by criterion, whether the startup meets a given incubator or accelerator program's stated rules and whether it clears the overall must-have gate.
You receive: A JSON object with a criteria array (each entry: the criterion name, one of the four comparison types, the required flag, the threshold, your applicant value, and a recomputed pass boolean) plus an overall_eligible verdict and a count of failed must-have criteria.
Part of Choose Business Model, Pitch Investors
Example
A sample of what this play produces. Your result is generated for your inputs.
- Program name
- Harborlight Founders Program, Example Batch 04 (fictional program used for illustration)
- Applicant
- STUD
- Failed must have count
- 0
- Overall eligible
- true
- Summary
- STUD clears all five must-have criteria for the Harborlight Founders Program (a fictional example program): pre-seed stage, 0 trailing revenue under the 100,000 cap, 0 prior institutional funding under the 500,000 cap, a founding team of 1 meeting the minimum, and a live working product. The one failed criterion, incorporation, is not a must-have; entity formation is pending and would be closed before program start. Overall verdict: eligible. This screen tests the frozen inputs above; it does not verify the program's real criteria or that the program will admit the applicant.
Criteria
| Name | Type | Required | Expected | Applicant value | Pass | Evidence note |
|---|---|---|---|---|---|---|
| Stage | enum_equals | true | pre-seed | pre-seed | true | STUD is pre-seed, a pre-revenue soft launch. |
| Trailing 12-month revenue (USD) | numeric_max | true | 100000 | 0 | true | Paid fulfillment has not opened, so trailing revenue is 0, under the 100,000 cap. |
| Prior institutional funding raised (USD) | numeric_max | true | 500000 | 0 | true | No institutional capital raised to date; the 1,000,000 target raise is a plan, not prior funding. |
| Founding team size | numeric_min | true | 1 | 1 | true | One founder, Dan Schmitz, meets the program's minimum of 1. |
| Working product live for users | boolean_true | true | true | true | true | stud.com is live as a soft launch: 265 plays across 14 playbooks are browsable and the waitlist is open. |
| Company already incorporated | boolean_true | false | true | false | false | Entity formation is pending. The criterion fails, and because the program marks it nice-to-have (not must-have) it does not block eligibility; incorporation would be completed before signing. |
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: STUD verifies the screen against your frozen inputs: every criterion you list in program_criteria appears exactly once in the deliverable with no extras or duplicates; each criterion's type is one of the exact values numeric_max, numeric_min, enum_equals, boolean_true; each threshold and must-have flag matches your program_criteria line (format: name|type|threshold|must_have, one per line); each applicant_value matches your applicant_profile line (format: name|value, one per line, and every criterion must have a profile value); each pass flag is recomputed by type (numeric_max: value <= threshold, numeric_min: value >= threshold, enum_equals: exact text match, boolean_true: value is true); failed_must_have_count equals the recomputed count of must-have criteria whose pass is false; and overall_eligible is true exactly when that count is zero. That comparison and counting is the only arithmetic checked. STUD does NOT verify that your profile values are true, that you transcribed the program's real criteria correctly, that the program will admit you, or anything about the program itself. The program name and company one-liner fields are context for the operator and are not checked.
Get early access to STUD the day it goes live.