Starting a chapter is mostly a project management problem dressed up as a vision problem. Founders think they need a manifesto. They actually need a calendar, a list of names, and the willingness to send fifty WhatsApp messages over thirty days. Here is the day-by-day operating manual we have used to seed chapters in Bengaluru, Hyderabad, Pune, Ahmedabad, Kochi, and most recently Indore.
Week one: the founding eight
Day one through day three, you do nothing visible. You sit down with a notebook and write a list of eighty people in your city who fit a single sentence: builders or operators who are working with AI in their daily job and who would show up to a serious working session. Not influencers. Not people you owe a favour. Not people you want to impress. Builders. From that eighty, you star eight. The starred eight are your founding cohort. They are the people whose presence at the first event will signal to everyone else that this is a real room.
Day four through day seven, you reach out to the starred eight one by one. Not a broadcast message. A specific WhatsApp note to each of them: I am starting a chapter of Bharath.CLUB in Bengaluru. Six tables a year, twelve people each, working sessions on what we are actually building. I want you to be one of the founding eight. First table is in three weeks. Are you in? Six of the eight will say yes. The two who do not, replace from your list of eighty. End of week one, you have a confirmed founding cohort.
Week two: the first event
Day eight through day fourteen is event production. Pick the date. Lock the venue. In most Indian cities, the right venue for a founding table is a private room at a restaurant the founding eight already know. Budget between 1,800 and 3,200 rupees per head depending on city. Send the formal invite to the founding eight, plus four additional invites each of them recommends. You are now looking at a room of twelve, which is the right size for a working table.
The first event is not a launch event. There is no manifesto, no slide deck, no welcome speech beyond ninety seconds. The first event is a structured working table: check-in, theme, deep dive, asks, close. The theme should be the most useful AI-native problem you have heard about in your city in the last month. Do not invent it. Borrow it from a conversation you already had.
Week three: the governance scaffolding
Day fifteen through day twenty-one is where most chapters quietly die because the founder thinks the hard work is done. It is not. After the first event, you need three things in writing: a six-month calendar, a decision-rights document, and a curation policy. The calendar locks the next six dates so people can put them in their diary. The decision-rights document names who decides who gets invited, who decides on themes, and what happens when there is a tie. Even if the answer is you decide, write it down. The curation policy is one paragraph: who fits this room and who does not, in plain language.
Send these three documents to the founding eight for comment. Give them seventy-two hours. Incorporate two pieces of feedback. Publish. This is the moment the chapter becomes a thing that exists outside your head.
Week four: the recurring rhythm
Day twenty-two through day thirty is when you set the cadence. The default rhythm we recommend for a new chapter is one table every six weeks, plus one informal coffee meet between tables. That is roughly nine touchpoints a year, which is enough to build relationships and not so many that people start ghosting. Set up the chapter WhatsApp group, but make it low-traffic by design. The group is for logistics and Asks, not banter. Pin the curation policy. Pin the calendar.
On day thirty, you do a quiet review with your founding eight. Twenty-minute call, four questions: what worked, what did not, who is missing from this room, and what should we keep doing. Write down the answers. Adjust. Send the second invite for the next table. The chapter is now alive.
The three failure modes to avoid
First, do not over-design before you run the first event. Almost every chapter that died in the last twelve months died because the founder spent six weeks designing a logo, a website, and a Notion wiki before they had hosted a single table. The wiki does not matter. The first table matters.
Second, do not let the founding cohort become a permanent inner circle. The founding eight are seed, not gatekeeper. By month six, half the regular attendees should be people the founding eight have not met before.
Third, do not run the chapter alone past day forty-five. Pick one co-host from the founding eight by the second event. Hosting alone is the fastest way to burn out, and burnout is the second most common cause of chapter death.
Pick the city. Pick the date. Today is day one. Send the first message before you close this tab.
Join the conversation
This essay is part of an ongoing community. If it resonated, the next step is to be in the room.
Join Bharath.club → Read more essays