Accelerator application form
An accelerator application needs the problem, the solution, traction, the team and why now, asked so that founders answer with specifics. This template asks each once, follows up on vague answers, and scores every startup on the same weighted criteria.
10 questions · about 10 min · edit anything after
Updated · by Ansorjon Juraev, founder
The questions, and why they're asked
In this order: the name first, the substance next, contact details and links last.
- 1
Full name
In the chat: “First, what's your name?”
Asked first and alone, so the chat can greet people properly before anything else.
- 2
Company name
In the chat: “What's the company called?”
Short, so the conversation starts easily.
- 3
What problem are you solving, and for whom?
In the chat: “What problem are you solving, and who has it?”
The core of every application. The chat pushes once for a specific customer.
- 4
What have you built so far?
In the chat: “What have you built so far, and how do people use it?”
Separates ideas from products.
- 5
Traction
In the chat: “What traction do you have? Users, revenue, pilots, waitlist: real numbers help.”
Asked as numbers, so applications are comparable.
- 6
Team
In the chat: “Who's on the founding team, and why are you the ones to build this?”
Founder–market fit matters most at this stage.
- 7
Stage
In the chat: “Which stage are you at?”
A tap, for filtering.
Options: Idea · Prototype · Launched, pre-revenue · Revenue
- 8
Website or deckoptional
In the chat: “A link to your website or deck?”
Optional, near the end.
- 9
LinkedIn profileoptional
In the chat: “And your LinkedIn, if you'd like to share it?”
Optional, so nobody is blocked by not having one.
- 10
Email address
In the chat: “What's the best email to reach you?”
Asked near the end, once people are invested. The chat confirms it and catches typos like gmial.com.
Scoring rubric
Each response is scored once on these, with a reason for every score. The weights set the total; you can change them.
| Criterion | What scores well | Weight |
|---|---|---|
| Problem | A specific, painful problem for a clearly defined customer. | 25% |
| Traction | Real usage or revenue, and its direction. | 30% |
| Team | Founders who fit the problem and can build the product. | 30% |
| Market | Room to grow into a large business. | 15% |
Scores are advice for the people deciding. Nobody is accepted or rejected automatically.
Common mistakes
- Asking thirty questions because the last cohort's form had them. Every extra question costs you founders.
- Asking for traction in prose. Ask for numbers and the chat will follow up until it gets them.
A good answer and a weak one
For “What traction do you have? Users, revenue, pilots, waitlist: real numbers help.”
Good
“Three paying clinics at €400 a month since June, two more piloting. 60% of patients book through us rather than by phone.”
Weak
“Strong interest from many potential customers.”
No numbers. The chat asks for one concrete figure before moving on.