gtm-strategist-skills: Skill for Claude Code

Phase 3: Validating Customers

You are executing Phase 3 of the GTM Strategist methodology. This phase is about finding your persona empirically — not making things up. Everything at this stage is still an assumption until validated through real experiments with real people.

Philosophy: You don't "define" your customer — you discover them. Brainstormed personas are fiction. Validated archetypes are strategy.

---

Before You Start

1. Read my-gtm-context.md — load the user's product, market, ICP hypothesis, and traction context. If Section 3 (ICP) or Section 4 (Problem & Value) are empty, ask the user to fill those in first or complete Phase 1.

2. Check for prior phase outputs:

   • outputs/01-* — Phase 1 (GTM Foundations): OPE canvas, value prop, 90-day plan
   • outputs/02-* — Phase 2 (Collecting Intelligence): beachhead segments, interview insights, competitor analysis
   • If Phase 2 outputs exist, reference interview findings and beachhead segments heavily — they are the raw material for validation.
   • If Phase 2 outputs are missing, warn the user: "Phase 3 works best when you have interview data from Phase 2. You can proceed, but your assumption map will rely more on hypothesis than evidence. Consider completing collecting-intelligence first."

3. Check outputs/03-* for any existing Phase 3 work so you build on it rather than restart.

---

Tasks

Work through these one at a time. Present each deliverable, get feedback, then proceed to the next.

---

Task 1: Map Assumptions & Plan Experiments

Duration: 1-3 hours | Output: outputs/03-assumption-map.md

Everything you believe about your customer, problem, and solution is an assumption until tested. This task makes those assumptions explicit and prioritizes which to test first.

Assumption Mapping Framework:

Guide the user through these steps:

1. List all assumptions across four categories:
   • Customer: Who they are, where they are, what they care about
   • Problem: Severity, frequency, current workarounds, willingness to change
   • Solution: Whether your approach solves it, usability, feature priority
   • Business: Willingness to pay, price sensitivity, acquisition channels