SkillAtlasSkill 详情

gtm-positioning-strategy

Powered by Awesome Copilot GitHub contributors from allcontributors.org

审核状态:已审核Quality 72Security 60

复制安装命令

用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。

复制前请先查看来源、License 和安全提示。

项目 README

来源文件:README.md

抓取于 2026年7月29日

🤖 Awesome GitHub Copilot

Powered by Awesome Copilot GitHub contributors from allcontributors.org

A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.

[!TIP] Explore the full collection on the website → awesome-copilot.github.com

The website offers full-text search and filtering across hundreds of resources, plus the Learning Hub for guides and tutorials.

Using this collection in an AI agent? A machine-readable llms.txt is available with structured listings of all agents, instructions, and skills.

📖 Learning Hub

New to GitHub Copilot customization? The Learning Hub on the website offers curated articles, walkthroughs, and reference material — covering everything from core concepts like agents, skills, and instructions to hands-on guides for hooks, agentic workflows, MCP servers, and the Copilot coding agent.

What's in this repo

ResourceDescriptionBrowse
🤖 AgentsSpecialized Copilot agents that integrate with MCP serversAll agents →
📋 InstructionsCoding standards applied automatically by file patternAll instructions →
🎯 SkillsSelf-contained folders with instructions and bundled assetsAll skills →
🔌 PluginsCurated bundles of agents and skills for specific workflowsAll plugins →
🍳 CookbookCopy-paste-ready recipes for working with Copilot APIs—

Install a Plugin

For most users, the Awesome Copilot marketplace is already registered in the Copilot CLI/VS Code, so you can install a plugin directly:

copilot plugin install <plugin-name>@awesome-copilot

If you are using an older Copilot CLI version or a custom setup and see an error that the marketplace is unknown, register it once and then install:

copilot plugin marketplace add github/awesome-copilot
copilot plugin install <plugin-name>@awesome-copilot

Contributing

See CONTRIBUTING.md · AGENTS.md for AI agent guidance · Security · Code of Conduct

The customizations here are sourced from third-party developers. Please inspect any agent and its documentation before installing.

Contributors ✨

Thanks goes to these wonderful people (emoji key):


Aaron Powell

Matt Soucoup

Troy Simeon Taylor

Abbas

Peter Strömberg

Daniel Scott-Raynsford

John Haugabook

Pavel Simsa

Harald Kirschner

Muhammad Ubaid Raza

Tom Meschter

Aung Myo Kyaw

JasonYeMSFT

Jon Corbin

troytaylor-msft

Emerson Delatorre

Burke Holland

Kent Yao

Daniel Meppiel

Gordon Lam

Mads Kristensen

Shinji Takenaka

spectatora

Yohan Lasorsa

Vamshi Verma

James Montemagno

Alessandro Fragnani

Ambily

krushideep

devopsfan

Tugdual Grall

Oren Me

Mike Rousos

Justin Yoo

Guilherme do Amaral Alves

Griffin Ashe

Ashley Childress

Adrien Clerbois

ANGELELLI David

Mark Davis

Matt Vevang

Maximilian Irro

NULLchimp

Peter Karda

Saul Dolgin

Shubham Gaikwad

Theo van Kraay

Tianqi Zhang

Will 保哥

Yuta Matsumura

anschnapp

hizahizi-hizumi

黃健旻 Vincent Huang

Bruno Borges

Steve Magne

Shane Neuville

André Silva

Allen Greaves

Amelia Payne

BBoyBen

Brooke Hamilton

Christopher Harrison

Dan

Dan Wahlin

Debbie O'Brien

Ed Harrod

Genevieve Warren

Guillaume

Henrique Nunes

Jeremiah Snee

Kartik Dhiman

Kristiyan Velkov

msalaman

Per Søderlind

Peter Smulovics

Ravish Rathod

Rick Smit

Rob Simpson

Robert Altman

Salih

Sebastian Gräf

Sebastien DEGODEZ

Sergiy Smyrnov

SomeSolutionsArchitect

Stu Mace

Søren Trudsø Mahon

Tj Vita

Peli de Halleux

Paulo Morgado

Paul Crane

Pamela Fox

Oskar Thornblad

Nischay Sharma

Nikolay Marinov

Nik Sachdeva

Nick Taylor

Nick Brady

Nathan Stanford Sr

Máté Barabás

Mike Parker

Mike Kistler

Giovanni de Almeida Martins

이상현

Ankur Sharma

Wendy Breiding

voidfnc

shane lee

sdanzo-hrb

sauran

samqbush

pareenaverma

oleksiyyurchyna

oceans-of-time

kshashank57

Meii

factory-davidgu

dangelov-qa

BenoitMaucotel

benjisho-aidome

Yuki Omoto

Will Schultz

Waren Gonzaga

Vincent Koc

Victor Williams

Ve Sharma

Vasileios Lahanas

Udaya Veeramreddygari

Tài Lê

Tsubasa Ogawa

Troy Witthoeft (glsauto)

Gerald Versluis

George Dernikos

Gautam

Furkan Enes

Florian Mücke

Felix Arjuna

Eldrick Wega

Dobri Danchev

Diego Gamboa

Derek Clair

David Ortinau

Daniel Abbatt

CypherHK

Craig Bekker

Christophe Peugnet

Christian Lechner

Chris Harris

Artem Saveliev

Antoine Rey

Ankit Das

Aline Ávila

Alexander Martinkevich

Aleksandar Dunchev

Alan Sprecacenere

Akash Kumar Shaw

Abdi Daud

AIAlchemyForge

4regab

Miguel P Z

Michael Fairchild

Michael A. Volz (Flynn)

Michael

Mehmet Ali EROL

Max Prilutskiy

Matteo Bianchi

Mark Noble

Manish Jayaswal

Luke Murray

Louella Creemers

Sai Koumudi Kaluvakolanu

Kenny White

KaloyanGenev

Kim Skov Rasmussen

Julien Dubois

José Antonio Garrido

Joseph Gonzales

Jorge Balderas

John Papa

John

Joe Watkins

Jan de Vries

Jakub Jareš

Jackson Miller

Ioana A

Hunter Hogan

Hashim Warren

Gonzalo

Gisela Torres

Shibi Ramachandran

lupritz

Héctor Benedicte

Ted Vilutis

Anthony Shaw

Chris McKee

CASTResearchLabs

白水淳

Imran Siddique

共产主义接班人

Ivan Charapanau

Tadas Labudis

Alvin Ashcraft

Jan Krivanek

Gregg Cochran

Josh N

ian zhang

Garrett Siegel

Roberto Perez

Dan Velton

Lee Reilly

Daniel Coelho

Vahid Faraji

Ashley Wolf

Noah Jenkins

Jeremy Kohn

Harri Sipola

Toru Makabe

Pham Tien Thuan Phat

Benji Shohet

Amaury Levé

Tim Deschryver

Mohammad Asad Alahmadi

fondoger

Yuval Avidani

Csaba Iváncza

Tim Heuer

lance2k

Andrea Liliana Griffiths

Ajith Raghavan

Catherine Han

Igor Shishkin

Burrito Verde

Joseph Van der Wee

Luiz Bon

Sanjay Ramassery Babu

Russ Rimmerman [MSFT]

Roberto Perez

Shehab Sherif

Smit Patel

Steven Vore

Subhashis Bhowmik

Tim Mulholland

Niels Laute

Pavel Sulimau

PrimedPaul

Zhiqi Pu

Ramyashree Shetty

ZdaPhp

pigd0g

rahulbats

suyask-msft

tagedeep

tinkeringDev

Travis Hill

Utkarsh patrikar

Yauhen

Yiou Li

Yuki Omoto

Abhi Bavishi

augustus-0

Branislav Buna

connerlambden

David Raygoza

Diego Porto Ritzel

Eric Scherlinger

Fatih

Felipe Pessoto

François

Geoffrey Casaubon

Anddd7

Anders Eide

Aymen

Kevin van Zonneveld

Luis Cantero

MV Karan

Marcel Deutzer

Jon Galloway

Josh Beard

Julian

Simon Kurtz

Temitayo Afolabi

JoeVenner

Pasindu Premarathna

ecosystem

Punit

Onur Senturk

Andrew Stellman

Jeonghoon Lee

Satya K

Samik Roy

Simina Pasat

Tyler Garner

Vijay Chegu

DTIBeograd

Anmol Behl

Brad Kinnard

Chad Bentz

Marcello Cuoghi

Josh Johanning

jennyf19

Saravanan Rajaraman

Patel Dhruv

Renee Noble

jjpinto

moeyui1

mohammadali2549

Vladislav Guzey

aparna198809

Ed McAdams

Emil Andersson

Mikael

Mrigank Singh

Jim Bennett

Alishahzad1903

Antonio Villanueva

Tim Hanewich

ming

Scott O'Hara

Salih

Shailesh

Shubham Jiyani

Srinivas Vaddi

Philippe D

Rajesh Goldy

dstrupl

wuwen

Tilak Patel

Vijay Bandi

Zixuan Jiang

Dennis Lembree

Dev Shah

Falco

AJ

Anush

Ayush Saklani

Carlos Alexandro Becker

Mangokernel

Mario Codes

Gonzalo Fleming

Steve Magne

Sertxito

Rayner Zeng

ilderaj

mvanderbend-msoft

Parveen Sharma

pmorong

vinod kumar

Vidhart Bhatia

Xiaoyun Ding

denis-a-evdokimov

Adriano Nogueira

Aezan

Andy Anderson

Kweku Dzata

Marcel

Navaneeth Reddy

James

Joseph Counts

Neha Mandge

Srikanth Patchava

Thomas Ray

Nixon Kurian

Petr Stupka

Pieter de Bruin

sudeepghatak

tlietz

dawright22

Alejandro Fernando Suarez Gomez

Burak Bayır

MUHAMMAD SAMIULLAH

Nikola Metulev

Joseph Kasprzyk

Lovy Jain

kimtth

Akash Dwivedi

Suren K
Add your contributions

This project follows the all-contributors specification. Contributions of any kind welcome!

📚 Additional Resources

™️ Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

测试与质量文档与办公

高风险

  • 来源需自行核对维护者身份。
  • 未检测到明显脚本安装指令。
  • 可能需要外部 token、网络权限或第三方服务。
  • 存在潜在风险命令,请谨慎安装。
  • 扫描发现:2 条。

Codex — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/github/awesome-copilot.git
  3. 将 "skills/gtm-positioning-strategy" 文件夹复制到 Codex 的 skills 目录中。
  4. 重启 Codex 让新的 skill 生效。

Codex — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Codex 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Codex 让新的 skill 生效。

Claude Code — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/github/awesome-copilot.git
  3. 将 "skills/gtm-positioning-strategy" 文件夹复制到 Claude Code 的 skills 目录中。
  4. 重启 Claude Code 让新的 skill 生效。

Claude Code — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Claude Code 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Claude Code 让新的 skill 生效。

Cursor — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/github/awesome-copilot.git
  3. 将 "skills/gtm-positioning-strategy" 文件夹复制到 Cursor 的 skills 目录中。
  4. 重启 Cursor 让新的 skill 生效。

Cursor — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Cursor 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Cursor 让新的 skill 生效。

GitHub Copilot — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/github/awesome-copilot.git
  3. 将 "skills/gtm-positioning-strategy" 文件夹复制到 GitHub Copilot 的 skills 目录中。
  4. 重启 GitHub Copilot 让新的 skill 生效。

GitHub Copilot — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 GitHub Copilot 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 GitHub Copilot 让新的 skill 生效。

Windsurf — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/github/awesome-copilot.git
  3. 将 "skills/gtm-positioning-strategy" 文件夹复制到 Windsurf 的 skills 目录中。
  4. 重启 Windsurf 让新的 skill 生效。

Windsurf — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Windsurf 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Windsurf 让新的 skill 生效。
查看 SKILL.md 原文
name: gtm-positioning-strategy
description: 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.
license: MIT
metadata:
  author: Smit Patel (https://linkedin.com/in/smitkpatel)
  source: https://github.com/beingsmit/technical-product-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.

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 (positioning statement) first with Crawl-Walk-Run methodology. If that validates, build out Layer 3.


5. Headline and Sub-headline Testing

Principle: Clear positioning requires testable structure: headline (what are you?) + sub-headline (for whom? why?).

Main Headline Formats:

  • "The [adjective] [category] that [differentiator]"
  • "[Product] for [specific use case]"
  • "[Product] that [core benefit]"

Examples:

  • "The customizable platform for [workflow]"
  • "Infrastructure for autonomous teams"
  • "The enterprise-grade alternative to [incumbent]"

Red Flags:

  • Using competitor name (defensive, not confident)
  • Too technical (buyer won't understand)
  • Claiming multiple benefits (choose one)
  • Vague ("the future of X" — unbelievable)

Sub-headline Purpose:

Clarifies who, why, how it's different from status quo.

Examples:

  • "Deploy anywhere. Scale instantly. Your infrastructure, your rules."
  • "For teams drowning in repetitive work. Automation that handles the 80%, humans handle the 20%."
  • "Enterprise-grade. No lock-in. Works with your existing stack."

How to Test:

A/B test headline + sub-headline combinations:

  • Variant A: Current messaging
  • Variant B: New positioning angle
  • Variant C: Different differentiation claim

Measure CTR, reply rates, conversion.

Pick winner based on data, not opinion.


6. Positioning Defensibility Assessment

Principle: A positioning is only valuable if competitors can't easily copy it.

Defensibility Hierarchy:

1. Structural Advantage (Strongest)

  • Hard to copy: unique data ownership, deployment flexibility, pricing model, network effects
  • Example: "Built for regulated industries with on-prem deployment" (can't copy without rebuilding architecture)

2. Market Position (Strong if First)

  • Defensible if you own it first and scale
  • Example: "First AI platform for [specific workflow]" (copycats look derivative)

3. Product Feature (Weak)

  • Easy to copy: UX, specific capability
  • Example: "Faster API calls" (competitor ships speed improvement in 6 weeks)

How to Assess:

For each positioning claim, ask:

  1. Can competitor copy this with single product sprint? (Yes = not defensible)
  2. Do we have structural advantage? (No = temporary positioning)
  3. Is this credible given current product? (No = don't claim it yet)
  4. Can we own this position before competitors react? (No = too slow)

Common Mistake:

Positioning on features competitors can easily match. This creates positioning treadmill — you're always defending, never owning.


Decision Trees

Should We Reposition?

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

Which Positioning Angle Should We Test?

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

Should We Move from Crawl to Walk Phase?

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

Common Mistakes

1. Claiming to be "better" at what everyone does

  • Unbelievable. Find different angle.

2. Positioning on easily-copied features

  • Competitors will match. Need structural advantage.

3. Waiting for perfect product before positioning shift

  • Product work should follow positioning, not precede

4. Testing too many positioning angles simultaneously

  • Can't determine what's working. Test one at a time.

5. Skipping validation phase

  • Jumping to full rebrand without testing = risk

6. One positioning for all buyer personas

  • Different personas care about different things

7. Generic positioning that doesn't differentiate

  • "Best-in-class," "innovative" = meaningless

Quick Reference

Crawl-Walk-Run Testing:

  • Crawl (1-2 weeks): A/B test messaging, measure reply rates
  • Walk (2-3 weeks): Align sales/product to winning angle
  • Run (ongoing): Full repositioning, measure pipeline/conversion

Word choice that converts:

  • ✅ Teammate, augments, you stay in control
  • ❌ Autonomous, replaces, fully automated

Positioning audit steps:

  1. Collect competitor messaging
  2. Identify your actual strengths (ask customers)
  3. Find under-served position
  4. Stake clear, defensible claim

Defensibility hierarchy:

  1. Structural advantage (unique data, deployment flexibility, pricing model)
  2. Market position (category ownership)
  3. Product feature (weakest, easily copied)

Testing hierarchy (signal strength):

  1. Outbound reply rates (highest)
  2. Sales call conversion (high)
  3. Website CTR (moderate)

Related Skills

  • ai-gtm: AI-specific positioning (copilot vs agent vs teammate)
  • technical-product-pricing: Price as a positioning signal
  • 0-to-1-launch: Positioning for new product launches

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.

发现问题?提交给管理员复核

评分:

评论 (0)

暂无评论,成为第一个评论者吧!