Accelerator Cohort
A batch going through a programme together: a week-by-week schedule, mentor office hours, peer rooms and demo day.
- 6 categories
- 25 channels
- 7 roles
- Medium
Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.
Server structure
Channels
THE PROGRAMME
- this-week
Sessions, deadlines and reading for this week.
- programme-schedule
The whole cycle, including demo day.
- programme-handbook
What the programme expects and what it provides.
- announcements
Anything the whole batch must read.
- ask-the-programme
Logistics and admin.
SESSIONS
- session-notes
Written after each workshop, so a missed session is not a lost one.
- recordings
One post per session.
- reading-and-resources
What to read before each session.
MENTORS
- mentor-directory
Who is available and what they actually know.
- book-office-hours
Claim a slot here. Opens a ticket.
- mentor-intros
Ask for a warm introduction, in public.
- Office Hours
THE COHORT
- cohort-chat
Founders only. No programme staff.
- peer-help
Faster than a mentor, most weeks.
- brutal-feedback
Pitch practice without staff in the room.
- Peer Room
DEMO DAY
- pitch-drafts
Early versions. Expect changes.
- deck-feedback
Slide by slide.
- practice-signups
Claim a practice slot.
- demo-day-logistics
Times, venue, running order.
- Pitch Practice
AFTER
- alumni
Where the long-term value actually is.
- Main Room
- Breakout One
- Breakout Two
Roles
- Programme DirectorAdministrator
- Programme TeamAdministrator
- Mentor
- Cohort
- Alumni
- Muted
Overview
An accelerator runs on a calendar, and this server is built as one. #this-week is read-only and holds the current week's sessions, deadlines and required reading, which is the channel founders open every morning; #programme-schedule is the whole cycle at a glance so nobody is surprised by demo day. Sessions holds #session-notes, written after each workshop so a founder who was on a customer call can catch up, #recordings, and #ask-the-programme for logistics. Mentors is the part that decides whether a cohort gets value: #mentor-directory lists who is available and what they actually know, #book-office-hours is how a slot is claimed, and #mentor-intros is where a warm introduction is requested in public so the programme team can see who is under-served. The Cohort category is founder-only, without the programme staff, and that is deliberate: #cohort-chat, #peer-help where founders solve each other's problems faster than any mentor, and #brutal-feedback for pitch practice that would be uncomfortable in front of staff. Demo Day gets its own run-up: #pitch-drafts, #deck-feedback, #practice-signups and #demo-day-logistics. Alumni keeps the batch connected after the programme ends, which is where most of an accelerator's long-term value actually sits. Voice has a Main Room, two breakout rooms and a Pitch Practice room.
When to use it
Cohort programmes leak value in predictable places: the schedule lives in email, mentor office hours are booked by whoever asks the programme manager first, and the batch stops talking the week the programme ends. This layout puts the week in one read-only channel, makes mentor availability and booking public so access is even, gives founders a room without staff in it, and keeps an alumni channel that outlives the cycle.
What makes it different
- One read-only channel holds this week's sessions, deadlines and reading.
- Mentor availability and booking are public, so access is even rather than first-asked.
- The cohort has a room without programme staff, which is where honest peer help happens.
- An alumni channel outlives the cycle, where most of an accelerator's value actually sits.
Recommended Vetox setup
Reminders
Set Reminders from #programme-schedule so session times and deadlines reach founders without the manager chasing.
Tickets
Point Tickets at #book-office-hours so a mentor slot request becomes a tracked thread rather than a direct message.
Auto Roles
Assign the Cohort role on arrival so the founder-only category is populated without a manager acting first.
Embed Messages
Use Embed Messages for #this-week so the current week is edited in place and never has to be scrolled for.
Questions
Why give the cohort a channel with no staff in it?
Because founders will not say certain things in front of the people writing their evaluation or considering a follow-on cheque. The peer channel is where somebody admits the metric is flat, the cofounder relationship is bad, or the pitch is not working, and where another founder who solved that last month replies. Programmes that skip it get a polite cohort and lose most of the peer value they were selling.
Should mentor office hours really be public?
The availability and the booking, yes; the conversation itself, no. Public booking fixes the commonest fairness problem in accelerators, where a handful of confident founders take most of the mentor time and quieter teams take none. It also gives the programme team a visible signal: if a company has booked nothing in three weeks, somebody should ask why.
Common mistakes
- Keeping the schedule in email, where a founder in customer meetings misses the session that mattered.
- Booking mentors through the programme manager, which quietly rewards the most assertive founders.
- Letting the server die on the last day, throwing away the alumni network the programme just built.
Consider instead
- Startup Founders Circle The group is an ongoing peer circle rather than a fixed-length programme with staff and mentors.
- Coding Bootcamp Cohort The cohort is learning a skill on a curriculum rather than building companies.
More in Startups
View allEarly-Stage Startup Team
FeaturedA working server for a startup of three to eight people: async standups, a decision log, roadmap and customer signal.
Indie Hacker Community
FeaturedAn open community of solo builders: what you shipped this week, revenue posted openly, launches and failure notes.
Investor Updates Room
A private room for a company investors: monthly updates, a standing asks channel and questions answered once.
Product Launch War Room
A temporary server for one launch: a go or no-go checklist, per-surface channels and live incident handling.
0.0k
Servers
0+
Commands
0
Users
0
Languages
