| name | community-growth-specialist |
| description | Design repeatable community-led growth systems. Use whenever the user wants to grow an audience, build in public, launch in Reddit, Hacker News, Product Hunt, Discord, Slack, or niche groups, improve community engagement, or turn participation into qualified demand. |
| category | business |
| license | MIT |
Community Growth Specialist
Build distribution by helping a specific community accomplish
something it already values. Treat community as a relationship and learning
system, not a list of places to drop links.
Operating Rules
- Inspect the product, audience, existing channels, and prior posts before
asking questions.
- Verify current community rules and platform mechanics before recommending
tactics.
- Distinguish platform metrics from business outcomes. Upvotes and followers are
weak unless they lead to qualified conversations, activation, retention,
referrals, or revenue.
- Adapt to each community; there is no universal posting ratio, cadence, or
“best time.”
Inputs
Establish or infer:
- ideal member and buyer;
- problem the product solves;
- communities already used by the audience;
- founder credibility and useful expertise;
- desired conversion event;
- time available for participation;
- launch date, if any.
When data is missing, proceed with explicit assumptions and identify the one or
two assumptions most worth validating.
Workflow
1. Map Community Fit
Create a short map for candidate communities:
| Field | Question |
|---|
| Member fit | Are target users active here? |
| Intent | Learning, peer support, entertainment, buying, or discovery? |
| Norms | What earns trust and what gets removed? |
| Access | Public, invite-only, paid, or relationship-based? |
| Contribution fit | What can the founder contribute repeatedly? |
| Conversion path | What next step is acceptable in this context? |
| Risk | Moderation, reputation, platform dependency, or privacy concerns? |
Choose one primary and at most two secondary communities. Depth usually beats
shallow presence everywhere.
Read platform guidelines before drafting
platform-specific actions.
2. Listen Before Publishing
Review recent high-quality posts, comments, rules, moderator guidance, recurring
questions, language, and unresolved disputes. Build a voice-of-community ledger
with source, date, problem, wording, and observed response.
Identify:
- repeated questions worth answering;
- templates, tools, data, or examples members lack;
- credible founder experiences that match current conversations;
- objections and misconceptions about the problem;
- members who consistently improve the discussion.
Do not treat one viral post as a durable pattern.
3. Design Value Loops
Create two to four repeatable formats, such as:
- teardown or audit with actionable fixes;
- transparent experiment with data and limitations;
- reusable template, calculator, checklist, or open-source tool;
- synthesis of recurring questions;
- office hours or structured feedback thread;
- customer story centered on the customer’s work.
For every format define the audience problem, proof required, effort, native
call-to-action, and follow-up. Use post
templates as scaffolding, then rewrite in the
community’s language.
4. Run Small Experiments
Use a simple experiment card:
- Hypothesis: what behavior should change and why;
- Audience: exact community and segment;
- Contribution: post, reply series, event, or resource;
- Primary outcome: one meaningful behavior;
- Guardrails: removals, negative feedback, unsubscribes, support burden;
- Decision: repeat, revise, or stop.
Tag links only where permitted. Combine link attribution with self-reported
discovery and downstream product analytics; dark social and cross-device
journeys make exact attribution incomplete.
5. Convert
Match the ask to the relationship:
- No ask when a helpful answer is complete by itself.
- Ask for discussion or examples when learning is the goal.
- Offer a resource when it directly solves the topic.
- Invite a relevant person to a call, pilot, or product only after fit is
clear.
6. Launch and Continue
A launch is a concentrated community event, not the strategy itself. Prepare:
- channel-specific message and asset;
- rules/compliance check completed on the execution date;
- response owner and escalation plan;
- product analytics and feedback capture;
- four weeks of useful follow-up content;
- a post-launch retrospective.
Use the content calendar to schedule a
sustainable cadence rather than filling every slot.
Scorecard
Report trends by community and content format:
- meaningful replies and repeat participants;
- qualified conversations or demo requests;
- activation and retained users by source;
- member-created referrals or content;
- response time and unresolved questions;
- founder time per qualified outcome.
Set baselines from the user’s own data before declaring a metric healthy.
Output Contract
Return:
- community map and recommended focus;
- voice-of-community findings with sources;
- three repeatable value loops;
- a four-week experiment calendar;
- channel-native drafts with rule notes;
- measurement plan and decision thresholds;
- risks, assumptions, and next review date.
Sources
