“If your group only interacts when you're on a call together, you don't have a community.”
Why most program communities go quiet
A community gets set up on day one with a welcome post and a rule about introductions. For two weeks it is busy. Then the founder gets busy, the posts stop, and the group becomes a place where call recordings are dropped and nobody replies. Clients notice. The silence between calls is where the drift starts, and the drift is what shows up as a non-renewal three months later.
That figure is from low-ticket memberships, but the shape carries. The first week tells the client whether anyone is there. A high-ticket client who posts an introduction and gets two emoji reactions has learned what the community is worth.
The three jobs a community has to do
Job 1: a weekly check-in every client answers
One post, same day every week, three questions: what did you do, what is the number, what is in the way. Every client answers, and the client success manager follows up with everyone who does not. This is the accountability the client paid for, made visible. It also gives the team a weekly read on every client without a call.
Job 2: wins that get a response the same day
A wins channel that nobody replies to is worse than none. Every win gets a reply from a team member within the day, and the best ones get pulled into the next live call. Wins are also where proof comes from: a client who posts a result is a client who can be asked for a testimonial that week, while the result is fresh.
Job 3: someone who starts conversations
Communities do not run themselves, whatever the platform promises. Someone has to post the check-in, tag the quiet clients, ask a follow-up question under a half-answered post, and connect two clients working on the same thing. In our teams that is the client success manager, and it is written into their week. Accountability is the main reason most clients hire a coach in the first place, and the community is where it either happens daily or does not.
The weekly rhythm
| Day | Post | Owner | Purpose |
|---|---|---|---|
| Monday | Check-in: what, number, obstacle | Client success manager | Every client heard from; quiet ones flagged by Tuesday |
| Tuesday | Follow-ups under every check-in | Client success manager | Nobody posts into silence |
| Call day minus 1 | Agenda and hot seat requests | Client success manager | Clients arrive with a reason to attend |
| Call day | Summary and actions within the hour | Client success manager | The call exists for people who missed it, and the actions are public |
| Thursday | Coach prompt tied to the week's lesson | Coach | One place the coach shows up between calls |
| End of week | Wins thread | Client success manager, coach replies | Results made visible; proof collected |
Who runs it
Not the founder, past 40 or so clients. Not the coach, whose hours are the constraint. The client success manager owns the community as part of owning the client. That is one reason we build the client success team before anything else: every part of delivery between calls, from check-ins to chat support to renewal, runs through the same person, and the community is the room they work in.
What to measure
- Check-in response rate per week. This is the community's attendance number.
- Clients with no post in 14 days. Each one gets a direct message, and the count goes on the weekly cohort review.
- Median time to first team reply on any client post.
- Wins per week per cohort, and how many became a testimonial or case study.
