gtm-positioning-strategy
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.
What this skill does
# 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.
## When to Use
**Triggers:**
- "Our messaging sounds exactly like competitors"
- "Brand awareness is strong but conversion is weak"
- "Sales team can't explain why we're different"
- "Buyers see us as interchangeable"
- "Should we reposition before we rebrand?"
- "How do we test positioning claims?"
**Context:**
- Competitive markets with similar offerings
- Messaging that isn't converting
- New product launches
- Repositioning existing products
- Sales team reports buyer confusion
---
## Core Frameworks
### 1. One Word Can Change Everything (The "Autonomous" Problem)
**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:**
- Autonomous (implies: no control, replacing humans)
- Replaces (threatens: job security)
- Fully automated (removes: human judgment)
- AI-first (means: unclear, buzzword)
**Words that convert:**
- Teammate (implies: collaboration, helping)
- Augments (helps: makes humans better)
- You stay in control (reassures: human oversight)
- Handles repetitive work (specific: saves time)
**How to Test Word Choice:**
Don't guess. Test.
**Test 1: Outbound Email A/B**
- Send 100 prospects Version A ("autonomous agent")
- Send 100 prospects Version B ("AI teammate")
- Measure: Reply rate, meeting booked rate
- Signal strength: High (real buyer intent)
**Test 2: Website Homepage A/B**
- Version A: Current positioning
- Version B: New word choice
- Measure: Click-through rate on key CTAs
- Duration: 1-2 weeks minimum
- Signal strength: Moderate (interest without commitment)
**Test 3: Sales Call Scripts**
- Half of AEs use positioning A
- Half use positioning B
- Measure: Demo-to-trial conversion
- Signal strength: High (real sales cycle)
**Common Mistake:**
Changing positioning based on internal consensus, not customer feedback. Your team isn't the buyer.
---
### 2. Test Before You Commit (Crawl-Walk-Run Positioning Rollout)
**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:**
- A/B test website headlines (new vs incumbent)
- Run two outbound email sequences (different positioning angles) to cold prospects
- Ask existing customers: "If we described ourselves as [new positioning], would you still recognize us?"
**Measurement:**
- Track CTR on web variants
- Track reply rates on outbound sequences
- Document qualitative feedback
**Go/No-Go:**
- At least one positioning variant outperforms incumbent by 20%+ on reply rate
- Existing customers don't say "wait, that's not what you do"
- Proceed if clear winner; if tied, run longer or test new angles
**Walk Phase (2-3 weeks): Alignment**
If testing validates, align product and sales to new positioning (but don't rebrand publicly yet).
**Actions:**
- Rewrite website copy (homepage, enterprise pages, CTAs)
- Create sales enablement: updated pitch deck, call scripts, email templates
- Update documentation to match new narrative
- Build use-case-specific examples
**Measurement:**
- Sales team feedback on messaging usability
- Website analytics on engagement (not conversion yet)
- Segment analysis (who's responding?)
**Go/No-Go:**
- Sales team says new messaging is easier to use
- CTR metrics improve vs incumbent
- No major customer confusion
- Proceed to Run
**Run Phase (2-3 weeks and ongoing): Scale**
Full commitment. This is the rebrand.
**Actions:**
- Launch dedicated landing pages per use case
- Outbound campaigns per positioning angle
- Update all customer-facing materials
- Train customer success team on new narrative
- Announce repositioning (if appropriate)
**Measurement:**
- Pipeline volume by positioning angle
- Win rate by positioning angle
- CAC efficiency by channel
- Customer retention (did we lose anyone?)
**Common Mistakes:**
- Skipping Crawl (jumping to full rebrand without validation)
- Running phases in parallel (creates confusion if messaging changes mid-rollout)
- Waiting for perfect product before repositioning (product should follow positioning, not precede it)
- Not measuring at each phase (can't determine if test "won")
---
### 3. Positioning Clarity Diagnosis
**The Pattern:**
If your messaging closely resembles competitors' messaging, you have a positioning problem, not a product problem.
**Positioning Failure Manifests As:**
- All competitors describe nearly identical value props
- Differentiation requires explaining complex technical details
- Buyers see offerings as interchangeable
- Marketing metrics (CTR, engagement) weak vs industry benchmarks
- Sales conversations get derailed by comparison questions
**How to Execute:**
**Step 1: Competitor Messaging Audit**
- Collect homepage headlines from 5-7 direct competitors
- Identify shared claims (these are commoditized)
- Map where competitors claim unique value
**Example:**
If everyone says "fastest," "most reliable," "easiest to use" — these are table stakes, not differentiation.
**Step 2: Assess Your Actual Strengths**
- What can you do that competitors can't, without massive R&D?
- What do your best customers choose you for? (Ask them)
- What structural advantages do you have? (Deployment model, data ownership, pricing, network effects, etc.)
**Step 3: Find Under-Served Position**
- Where do existing solutions fail users?
- What problem is everyone ignoring?
- What buyer segment is under-served?
**Step 4: Stake a Clear Claim**
Must be:
- Something you can own now (not future roadmap)
- Something competitors can't easily copy (structural advantage)
- Resonant with your best customer segments
**Common Mistakes:**
- Claiming you're "better" at what everyone does (unbelievable)
- Positioning on features competitors already have
- Multiple positions simultaneously (choose one)
- Waiting for perfect product before positioning shift
---
### 4. Market Positioning Architecture (Three Layers)
**Layer 1: Market Context**
- What problem is the market experiencing?
- Why is it experiencing this problem now?
- What happens if problem goes unsolved?
**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)**
- **Who we serve**: What customer segment?
- **What problem we solve**: The specific pain
- **How we're different**: Why we matter vs alternatives
- **Proof**: Why should they believe us?
**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:
- Why the world is changing
- Why existing solutions don't work
- Why our approach is better
- What the future looks like with us
**How to Execute:**
Write all three layers before testing. Test Layer 2 (positioningRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".