Use when launching a product, entering a new market, or repositioning an existing offering to reach paying customers
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill design-go-to-market --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Design Go To Market?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-design-go-to-market)More formats (shields.io, HTML) on the badges page.
---
name: design-go-to-market
description: Use when launching a product, entering a new market, or repositioning an existing offering to reach paying customers
source: Geoffrey Moore "Crossing the Chasm" (1991); Steve Blank "The Four Steps to the Epiphany"
tags: [go-to-market, product-launch, distribution, market-segmentation, positioning]
related: [apply-diffusion-of-innovations]
verified: true
---
# Design Go-to-Market
Build a focused launch plan that moves a product from concept to paying customers in a defined segment.
## Why This Is Best Practice
**Adopted by:** Salesforce, HubSpot, Andreessen Horowitz portfolio companies
**Impact:** Moore's "whole product" model shows that B2B startups crossing the chasm succeed 3× more often when they dominate a single beachhead before expanding
**Why best:** Most failed launches spread effort across too many segments simultaneously. Concentrating on one beachhead segment lets you build a complete solution, generate referenceable customers, and create word-of-mouth before expanding.
## Steps
1. **Define the beachhead segment** — Identify a single, reachable customer group with a hair-on-fire problem your product solves completely. The segment should be small enough to dominate but large enough to sustain initial revenue.
2. **Map the buyer journey** — Document each stage from awareness to purchase to retention. Identify who influences, who decides, and who pays.
3. **Craft the positioning statement** — Use the template: "For [segment] who [need], [product] is a [category] that [key benefit], unlike [alternative] which [weakness]."
4. **Select distribution channels** — Choose channels where your segment already shops (direct sales, PLG, marketplaces, partners). Validate cost-per-acquisition fits unit economics.
5. **Define the whole product** — List everything a customer needs to achieve the promised outcome: integrations, support, training, professional services. Fill gaps before launch.
6. **Set launch metrics** — Define leading indicators (trial signups, activation rate) and lagging indicators (paid conversions, net revenue retention) with 30/60/90-day targets.
7. **Build the sales motion** — Write talk tracks, objection responses, and a competitive battle card. Train anyone who speaks to customers.
8. **Execute and iterate** — Run the launch, measure against targets weekly, and adjust channel or message before scaling spend.
## Rules
- Never target more than one beachhead segment in the first launch cycle.
- Positioning must be written before any marketing copy is created.
- Distribution channel must reach the segment without requiring behavior change from the buyer.
- Whole product gaps must be resolved, not roadmapped, before GA launch.
- Metrics must include both acquisition and retention signals from day one.
## Examples
Slack launched exclusively to developers at technology companies before expanding. They nailed activation (team creates a channel, sends 2,000 messages) as their conversion metric — a concrete whole-product signal that the product was delivering value.
## Common Mistakes
- **Boiling the ocean** — Listing five target segments dilutes message and sales focus; no segment feels the product is built for them.
- **Skipping the whole product** — Launching with missing integrations forces customers to do workarounds, killing referrals.
- **Vanity launch metrics** — Tracking press mentions instead of activation rate masks whether the product actually delivers value.
## When NOT to Use
- Do not run a full GTM process for an internal tool or productivity feature with no external customers — the beachhead and distribution channel steps do not apply when the "buyer" is a fixed internal team.
- Do not use this framework when the product has not yet achieved problem-solution fit; launching with a GTM plan before validating that the product solves the problem burns distribution budget on a message that will change.
- Do not apply the single-beachhead constraint to a platform business where multi-sided network effects require simultaneously acquiring supply and demand — forcing one beachhead in that context prevents the minimum viable network from forming.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!