Milestone map
Milestone map
3 milestones
Pick accelerators and write the application
2–4 weeks
Pick 3–5 accelerators that genuinely fit your stage and domain. Write the full application for at least one. Strong applications are clear on what you build and your real traction. They also say why this team. 'Why this team' means earned insight, not credentials. Writing it forces precision, even if you're not accepted.
Proof required
List 3–5 target accelerators, each with one sentence on why it fits now. Share your full draft answers for at least one application, not a summary. Any traction numbers must be real.
What gets checked
- Each accelerator has a specific fit reason. 'It's a good accelerator' doesn't count.
- The draft answers every required question.
- Traction numbers are real and match the financial evidence available.
Common mistakes
- Choosing by prestige, not fit. Programmes that don't fund your stage waste a cycle.
- Writing a summary instead of the actual answers.
- Answering 'why this team' with CVs. Insight earned from customers or the domain is stronger.
Powstik Guide
A shortlist of three to five programmes and one full application.
Steps
- Check each programme's stage and focus.
- Write one line on why each fits now.
- Draft every answer for one application.
- Get a founder to read it.
Template
| Programme | Why it fits now | Deadline | |-----------|-----------------|----------| Application draft attached ☐ Reviewer feedback:
What gets sent back
- Programmes that don't fit your stage.
- Incomplete application.
- No reasons given.
Resources
Foundationstart here
Arena
What a verifier looks for
- Ask whether they've spoken to founders from each programme. Informed targeting is more credible.
- Traction claims must match a payment processor or equivalent evidence.
- Ask what they know about the customer that only doing the work taught them.
You'll sign in first, then come straight back here.
Submit applications and attend interviews
4–8 weeks (applications submitted + interview timeline)
Submit to your target programmes and aim for at least one interview. Most applicants aren't interviewed, so an invitation shows the application worked. Interviews stress-test how well you understand your own business. Write a reflection: what you were asked, how you answered, and what you'd change.
Proof required
Show submission confirmations for at least 2 programmes. For one interview, name 3 questions and how you answered each. Name one answer you'd now give differently. With no interview, write why you think that was, using any feedback.
What gets checked
- Submission confirmed for at least 2 programmes.
- Questions are recorded as asked, not 'they asked about traction'.
- The changed answer is specific, like using real retention data instead of a description.
Common mistakes
- No invitation. It's common; the written hypothesis is still valuable.
- Reporting the outcome instead of the content. The questions and answers are the data.
- Applying to only one programme. Low acceptance rates make that risky.
Powstik Guide
Two or more submissions and notes from an interview.
Steps
- Submit to at least two programmes.
- Save each confirmation.
- Rehearse short answers for interviews.
- Write down three questions you were asked.
Template
| Programme | Submitted | Interview? | |-----------|-----------|------------| Interview questions and my answers: 1. 2. 3.
What gets sent back
- Fewer than two submissions.
- No confirmations.
- No interview notes if interviewed.
Resources
Foundationstart here
What a verifier looks for
- Confirmations must show the programme name and a date in the current cycle.
- Specific questions suggest the reflection was written close to the interview.
- The 'answer differently' section is the strongest evidence of real learning.
You'll sign in first, then come straight back here.
Receive an offer and decide
2–4 weeks (offer → decision)
Receive an offer from at least one accelerator and decide whether to take it. Accepting isn't automatically right. Weigh dilution, time commitment and programme fit against what your business needs now. Document the decision and your reasons.
Proof required
Share the offer email with the programme name visible; equity terms can be redacted. State whether you accepted or declined. Write 150 words on what drove the decision, including anything that made you hesitate.
What gets checked
- An offer is shown. An interview invitation isn't an offer.
- The reasons are specific. 'It was a great opportunity' doesn't count.
- At least one hesitation or downside is named, even for an eager yes.
Common mistakes
- No offer. That's legitimate; instead submit a specific analysis of what you'd change next cycle.
- No stated reasons. 'We accepted' isn't a documented decision.
- No tradeoffs named. Every offer involves equity, location or fit tradeoffs.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- The offer must name the programme. A generic 'congratulations' isn't verifiable.
- Ask what equity was offered and whether it affected the decision.
- With no offer, the analysis must say specifically what changes next cycle.
You'll sign in first, then come straight back here.
Part of