
What Incubators Look For in Startup Applications
Written from the evaluator's side of the table: the rubric applications are actually scored against, and the six answers that decide whether you make the shortlist.
If you have applied to incubation programs and been rejected without explanation, it helps to see the process from the other side. Applications are not read as stories. They are scored against a rubric, usually by several people independently, and then compared.
Here is roughly what that rubric contains.
Screening: eligibility and completeness
Before anyone assesses quality, applications are filtered on hard criteria: entity type, incorporation date, sector, geography, stage, and whether the required documents are attached.
A significant share of applications are eliminated here - not for being weak, but for being ineligible or incomplete. Check the criteria against your actual documents before writing anything. Attach what is asked for, in the format asked for.
The six things evaluators score
1. The problem. Is it specific, real and worth solving? Evaluators are looking for evidence you have talked to people who have it. "Small manufacturers lose two days a month reconciling supplier invoices by hand - we interviewed 40 and 31 described the same workflow" carries more weight than any market-size statistic.
2. The solution and its stage. What have you actually built, and where is it? Idea, prototype, pilot, live with paying users. Be accurate. Overstating stage is caught in the interview and destroys credibility across everything else you claimed.
3. The team. Who are you, what have you done, and does your combined skill set cover the work? Evaluators look for domain insight - why you see this problem clearly - and evidence of shipping something before. Gaps are fine if you name them; unacknowledged gaps read as blind spots.
4. Traction. Any evidence that the market has responded. Users, revenue, pilots, letters of intent, waitlist, retention. If you have none, say what you have learned instead and be concrete about it. Nobody expects a pre-seed applicant to have revenue; everyone expects them to have talked to customers.
5. Fit with the program. What do you specifically need from this incubator, and can it provide that? "We need controlled-environment lab access and introductions to agri-input distributors" is a strong answer. "We want mentorship and networking" is the answer everyone gives and tells the evaluator nothing.
6. Coachability and clarity. Partly assessed at interview, but visible in the written application through whether you answered the question asked, whether you were honest about weaknesses, and whether you can explain a complex thing simply.
How the scoring works
At a well-run program, several evaluators score the same application independently against weighted criteria, and the scores are aggregated rather than debated into consensus. Weights differ by program - a deep-tech incubator may weight technical novelty heavily; a market-focused accelerator may weight traction.
Two consequences for applicants.
Consistency beats brilliance. Being solid across all six criteria usually outperforms being exceptional on one and weak on three. An application that scores 4/5 on everything typically beats 5/5 on team and 2/5 elsewhere.
Write for skim-then-read. Evaluators are working through a stack. Front-load each answer with the point, then support it. Do not build to a conclusion in the final sentence.
What actively hurts
Vagueness. "Significant market opportunity", "innovative platform", "revolutionary approach". These appear in every rejected application.
Unsourced numbers. A market size with no citation is assumed to be invented.
Ignoring competitors. Claiming no competition is read as not having looked. Naming three and explaining what you do differently is read as knowing the field.
Answering a different question. Word limits exist because the evaluator has a specific thing to assess. Answer that thing.
Obvious copy-paste. Referencing the wrong program, or writing so generically that it could be any program, is immediately visible.
Before you submit
Have someone outside the company read it cold and tell you, in their own words, what you do and why it matters. Whatever they cannot reproduce, the evaluator will not either.
Then check the boring things: every question answered, every document attached in the requested format, no placeholder text, and a working link to anything you referenced.
For incubation managers reading this
If your selection process is a form feeding a spreadsheet, you are almost certainly losing consistency between evaluators, and you have no defensible record when a rejected applicant or a funder asks how the decision was made.
A weighted rubric with scored options, panel members assigned per program, independent scoring, and aggregated per-question and per-evaluator breakdowns is what makes the outcome comparable across evaluators and across cohorts - and what turns "we selected these six" into something you can actually evidence.
Selection criteria vary by program. Always work from the specific program's published criteria.
Frequently asked questions
- Does traction matter if we are pre-revenue?
- Yes, but traction is not only revenue. Evidence that you have built something, put it in front of real users, and learned from the result all count. A pre-revenue team with fifty structured customer conversations and a working prototype reads far stronger than a pre-revenue team with a polished deck and no contact with the market.
- How much does the idea matter versus the team?
- Most evaluators weight team more heavily, because ideas change during a program and people generally do not. What they look for is domain insight, evidence of shipping, and whether the founders' combined skills cover the actual work. A solo non-technical founder with a purely technical product is the most common structural concern.
- Should we apply if we do not meet every criterion?
- Distinguish hard eligibility from soft preference. Hard criteria - entity type, incorporation age, sector, geography - will disqualify you at screening regardless of quality, so do not spend the time. Soft preferences are worth a strong application. If you cannot tell which is which, ask the program office.
- Does the same application work for every program?
- No, and reusing one is visible immediately. The core facts stay constant, but the framing should address what each program selects for and what you specifically want from it. Evaluators can tell within a paragraph whether an application was written for them.
