TThe Chapter Launch Manual

Six weeks is the cliff. A chapter that has not held three sustained gatherings by week six rarely holds a fourth. We have watched this pattern repeat across enough cities now to stop calling it anecdote. Bengaluru, Pune, Indore, Bhubaneswar, Chandigarh, Coimbatore. The chapters that died did so for variations of the same three reasons. The chapters that survived did variations of the same five things. None of it is glamorous. All of it is procedural.

This is the manual we wish every founder had on day zero. It is not a vision document. It is a checklist.

¶The three deaths

Most chapters die from founder fatigue. A single person carries the calendar, the venue, the messaging, the follow-up, and the apology when nine people RSVP and three show. By week four, that person is rationing energy. By week six, they have stopped answering messages. The chapter does not formally end. It just thins out, like a tea stall at 11 pm.

The second death is venue drift. The first three meets happen in three different places because no one has booked anything stable. Members lose the muscle memory of where to go. A community is not just a list of people, it is a recurring spatial habit, and chapters that wander lose that habit fast. We have seen Pune chapters revive after they locked a single coffee shop on FC Road for the second Saturday of every month, no exceptions.

The third death is purpose dilution. A chapter starts as "AI builders in Bhopal" and within four weeks is hosting a generic networking mixer because that is what the most senior member wanted. The chapter loses the people who came for the original promise. It does not gain enough new people fast enough to compensate. Six weeks later, the founder is asking why nobody came.

¶The five survivals

Survivors do five things, and they do them in a specific order.

First, they declare a cadence before they declare anything else. Second Saturday, 10 am, Indiranagar. Or first Wednesday evening, 7 pm, Koregaon Park. The cadence is published before the first event. It does not change for the first six months. Cadence is the load-bearing wall.

Second, they pick a venue with a host. Not a venue you rent. A venue where someone who works there knows your chapter's name. The cafe owner in Bhubaneswar who keeps the back room open for the third Sunday. The co-working space in Tumakuru run by a founder who joined the chapter on day one. A hosted venue costs less goodwill to keep than a rented one, and goodwill is what runs out first.

Third, they install a second-in-command before week three. Not a co-founder with title politics, just one other person whose name is on the calendar invite. This single act cuts founder fatigue by more than half. The bus factor goes from one to two. The chapter stops being a personality and becomes an institution, even if a small one.

Fourth, survivors publish notes. Not minutes. Notes. A short paragraph after each meet, posted to the same channel, naming three things that were discussed and one question left open. This does two things. It tells absent members that the chapter is real and worth coming back to. It tells future members what kind of room they would be walking into. Bareilly's chapter doubled in three months on the strength of public notes alone.

Fifth, survivors run rituals, not events. An event is a one-off with a guest speaker. A ritual is something that happens every time, no matter who is in the room. A two-minute round of introductions where each person says what they shipped this fortnight. A closing question that goes around the circle. A WhatsApp message the day after with the next date already locked. Rituals make the chapter robust to bad weeks. Events make it dependent on good ones.

¶The first six weeks, by week

Week one, send personal invites to thirty people, host a meet of twelve to fifteen, declare the cadence. Week two, send notes, identify the second-in-command, confirm next venue. Week three, run the second meet, add a ritual, invite one outsider from a different professional network. Week four, run a smaller working session of six to eight people focused on actual work, not introductions. Week five, send a one-month note to the whole list with what happened. Week six, run the third full meet, and at the end, ask one member to host the fourth.

If you have done these six things, you have a chapter. If you have skipped two of them, you do not.

¶What to do this week

Open a document and write down your chapter's cadence, venue, and second-in-command. If any of those three are blank, fill them before you do anything else. Then write the calendar invite for your next three meets, all of them, with the same time and place, and send it. The act of declaring three meets at once changes what your chapter is. It stops being a hope. It becomes a schedule. Schedules survive in India. Hopes do not.