Skip to content
Automation
Skill

/gtm

Activate for: go to market, GTM, GTM strategy, go-to-market, ICP, ideal customer profile, target customer, who to sell to, channel strategy, sales channel, how to acquire customers, customer acquisition, outreach strategy, LinkedIn outreach, cold email, sales process, sales

From plugin
agentfactory-business-plugins
2997 skills30 agents8 commands
Install
$ npx -y skills add panaversity/agentfactory-business-plugins --skill gtm --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/gtm

Context preview

The summary Claude sees to decide when to auto-load this skill.

Activate for: go to market, GTM, GTM strategy, go-to-market, ICP, ideal customer profile, target customer, who to sell to, channel strategy, sales channel, how to acquire customers, customer acquisition, outreach strategy, LinkedIn outreach, cold email, sales process, sales

SKILL.md

gtm.SKILL.md
name: gtm
description: >
  Activate for: go to market, GTM, GTM strategy, go-to-market, ICP, ideal
  customer profile, target customer, who to sell to, channel strategy, sales
  channel, how to acquire customers, customer acquisition, outreach strategy,
  LinkedIn outreach, cold email, sales process, sales funnel, pricing strategy,
  price point, pricing tiers, positioning statement, positioning, how to position,
  first customers, early adopters, 90-day plan, launch plan, customer success,
  onboarding, retention.
  NOT for: customer discovery (use discovery), competitive analysis (use market),
  unit economics (use financials), pitch deck (use pitch).
license: Apache-2.0
metadata:
  author: Panaversity
  version: "1.0"
  plugin-commands: "/gtm"

CONTEXT LOADING

Before executing, check for `innov.local.md` in the working directory. If found, extract:

  • venture: name, stage, type, target_customer
  • customer_profiles: personas, pains, gains, WTP, buying_process
  • competitive_landscape: differentiation, moat_building
  • financial_model: unit_economics (CAC, LTV, pricing)

If `innov.local.md` is not found: Continue with conversation context. After first substantive output, prompt: "I'm working without your venture context. Run Exercise 8 from Chapter 40 to build innov.local.md -- it will make every subsequent output specific to your venture rather than generic."

STAGE-AWARE CALIBRATION

Check venture.stage and calibrate:

  • IDEA: Warning -- "GTM strategy at the IDEA stage is premature. You don't have an ICP grounded in customer evidence yet. Consider running /discovery first."
  • DISCOVERY: Warning -- "You don't have a validated ICP yet. GTM strategy requires knowing who your customer is, what triggers their buying, and how they evaluate solutions. Complete discovery first."
  • VALIDATION: GTM planning is appropriate -- you should be defining your ICP from validated customer data.
  • MVP: This is your focus stage. GTM should be specific, measured, and iterated weekly.
  • GROWTH: This is your focus stage for scaling what works.

DLA PROGRESSION CHECK

If no customer_profiles with validated data exist in innov.local.md: "You are building a GTM strategy without validated customer profiles. Your ICP will be based on guesses rather than evidence. Consider running /discovery to ground your ICP in real customer data."

GO-TO-MARKET WORKFLOW

Task Types

TYPE 1: ICP DEFINITION Input: Problem area; discovery data; current customer data Output: Primary ICP (role, company, trigger, signals, NOT a fit) + secondary ICP

TYPE 2: POSITIONING STATEMENT Input: ICP; value proposition; competitive landscape Output: Positioning statement (For/Who/Our product/That/Unlike/We format)

TYPE 3: CHANNEL STRATEGY Input: ICP; team constraints; budget; existing assets Output: Channels ranked by CAC efficiency; Week 1 activation for each

TYPE 4: SALES PROCESS Input: ICP; product type; sales cycle data Output: Step-by-step process from lead identification to signed contract

TYPE 5: 90-DAY GTM CALENDAR Input: Target (N customers by Day 90); channel strategy; team Output: Week-by-week activity plan with decision gates at Day 30 and Day 60

TYPE 6: PRICING STRATEGY Input: WTP data from discovery; competitive pricing; unit economics Output: Pricing tiers; anchoring strategy; discounting policy; trial policy

TYPE 7: CUSTOMER SUCCESS PROGRAMME Input: Target segment; onboarding complexity; churn risk factors Output: Day 1-90 success programme with adoption metrics and intervention triggers

ICP Output Structure

IDEAL CUSTOMER PROFILE (ICP)
Venture: [Name] | Version: [N] | Based on: [N discovery interviews + N customers]
================================================================
PRIMARY ICP:
  Company:
    Sector:       [Specific -- not "all industries"]
    Size:         [Revenue band OR headcount band]
    Geography:    [Region / country / city tier]
    Technology:   [What systems they use; what they do NOT use]
    Structure:    [Number of relevant staff; team maturity]

  Person:
    Role:         [Job title -- be specific; CFO != VP Finance != Controller]
    Seniority:    [Level; direct reports; budget authority]
    Cares about:  [Their top 3 professional priorities right now]
    How they buy: [Solo / committee; budget cycle; evaluation process]

  Buying Trigger:
    [The specific event that makes them ready to buy RIGHT NOW]
    Why trigger matters: Customers without a trigger browse but don't buy.

  Signals (how to identify ICP prospects):
    [What they post; what groups they join; what events they attend]

  NOT a fit (explicitly exclude):
    [Who wastes your time -- be specific; saves sales team hours]

SECONDARY ICP (if applicable):
  [Same structure]

ICP CONFIDENCE: [LOW / MEDIUM / HIGH] -- based on [N] paying customers
Next validation: [What ICP assumption still needs more customer data]
================================================================

Positioning Statement Format

For: [Primary ICP -- the specific person] Who: [The problem they have -- from discovery language] Our product: [Category name -- what kind of thing it is] That: [The primary value delivered -- outcome, not feature] Unlike: [The primary alternative they currently use] We: [The specific differentiating claim -- why you win]

Channel Strategy Framework

CHANNEL ARCHETYPES:

FOUNDER-LED OUTREACH (early stage; months 1-6): CAC: Low (founder time) | Scale: Low | Speed: Fast Best for: ICP refinement; first 10 customers

CONTENT / THOUGHT LEADERSHIP (months 3-12): CAC: Medium-low | Scale: Medium | Speed: Slow to start; compounds Best for: Building inbound pipeline over 6-12 months

COMMUNITY AND ASSOCIATIONS (months 3-9): CAC: Medium | Scale: Medium | Speed: Medium Best for: Warm introductions in trust-based markets

REFERRAL PROGRAMME (months 6+): CAC: Low | Scale: Medium | Speed: Depends on customer base Best for: Once you have 10+ happy customers

INSIDE SALES (months 9-18; requires f

Read more
Ships withagentfactory-business-plugins

🚀 Marketplace of domain-specific plugins for building enterprise AI agents. Enable AI agents to perform finance, banking, legal, and sales workflows using modular domain plugins.

Get the whole plugin