I started building what became Age of Geeks in 2016, back when it was still called Machine Learning India and "community-led growth" wasn't a phrase anyone used yet. There was no playbook to follow. Everything below, I learned by getting it wrong first.
Lesson 1: Growth without structure burns out, including you
Early on, growth felt like the only metric that mattered, so that's what I chased. More members, more posts, more reach. What I didn't have was any structure underneath that growth: no onboarding sequence, no clear sense of what a new member should do once they joined. The community grew, but it grew shapeless, and shapeless growth is exhausting to manage because every new member is starting from zero with no system to catch them.
The fix wasn't slowing down growth. It was building the structure (a clear first action, a clear place to ask questions) before pushing harder on numbers.
Lesson 2: An announcement channel isn't a community
For longer than I'd like to admit, what I was running was closer to a broadcast list than a community: I posted, people read, occasionally someone commented. That's not nothing, but it's not community either. A real community has conversation that happens without you initiating it every time. If every thread starts with your post and nothing continues after your post, you're building an audience, not a community, and audiences don't compound the way communities do.
Lesson 3: The first 100 members set the culture permanently
The tone, the norms, the kind of questions people feel safe asking: all of that gets set by whoever shows up first, and it's far easier to shape at 100 members than to fix at 10,000. I spent a lot of early energy on growth tactics that would have been better spent on curating who those first hundred were and how they treated each other, because that culture became the operating system for everyone who joined after.
Lesson 4: You need a feedback loop before you need scale
It's tempting to think you'll add the systems (feedback channels, moderation structure, content calendars) once you're bigger and it's worth the investment. In practice, retrofitting structure onto an already-large, already-chaotic community is far harder than building it in from the first hundred members. The loop that lets members flag what's not working needs to exist before you have thousands of people whose complaints you can no longer see, let alone act on.
Lesson 5: Consistency beats intensity, every time
A huge push for two weeks followed by silence for a month does less for a community than a modest, boring cadence that never breaks. Members build habits around your community the way they build any habit: through repetition, not intensity. The communities and content systems I've since built for clients like Zuper, Redbelly Network, and Tonomy Foundation all lean on this same principle, a sustainable rhythm that a small team can actually maintain, over a burst that looks impressive for a month and then disappears.
What this taught me about doing this for other people's startups
Every client engagement I've taken on since 2016 carries these five lessons somewhere in it, whether that's building Zuper's customer community, running community for Redbelly Network through a Web3 growth push, or handling marketing for Tonomy Foundation. The specifics change. The underlying pattern doesn't: structure before scale, real conversation over broadcast, and a first hundred members you actually pay attention to.
If you're at the point of building a community from zero and want to skip some of the mistakes I made the first time, book a 15-minute call and we'll talk through what your first hundred should actually look like.
