Find and own a defensible market position. Use when messaging sounds like competitors, conversion is weak despite awareness, repositioning a product, or testing positioning claims. Includes Crawl-Walk-Run rollout methodology and the word change that improved enterprise deal progression.
npx skills add https://github.com/github/awesome-copilot --skill gtm-positioning-strategy
Find and own a defensible market position. Turn generic messaging into clear differentiation — or at least test whether your differentiation actually resonates before committing to it.
Triggers:
Context:
The Pattern:
Early enterprise conversations for an autonomous AI product. Positioned as "autonomous AI agent."
Developers: "Cool, but scary."
Managers: "Will this replace our team?"
Deal progression: Slow. Lots of "we'll think about it."
The Change:
One word: "autonomous" → "AI teammate"
Same product. Same capabilities. Different framing.
Result:
Developers: "This helps me."
Managers: "This makes my team more productive."
Deal progression: Measurably faster.
Why This Matters:
Positioning isn't what you do. It's what you don't say.
We could've said "replaces developers" (technically true for some tasks). Would've killed every enterprise deal.
The Framework: Word Choice Shapes Buyer Psychology
Words that scare enterprises:
Words that convert:
How to Test Word Choice:
Don't guess. Test.
Test 1: Outbound Email A/B
Test 2: Website Homepage A/B
Test 3: Sales Call Scripts
Common Mistake:
Changing positioning based on internal consensus, not customer feedback. Your team isn't the buyer.
The Pattern:
Positioning changes create risk. Brand confusion. Sales misalignment. Customer churn (if existing customers don't recognize you).
De-risk through phased rollout:
Crawl Phase (1-2 weeks): Validation
Test messaging without committing product/org resources.
Actions:
Measurement:
Go/No-Go:
Walk Phase (2-3 weeks): Alignment
If testing validates, align product and sales to new positioning (but don't rebrand publicly yet).
Actions:
Measurement:
Go/No-Go:
Run Phase (2-3 weeks and ongoing): Scale
Full commitment. This is the rebrand.
Actions:
Measurement:
Common Mistakes:
The Pattern:
If your messaging closely resembles competitors' messaging, you have a positioning problem, not a product problem.
Positioning Failure Manifests As:
How to Execute:
Step 1: Competitor Messaging Audit
Example:
If everyone says "fastest," "most reliable," "easiest to use" — these are table stakes, not differentiation.
Step 2: Assess Your Actual Strengths
Step 3: Find Under-Served Position
Step 4: Stake a Clear Claim
Must be:
Common Mistakes:
Layer 1: Market Context
Example:
"Infrastructure teams manage increasingly complex deployments across hybrid environments. Organizations adopt microservices and distributed systems. This creates operational complexity that traditional monitoring tools can't handle."
Layer 2: Positioning Statement (1-2 sentences)
Example:
"We help platform teams ship faster through [core capability] that connects [workflow A], [workflow B], and [business outcome] in real-time."
Layer 3: Narrative
Expand positioning into story:
How to Execute:
Write all three layers before testing. Test Layer 2 (positioning statement) first with Crawl-Walk-Run methodology. If that validates, build out Layer 3.
Principle: Clear positioning requires testable structure: headline (what are you?) + sub-headline (for whom? why?).
Main Headline Formats:
Examples:
Red Flags:
Sub-headline Purpose:
Clarifies who, why, how it's different from status quo.
Examples:
How to Test:
A/B test headline + sub-headline combinations:
Measure CTR, reply rates, conversion.
Pick winner based on data, not opinion.
Principle: A positioning is only valuable if competitors can't easily copy it.
Defensibility Hierarchy:
1. Structural Advantage (Strongest)
2. Market Position (Strong if First)
3. Product Feature (Weak)
How to Assess:
For each positioning claim, ask:
Common Mistake:
Positioning on features competitors can easily match. This creates positioning treadmill — you're always defending, never owning.
Is brand awareness strong but conversion weak?
├─ Yes → Positioning problem, test new angles
└─ No → Continue...
│
Does our messaging sound like competitors?
├─ Yes → Positioning problem
└─ No → Not a positioning issue
Do we have structural advantage competitors can't copy?
├─ Yes → Position on structural advantage
└─ No → Continue...
│
Are we first in a category?
├─ Yes → Position on category ownership
└─ No → Find under-served segment/use case
Did new positioning outperform incumbent by 20%+?
├─ Yes → Move to Walk (alignment phase)
└─ No → Continue...
│
Did we run test long enough (2+ weeks)?
├─ No → Run longer
└─ Yes → Try different positioning angle or stay with incumbent
1. Claiming to be "better" at what everyone does
2. Positioning on easily-copied features
3. Waiting for perfect product before positioning shift
4. Testing too many positioning angles simultaneously
5. Skipping validation phase
6. One positioning for all buyer personas
7. Generic positioning that doesn't differentiate
Crawl-Walk-Run Testing:
Word choice that converts:
Positioning audit steps:
Defensibility hierarchy:
Testing hierarchy (signal strength):
*Based on positioning work at AI agent and developer platforms, including navigating the framing spectrum from "autonomous" to "AI companion" and how category framing changes enterprise buyer perception. Also includes Crawl-Walk-Run rollout methodology from repositioning products without breaking existing customer recognition. Not theory — patterns from testing positioning before committing to rebrands.*
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.
Take github/gtm-positioning-strategy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.