agentleFS
varunk130varunk130/claude-code-skills/skills/strategic-management/go-to-market-strategy/SKILL.md

go-to-market-strategy

Skill1 starsChanged 23 days agoMITView on GitHub

Creates a complete go-to-market (GTM) plan - launch goals, prioritized target segments, channel strategy with owners, messaging matrix by persona, launch timeline, sales enablement checklist, and 30/60/90-day success metrics. Use when planning a product launch or major feature release; expanding into a new market or segment; designing an enterprise sales play; choosing between product-led, sales-led, marketing-led, or channel-led motions; or turning a launch idea into a one-page plan.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask for anything critical that is missing before planning.

    line 33
  2. Distinctive:

    Every benefit needs a proof point: a metric, a customer result, or a demonstration.

    line 89
  3. Distinctive:

    Use one generic message for all personas

    line 133
  4. Distinctive:

    Wait until 90 days to judge whether the launch is working

    line 135
  5. Distinctive:

    Treat go-to-market as a one-day event instead of a 90-day program

    line 136

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Go-to-Market Strategy

Most launches fail from poor go-to-market, not bad products.

What this skill is

A workflow that turns "we are launching X" into a go-to-market (GTM) plan a team can execute. It clarifies the launch type and goals, prioritizes segments, maps channels and messages to each one, and sets a timeline and metrics that show within 30 days whether the launch is working. The result fits on one page, with a detailed plan behind it.

What it solves

  • 50-page launch decks nobody reads, or back-of-napkin plans that miss critical channels
  • Launches aimed at "everyone" with no prioritized segment
  • One generic message used for every persona
  • Channels chosen by habit rather than where the segment actually discovers products
  • Sales hearing about the launch on launch day, with no enablement
  • Success judged only at 90 days, too late to correct course

When to invoke

  • Launching a new product, a major feature, or a new pricing tier
  • Expanding into a new geography, industry, or customer segment
  • Designing an enterprise sales play for a target account list
  • Choosing or changing the primary go-to-market motion
  • Reviewing a launch plan before committing budget

Phase 1: Gather launch inputs

Ask for anything critical that is missing before planning.

InputPriority
What is launching (product, feature, expansion)Critical
Target customers and segmentsCritical
Launch date or windowCritical
Available budget and teamNice to have
Competitive positioningNice to have
Current sales motionNice to have

Phase 2: Define launch type and goals

Launch tierTypical scopeInvestment
Tier 1New product or market entryFull campaign, press, sales push
Tier 2Major feature or new segmentTargeted campaign and enablement
Tier 3Incremental improvementChangelog, in-product messaging

Set two or three measurable goals (for example, pipeline created, activated accounts, or revenue) with a target and a date.

Phase 3: Prioritize target segments

Score each candidate segment 1-5:

SegmentBenefit receivedReachabilityBuying authorityBuying process simplicityTotal
[Segment A]

Pick one primary and at most two secondary segments. Name the segments deliberately left out.

Phase 4: Choose the motion and map channels

Select the primary motion:

MotionFlowFits when
Product-Led Growth (PLG)Trial → conversion → expansionLow price point, fast time to value
Sales-ledOutbound → demo → closeHigh contract value, complex buying
Marketing-ledContent → Marketing Qualified Lead (MQL) → Sales Qualified Lead (SQL) → closeConsidered purchase, education needed
Channel-ledPartner → referral → closePartners own the customer relationship

Then map channels per segment:

SegmentDiscovery channelsExpected Customer Acquisition Cost (CAC)Owner
[Segment A]$

Phase 5: Build the messaging matrix

PersonaPainFeatureBenefitProof point
[Economic buyer]
[Daily user]
[Technical evaluator]

Every benefit needs a proof point: a metric, a customer result, or a demonstration.

Phase 6: Build the timeline

WindowActivities
Pre-launch (4-8 weeks)Positioning sign-off, sales enablement, beta customers, content, press briefings
Launch dayAnnouncement, in-product messaging, sales outreach, partner notification
Post-launch (first 90 days)Follow-up campaigns, customer stories, feedback loop, iteration

Assign an owner and a date to every milestone.

Phase 7: Define success metrics

HorizonFocusExample metrics
30 daysLeading indicatorsSign-ups, demos booked, pipeline created
60 daysEngagementActivation rate, feature adoption, trial conversion
90 daysBusiness outcomesRevenue, win rate, retention of launch cohort

Set a threshold for each metric that would trigger a course correction.

Output

  • GTM one-pager plus a detailed plan
  • Launch tier and measurable goals
  • Target segment prioritization
  • Motion choice and channel strategy with owners
  • Messaging matrix by persona
  • Launch timeline with milestones and owners
  • Sales enablement checklist
  • 30/60/90-day success metrics with correction thresholds

Operating rules

Always

  • Prioritize one primary segment and name what is out of scope
  • Match the motion to price point and buying complexity
  • Tie every message to a persona and a proof point
  • Enable sales before launch day
  • Set leading indicators that show progress within 30 days

Never

  • Target "everyone" or every channel at once
  • Use one generic message for all personas
  • Launch without an owner for each channel and milestone
  • Wait until 90 days to judge whether the launch is working
  • Treat go-to-market as a one-day event instead of a 90-day program

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.