Community Building Template for Product Growth

Start with 20-30 real power users invited personally. Ask each to introduce themselves and post one genuine question or tip in the first week. Have your team participate as real humans (not brand accounts) answering questions and sharing insights. The first 50 conversations set the tone for everything after. If those 50 are genuine, the community scales with that DNA.

Where your users already spend time. Developers live on Discord and GitHub Discussions. Enterprise buyers prefer Slack or branded platforms (Circle, Bettermode). If your users are not on any chat platform regularly, a forum model (Discourse) with email digests may work better than real-time chat. Do not choose based on features. Choose based on member behavior.

A new community needs 15-20 hours per week for the first 3 months: seeding content, moderating, responding, and building programs. After 6 months, if you have active champions, this drops to 8-12 hours per week. At 2,000+ members, you likely need a dedicated community manager. The [Product-Led Growth Handbook](/plg-guide) covers the economics of community investment.

Track three things: support deflection (community answers vs. support tickets), retention lift (community members vs. non-members), and referral attribution (signups that mention community or use a community link). Use the [churn rate glossary entry](/glossary/churn-rate) to calculate the dollar value of improved retention among community members.

When you have fewer than 500 active users (one-to-one relationships are better), when your product does not have a learning curve or peer discussion potential (simple utility products), or when you do not have someone willing to commit 15+ hours per week for 6 months. A dead community is worse than no community. ---