go-to-market
Skill9 starsChanged 8 months agoMITView on GitHub
Plan comprehensive go-to-market launches for products and features. Use when launching new products, entering new markets, or planning major releases.
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
4
Distinctive
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
- Distinctive: line 40
Use the product-positioning skill for full positioning work.
- Distinctive: line 73
Not all launches are equal.
- Distinctive: line 246
Marketing role: Create partner-ready materials.
- Distinctive: line 323
Before executing a GTM strategy:
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Go-to-Market Strategy
When to Activate
- Launching a new product or service
- Entering a new market segment or geography
- Planning a major product release or version upgrade
- Building a GTM strategy for an acquisition or partnership
- Evaluating which GTM motion to adopt (PLG, sales-led, channel, hybrid)
- Annual or quarterly GTM planning
- Product-market fit established and ready to scale distribution
First Questions
- What are you launching? (New product, feature, market expansion, repositioning)
- Who is the target customer? (ICP, buyer persona, user persona)
- What is the value proposition? (Why should they care? Why now?)
- What is the competitive landscape? (Who else solves this problem?)
- What is the GTM motion? (PLG, sales-led, channel, community, hybrid)
- What is the pricing strategy?
- What is the launch timeline? (T-minus weeks/months)
- What resources are available? (Team, budget, existing channels)
- How will you measure success? (Revenue target, adoption target, pipeline target)
GTM Strategy Components
1. Target Market Definition
- Total Addressable Market (TAM): Everyone who could theoretically buy.
- Serviceable Addressable Market (SAM): The portion you can reach with your current channels and product.
- Serviceable Obtainable Market (SOM): Realistic share you can capture in the near term.
- Ideal Customer Profile (ICP): The specific type of company/person most likely to buy and succeed.
2. Value Proposition
- Use the product-positioning skill for full positioning work.
- The GTM value proposition should answer: "Why should this specific customer buy this specific product right now?"
- "Right now" is critical — what trigger event or market condition makes this timely?
3. Channel Strategy
How will you reach your target market?
| Channel | Best For | Considerations |
| Direct sales | High ACV, complex products, enterprise | Expensive. Requires sales team. Long cycles. |
| Self-serve / PLG | Low-to-mid ACV, simple onboarding, tech-savvy users | Requires product investment. See plg-strategies skill. |
| Channel / Partners | Geographic expansion, industry verticals, integration ecosystems | Less control. Revenue share. Partner enablement needed. |
| Community-led | Developer tools, open source, niche communities | Slow to build. Authentic relationship required. |
| Marketplace | App stores, platform ecosystems | Distribution built in. Competition is high. Platform dependency. |
4. Pricing Strategy
- Value-based pricing: Price based on the value delivered to the customer (preferred).
- Competitive pricing: Price relative to alternatives.
- Cost-plus pricing: Cost to deliver + margin (rarely optimal for software).
- Penetration pricing: Low price to gain market share, increase later.
- Skimming pricing: High price initially, reduce over time.
Pricing decisions to make:
- Per seat, per usage, flat rate, or tiered?
- Monthly vs. annual billing? (Offer both; incentivize annual.)
- Free tier or trial? (See PLG strategies skill.)
- Enterprise / custom pricing?
5. Launch Plan
See launch tier framework below. The launch plan operationalizes the strategy.
Launch Tier Framework
Not all launches are equal. Tier your launches to allocate resources appropriately.
Tier 1 — Major Launch
What qualifies: New product, new market entry, major platform change, company milestone (funding, acquisition). Resources: Full cross-functional team. Dedicated budget. 8-12 week preparation. Activities:
- Press release + media outreach (exclusive or embargo)
- Product Hunt / launch event
- Email to full customer base
- Paid amplification
- Sales enablement (training, battlecards, demo environment)
- Content package (blog, video, case study)
- Social media campaign
- Customer webinar / event
- Analyst briefing (if relevant)
Tier 2 — Moderate Launch
What qualifies: Major feature release, new integration, significant pricing change. Resources: Marketing team lead. Moderate budget. 4-6 week preparation. Activities:
- Blog post + email to relevant customer segment
- In-product announcement
- Social media posts
- Sales notification and brief
- Help documentation
- Targeted paid amplification (optional)
Tier 3 — Minor Launch
What qualifies: Feature update, UX improvement, minor new capability. Resources: Product marketing + product team. Minimal budget. 1-2 week preparation. Activities:
- In-product notification or changelog entry
- Help documentation update
- Email to affected users (if behavioral change)
- Internal Slack announcement
Launch Timeline Template
T-8 Weeks (Tier 1 Launch)
T-8: Strategy finalization
- Positioning and messaging approved
- Target audience and segments defined
- Launch tier and resource plan confirmed
- Success metrics defined
T-6: Content creation begins
- Blog post, landing page, email copy
- Sales enablement materials
- Social media content plan
- Press release draft
- Video / demo production
T-4: Cross-functional alignment
- Sales training / enablement session
- Customer success briefing
- Support team documentation and training
- Beta / early access program (if applicable)
- Press outreach begins (embargoes, exclusives)
T-2: Final preparation
- All content reviewed and approved
- Landing pages live (gated or unlisted)
- Email sequences loaded and tested
- Ad campaigns built and ready
- QA of product / feature
- Internal launch readiness review
T-1: Pre-launch
- Final go/no-go decision
- Press embargo confirmations
- Social media posts scheduled
- Internal announcement prepared
T-0: LAUNCH DAY
- Execute launch day playbook (see launch-playbook skill)
T+1 to T+7: Post-launch amplification
- Monitor metrics and social conversation
- Respond to press and social media
- Send follow-up emails to non-openers
- Collect and share early customer feedback
T+14: Post-launch review
- Performance vs. goals assessment
- Lessons learned
- Ongoing amplification planCross-Functional Launch Checklist
Product Team
- Feature/product is GA-ready (no critical bugs)
- Documentation and help articles written
- API documentation updated (if applicable)
- Changelog updated
- In-product announcements configured
- Analytics and event tracking implemented
Marketing Team
- Positioning and messaging finalized
- Landing page live and tested
- Blog post written and scheduled
- Email campaigns built and tested
- Social media content created and scheduled
- Paid campaigns built and budgeted
- Press release written and distribution planned
- Video / demo produced (if applicable)
- Customer case study secured (if available)
Sales Team
- Sales training completed
- Battlecards updated with new positioning
- Demo environment ready with new feature/product
- Pricing and packaging communicated
- Objection handling document updated
- Target account list identified for outreach
Customer Success Team
- Existing customer communication planned
- Upgrade/migration path documented
- Onboarding materials updated
- Success metrics defined for new feature/product
- Proactive outreach plan for high-value accounts
Support Team
- Knowledge base articles published
- Support team trained on new feature/product
- Escalation paths defined for launch issues
- FAQ document prepared
- Ticket volume spike plan in place
Post-Launch Measurement Framework
Launch Metrics Dashboard
| Metric | T+1 Day | T+7 Days | T+30 Days | T+90 Days |
| Awareness: Page views, impressions | ✓ | ✓ | ✓ | |
| Engagement: Sign-ups, trials, demos requested | ✓ | ✓ | ✓ | ✓ |
| Activation: Users who reach value milestone | ✓ | ✓ | ✓ | |
| Revenue: Pipeline, bookings, expansion | ✓ | ✓ | ||
| Retention: Usage retention, churn impact | ✓ | |||
| Satisfaction: NPS, CSAT, support tickets | ✓ | ✓ | ✓ |
Launch Success Criteria (Define Before Launch)
- Set specific, measurable goals for each metric.
- Example: "Within 30 days: 500 sign-ups, 25% activation rate, $50K pipeline."
- Include a stretch goal and a minimum viable outcome.
Post-Launch Decision Framework
- Exceeding targets: Increase amplification. Invest more in this channel/product.
- Meeting targets: Continue plan. Optimize based on data.
- Below targets: Diagnose. Is it awareness (not enough people know), activation (people try but don't stick), or conversion (people stick but don't pay)?
- Way below targets: Emergency retrospective. Reassess positioning, channel, or product-market fit.
GTM for Different Motions
Product-Led Growth (PLG) GTM
- Primary channel: Product itself. Self-serve sign-up.
- Marketing role: Drive awareness and traffic. Optimize conversion funnel. Create educational content.
- Sales role: Assist on larger deals (PQL-based outreach). No cold outbound for small deals.
- Key metric: Sign-up → Activation → Conversion rate.
- See: plg-strategies skill for detailed PLG guidance.
Sales-Led GTM
- Primary channel: Outbound sales. Demos. Proposals.
- Marketing role: Generate qualified leads (MQLs). Create sales enablement content. Build brand awareness for inbound.
- Sales role: Drive the full sales process. AE-led demos, negotiations, closing.
- Key metric: Pipeline generated → Win rate → ACV.
- Best for: High ACV (>$20K/year), complex products, enterprise.
Channel / Partner GTM
- Primary channel: Resellers, distributors, integration partners, consultancies.
- Marketing role: Create partner-ready materials. Through-partner and to-partner marketing.
- Sales role: Manage partner relationships. Enable partner sales teams.
- Key metric: Partner-sourced pipeline → Partner revenue → Partner satisfaction.
- Best for: Geographic expansion, vertical penetration, ecosystem plays.
Community-Led GTM
- Primary channel: Developer community, user community, open-source ecosystem.
- Marketing role: Community building, developer relations, content, events.
- Sales role: Minimal initially. Enterprise sales overlay when community creates inbound.
- Key metric: Community size → Active contributors → Commercial conversion.
- Best for: Developer tools, open-source, technical products.
Hybrid GTM (Most Common for Scale-ups)
- Combine PLG for SMB/mid-market self-serve with sales-led for enterprise.
- Marketing generates both self-serve sign-ups and sales-qualified leads.
- Product-qualified leads (PQLs) bridge the two motions.
- Key design question: At what deal size / account size does the motion shift from self-serve to sales-assisted?
GTM Strategy Document Template
GO-TO-MARKET STRATEGY
Product/Initiative: [Name]
Date: [Date]
Owner: [Name]
1. EXECUTIVE SUMMARY
[3-5 sentences: What, for whom, why now, expected outcome]
2. TARGET MARKET
- TAM/SAM/SOM
- ICP definition
- Buyer and user personas
- Market timing / trigger events
3. VALUE PROPOSITION & POSITIONING
- Positioning statement
- Key messages (3-5)
- Competitive differentiation
4. GTM MOTION
- Primary motion (PLG / Sales-led / Channel / Hybrid)
- Channel strategy
- Lead generation approach
5. PRICING & PACKAGING
- Pricing model and tiers
- Competitive pricing context
- Discount / promotion strategy
6. LAUNCH PLAN
- Launch tier (1/2/3)
- Timeline with milestones
- Cross-functional responsibilities
7. SALES ENABLEMENT
- Training plan
- Materials (battlecards, demo, objection handling)
- Target account strategy
8. SUCCESS METRICS
- KPIs with targets
- Measurement timeline
- Success / failure criteria
9. BUDGET & RESOURCES
- Budget allocation by channel
- Team resources required
- External vendor / agency needs
10. RISKS & MITIGATIONS
- Top 3-5 risks
- Mitigation plans for eachQuality Gate
Before executing a GTM strategy:
- Is the target customer defined specifically enough to build a prospect list?
- Is the value proposition differentiated from alternatives (not just "we're better")?
- Does the GTM motion match the product complexity and deal size?
- Is pricing validated (not just guessed) — through customer research or competitive analysis?
- Are all cross-functional teams (product, sales, CS, support) briefed and aligned?
- Is the launch tiered appropriately for the significance of the announcement?
- Are success metrics defined with specific targets before launch (not after)?
- Is there a post-launch measurement plan with a clear timeline?
- Have you identified the top 3 risks and created mitigation plans?
- Is there an owner for every deliverable in the launch plan?
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- emotixco/claude-skills-founder★ 725same name
- magnus919/agent-skills★ 162same name
- vredin/vredin-CC-Harness★ 9same name
- astDeniss/business-skills★ 8same name
- ceeinbeta/pm-skills★ 3same name
- Cure-Consulting-Group/ProductEngineeringSkills★ 3same name
- mcveloria/pm-skills★ 3same name
- mariomile/builder-os★ 2same name
- AdeyStudios/skills★ 1same name
- fullstackinnoAI/skills★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use pitch-deck.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillpitch-deck
Populates investment banking pitch deck templates with data from source files. Use when: user provides a PowerPoint template to fill in, user has source data (Excel/CSV) to populate into slides, user mentions populating or filling a pitch deck template, or user needs to transfer data into existing slide layouts. Not for creating presentations from scratch.
Also in 3 projects that use this
In this repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ab-testingSkill
- analytics-attributionSkill
- analytics-dashboardsSkill
- cohort-analysisSkill
- marketing-reportingSkill
- brand-architectureSkill
- brand-guidelinesSkill
- brand-positioningSkill
- brand-voiceSkill
- competitive-positioningSkill
- visual-identitySkill
- community-strategySkill
- blog-seo-writingSkill
- content-auditSkill
- content-pillarsSkill
- content-repurposingSkill
- editorial-calendarSkill
- storytelling-frameworksSkill
- thought-leadershipSkill
- ugc-strategySkill
- ad-copySkill
- copywriting-frameworksSkill
- cta-optimizationSkill
- headline-formulasSkill
- landing-page-copySkill
- microcopy-uxSkill
- sales-page-copySkill
- campaign-conceptsSkill
- cro-frameworksSkill
- funnel-designSkill
- landing-page-optimizationSkill
- email-automationSkill
- email-copywritingSkill
- email-deliverabilitySkill
- email-segmentationSkill
- email-sequencesSkill
- growth-loopsSkill
- plg-strategiesSkill
- referral-programsSkill
- viral-mechanicsSkill
- influencer-outreachSkill
- influencer-roiSkill
- martech-stackSkill
- utm-trackingSkill
- ad-creative-testingSkill
- budget-allocationSkill
- google-adsSkill
- linkedin-adsSkill
- meta-adsSkill
- retargetingSkill
- crisis-communicationSkill
- media-pitchingSkill
- competitive-analysisSkill
- launch-playbookSkill
- product-positioningSkill
- press-releasesSkill
- customer-interviewsSkill
- market-researchSkill
- The first 60 shown.
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
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.

