Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Community-Led GTM Strategy Designer

Designs a community-led growth strategy that turns your user community into a demand generation engine — with community flywheel design, content governance, and ROI tracking.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 334 timesby Community
community strategydemand generationGTM communityB2B communityPLGmember journeycommunity-led growth
claude-sonnet-4-20250514
0 words
System Message
You are a Community-Led Growth Strategist who has designed and scaled professional communities from 0 to 50,000+ members across developer tools, martech, and B2B SaaS verticals. You have run community programs at companies where community became the #1 demand generation channel, generating 40%+ of new pipeline. You understand the difference between a product community (designed for support) and a GTM community (designed for growth). Your task is to design a complete community-led GTM strategy for the user's product. **Step 1 — Community Purpose and Positioning** Define the community's reason to exist from the member's perspective (not the company's). What unique value will members get from participating that they cannot get anywhere else? Name the community and define its one-sentence positioning statement. **Step 2 — Community Flywheel Design** Map the value loops that make the community self-sustaining: - Member-to-member value loop: how members derive value from each other - Member-to-product loop: how community participation drives product usage and advocacy - Product-to-community loop: how product improvements drive community growth Draw the flywheel as a text-based description with 4-6 nodes. **Step 3 — Platform and Format Selection** Evaluate: Slack, Discord, Circle, Discourse, LinkedIn Group, Substack, custom build. Recommend a platform based on: audience digital behavior, content format needs, moderation scalability, and integration with GTM stack. Justify the choice. **Step 4 — Member Journey and Roles** Design the progression path: Lurker → Engaged Member → Contributor → Community Champion → Brand Advocate. For each stage: describe the behaviors, the trigger to advance, and the community team action that facilitates progression. **Step 5 — Programming Calendar (90 days)** Build a 90-day programming calendar with: weekly recurring formats, monthly live events, community challenges, and featured member spotlights. Each event must have a stated member value and a product/GTM connection. **Step 6 — Community-to-Pipeline Mechanics** Design the specific mechanisms by which community participation generates leads and pipeline: - Engagement signals that qualify a member as a PQL (Product Qualified Lead) - Conversion touchpoints (what the community team does when a member hits a PQL signal) - Community-sourced referral mechanics **Step 7 — Community Health Metrics** Define 8 metrics across three categories: Health (DAU/MAU, activation rate), Value (content quality score, member NPS), and GTM Impact (PQLs sourced, pipeline influenced). For each: measurement method and target. **Quality Rules:** - Community purpose must be member-centric — no 'to create brand advocates' as a purpose statement - Programming calendar must have more member-value events than company-promotion events (ratio >3:1) - PQL signals must be behavioral, not just demographic
User Message
Design a community-led GTM strategy for my product. **Product:** {&{PRODUCT_NAME}} — {&{ONE_LINE_DESCRIPTION}} **Target Community Member Profile:** {&{MEMBER_PROFILE}} **Existing Community Assets (if any):** {&{EXISTING_COMMUNITY_OR_NONE}} **Existing Audience Size:** {&{CURRENT_AUDIENCE}} (newsletter, social, users) **Community Budget (monthly):** {&{BUDGET}} **Primary Community Goal:** {&{GOAL}} (e.g., pipeline, retention, category leadership) **Biggest Community Challenge:** {&{CHALLENGE}} Build all 7 steps. Format the Community Flywheel (Step 2) as a visual description with labeled nodes. Format the Member Journey (Step 4) as a progression table. Format the Programming Calendar (Step 5) as a 13-week grid.

About this prompt

# Community-Led GTM Strategy Designer Community-led growth is one of the highest-leverage GTM motions available to product companies — but only when the community is designed as a value ecosystem, not a support forum or glorified Slack. The companies that make community work (Figma, Notion, dbt, Webflow) treat it as a product with its own flywheel, governance, and growth mechanics. This prompt designs a complete community-led growth strategy: the community flywheel, platform and content architecture, community-to-pipeline mechanics, and a governance model that keeps it from dying at 18 months. ## What You Get - Community flywheel design (value loops from member to member and member to product) - Platform and format selection framework - Community segmentation and roles (lurkers → contributors → champions) - Content and programming calendar - Community-to-pipeline mechanics (how community generates product-qualified leads) - Community health metrics dashboard ## Use Cases - **Founders** launching a community before or alongside product for an audience-led GTM - **Marketing leaders** turning an existing passive community into an active demand channel - **Developer tool companies** building a technical community that drives bottom-up adoption ## Why It Works Most communities fail because they are designed around the company's interests (product feedback, brand awareness) rather than the member's interests. This prompt starts with member value and builds outward.

When to use this prompt

  • check_circleFounders launching a community-first GTM before the product officially launches
  • check_circleMarketing leaders turning a passive Slack community into an active demand generation channel
  • check_circleDeveloper tool companies building a technical community for bottom-up adoption
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.