Community Before a Home

Most community advice starts from a place of assumed infrastructure. Build your Slack, grow your newsletter, launch your forum, and the people will come.

None of that helps before the infrastructure exists, when you have no owned platform, no audience, and no brand recognition, just a cause you believe in and a set of spaces you don't control.

I have spent the last few years figuring out what community building looks like under those conditions, and I am applying the same principles again while building community presence for IOMETE, a data lakehouse platform, in a technical space dominated by companies with far larger marketing budgets.

Earning trust in a community that doesn't know you exist

In 2021 I became lead organizer of hackCBS, a student-run hackathon at a college in Delhi. We had an existing reputation and sponsor relationships, but the edition we were planning was the first one after COVID and everything about the context had changed. Developers were hungry to get back in person, and that was the tailwind. Giving 500 of them a reason to show up at our event specifically was a separate problem.

The developer community we wanted to reach was already gathered in Discord servers, college tech clubs, and LinkedIn groups that had nothing to do with us. Rather than waiting for them to come to us, we went to where they already were.

In practice that meant physically showing up at other hackathons as participants, joining established developer servers and spending weeks answering questions and contributing to conversations before mentioning hackCBS once. We'd reach out individually to developers who had won competitions, or spoken at events, and ask what they wished hackathons did better, with no pitch attached. We also reached out to micro-influencers who were still building their own brands and were willing to share information with their communities for free. We went to colleges and distributed pamphlets. We did the unglamorous work because there was no shortcut to it.

The relationships came before the ask. When we did eventually invite people, the response was warmer than a cold invitation would have produced, because we had already demonstrated we were worth paying attention to. hackCBS became one of India's largest student-run hackathons and made a case for why it was the first MLH Member hackathon in the Asia Pacific region. The platform came after the community work.

Building community when people are suspicious of you

I then moved into Web3 community building at HackQuest and the TON Foundation. At hackCBS the community was neutral; they had no reason to distrust us. In Web3, the communities I needed to reach had spent years being oversold and underdelivered. Skepticism was a survival instinct.

What worked at hackCBS, showing up consistently and being useful, was still necessary but no longer sufficient. In Web3 you also had to survive the interrogation that began the moment anyone realized you were affiliated with a project. Every claim got pressure-tested and every piece of content picked apart. The community had a forensic eye for inauthenticity that most community people are unprepared for.

This forced me to develop a much sharper instinct for the difference between content that serves the community and content that serves the product. In a skeptical community that line is visible, and people will call you out the moment you cross it. The TON events that built the most lasting engagement were the ones where we spent most of the time teaching something useful, TACT fundamentals, wallet architecture, or how to take an idea and build a project on TON. We let the platform speak for itself once trust was already in the room.

Alongside the events, I ran weekly online coding challenges, shipped regular developer content on X, compiled resource documents and shared them across channels, and ran meme contests and discussions on Telegram. These all helped to keep the community engaged between the bigger moments. The goal was to be present wherever the community actually lived instead of chasing impressions.

In a neutral community you earn trust by showing up. In a skeptical community you also have to demonstrate that you are there for them.

A framework for community building without a home base

Across these experiences a few principles held true regardless of context.

• ‍Contribution earns access. The instinct when you need community is to create it, to build the platform and expect people to arrive. In practice, access to the right people comes from demonstrating value in their spaces first. The platform, if it ever gets built, is something you graduate to once you have done enough of that work to have an audience worth inviting.
• Content is your community when you don't have a platform. Every article, comment, and talk does the connective work that a Slack or forum would normally do, creating a recurring reason for people with shared interests to gather around something. The content that works takes a real problem seriously, and it is rarely the content most obviously about your product. People follow ideas before they follow products.
• Other people's communities are your research lab. Being forced to show up in spaces you don't own teaches you things about your audience that no internal research surfaces as clearly. You hear how practitioners actually talk about their problems. You get the frustrated, specific, unfiltered language that no user interview captures. That vocabulary is worth more than most positioning documents.
• Owned communities need a reason to exist on arrival. Launched too early, they become ghost towns that do more harm than no community at all. The energy spent moderating an empty forum is better spent deepening your presence in communities that are already alive.

The signals that tell you it's time to build your own

Most advice on this topic says to build "when you have enough of an audience," which only restates the question. The signals worth watching are more specific:

• - The same questions appearing repeatedly across platforms
• - People finding you through different channels wanting to connect with each other, not just with you
• - Conversations that start in a Reddit thread or a LinkedIn comment, that strain for somewhere to continue.

The common thread in all of this is pull: people actively looking for a place to gather that doesn't exist yet, as opposed to a team deciding a community would be good for growth. That gap, when you can feel it rather than project it, is when an owned platform earns its existence. There is also a readiness check on your side: whether you understand your audience well enough to design an experience they will find valuable, and whether you have the content, programming, or draw to make the space feel alive from day one.

An owned community is a promise to your members that the space will be worth their time, and you should only make that promise when you are confident you can keep it.

The home base is not where community building starts. It is where it graduates to, once you have done enough of the real work elsewhere to deserve one.