Community-Led Retention Loop Playbook 2026
Your advocates are already in your data: the accounts and people using the product well past what your successful customers do. This play takes them from the weekly check, looks for a reason to wait, and puts one ask on the account in your CRM: a community invite your team chose to automate, a CSM's personal ask – or no move, with the reason noted.
Your advocates are already in your data: the accounts using the product well past what your successful customers do, and the people inside them doing the most. Keep a list, so reference and community asks don't depend on who happens to come to mind.
This play is a small add-on to the weekly check: the accounts it finds well past the benchmark come here. Each one gets a records check, then one ask on the account in your CRM, or a note on why not now.
Measure it on how many asks get a yes, new community members who post in week one, references and case studies per quarter, and net revenue retention for advocates against a matched group.
How it works11 steps
01SignalTake the accounts and people well past the benchmark
Use the benchmark your weekly check already runs on: 20 or so comparison customers in the segment, 12+ months in, renewed at the same or higher revenue; the median of two or three measures (say, active users as a share of seats and the core action per active user per week); and median ARR. Your CS lead approves it; the benchmark play has the method. Each week, take (defaults; tune them):
- Account well past: at least 1.5× the benchmark on every measure, for eight weeks running. A two-week spike is a project deadline.
- People well past: users in those accounts doing the core action at least twice as often as the median active user in your comparison customers, for eight weeks, with 90+ days on the product.
- Beside them: plan and ARR against peers, and community posts, answers and event visits.
Under about a hundred accounts, do it by hand.
02ScoreCheck the records before asking anyone
- Renewal & open deals: from the CRM. An ask near a renewal or during an expansion deal reads as a trade.
- Tickets, last 30 days: from your help desk, and how they closed.
- Last ask & answer: by default, one ask per person per quarter, to limit how much you ask of them.
- Best-fit ask: is the person already in your community (Common Room shows who is), and are they a deep user of the one use case your prospects ask about most? Name that use case once, with sales.
03DecisionDecide whether this is a good time to ask
Leave it alone (defaults) if the renewal is within 60 days or in procurement, an expansion deal is open, a ticket opened in the last 30 days or closed unhappy, the person was asked in the last 90 days, or the account had a budget or org change. If it also pays below peers, the weekly check's expansion move goes first. Everything else picks an ask.
These checks decide the community invite and the personal ask.
04ActionLeave it alone, and write down why
Set Recommended move to No move, write the reason in one line, and set Review date to when it could change. An ask during a hard week can cost you the advocate. The leave-alone play has more.
05DecisionPick the ask the evidence supports
Defaults, in this order:
- Personal: ARR at or above peers, and the person is a deep user of the use case prospects ask about. A reference or case study, asked by the CSM.
- Community: not yet in your community.
- Neither: already in your community and not a reference fit. No ask from this play this quarter; note why.
Don't forget to ask your customers to leave you a review on public sites.
06ActionSend the community invite your team chose to automate
Customer.io sends it from the community manager's name, personalized to what the person built, and a webhook step writes the send to the contact and account in HubSpot. Add people to the invite list a few a day, so the community manager can keep up with welcomes. Until your team is happy to automate it, the invite goes to the owner as a draft task.
07ActionDraft the personal ask on the record
A task for the CSM with the evidence: what the person built, for how long, and why a prospect would want to hear from them.
08Human stepThe community manager welcomes them in week one
A welcome message, an intro that names what they're good at, and one specific first question to answer. Where there's no community manager, the CSM does it.
09Human stepThe CSM decides and makes the personal ask
The CSM reads the evidence and asks as drafted, changes it, or passes. Before asking, record the success measure and the review date: a reference call held or a case study agreed is progress; a renewal at the same ARR or more is the result.
10ActionTag advocates on the record, and watch for a drop
When someone says yes, set Advocate on the contact. If their account falls below the benchmark, the move lands on the account flagged Advocate and runs as the churn-risk save; if the advocate leaves the company, run the champion departure play. Slack can nudge with the task link; the work happens on the record.
11OutcomeReview what changed, then sharpen the benchmark
Eight weeks after each ask, record three answers: did they act (joined and posted, reference held, case study agreed), is the account still paying the same or more, and what else played a part? Sends are activity, not progress. If nothing moved, change the ask, stop it, or give it time.
Each quarter, compare advocates' NRR with a matched group: same segment and plan, as far past the benchmark at the time of the ask, never asked. Matching makes it fair, but it's a comparison, not proof: customers who became advocates may already have been more likely to stay. Then update which accounts and people this play takes.
Setup and templates
Sources: account measures and each user's core action per week from a weekly saved query in PostHog, Amplitude or Mixpanel; ARR, plan and renewal date from billing or the CRM; tickets from your help desk; community activity from Common Room (connect your Slack, Discord or forum, and your events tool) or your forum. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack on the schedule you set. By hand: one spreadsheet each Monday, a row per person in the accounts past the benchmark, with the account's numbers beside theirs.
Properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account and contact objects:
| Property | Type | Filled by |
|---|---|---|
| Users past the benchmark (company) | Number | Weekly check |
| Recommended move (company) | Dropdown select: Community invite · Personal ask · No move | Weekly check |
| Move reason (company) | Single-line text | Weekly check |
| Success measure (company) | Single-line text | Account owner |
| Review date (company) | Date picker | Weekly check, then account owner |
| Review result (company) | Dropdown select: Said yes and acted · Said yes, not yet · Said no · No reply · Stopped | Account owner |
| Advocate (contact) | Dropdown select: Community · Review · Reference · Case study | Account owner |
| Last ask date (contact) | Date picker | Customer.io webhook step, or account owner |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand. The weekly list is a saved view: Recommended move is known and Review date is this week or overdue. In HubSpot that's two filter groups: Review date is This week, or Review date is before Today. Move reason names the person and why. Each ask creates a task for the owner, "Advocacy: [move] – [name]", with the draft in the body; once your team automates a lane, its sends log as activities instead. Customer.io writes each send to HubSpot with a webhook step that calls HubSpot's API. If the From address is a HubSpot user's, a BCC to your HubSpot logging address also works. HubSpot's Slack app sends task notifications; custom messages need a workflow (Professional or Enterprise).
Apply these checks to marketing emails sent by hand or automatically: permission to send, accurate sender details, required address information, an easy unsubscribe and shared suppression checks. Keep required service notices separate from marketing.
Community invite (automated):
Hi [name] – you've [what they've done, e.g. built 40 reports] in [product] this quarter. People in our community ask how to do exactly that. Would you join and share how you set it up? [link] – [community manager]
Public reviews: don't forget to ask your customers to leave you a review on public sites. One ask, one reminder a week later, then stop.
Hi [name] – would you share an honest review of your experience with [product] on [review site]? It helps other teams decide, good or bad. About ten minutes: [link] – [sender]
Personal ask (CSM):
Hi [name] – the way your team runs [use case] is what prospects ask us about most. Would you be open to [a reference call now and then / a short case study]? Expect [two or three calls a year, scheduled around you]. No is a fine answer.
Get permission before publishing. Check factual claims and don't imply an exceptional result is typical. If you reward participation, disclose that to the prospect hearing the reference or alongside the published case study.
No move: "No move – [reason]. Recheck [date]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark with your team, and you approve it. Every week we check every account in the agreed segment, and the recommended ask and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your team makes every call, including which asks run on their own. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive, and Customer.io for Ortto or Userlist. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan. The play stays the same.
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
Second-Value Seeding Playbook 2026
Your best customers show you which feature comes after the first. This play checks every account against them each week, finds the feature customers like it added next and kept, and puts the move on the account in your CRM: an in-app prompt and a short story, the CSM on the next call – or no move, with the reason noted.
What Changed After the Release Playbook 2026
Every release, price change and campaign is a change worth measuring. This play picks the accounts a change should touch before it ships, tells and guides only them, and four weeks on sorts each one: moved, tried and dropped, no change, or the wrong way. Accounts that moved are left alone; the rest get a move on the CRM record.
Pricing Migration Without the Churn Spike 2026
New pricing is a chance to put every customer on the plan that fits how they already work. This play sorts each account by its usage against the new packaging and your successful customers, then runs the move on the CRM record: a wave notice, an upgrade case, a call first – or no move until renewal, with the reason noted.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.