Many companies say they have a community because they have opened a Discord server, accumulated followers, or issued a token.

Those things can assemble people in the same digital space. They do not automatically create relationships, shared identity, or participation.

An audience receives. A customer transacts. A user engages with a product. A community member participates in a group whose value is partly created by other members.

The distinction matters because each group requires a different strategy.

Four groups companies routinely confuse

Audience: People who pay attention to the company or its ideas. The primary value flows from the company to the individual.

Customers or users: People who exchange money, data, or behavior for a product outcome. They may never interact with one another.

Network participants: People whose activity increases the utility of a shared system, such as developers, liquidity providers, creators, or node operators.

Community: People who develop repeated relationships, shared norms, identity, and mutual value around an interest or purpose.

One person can occupy several roles. A developer may use the product, contribute code, answer peer questions, and publicly advocate for the network. But the roles should not be treated as identical.

The peer-value test

Remove the company from the room for one week.

Would members still help one another, exchange knowledge, build things, organize activities, or maintain relationships?

If all activity stops, the company may have an audience or support channel rather than a community. That is not necessarily a failure. A useful customer-support environment can be more valuable than a forced community. The mistake is designing for one group while measuring another.

Community requires a reason to return

People do not repeatedly participate because a brand wants engagement. They return because the group provides a recurring form of value.

That value might be:

  • privileged access to expertise or information;

  • professional identity and status;

  • collaboration with capable peers;

  • influence over a product or network;

  • economic opportunity;

  • learning and skill development;

  • cultural belonging;

  • recognition for meaningful contribution.

The company should be able to complete this sentence:

Members return because they can ______ with people they could not easily ______ elsewhere.

If the answer is "receive our announcements," the company has a distribution channel.

Design participation, not just programming

Events, AMAs, office hours, and announcements are programming. They can create occasions for participation, but only if members have a role beyond attendance.

A healthier participation ladder might include:

  1. Observe public content.

  2. Ask or answer a question.

  3. Attend a working session.

  4. Share an example or resource.

  5. Contribute to a project.

  6. Host a discussion or help another member.

  7. Shape a program, product, or governance decision.

Each step requires a clear invitation. Telling people to "engage" is not community design.

Measure relationships and contribution

Member count is the easiest number to inflate and one of the weakest indicators of community health.

Track instead:

  • the percentage of new members who make a meaningful first contribution;

  • returning active members by cohort;

  • member-to-member replies versus staff-to-member replies;

  • the number of unique contributors;

  • time to first useful response;

  • participation across programs, not only chat volume;

  • contributions that create product, support, knowledge, or distribution value;

  • movement up the participation ladder.

Even Discord's own community guidance emphasizes engagement and retention as indicators of health, not simply server size.

Be willing to say you do not need a community

Some products need excellent onboarding, support, education, and customer communication-not a member-led social system.

Community becomes commercially useful when peer relationships, contribution, identity, or network participation improve the product or purpose. If none of those conditions exists, forcing customers into a chat room creates operational cost without durable value.

The strongest community strategy sometimes begins with intellectual honesty: deciding which group the company actually has and what that group needs.

lowob takeaway: A platform gathers people. A community gives them a reason to matter to one another.

Selected sources: Discord: Understanding Server Insights; a16z crypto: Building an engaged Web3 community