How to Design Growth Loops and GTM Motions: A Product Manager's Playbook

Design sustainable traction by pairing self-reinforcing growth loops with targeted go-to-market motions, then validate and scale using the loop coefficient formula and ready-to-use templates from the phuryn/pm-skills repository.

The phuryn/pm-skills repository ships opinionated knowledge assets that teach product managers exactly how to design growth loops and GTM motions as a unified system. Its SKILL.md files and CLI-style commands provide step-by-step frameworks, scoring worksheets, and execution roadmaps you can apply immediately. This guide distills the methodology documented in pm-go-to-market/skills/growth-loops/SKILL.md and pm-go-to-market/skills/gtm-motions/SKILL.md into an actionable architectural blueprint.

Map Product Value to Growth Loop Types

As implemented in phuryn/pm-skills, a growth loop is a self-reinforcing flywheel that generates new users or revenue each time the cycle completes. The source code describes five proven loop types. Selecting the right one depends on your product's core action, network effects, and friction points.

Viral Loop

Viral loops excel when users naturally share content to gain social visibility or free-tier upgrades. The core trigger follows a create-then-share path: a user produces content, distributes it, and a new user discovers the product. This loop fits best with design tools, video platforms, and any product where shareable output is the primary value.

Usage Loop

Usage loops thrive on content platforms where consumption fuels more creation. The flywheel spins as creators publish, others consume that content, and the consumption itself attracts new creators seeking an audience. Typical incentives include low-friction publishing and algorithmic boosts that reward volume.

Collaboration Loop

Collaboration loops power team-oriented tools such as docs, design systems, and chat apps. The trigger is an invitation to co-create: one user imports colleagues, collaborative features lock in the team, and admin controls deepen adoption. This loop is ideal when the product's value increases directly with the number of active teammates.

User-Generated Loop

User-Generated loops dominate trend-driven media environments like TikTok or Pinterest. The cycle starts when a user discovers a trend, replicates or remixes it, and shares the result, which in turn inspires the next wave of participants. Trend-participation rewards and low creation barriers are the key incentives.

Referral Loop

Referral loops rely on direct incentives for acquisition rather than organic content sharing. A user refers others, receives a reward—such as monetary credit or feature unlocks—and is motivated to repeat the action. This model works well when you can clearly attribute signups and distribute rewards at low marginal cost.

To decide which loop fits your product, follow the two-step process documented in pm-go-to-market/skills/growth-loops/SKILL.md:

1. Define product value – Document the primary user action, existing network effects, and friction points (Growth Loops § Step 1).

2. Evaluate loop fit – Match your product type and observed user behavior against the five loop archetypes (Growth Loops § Step 2).

Select GTM Motions That Seed the Loops

A GTM motion is the acquisition channel or tactic you activate to inject users into your chosen growth loop. The phuryn/pm-skills source code defines seven motions, each mapped to the loops they fuel best, along with recommended tools and quick-start tactics.

• Inbound – Fuels Viral and Usage loops. Primary tools include HubSpot and SEO suites. Quick-start tactic: publish high-value, shareable content that demonstrates the product's output.

• Outbound – Drives Collaboration and enterprise Referral loops. Use LinkedIn Sales Navigator and Apollo to target decision-makers with demos that showcase collaborative features.

• Paid Digital – Provides initial lift for any loop. Run low-budget seed campaigns on Google or Meta Ads to validate loop coefficient before scaling.

• Community – Accelerates User-Generated and Referral loops. Launch a private community on Discord or Circle that highlights top creators and their work.

• Partner – Strengthens Collaboration and Referral loops through integrations. Co-build embeddable widgets or connectors via the Stripe or Shopify App Store ecosystems.

• ABM – Targets Collaboration and Referral loops inside large accounts. Use Terminus or Demandbase to tailor demos that highlight collaborative ROI.

• PLG – Powers Viral, Usage, and self-serve Referral loops. Instrument the freemium tier with Hotjar and Amplitude, and bake sharing UI directly into the product experience.

Use the scoring worksheet in pm-go-to-market/skills/gtm-motions/SKILL.md (GTM Motions § Step 3) to rate each motion from 1 to 10 on fit, budget, and resource constraints. The top-scoring motions become your primary acquisition engine.

Calculate the Loop Coefficient

Growth velocity is predictable. According to the phuryn/pm-skills source code, the loop coefficient (K) determines whether your flywheel compounds or stalls.

K = (Invites / User / Cycle) × (Conversion Rate)

Invites per user per cycle measures how many times an average user triggers the loop. Conversion rate is the percentage of those invites that become active users. If K > 1, the loop compounds organically; if K < 1, you must increase trigger frequency or conversion before relying on it as a primary engine (Growth Loops § Step 4).

Build a 30-60-90 Day Rollout Roadmap

The rollout template in pm-go-to-market/skills/growth-loops/SKILL.md and pm-go-to-market/skills/gtm-motions/SKILL.md structures execution into three phases.

• Days 0–30: Validate – Run a low-budget paid test that drives users into the loop and measure K. Do not scale until the coefficient is directionally positive.

• Days 31–60: Optimize – Refine the trigger, remove friction, and add incentives. Iterate the GTM motion mix based on early CAC and activation data.

• Days 61–90: Scale – Double down on the highest-K loop and add a secondary motion such as Community to amplify a User-Generated loop.

Measure Loop Health and Motion ROI

A unified dashboard prevents over-optimization of top-of-funnel metrics at the expense of retention. Track loop-specific health signals separately from motion-level efficiency.

• Loop health metrics – Shares per user, referral conversion rate, and activation lag.

• Motion KPIs – Customer acquisition cost (CAC), MQL-to-SQL rate, and churn of users acquired by each channel.

• Unified view – Combine loop-derived growth rate with motion-level ROI to reallocate budget toward the highest-compounding pair.

Automate the Framework with the pm-skills CLI

The phuryn/pm-skills repository exposes these frameworks through a CLI-style interface. After installation per the root README.md, you can run structured analyses from your terminal.

pm-skill run growth-loops \
  --args '{
    "product_description": "A collaborative design tool for remote teams",
    "primary_action": "create and share design files",
    "target_user": "product designers, engineers",
    "existing_sharing": "link sharing, embed codes",
    "constraints": "needs fast onboarding"
  }'

Expected output includes a ranked loop evaluation, recommended primary loop, and a 30-60-90 roadmap. Full schema details live in pm-go-to-market/skills/growth-loops/SKILL.md § Output.

pm-skill run gtm-motions \
  --args '{
    "product_description": "A collaborative design tool for remote teams",
    "price_point": "$15/mo per user",
    "sales_cycle": "4 weeks",
    "team_size": "3 marketers, 2 salespeople",
    "budget": "$20k/quarter",
    "existing_channels": ["blog", "free trial"]
  }'

This command returns motion scores, a recommended motion stack, a tool list, and a 90-day execution plan. Reference pm-go-to-market/skills/gtm-motions/SKILL.md § Output for response formatting.

Summary

• Select the loop that matches your product’s core action: Viral, Usage, Collaboration, User-Generated, or Referral.
• Pair it with GTM motions that deliberately seed users into that loop, scored on fit, budget, and resources.
• Calculate K every cycle; only scale when the loop coefficient exceeds 1.0.
• Execute in 30-60-90 day phases: validate, optimize, then compound.
• Use the pm-skills CLI and the documented SKILL.md files to automate analysis and maintain a single source of truth.

Frequently Asked Questions

What is the difference between a growth loop and a GTM motion?

A growth loop is a self-reinforcing in-product cycle where user actions generate new users, while a GTM motion is an external acquisition channel or tactic that feeds users into that cycle. According to the phuryn/pm-skills source code, loops create compounding growth, whereas motions provide the initial traffic and ongoing fuel.

How do I calculate the loop coefficient for my product?

Compute K by multiplying the average invites per user per cycle by the invite-to-user conversion rate, as defined in pm-go-to-market/skills/growth-loops/SKILL.md. If K is greater than 1, each existing user generates more than one new user and the loop scales organically. If K is below 1, prioritize improving the trigger frequency or conversion rate before increasing spend.

Which GTM motion is best for a product-led growth (PLG) strategy?

PLG as a motion is purpose-built for Viral, Usage, and self-serve Referral loops because it embeds sharing and discovery inside the product experience. The phuryn/pm-skills framework recommends instrumenting freemium tiers with tools like Hotjar and Amplitude, then baking sharing UI directly into natural workflow moments. For execution details, see pm-go-to-market/skills/gtm-motions/SKILL.md § Step 3.

Where can I find the templates and scoring worksheets?

All templates, scoring worksheets, and CLI commands live in the phuryn/pm-skills repository. The core skill definitions are in pm-go-to-market/skills/growth-loops/SKILL.md and pm-go-to-market/skills/gtm-motions/SKILL.md, while the orchestration example is in pm-go-to-market/commands/plan-launch.md. Installation and usage instructions are in the repository root README.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}