Skip to content
Matthew Blode
Blog
Product & craft2 min read

We built a community the same way we build products

Luca Bonelli started a WhatsApp group and pulled Ryan Hendler and me in as co-founders. We wanted to share how we actually build day to day, not track AI headlines. It grew to 70 people and thousands of messages. Then Greg Brockman tweeted about us.

Based on the growth of the Vibe Coding Micro Community (VCMC) from 2025-2026.

Community is a product

Most communities die because nobody treats them like one. Spin up a Slack, invite 200 people, watch engagement flatline in two weeks.

VCMC had a constraint instead of a plan. Luca started a WhatsApp group and pulled Ryan and me in. We wanted somewhere to share what actually worked in our 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. Share what works, not what sounds impressive, and the signal stays high.

The cold start problem

Nobody wants to post in an empty room, or be first to share something vulnerable in front of strangers.

So we were the first three users, and we used the product relentlessly. Real builds, real questions, real failures, every day. New people landed in a live conversation between builders who weren't performing, so it felt safe to contribute. One shares a prompt that halved their deploy time, another a Claude Code workflow that broke their staging. Both valuable because both are true.

It grew to 70 people and thousands of messages with no marketing. We capped membership at 100. Every invite was personal: someone we had worked with, met at an event, or whose work we respected.

People in a room

The real test was the meetup. Our "Shipping with AI" event drew around 56 people, over a 50-person cap. Founders, operators, and engineers, most of them already active in the group.

Then Greg Brockman tweeted about us, and the thing clearly had its own gravity.

Meetups are a feature, not the product. The daily chat builds the trust. The event is where it shows up in person.

Engagement loops, not announcements

Communities also die when they turn into announcement channels. Someone posts a link, nobody responds, and soon the only people posting treat the group as distribution.

We designed against that: conversations, not broadcasts. Share a workflow and three people say how they'd do it differently. Hit a wall and two offer to pair within the hour. That loop is the retention mechanic. People come back because their contribution matters and they get something useful back.

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, but it was serious product thinking. Website, visual identity, positioning, all of it existed before the Greg Brockman moment. When attention arrived, we had somewhere to point people, and looked like we'd been doing this for years, not months.

What I learned

Community building is product building with a different input: people and conversations instead of code and design. Same principles. Solve the cold start, design the loop, curate ruthlessly, ship and iterate.

The group chat is still the core product. No algorithms, no feeds, no content strategy. Just builders talking to builders, and that turned out to be enough.