mcpbeat

Gtm Strategy

phuryn/gtm-strategy

Create a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline. Use when planning a product launch, creating a GTM plan from scratch, or defining a launch strategy for a new market.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
24819
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/phuryn/pm-skills --skill gtm-strategy

The instruction itself

14 sections, as written by the author

GTM Strategy

Overview

Create a comprehensive go-to-market strategy for a product launch. This skill covers marketing channels, messaging development, success metrics definition, and launch planning.

When to Use

  • Planning a product launch
  • Creating a GTM plan from scratch
  • Defining a launch strategy for a new market
  • Developing product-to-market fit strategy
  • Preparing a product go-live roadmap

How It Works

Step 1: Gather Research Data

The system will help you load and analyze early research about your product and target market. Provide:

  • Product description and key features
  • Target market segment details
  • Market research or validation data
  • Competitive landscape information
  • Any available customer interviews or survey data

Step 2: Define Marketing Channels

Evaluate which channels best reach your target audience:

  • Digital marketing channels (paid search, social media, display)
  • Content and inbound channels (blog, SEO, thought leadership)
  • Sales and outbound channels (direct outreach, partnerships)
  • Community and grassroots channels
  • Product-led and viral channels

Step 3: Develop Messaging

Create audience-specific messaging that resonates:

  • Core value proposition for target segment
  • Key differentiators and competitive advantages
  • Pain point validation and solution mapping
  • Proof points and social proof strategies
  • Channel-specific messaging variations

Step 4: Define Success Metrics

Establish measurable KPIs to track launch success:

  • Awareness metrics (impressions, reach, brand recall)
  • Engagement metrics (CTR, cost per engagement, time on site)
  • Conversion metrics (signups, demos requested, trials started)
  • Revenue metrics (MRR, customer acquisition cost, lifetime value)
  • Market metrics (market share, segment penetration)

Step 5: Create Launch Plan

Build a phased launch timeline:

  • Pre-launch preparation (messaging, channels, timeline)
  • Launch day activities and announcements
  • Post-launch momentum (content, partnerships, communities)
  • Measurement and optimization cadence
  • Success criteria and go/no-go decision points

Input Format

Use $ARGUMENTS to pass:

  • Product name and description
  • Target market segment
  • Research data or file path
  • Launch timeline and constraints
  • Budget or resource limitations

Output

A structured GTM strategy document including:

  • Recommended marketing channels with justification
  • Channel-specific messaging and positioning
  • Launch timeline with key milestones
  • KPI targets and measurement framework
  • Risk mitigation strategies
  • 90-day execution roadmap

Framework

This skill applies Product Compass GTM strategy methodology, focusing on market selection, channel fit, and message-market fit for sustainable product growth.

Tips

  • Start with your most confident customer segment
  • Validate assumptions through customer interviews before full launch
  • Focus on a few channels excellently rather than many channels poorly
  • Establish baseline metrics before launch to measure impact
  • Plan for feedback loops and optimization

Further Reading

How to use it

Copy the folder

Take phuryn/gtm-strategy from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.