Does Your Business Really Need a Community?

“We need a community” often means “we want loyalty, peer help, and lower support load” - which is fair - while the proposed solution is “start a Facebook group this week.” Sometimes that works. Often you needed clearer channels, better onboarding, or a CRM, not a membership platform. This post helps you decide whether your business really needs a community before you fund one.

Full operating context: building and running an online community.

Community vs following vs broadcast

Mode	Members do what	You own what
Broadcast (SMS, status, newsletter)	Receive	List / channel
Social following	React in rented feeds	Almost nothing
Support inbox	Talk one-to-one with you	Tickets
Community	Talk to each other + you, persistently	Space + norms (+ hopefully data)

If people never need each other, community software is overhead. For the rented-vs-owned tension, see community vs social media following.

Signals you likely do need a community

Score yes/no:

1. Customers or members already teach each other (WhatsApp chaos is a clue)
2. Peer status matters (alumni, professionals, cooperatives)
3. Repeat participation beats one-off purchases
4. Support questions repeat and peers could answer safely
5. You have (or will fund) moderation hours every week
6. You can name a purpose beyond “engagement”
7. Sensitive topics need roles and privacy, not public comments

Five or more yes: community is a serious candidate. Two or fewer: fix channels and CRM first.

Signals you probably do not (yet)

• You only want to announce sales
• Nobody on the team will moderate after launch week
• Your product is a one-time transaction with no peer overlap
• Leadership wants “virality” without staffing
• You refuse any platform or CM budget (see cost to build an online community)
• Legal / reputation risk is high and you have no playbook

A dead community damages brand more than no community.

East Africa reality checks

WhatsApp groups feel like community because they are familiar. They struggle with search, roles, scale past a few hundred active people, and sensitive SACCO/HR topics. Use them as an on-ramp; do not pretend they are a full strategy if those limits already hurt.

Mobile-first is mandatory. If members will not open a clunky desktop-only portal, your “need” dies at UX.

Trust is the currency. Communities around money, health, or credit need clearer norms than a hobby fandom. Budget governance, not only emojis.

Mini business case (one page)

Write and share with whoever holds the budget:

Section	Prompt
Purpose	Members gather to ____ so that ____
Who	Ideal member profile (not “everyone”)
Alternatives rejected	Why not newsletter / support-only / social ads
Costs	Platform + launch + weekly hours [VERIFY]
Benefits	2–3 measurable or clearly observable outcomes
Owner	Named human, not “marketing”
Kill criteria	What results by day 60 mean we stop or pivot

If you cannot fill kill criteria, you are collecting a hobby.

Decision scorecard

Rate 1–5. Multiply by weight. Thresholds are guides, not law.

Criterion	Weight	Score (1–5)
Peer interaction already happens	5
Clear purpose sentence	5
Staff hours available	5
Budget for 6 months run-rate	4
Differentiated from social following goal	4
Risk manageable with guidelines	4
Mobile access realistic	3

High totals → pilot a small owned space. Mid → pilot with strict kill date. Low → invest in broadcast + support quality first.

Pilot before identity crisis

A sane test:

1. 30–90 days
2. Cap invites (e.g. 50 founding members)
3. Seed useful content
4. One moderator SLA
5. Weekly metrics: posts, replies, unanswered, returning members
6. Decision meeting with the scorecard in hand

Do not rebrand the company around “community-led growth” on day two of an empty forum.

Alternatives that often win first

Need	Try first
Announcements	Newsletter / status / SMS
Lead nurture	CRM + honest follow-up
FAQ load	Searchable help centre
Loyalty	Points / punches / account benefits
Feedback	Structured interviews + surveys

Community can come later when peers are already trying to connect.

Stakeholder conversation script

When someone senior pushes “we need Community with a capital C,” ask:

1. What will members do for each other that staff cannot scale?
2. Who loses a day a week if engagement is low?
3. What does success look like on day 60 - in numbers?
4. What will we stop doing to free moderation time?
5. If this fails, what do we learn without blaming the logo on the tool?

If answers are blurry, schedule discovery - not a platform purchase. Budget reality lives in community build costs; do not approve tools orphaned from hours.

When “yes” still means “not yet”

You might pass the scorecard and still wait because:

• A product launch or AGM already owns the next 60 days of attention
• Moderator candidates are on leave or overloaded
• Payments / legal wrappers for membership are unfinished
• You have not cleaned the member data you would invite

Delaying is cheaper than launching into silence. Put a date on the calendar; do not let “someday community” float forever.

Bottom line

Need community when members need each other and you will staff the space. Skip it when you really needed a channel, a help centre, or a following strategy dressed up as belonging. Cross-check rented vs owned attention in community vs social media following, price the work via community build costs, and keep the operating map in the founder’s guide. Honest “no” beats an empty group with your logo on it.