Incubator20
Walk into the timed business-strategy simulation knowing the format — and write a 300–450 word plan that shows your thinking at its best.
What it is
Incubator20 is a timed business-strategy simulation. You receive a realistic business scenario, frame the problem, build a plan section by section, and commit a final business plan of 300 to 450 words total. It is a work sample: the output is the kind of strategic writing you would produce in a real role, under real time pressure.
How a session flows
Brief
You read the scenario. The timer has not started yet, so read it properly — most weak plans trace back to a skimmed brief.
Frame
The timer starts. You answer framing questions that force you to define the problem before proposing anything. Your framing answers carry into the next phase.
Build
You draft the plan across structured sections on the plan canvas, with a live word counter against the 450-word ceiling. An AI chat is available inside the session to think out loud with — it is part of the format, not a shortcut.
Commit
You review the full plan and submit. The plan must land between 300 and 450 words to submit; the screen tells you exactly how many words to add or trim. If time expires, you can still submit whatever you have written, as long as it is not empty.
How to approach it
- Spend framing time on framing. A precise definition of the problem makes every later sentence easier and sharper.
- Decide, do not survey. 300–450 words leaves no room for "on the other hand" tours. Pick a direction and argue it.
- Use the structure. The plan sections exist to keep you covering strategy, execution, and risk — write to them rather than around them.
- Budget words like money. Draft tight from the start; cutting 150 words under a timer is harder than writing 350 deliberate ones.
- Leave commit time. Reserve the final minutes for a full read-through. One pass for clarity is worth more than one extra paragraph.
What reviewers look at
Reviewers read your plan as evidence of judgment, not polish:
- Clarity of thought — is the problem defined and the logic traceable?
- Decision quality — did you commit to a direction and justify it with the scenario's facts?
- Prioritization — did you spend your scarce words on what matters most?
- Realism — does the plan respect constraints, or does it assume them away?
Your result becomes a supporting signal on your profile, reviewed by humans alongside everything else — see how results are used.