Community platforms

What this category covers

Places where your members talk to each other rather than only to you: forums, member spaces, course communities and the paid variants of all three. Products here differ less in features than in what kind of gathering they are shaped for.

Internal team chat belongs in team communication. Support queues where customers talk to staff sit in customer support. Courses with a discussion area attached are in learning and LMS.

Structure decides the culture

The shape of a space changes how people behave in it.

Forum-shaped products organise around topics that stay findable for years, which suits questions, answers and anything worth a search result. Chat-shaped products organise around the present moment, which suits energy and loses history. Feed-shaped products favour announcements and light reactions over discussion.

Pick the shape from what you want members to do. A support-flavoured community that runs on a chat product answers the same question forty times, because nothing written yesterday can be found today.

Many products now blend all three. Check which one the default view actually is, since that is what most members will ever see.

Ownership, reach and the case for your own space

Running a community on a social network is cheap and rented.

Reach depends on decisions nobody explains, the member list is not exportable, and the archive belongs to somebody else. Your own platform starts slower, keeps the search traffic, owns the mailing list and lets you write to members without an algorithm in the way.

The honest answer for most organisations is both: a public presence where people already are, and a home where the durable material lives. What matters is knowing which one you can afford to lose.

Moderation is the operating cost

Every community becomes a moderation problem at some size, and the tools decide how expensive that is.

• Member states covering approval, restriction, suspension and removal.
• Content controls for reporting, queues, keyword filters and rate limits on new accounts.
• Roles so trusted members can act without being handed the keys to everything.
• Audit trails showing who removed what, because moderation disputes are inevitable.
• Spam defence, which is the daily work once the space is public and indexed.

Ask what a moderator’s day looks like inside the product, not what the settings page contains. Ten minutes of watching someone clear a queue tells you more than the feature comparison.

Getting the first hundred members to stay

New spaces fail from emptiness far more often than from missing features.

Onboarding decides most of it. A member who arrives, sees nothing addressed to them and leaves does not come back. Look for tools that route newcomers to an introduction, surface unanswered questions, and let you send a sequence of messages in the first fortnight.

Notification quality is the other half. Too little contact and members forget the space exists. Too much and they mute it, which is the same outcome with extra steps.

Whoever runs the community needs a rhythm: something regular that members can rely on, and a rule that no question stays unanswered overnight. Software supports that habit and never replaces it.

Money, membership and what plans meter

Pricing here runs by members, by staff seats, by a percentage of paid memberships, or a flat fee per space. Percentage models deserve a spreadsheet before signing, because the cost rises exactly as fast as the revenue does.

If you charge for access, check the whole payment path: supported methods, payouts to your country, tax handling, and what happens to a member when their card fails. Failed renewals are where paid communities lose people without noticing, and the wider pattern of quiet meters is set out in what pricing pages hide.

Before committing, export a test space. If the content and member list come out as files you can read, the platform is a choice rather than a cage.

The first ninety days

New communities are fragile in a predictable way, and the early weeks decide whether one survives.

Seed it before opening. Twenty or thirty conversations already in place means an arriving member sees a room rather than an empty hall, and nothing depresses signups faster than a space with two posts in it.

Invite people individually rather than announcing broadly. A community grows from a core who feel some responsibility for it, and that core is built by asking specific people to take part.

Answer everything, quickly, for the first month. Silence teaches members that posting is pointless, and that lesson is difficult to reverse.

Then hand parts of it over. A community where only staff reply is a support channel, and the transition to members answering each other is what makes it worth running at all.