Onboarding a Cohort in the First Two Weeks
What to collect, what to set up and what to leave alone. A first fortnight that gets a cohort working instead of sitting through orientation.
The fortnight sets the tone
Most incubation programmes open with an orientation that lasts two days and covers everything. Founders sit through sessions on topics they will not need for four months, meet twenty mentors they will never contact again, and leave with a folder.
Then week three arrives and nobody is quite sure what happens next.
The alternative is a first fortnight built around three jobs: capture the baseline, set up what the startup needs to operate, and get one useful thing done.
Capture the baseline on day one
This is the step most often skipped and the one you cannot recover later.
Record, for every startup entering:
- Stage, from your own list
- Revenue or usage, with the definition attached
- Headcount, with the definition attached
- Funding raised to date, and from whom
- What they say their biggest constraint is
That last one is worth as much as the others combined, and it is worth capturing in the founder's own words. At graduation, comparing what they thought the constraint was with what it turned out to be is the single most interesting thing you will learn about the cohort.
Without a baseline, every outcome claim you make later is an assertion. With one, it is a measurement. It takes twenty minutes per startup and it is the cheapest thing in the programme.
Collect only what you need to operate
There is a strong instinct to gather everything at intake while founders are compliant and enthusiastic. Resist most of it.
Collect now, because you cannot operate without it:
- The signed agreement
- Bank details, if you will disburse anything
- Statutory documents your scheme requires
- Space requirements, if you have space
- A named primary contact and a second contact
Collect later, at the point it is needed:
- Detailed team CVs
- Market research and competitive analysis
- Financial projections
- Anything a mentor might want
The second list is where onboarding bloats. Each item is individually reasonable and collectively they produce a week of paperwork before anyone has done any work.
Set up access properly, once
Whatever system you run on, week one is when to get permissions right, because it is the only time anyone will think about them.
For each startup: who from that team gets access, what can they see of their own record, and who is the primary contact for requests. For your own staff: who runs this programme, who can see funding, who can approve space.
Doing this once at cohort setup takes an hour. Doing it reactively over six months produces an access list nobody can explain, and an access review nobody wants to run.
Do not introduce everyone to everyone
The group mentor introduction is a fixture of incubation programmes and it produces almost nothing. Twenty founders meet twenty mentors, everyone is pleasant, and no relationship forms because no specific problem was in the room.
Better: in week two, when you know what each startup is actually stuck on, introduce two or three mentors properly - with context on both sides about why this pairing. Three real introductions beat forty handshakes, and mentors notice the difference in how their time is used.
Make week one produce one thing
Every founder should finish the first fortnight having completed something concrete they would not have done otherwise. What it is matters less than that it exists:
- A customer interview plan, and two interviews done
- A pricing page, live
- The statutory registration they had been putting off
- A working demo of the one feature that was blocking a conversation
The reason is momentum. A programme that opens with two days of talking and then goes quiet teaches founders that the programme is something that happens to them. One completed thing in week one teaches the opposite, and that expectation holds for months.
Tell them the schedule for the whole year
At onboarding, give the dates:
- When updates are due, all four
- When reviews happen
- When any tranche decisions fall
- When the programme ends, and what graduation means for space
Founders plan around known dates and are ambushed by unknown ones. This is also the moment to say what happens if an update is missed, so it is a stated expectation rather than a later surprise.
A first-fortnight checklist
Before day one
- Agreement signed and stored
- Bank details captured, if disbursing
- Space allocated, if applicable, with deposit terms agreed
- Portal access created for the founding team
Day one
- Baseline recorded: stage, revenue, headcount, funding, constraint
- Half-day orientation, once
- Year schedule handed over
Week one
- Each startup has one concrete thing to complete
- Primary contact confirmed both ways
Week two
- Two or three targeted mentor introductions per startup
- First check-in on the week-one deliverable
- Anything outstanding from onboarding chased and closed
What to leave alone
Some things genuinely should wait. Do not restructure a founder's business model in week one, do not push them to change their pricing before they have talked to a customer, and do not ask them to redo their deck for an event that is nine months away.
The strongest programmes spend the first fortnight learning what each company actually needs and setting up the machinery to help. The weakest spend it demonstrating value.
Frequently asked questions
- What should be collected before day one?
- Only what you need to operate: signed agreement, bank details for any disbursement, statutory documents required by your scheme, and emergency contacts. Everything else can wait. Collecting detailed team CVs and market research before the programme starts is work nobody uses.
- How long should orientation be?
- Half a day, once. Multi-day orientations are mostly information that would be better written down and read when needed. The founders came to work on their company, and week one is when their motivation is highest.
- Should startups be introduced to all mentors at the start?
- No. A group introduction to twenty mentors produces no relationships. Match on the specific problem a founder has in week two, when you know what it is, and introduce two or three people properly.
- What is the most commonly missed onboarding step?
- Recording the entry baseline - stage, revenue, headcount, users - on day one. Without it you cannot show movement at graduation, and reconstructing it later means asking founders to remember where they were a year ago.
