MR
Mayur Rathi
@github
⭐ 34.1k GitHub stars

Gtm-Positioning-Strategy

Gtm-Positioning-Strategy是一款code方向的AI技能,核心价值是Find and own a defensible market position,可用于解决开发者在code领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。

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

Last verified on: 2026-05-30
mkdir -p ./skills/gtm-positioning-strategy && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/gtm-positioning-strategy/SKILL.md -o ./skills/gtm-positioning-strategy/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# 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

🎯 Best For

  • QA engineers
  • Developers writing unit tests
  • Claude users
  • GitHub Copilot users
  • Software engineers

💡 Use Cases

  • Generating test cases for edge conditions
  • Writing integration test suites
  • Code quality improvement
  • Best practice enforcement

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Gtm-Positioning-Strategy to Your Work

    Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.

  4. 4

    Review and Refine

    Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.

❓ Frequently Asked Questions

Does this generate test mocks?

Many testing skills include mock generation. Check the install command and skill content for details.

Is Gtm-Positioning-Strategy compatible with Cursor and VS Code?

Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.

Do I need specific dependencies for Gtm-Positioning-Strategy?

Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.

How do I install Gtm-Positioning-Strategy?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/gtm-positioning-strategy/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Not testing edge cases

AI tends to generate happy-path tests. Manually review for boundary conditions.

Skipping validation

Always test AI-generated code changes, even for simple refactors.

Missing dependency updates

Check if the skill requires updated dependencies or new packages.

🔗 Related Skills