agentleFS
jpoindexterjpoindexter/Vanta/.claude/skills/gtm-builder/skill.md

gtm-builder

Skill2 starsChanged 5 months agoMITView on GitHub

Scale-stage skill: builds GTM function resources from scratch — market segmentation, messaging architecture, sales playbook, analyst/investor narrative. Use when someone says: build GTM, go to market, sales playbook, messaging, market segmentation, investor narrative, analyst briefing, enterprise sales, grow beyond organic.

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:

    Before running GTM Builder, have:

    line 16
  2. Distinctive:

    Write the moat narrative as: "Here's what we've built over [time period] that a competitor starting today couldn't replicate in under two …

    line 164
  3. Distinctive:

    Don't build the GTM execution layer until the strategy layer is locked.

    line 249

≈ “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

GTM Builder

Scale-stage go-to-market function builder. Takes a product with validated PMF and builds the commercial infrastructure to grow it beyond founder-led organic traction.

The Failure Mode This Prevents

Organic growth has a ceiling, and most Scale-stage founders hit it before they've ever had to build a real GTM function. Signs: flattening user curves, rising customer acquisition costs, pipeline that only moves when the founder is personally involved. Founder hustle got you here, but scaling requires creating and implementing an actual go-to-market strategy. AI can help you build, then run, that complete GTM engine — but you have to actually design it first.

Inputs Required

Before running GTM Builder, have:

  1. Validated problem hypothesis (from problem-hypothesis)
  2. Current ICP definition (from customer discovery data)
  3. Core value proposition (what the product does and for whom)
  4. Current acquisition channels and their unit economics (CAC, LTV, payback period)
  5. Current customer base — size, segments, use cases
  6. Top 3 competitors and their positioning
  7. Pricing model

Phase 1 — Market Segmentation

Most founders have a vague ICP. GTM requires a precise one — not because precision is philosophically better, but because every piece of GTM collateral requires a specific audience to be effective. "SMBs in fintech" can't be converted; "finance managers at Series A–C SaaS startups managing 5–50-person teams without a dedicated FP&A hire" can.

Segmentation dimensions:

Firmographic:

  • Industry (primary + adjacent)
  • Company stage / headcount / revenue
  • Business model (B2B/B2C/marketplace)
  • Geography (if relevant to the product)

Technographic:

  • Stack signals that correlate with ICP fit (what tools they use)
  • Maturity signals (DIY vs. buying solutions)

Behavioral:

  • How they currently solve the problem (proxy for urgency and switching cost)
  • Where they search for solutions
  • What content they consume

Segment prioritization matrix:

SegmentSizeProblem UrgencyCAC (est.)LTV (est.)Strategic Value
Primary
Secondary
Future

Rank by (problem urgency × LTV) / CAC. Primary segment is where all GTM energy goes first.

Buyer landscape mapping:

For the primary segment:

  • Who holds budget? (decision maker)
  • Who influences the decision? (champion, influencer, blocker)
  • Who uses the product? (end user — may not be the buyer)
  • What does each care about? (buyer: ROI/risk/compliance; champion: career/recognition; user: speed/quality-of-life)

Different messages for different roles. A champion-facing message that leads with "saves you 2 hours a week" and a buyer-facing message that leads with "reduces reconciliation errors by 40%" are about the same product.

Phase 2 — Messaging Architecture

Core message hierarchy:

Level 1 — Category: What game are you playing? Define the category you're in, or the new category you're creating.

"The [category] for [specific person]"

Level 2 — Value proposition: What specifically do you do for them?

"[Outcome] without [cost/tradeoff]"

Level 3 — Proof points: What makes that credible?

Three specific, falsifiable claims. Metrics > testimonials > features.

Level 4 — Differentiation: Why you vs. alternatives?

The one thing you do that competitors fundamentally can't (not won't — can't).

Message-by-audience matrix:

AudienceLead WithProof PointsCTA
Buyer/ExecutiveBusiness outcome, ROI, riskMetrics, case studies, complianceBook a call
Champion/ManagerCareer impact, team efficiencyTime saved, errors reducedStart a trial
End UserDaily workflow improvementSpeed, quality, easeSign up
AnalystMarket positioning, differentiationTAM, growth, technical moatAnalyst brief
InvestorCategory, moat, unit economicsRevenue metrics, retention, NRRInvestor deck

Messaging test: For each message, ask:

  • Does it speak to what the audience actually cares about (not what you wish they cared about)?
  • Is it falsifiable? Could a skeptic challenge it? Good — make it defensible.
  • Does it create urgency or just awareness?

Phase 3 — Sales Playbook

Playbook structure (minimum viable version):

Ideal Customer Profile Card: One page. Title, company profile, key identifiers, where to find them, typical objections, champion vs. buyer dynamics, deal timeline typical, average contract value range.

Qualification criteria: Define MEDDIC or equivalent for your deal type:

  • Metrics: What does "success" look like in numbers for this buyer?
  • Economic buyer: Who approves the spend?
  • Decision criteria: What does the buyer use to evaluate options?
  • Decision process: What are the steps from "interested" to "signed"?
  • Identify pain: Is the pain urgent, specific, and funded?
  • Champion: Who inside the account is advocating for your product?

Objection handling: For your top 5 objections, define: the underlying concern, the honest answer, the proof point.

ObjectionReal ConcernResponseProof
"We built something internally"Switching cost / NIH
"We're too small for this"Budget / fit
"We need to see more customers like us"Risk
"Let's revisit next quarter"Not urgent enough
"How do we know you'll be around?"Startup risk

Demo script: Define the demo flow as: problem statement → protagonist story → product walkthrough → specific outcome. The demo is a story, not a feature tour. The hero is the user, not the product.

Follow-up cadence: Define the exact sequence of touchpoints from first meeting to signed contract. No "follow up when it makes sense" — define the triggers and templates.

Phase 4 — Analyst and Investor Narrative

Analyst briefing structure:

Enterprise buyers will often check with analysts before signing multi-year contracts. Your analyst narrative needs to:

  1. Define the category you're in (or creating)
  2. Articulate the market problem and why now
  3. Position against alternatives (direct, indirect, DIY)
  4. Present your differentiation as structural, not feature-based
  5. Provide proof of traction (metrics, customer names if permissioned)

Investor metrics narrative:

By Scale stage, you're talking to growth investors, not seed investors. The metrics they care about:

  • ARR / MRR (and growth rate)
  • Net Revenue Retention (NRR) — the most important single number
  • CAC by channel
  • LTV by segment
  • Payback period
  • Gross margin
  • Rule of 40 (growth rate + profit margin ≥ 40%)

Build a one-page metrics narrative that shows: where you are, trajectory, and what the numbers reveal about your moat.

Moat narrative (1 page):

Answer the key question investors will ask: "If a well-funded incumbent copied your product today, would your users stay?"

Three sources of structural moat for an AI-native startup:

  1. Accumulated user data and behavioral fingerprints (time-locked, can't be bought)
  2. Domain expertise encoded in the product (industry-specific logic, edge cases, integrations)
  3. Workflow lock-in (the deeper users build their workflows around your product, the higher the switching cost)

Write the moat narrative as: "Here's what we've built over [time period] that a competitor starting today couldn't replicate in under two years — and here's why."

Phase 5 — GTM Execution Layer

Once strategy is defined, build the operational execution layer:

Content pipeline:

  • Content types by audience (thought leadership for analysts, case studies for buyers, how-to for users)
  • Publication cadence
  • Distribution channels

Outbound sequences:

  • ICP-specific outreach sequences (not generic)
  • Follow-up logic
  • Re-engagement triggers

CRM hygiene:

  • Pipeline stages defined
  • Stage-specific follow-up triggers
  • Reporting cadence

Metrics reporting:

  • Weekly GTM brief: pipeline, CAC by channel, conversion rates, content performance
  • Monthly board narrative

Output Format

## GTM Plan

**Product:** [Name]
**Stage:** Scale
**Date:** [Date]

---

### Primary Segment

**ICP Definition:** [Specific, not vague]
**Buyer Landscape:** [Decision maker / champion / user / blocker]
**Where to Find Them:** [Channels, communities, events]

---

### Messaging Architecture

**Category:** [What game you're playing]
**Core Value Prop:** [Outcome without tradeoff]
**Top 3 Proof Points:** [Specific, falsifiable]
**Key Differentiator:** [What you can do that competitors fundamentally can't]

**Message-by-Audience Matrix:**
[Table]

---

### Sales Playbook

**ICP Card:** [One-paragraph]
**Qualification Criteria:** [MEDDIC or equivalent]
**Top 5 Objections + Responses:** [Table]
**Demo Story:** [Problem → protagonist → product → outcome]
**Follow-up Sequence:** [Defined cadence]

---

### Analyst and Investor Narrative

**Category Narrative:** [1 paragraph]
**Key Metrics:** [Current state + trajectory]
**Moat Narrative:** [1 paragraph — what competitors can't replicate in 2 years]

---

### Execution Priorities (Next 90 Days)

| Initiative | Owner | Timeline | Success Metric |
|-----------|-------|----------|----------------|
| | | | |

Rules

  • Segment before messaging. Generic messaging is indistinguishable from noise. If the message works for everyone, it resonates with no one.
  • The moat narrative must be specific. "We have a better product" is not a moat. "We have 18 months of behavioral data from 5,000 users in regulated industries that trained our edge-case logic" is a moat.
  • Don't build the GTM execution layer until the strategy layer is locked. Automating outreach for the wrong message just means you burn your list faster.
  • Revenue metrics are the only honest PMF evidence at Scale stage. Everything else is a leading indicator.

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.