| date | "2026-02-07T00:00:00.000Z" |
| created | "2026-02-07T00:00:00.000Z" |
| name | community-led-growth |
| version | 1.0.0 |
| description | 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. |
| tags | ["community-led-growth","skill"] |
Community-Led Growth
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.
Before Starting
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):
1. Business Model
- What does the company sell?
- Revenue model (SaaS, marketplace, services, etc.)?
- Current GTM motion (sales-led, product-led, or both)?
2. Community-Business Relationship
- How does the community relate to the product today?
- Is community pre-sale, post-sale, or both?
- What happens when community members become customers (or vice versa)?
3. Data
- Can you track community members through the customer journey?
- Do you have data on community members vs. non-members? (retention, LTV, NPS)
- What attribution exists?
What CLG Is (and Isn't)
CLG is: Using community as a strategic growth channel that contributes to acquisition, activation, retention, and expansion — with measurable impact.
CLG is not:
- Replacing your sales or marketing team with a Discord server
- Building community to "check a box"
- Counting members as a vanity metric
- Hoping community magically generates revenue
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).
The CLG Flywheel
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.
CLG Across the Customer Journey
Acquisition
Community as discovery channel:
- Public community content indexed by search engines
- Member-generated content shared externally
- Events that attract non-members
- Community-influenced content marketing
Community as social proof:
- Prospects can see active, engaged users before buying
- Member testimonials and case studies
- "Join 5,000 professionals already using [product]"
Community as try-before-you-buy:
- Free community tier that demonstrates product value
- Peer recommendations within the community
- Prospects asking "should I buy X?" and getting authentic answers
Activation
Community accelerates onboarding:
- New users get help from experienced users (faster than docs)
- Best practices shared by peers feel more credible than company content
- Templates, workflows, and examples created by community
Community creates accountability:
- New users share their setup progress
- Peers encourage and troubleshoot
- "Getting started" cohorts
Retention
Community increases switching costs (positively):
- Relationships built within the community
- Custom content and resources tied to the product
- Peer accountability and support
- Identity: "I'm part of the [Product] community"
Community provides ongoing value:
- Continuous learning and tips
- Network effects (more members = more value)
- Direct line to product team
Expansion
Community drives upsells:
- Members see advanced use cases from other members
- Power users share workflows that require paid features
- "How I use [premium feature]" content
Community identifies expansion opportunities:
- Members asking about features they don't have access to
- Discussion around pain points that paid tiers solve
- Usage patterns visible in community behavior
Advocacy
Community members become evangelists:
- Organic word-of-mouth from satisfied members
- Member-created content (tutorials, reviews, case studies)
- Conference talks and meetup presentations by members
- Referral programs powered by community relationships
CLG Operating Model
Integrating Community with GTM
Community + Marketing:
- Community insights fuel content marketing
- Member stories become case studies
- Community content becomes SEO assets
- Events drive top-of-funnel awareness
Community + Sales:
- Prospects directed to community for peer validation
- Sales references warm intros within community
- Community engagement as buying signal (higher intent)
- Champions identified for expansion conversations
Community + Product:
- Community feedback loop accelerates product development
- Beta testing with engaged community segment
- Feature adoption driven by community education
- Community as continuous user research panel
Community + Support:
- Peer-to-peer support deflects tickets
- Community knowledge base supplements documentation
- Power users as de facto support agents
- Support insights surface product improvements
Measuring CLG Impact
Attribution Framework
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 |
Building the Business Case
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
What to Present to Leadership
Don't show: total members, total posts, engagement rate.
Show instead:
- Revenue influenced by community
- Cost savings from community (support deflection)
- Retention differential (community members vs. non-members)
- Pipeline influenced (prospects who engaged community before buying)
- NPS differential
Implementation Roadmap
Phase 1: Instrument (Month 1-2)
- Tag community members in CRM
- Set up cohort tracking (community vs. non-community)
- Implement attribution for community-sourced signups
- Baseline current metrics
Phase 2: Optimize (Month 3-4)
- Identify highest-impact CLG touchpoints
- Create community → product conversion paths
- Train sales on community as resource
- Launch community-powered content engine
Phase 3: Scale (Month 5-6)
- Automate community → CRM data flow
- Build CLG dashboard for leadership
- Expand successful programs
- Document ROI for continued investment
Task-Specific Questions
- What's your current GTM motion? (sales-led, product-led, hybrid)
- Can you identify community members in your customer data?
- Do you have any data on community members vs. non-members today?
- What's the biggest business challenge you want community to address?
- Who in your organization needs to be convinced that community drives growth?
Related Skills
- community-growth: For general community member acquisition
- community-metrics: For detailed measurement frameworks
- community-monetization: For monetizing the community directly
- community-feedback: For product feedback from community
- community-strategy: For overall community planning
