Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
.claude/skills/gtm-positioning-strategy/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-18 | ✗→✓ | ▲ Improved | — | — |
| case-12 | ✗→✓ | ▲ Improved | — | — |
| case-08 | ✗→✓ | ▲ Improved | — | — |
| case-11 | ✗→✓ | ▲ Improved | — | — |
| case-15 | ✗→✓ | ▲ Improved | — | — |
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 issueDo 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 caseDid 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 incumbent1. 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.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-18 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-23 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted. The headline lift of +39 percentage points is the difference between those two pass rates over the 23 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.