Lightening Tech Evidence, not opinion

Content, Social & Communications

Community management

A Discord, WhatsApp group or Circle space run daily rather than left open — rules enforced, questions answered fast, and members talking to each other instead of only to us.

From
$300–$2,500/mo
Typical time
ongoing
Usually bought by
Creators, brands

What this actually solves

There are two reasons a business pays for this, and they lead to different work.

The first is a membership, course or paid group where the community is not a marketing channel but the product itself. If the space goes quiet, people cancel — not because the content got worse but because the reason they were paying was the room, and the room is empty. That owner is not buying engagement. They are buying churn prevention, and they usually know it.

The second is a brand whose customers already talk to each other somewhere and would rather that conversation happened on ground it can see and participate in. What is being bought there is proximity, and it comes with a side effect worth naming — a functioning community answers its own questions. Long-standing members reply to new ones faster and often better than a support queue does, because they have used the product in the same way for longer. That reduces support load, and it is the part of the value most proposals forget to mention.

Both cases fail the same way. Somebody opens a space, posts a welcome message, and treats it as a broadcast channel. Questions arrive and sit unanswered for two days. After a month of that, people stop asking, and a silent community is worse than none — it is a room with the lights on and nobody in it, visible to every prospective member who looks.

What we do, and in what order

  1. Read the archive and write the rules. Everything already posted gets read, which is how we find the questions that keep recurring and the people who are already answering them. Then the rules — short, specific, enforceable, and covering the two things that actually cause trouble — self-promotion and how disagreements are handled. First one to two weeks.
  2. Build the entry path and the pinned layer. A welcome that does something rather than greets — a prompt each new member can answer without effort, an introduction channel, and a pinned FAQ assembled from the recurring questions found in step one. Where the platform allows it, the welcome is automated through Zapier or Make so nobody arrives to silence at midnight. Week two to three.
  3. Run the space daily. Every question answered inside the agreed window, spam and off-topic promotion removed, disputes handled, and good answers from members pinned or moved into the FAQ so the same ground is not covered forty times. Thirty to sixty minutes per working day, ongoing.
  4. Programme the conversation weekly. A question of the week, a poll, a small challenge, or a prompt drawn from something that actually happened in the space — never a generic icebreaker, which reads as filler and gets ignored. Half a day a week.
  5. Report monthly and grow the moderator bench. Active members, new members, questions asked and answered, response times against the agreed window, and the recurring topics list for your product team. Plus the members who have been consistently helping, proposed for moderator status. Half a day a month.

Tools, depending on where the community lives — Discord, Circle, Skool, WhatsApp Business or Facebook Groups, Zapier or Make for the welcome automation, and a running sheet of questions and their canonical answers that becomes the FAQ and survives any change of manager.

What moves the price

The range is $300–$2,500/mo and the arrangement is ongoing, because a community is a habit rather than a launch. Three things decide where in that range a space sits.

Size and message volume. A few hundred members with a handful of posts a day is a different job from several thousand paying members asking questions continuously. The work scales with messages, not with the member count on the badge.

The response window you want. Same-working-day is the standard commitment. A guaranteed short response time, or cover across a timezone where the working day does not overlap with ours, costs more and is priced honestly rather than absorbed and then quietly missed.

Whether events are in scope. Running live sessions, AMAs, office hours or challenges inside the community is its own workload — scheduling, promotion, hosting, follow-up — and it is quoted separately from day-to-day moderation.

What usually goes wrong

Every question gets answered instantly, by us. It looks like excellent service and it kills the thing you are paying for. If the manager always replies within ninety seconds, members learn there is no point answering each other, and within two months the community has become a helpdesk with a chat interface. The working rule is to wait about twenty minutes on anything a member could plausibly answer. If someone does, thank them publicly and add to their answer rather than replacing it. If nobody does, answer it properly.

A dispute gets settled in public. Correcting someone in front of the room feels like enforcement and reads as humiliation, and the people it deters are not the person being corrected — they are the silent majority who now understand what happens if they post something wrong. State the rule publicly and briefly, take the specifics to a direct message. The lurkers are watching how you treat people, and they are most of your membership.

The same question is answered fresh forty times. Nothing gets pinned, no FAQ is built, and the archive is never mined, so every new cohort asks the identical five questions and the manager types the identical five answers. This is the slow leak that makes community management look unaffordable. Every recurring answer belongs in a pinned post, the sheet, or the product's own documentation, and part of the monthly work is moving it there.

See where the site stands before you brief anyone.

If the site is already live, start from what it scores rather than from a guess. The audit reports what it checked, what it found, and — the part most tools leave out — what it could not check, and why.

See the website audit Talk about this work

Questions people ask before they commit.

What does daily actually mean?
A defined window on working days, agreed in writing before we start, during which every new question gets a response and the space is moderated. It is not around-the-clock coverage unless you buy that, and it is not a promise to reply within minutes. The response window is one of the three things that decides where in the range your fee sits.
Our group has gone completely quiet. Can it be restarted?
Usually, but not by posting more. A silent group is almost always a group where questions went unanswered long enough that people stopped asking. The first month is spent answering the backlog, pinning what should have been pinned months ago, and asking a small number of questions that people can answer from their own experience rather than having to research.
Will you use AI to write the replies?
No. This is the one service in this category where we do not. Members read each other's messages, so a reply written by a model is spotted in a room full of people who have been reading your tone for a year, and it costs more trust than the time it saves. We do use AI to analyse the archive — the recurring questions, the repeat complaints, who is already helping others.
What do we get that is not just activity?
A monthly report with the recurring topics in it. Which questions came up repeatedly, which complaints appeared more than once, which features people asked for without filing a support ticket. That document is usually more useful to a product team than anything the support inbox produces, because people say things to peers that they will not put in a ticket.
Can you moderate a group in a language we do not speak?
Ask us before assuming yes. Moderation depends on catching tone, sarcasm and the moment a disagreement turns personal, and that needs someone reading the room properly rather than translating it. Where we cannot do that we will say so rather than take the retainer.
Do you own the community if we stop working together?
No. The server, group and any tools sit on your account and your billing. We hold admin access, not ownership, along with the rules document, the pinned FAQ and the question log. If we part company you remove one account and nothing of yours is stranded.

Often taken together.

Start with the brief, not the invoice.

Send what you are trying to achieve. You get a written scope, a price and a date — or an honest “this is not the right service for that”.

Talk about Community management All Content, Social & Communications services