We built a community the same way we build products

Community is a product

Most communities die because nobody treats them like a product. Someone creates a Slack, invites 200 people, posts a welcome message, watches engagement flatline within two weeks.

VCMC did not start with a plan. Ryan, Luca, and I wanted a place to share what was working in our day-to-day builds. Not AI news. Not fundraising takes. Not AGI timelines. Workflows, prompts, tools, failures, shortcuts. The stuff that saves you three hours on a Tuesday.

That constraint was the product. Share what works, not what sounds impressive. Failures and shortcuts over polished case studies. People kept showing up because the signal stayed high.

The cold start problem

Communities have the worst version of the cold start problem. Nobody wants to post in an empty room. Nobody wants to be first to share something vulnerable in front of strangers.

We were the first three users, and we used the product relentlessly. Posted every day. Real builds, real questions, real failures. We set the tone before anyone else arrived.

New people did not land in a ghost town. They landed in an active conversation between builders who were not performing. That made it safe to contribute. One person shares a prompt that cut their deploy time in half. Another shares a Claude Code workflow that broke their staging. Both valuable because both are true.

The group grew to 70 people and 15,000 messages with no marketing. Every invite was personal. Every new member was someone we had worked with, met at an event, or whose work we respected. Curation is not gatekeeping. It is product design.

Sixty people in a room

First real test was the meetup. We ran a "Shipping with AI" event and 60 people showed up. Startmate, Me&u, Airtree, Archangel VC, OpenAI, Blinq, Buildpass, Cuttable. Pretty sure that was the highest density of top builders in one room in Australian history.

The second meetup sold out at 52 guests with a 16-person waitlist. OpenAI's Scott Falkner spoke and posted about it to 142 likes. Then Greg Brockman tweeted about us. We looked at each other and thought: this thing has its own gravity now.

Events work because the group chat works. Meetups are a feature, not the product. Daily conversation builds the trust. Events are where it compounds in person.

Engagement loops, not announcements

Most communities die when they become announcement channels. Someone posts a link. Nobody responds. Within a month, the only people posting treat the group as a distribution channel.

We designed against that. The group runs on conversations, not broadcasts. Someone shares a workflow, three people respond with how they would do it differently. Someone hits a wall, two people offer to pair on it within an hour. That loop is the retention mechanic.

What keeps people coming back is not content pushed at them. It is the feeling that their contribution matters and they will get something useful back. Contribute, receive value, contribute again.

Build the brand before you need it

We built vcmc.ai with a proper brand page, "in case the New York Times picks up on this group." Sounds like a joke. Serious product thinking. Build the infrastructure before you need it.

Website, visual identity, positioning. All of it existed before the Greg Brockman moment. When attention arrived, we had something to point people to. We looked like we had been doing this for years, not months.

What I learned

Community building is product building with a different input. The raw material is people and conversations instead of code and design. The principles are identical. Solve the cold start. Design the loop. Curate ruthlessly. Ship the MVP and iterate.

The group chat is still the core product. Seventy people sharing how they actually build, every day. No algorithms, no feeds, no content strategy. Just builders talking to builders.

That turned out to be enough.