How to Design Growth Loops and GTM Strategies Using PM Skills

PM Skills provides an AI-driven framework that combines the growth-loops and gtm-motions skills through the /growth-strategy command to design sustainable growth flywheels and comprehensive go-to-market strategies.

Designing effective growth mechanisms requires balancing product-native acquisition engines with external market motions. The phuryn/pm-skills repository offers a structured, AI-guided approach to evaluating five classic flywheel mechanisms against seven acquisition channels, then synthesizing them into a cohesive 90-day growth playbook. This framework separates product-led growth from market-led execution while embedding continuous measurement through loop coefficients and CAC metrics.

Understanding the Growth Loops Framework

The growth-loops skill, defined in pm-go-to-market/skills/growth-loops/SKILL.md, provides a systematic method for identifying and designing sustainable acquisition mechanisms. Rather than relying on linear funnels, this framework evaluates five classic flywheel types:

  • Viral Loop – Users naturally invite others during normal usage
  • Usage Loop – Increased product usage generates more value and visibility
  • Collaboration Loop – Multi-user features create organic expansion
  • User-Generated Content Loop – Users create content that attracts new users
  • Referral Loop – Explicit incentive programs drive acquisition

The skill walks through a five-step process: defining product value, fitting loops to your product type, designing specific mechanics, calculating a loop coefficient, and building an implementation plan. This coefficient serves as a quantitative health metric for sustainable growth, distinct from vanity metrics.

Evaluating GTM Motions and Strategy

Once you've identified your primary growth loop, you must layer external acquisition channels. The gtm-motions skill, located in pm-go-to-market/skills/gtm-motions/SKILL.md, scores seven acquisition motions against your specific product characteristics, market conditions, budget constraints, and team capacity:

  1. Inbound – Content and SEO-driven acquisition
  2. Outbound – Direct sales and prospecting
  3. Paid Digital – Performance marketing channels
  4. Community – User-led engagement and advocacy
  5. Partners – Channel and integration partnerships
  6. ABM – Account-based marketing for enterprise
  7. PLG – Product-led growth tactics

After selecting your optimal motion stack, the gtm-strategy skill in pm-go-to-market/skills/gtm-strategy/SKILL.md expands these motions into a detailed launch blueprint. This includes channel selection, messaging frameworks, KPI definitions, and a phased rollout timeline—transforming strategic decisions into executable tactics.

Orchestrating the Complete Workflow

The /growth-strategy command, implemented in pm-go-to-market/commands/growth-strategy.md, orchestrates the entire workflow by running both skills sequentially and synthesizing outputs into a single growth playbook. This command prompts you for critical context—product description, current metrics, team resources, and market constraints—then executes the analysis.

The unified output includes:

  • Ranked evaluation of all five growth loops with primary and secondary recommendations
  • A GTM motion matrix showing investment levels, expected ROI, timeline, and required tooling
  • A 90-day growth roadmap with specific experiments, success metrics, and resource allocation guidelines

By separating the product-led (loops) and market-led (motions) dimensions, the framework ensures you establish sustainable organic mechanisms before layering paid acquisition for scale.

Step-by-Step Implementation

To run the complete workflow from a Claude-compatible client, use the orchestrating command:

/growth-strategy B2B collaboration platform — growth plateaued at 4k MAU

This command executes four stages:

  1. Context Collection – Prompts for product description, current MAU, team size, and budget constraints
  2. Loop Analysis – Runs growth-loops to return a ranked table of the five flywheel mechanisms
  3. Motion Scoring – Executes gtm-motions to score the seven acquisition channels
  4. Playbook Generation – Produces a markdown document containing:
    • Primary Growth Loop (e.g., Collaboration Loop)
    • Secondary Loop (e.g., Referral)
    • Motion Stack (e.g., Inbound + PLG + Community)
    • 90-day experiment plan with metrics and next-step prompts

If you prefer granular control over the workflow, invoke the components separately:


# Evaluate growth loops for product-fit

/growth-loops "AI-powered design tool that lets teams co-edit mockups"

# Score acquisition channels

/gtm-motions "AI-powered design tool for enterprise teams"

You can then feed these outputs into /gtm-strategy to develop detailed messaging and launch timelines, or proceed directly to implementation.

Summary

  • Growth loops focus on product-native flywheels (Viral, Usage, Collaboration, UGC, Referral) evaluated through the growth-loops skill with quantitative loop coefficients
  • GTM motions cover external acquisition channels (Inbound, Outbound, Paid, Community, Partners, ABM, PLG) scored against your specific constraints in gtm-motions
  • End-to-end orchestration happens through the /growth-strategy command, which produces a unified 90-day playbook from pm-go-to-market/commands/growth-strategy.md
  • Implementation flexibility allows running the complete workflow or individual skills depending on your team's needs and current growth stage

Frequently Asked Questions

What is the difference between growth loops and GTM motions in PM Skills?

Growth loops are product-native mechanisms where existing users drive new user acquisition through product usage (viral invites, collaboration features, content creation). GTM motions are external marketing and sales channels (inbound content, outbound sales, paid ads) that require ongoing investment. The PM Skills framework evaluates loops through pm-go-to-market/skills/growth-loops/SKILL.md and motions through pm-go-to-market/skills/gtm-motions/SKILL.md, treating them as complementary layers in your growth strategy.

How do I calculate the loop coefficient when designing growth loops?

The growth-loops skill calculates a loop coefficient during the design phase by quantifying how many new users each existing user generates per cycle. This involves analyzing invitation rates, conversion rates, and cycle time. The coefficient appears in the implementation plan output from pm-go-to-market/skills/growth-loops/SKILL.md and serves as your North Star metric for loop health—values above 1.0 indicate sustainable viral growth.

Can I run the growth and GTM components separately instead of using the combined command?

Yes. While /growth-strategy orchestrates both, you can invoke /growth-loops and /gtm-motions independently to customize each analysis phase. This modular approach, documented in the respective SKILL.md files, allows teams to deep-dive into flywheel mechanics before committing to specific acquisition channels, or to update GTM tactics without re-evaluating core product loops.

What specific deliverables does the /growth-strategy command produce?

The command generates a markdown growth playbook containing: (1) a ranked table of the five growth loops with primary/secondary recommendations, (2) a GTM motion matrix scoring investment, ROI, and timeline for each channel, (3) a 90-day experiment roadmap with specific metrics (CAC, payback period, North Star), and (4) actionable next-step prompts for implementation. This output synthesizes the analyses from both pm-go-to-market/skills/growth-loops/SKILL.md and pm-go-to-market/skills/gtm-motions/SKILL.md into a single executable document.

Have a question about this repo?

These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:

Share the following with your agent to get started:
curl -s "https://instagit.com/install.md"

Works with
Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →