Skills/Community Led Growth/SKILL.md
When the user wants to use community as a business growth engine, implement community-led growth (CLG), or connect community metrics to revenue. Also use when the user mentions 'community-led growth,' 'CLG,' 'community as growth engine,' 'community GTM,' 'community flywheel,' or 'community revenue.' For general community growth, see community-growth. For monetizing the community itself, see community-monetization.
npx skillsauth add studio-self/tribalism community-led-growthInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in community-led growth strategy. Your goal is to help users turn their community into a measurable business growth engine — not a cost center, but a revenue driver that compounds over time.
Check for community context first:
If .claude/community-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
CLG is: Using community as a strategic growth channel that contributes to acquisition, activation, retention, and expansion — with measurable impact.
CLG is not:
The data: Figma attributes 30%+ of new user acquisition to community-created templates and plugins. Notion's community generates 80%+ of templates that drive product adoption. Atlassian's community deflects $20M+/yr in support costs while driving feature adoption. HubSpot community members have 2x higher retention and 1.4x higher expansion revenue. Gainsight community members show 15% lower churn. MongoDB's community-answered questions save ~$15M/yr in support costs. Companies with active CLG motions see 25-40% lower CAC on community-influenced deals (Common Room data).
Members contribute knowledge → Knowledge attracts prospects →
Prospects become customers → Customers join community →
Customers contribute knowledge → (Flywheel accelerates)
Every turn of the flywheel makes the next turn easier. The community becomes a moat that competitors can't replicate because it's built on collective human knowledge and relationships.
Community as discovery channel:
Community as social proof:
Community as try-before-you-buy:
Community accelerates onboarding:
Community creates accountability:
Community increases switching costs (positively):
Community provides ongoing value:
Community drives upsells:
Community identifies expansion opportunities:
Community members become evangelists:
Community + Marketing:
Community + Sales:
Community + Product:
Community + Support:
Track these cohorts separately:
| Cohort | Metric | Comparison | |--------|--------|-----------| | Community members | Conversion rate | vs. non-community visitors | | Community members | Time to first value | vs. non-community users | | Community members | Retention at 90 days | vs. non-community customers | | Community members | LTV | vs. non-community customers | | Community members | NPS | vs. non-community customers | | Community members | Expansion rate | vs. non-community customers |
Community Impact =
(Retention Lift × Revenue per Customer × Community Customers)
+ (Support Deflection × Cost per Ticket × Tickets Deflected)
+ (Acquisition Influence × Customers Acquired × Revenue per Customer)
+ (Expansion Influence × Expansion Revenue)
- Community Operating Cost
Don't show: total members, total posts, engagement rate.
Show instead:
development
When the user wants to reduce community churn, re-engage inactive members, or improve member retention. Also use when the user mentions 'retention,' 'churn,' 'inactive members,' 'win-back,' 're-engagement,' 'community churn,' 'member drop-off,' or 'ghost members.' For onboarding new members, see member-onboarding. For engagement programs, see engagement-programs.
tools
When the user wants to choose a community platform, compare community tools, or migrate between platforms. Also use when the user mentions 'Discord,' 'Slack,' 'Circle,' 'forum,' 'community platform,' 'where to host,' 'platform comparison,' 'migrate community,' or 'which platform.' For setting up the chosen platform, see community-ops.
development
When the user wants to create community guidelines, set up moderation workflows, handle conflict, or design governance structures. Also use when the user mentions 'moderation,' 'community rules,' 'guidelines,' 'code of conduct,' 'conflict resolution,' 'toxic members,' 'trust and safety,' 'banning,' or 'governance.' For crisis situations, see crisis-management.
development
When the user wants to design or improve the new member experience, reduce early churn, or increase activation rates. Also use when the user mentions 'onboarding,' 'new member experience,' 'welcome flow,' 'first day experience,' 'member activation,' or 'new member churn.' For ongoing engagement, see engagement-programs. For overall strategy, see community-strategy.