agentleFS
patonkikhpatonkikh/APES/skills/growth/go-to-market-planner/skill.md

go-to-market-planner

Skill3 starsChanged 4 months agoMITView on GitHub

Produce a go-to-market plan: target segments, channels, launch phases, messaging, and success metrics. Use when launching a product, entering a new market, or planning a GTM strategy after positioning is defined.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    If value proposition is missing, stop and request it — GTM without positioning produces generic campaigns.

    line 34
  2. Distinctive:

    Start with 10–20 design partners before paid acquisition.

    line 150
  3. Distinctive:

    Document what you will not do in launch (non-goals).

    line 152

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Planner

Purpose

Produce a go-to-market (GTM) plan: who to reach first, through which channels, in what sequence, with what message, and how to measure launch success.

Input: Product/PRD summary, value proposition, competitive context (optional), budget and timeline constraints
Output: GTM Plan with segment prioritization, channel mix, phased launch timeline, messaging pillars, and KPI dashboard
Examples: See examples.md for worked input/output.


Workflow

Step 1: Confirm launch readiness inputs

InputRequiredSource skill
Target customer & problemYesproduct/problem-statement-builder
Value propositionYesproduct/value-proposition-designer
MVP scopeYesproduct/prd-generator or feature-prioritization
Competitive wedgeRecommendedproduct/competitive-analysis
Pricing directionRecommendedgrowth/pricing-strategy-advisor

If value proposition is missing, stop and request it — GTM without positioning produces generic campaigns.

Step 2: Define ICP and beachhead segment

FieldDefinition
ICP firmographicsCompany size, industry, geography
PersonaBuyer vs user vs champion
Pain intensityMust-have vs nice-to-have
ReachabilityCan we find and contact them?
Willingness to payBudget owner identified?

Rank 1–3 segments; pick one beachhead for launch (not everyone at once).

Step 3: Select GTM motion

MotionUse whenPrimary channels
Product-led (PLG)Low touch, self-serve, fast TTVProduct, content, community
Sales-ledHigh ACV, complex buy, enterpriseOutbound, demos, partners
Community-ledDeveloper tools, open coreDocs, Discord, advocates
HybridMid-market SaaSPLG entry + sales assist

State chosen motion and why alternatives were rejected.

Step 4: Build channel plan

Per channel document:

ChannelRole in funnelOwnerBudgetLeading indicator
Content/SEOAwarenessMarketing$Organic traffic
PaidAcquisitionGrowth$CAC
Product viralityActivationProduct—Invite rate
Sales outboundConversionSales$SQLs
PartnershipsDistributionBD—Referral pipeline

For AI products: add trust channels (demos, case studies, security page) — buyers need proof, not hype.

Step 5: Phased launch timeline

PhaseDurationGoalActivities
Alpha2–4 wkLearnDesign partners, qualitative feedback
Beta4–8 wkValidateLimited access, measure activation
GAongoingScaleFull channel mix, optimize CAC/LTV

Each phase has entry criteria, exit criteria, and kill criteria if metrics fail.

Step 6: Messaging architecture

LevelContent
One-linerProblem + outcome
Elevator pitch30-second version for ICP
Pillars3 proof-backed themes (not feature lists)
Objection mapTop 5 objections + responses
AI disclosureHow you describe AI capabilities honestly

Align with value proposition; do not invent new positioning here.

Step 7: Define launch KPIs

MetricTargetMeasurement
Activatione.g. 40% complete core action D7Product analytics
PipelineSQLs or signups/weekCRM / product
CAC (if paid)< X% of LTVFinance + ads
NPS / qualitativeBaseline scoreSurveys

Link events to product/analytics-instrumentation-planner or growth/experiment-designer.

Step 8: Validate

Run Validation checklist.


Decision Rules

ConditionAction
No single beachhead segmentStop; force rank — launch one segment first
B2B enterprise + PLG only budgetFlag mismatch; recommend sales assist or narrow ICP
Pre-product / no MVPLimit to alpha design-partner plan only
Regulated industryAdd compliance review gate before public GA
AI product without eval metricsRequire quality KPI in launch dashboard
Launch date immovableCut channels, not measurement

Validation

  • Beachhead ICP defined with firmographics and persona
  • GTM motion selected with rationale
  • ≥3 channels with owners and leading indicators
  • Phased timeline with entry/exit/kill criteria
  • Messaging pillars tied to value proposition
  • Launch KPIs with targets and data sources
  • Dependencies on pricing and analytics documented
  • Risks and mitigations listed (competitor response, budget)

Anti-patterns

  • Spray and pray — every channel at once with no beachhead.
  • Launch without activation metric — vanity traffic, no product signal.
  • Feature launch, not outcome launch — messaging is a changelog.
  • Ignoring sales cycle — enterprise GTM with self-serve assumptions.
  • AI hype positioning — overpromising capabilities eval cannot support.

Best Practices

  • Start with 10–20 design partners before paid acquisition.
  • Pair qualitative interviews with funnel metrics each phase.
  • Document what you will not do in launch (non-goals).
  • Refresh competitive messaging quarterly in fast-moving AI categories.
  • Hand off instrumentation before beta opens.

Output Structure

# GTM Plan: [Product Name]

## Launch context
[Motion, beachhead, timeline constraints]

## Beachhead ICP
[Segment definition and ranking]

## Channel plan
| Channel | Funnel stage | Owner | KPI |
|---------|--------------|-------|-----|

## Launch phases
### Alpha / Beta / GA
[Criteria and activities]

## Messaging
[Pillars, pitch, objections]

## KPIs
| Metric | Target | Source |
|--------|--------|--------|

## Risks
| Risk | Mitigation |
|------|------------|

## Dependencies
[Pricing, analytics, product readiness]

Next Skills

OutcomeRecommended Skill
Set price before launchgrowth/pricing-strategy-advisor
Design launch experimentsgrowth/experiment-designer
Instrument funnelsproduct/analytics-instrumentation-planner
Refine positioningproduct/value-proposition-designer
Competitive contextproduct/competitive-analysis

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.