Agent skill
positioning-statement
Use when a product, service or company needs clear positioning, or when the current positioning feels vague, interchangeable with competitors, or disconnected from why customers actually buy.
Filed under Positioning and messaging.
From noahatcheckpoint/gtm-skills · 40 skill entries · 1 · pushed 2026-10-26
What it does when it runs
Use when a product, service or company needs clear positioning, or when the current positioning feels vague, interchangeable with competitors, or disconnected from why customers actually buy. Works from real alternatives and differentiated capabilities to a defensible category choice, a positioning statement, and a proof map the whole team can reuse.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Ask about positioning-statement
Opens your assistant with this page's recorded context. Check the linked sources before relying on it.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/noahatcheckpoint/gtm-skills.git /tmp/gtm-skills git -C /tmp/gtm-skills sparse-checkout set "skills/positioning-statement" mkdir -p ~/.claude/skills/positioning-statement cp -R "/tmp/gtm-skills/skills/positioning-statement/." ~/.claude/skills/positioning-statement/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from noahatcheckpoint/gtm-skills/blob/5f12755a56da598efff4802c527698abb1cf544c/skills/positioning-statement/SKILL.md, which is licensed MIT (skill frontmatter). 1,008 words, 8 headings.
Positioning Statement
This skill produces positioning that explains, in terms a buyer already understands, why your offer is the better choice for a specific kind of customer. The output is a short positioning statement plus the reasoning underneath it, so the team can defend every word.
When to use
- Launching a product, a new tier, or entering a new segment.
- Prospects keep comparing you to the wrong competitors, or asking "so what is it exactly?"
- The homepage headline could belong to any company in the space.
- Sales and marketing describe the product in different ways.
- Win rates are fine with one segment and poor with another, and nobody knows why.
What you need
Ask for what is missing before you start. Positioning built without customer evidence is a guess and should be labeled as one.
- The offer: what it is, how it is sold, rough price point.
- Your happiest customers: who they are and, ideally, their own words for why they chose you.
- Deals you lost: to whom, and the reasons given.
- What buyers did before you: spreadsheets, an agency, an incumbent platform, hiring a person, doing nothing.
- Capabilities you believe are distinctive: features, delivery model, expertise, data, pricing structure.
- Current messaging: homepage hero, pitch deck opening, or elevator pitch.
Process
- List the real alternatives. Ask: if we disappeared tomorrow, what would our best customers do instead? Include non-product options ("keep using spreadsheets", "hire a contractor", "live with the problem"). Status quo is usually the biggest competitor and the one most teams forget.
- Isolate what is genuinely different. For each alternative, list what you have or do that it lacks. Strip out table stakes (things every serious option offers). Keep only attributes a customer would notice and could verify.
- Translate attributes into value. For every differentiator, answer "so what?" until you reach an outcome the buyer cares about: time saved, risk removed, revenue gained, a job done that could not be done before. Then attach proof: a metric, a customer quote, a demo moment, a guarantee.
- Find who cares most. Identify the customers for whom that value matters most. They are usually a narrower group than your full customer base. Describe them by the situation that makes the value urgent, not just by size or industry.
- Choose the market frame. Pick the category or reference point that makes your value obvious within seconds. Three options:
- Existing category, win head on: works if you are clearly better on what the category already values.
- Subcategory: an existing category plus a qualifier ("X for regulated teams") when you beat the leader for a specific segment.
- New category: only when no existing frame fits and you have the budget and patience to educate a market. Treat this as the expensive option. A useful test: once the buyer hears the category, do they correctly assume your competitors, your price range and your must-have features?
- Add a trend if, and only if, it is real. A relevant shift (regulation, a technology change, a buying behavior change) can explain "why now", but it should support the positioning, not replace it.
- Write the statement. Use the template below. Then write a 10-word version a rep can say out loud.
- Stress test. Swap your company name for your top competitor's. If the statement still reads true, it is not differentiated. Rewrite until it fails that test.
Output format
Positioning summary
For [target customer in a specific situation]
who [struggle or need, in their words],
[product] is a [market frame]
that [primary value, stated as an outcome].
Unlike [main alternative, including status quo],
we [key differentiator that delivers the value].
Spoken version (10 words or fewer): ...
Alternatives map
| Alternative | Why buyers choose it | Where it falls short | Our differentiator |
Value and proof
| Differentiator | Value to the buyer | Proof we can show |
Best-fit customers: [situation-based description]
Market frame chosen: [category] because [reason]; rejected: [option] because [reason]
Why now (optional): [trend]
Competitor swap test: [pass/fail and what you changed]
Assumptions to validate with customers: ...
Quality checklist
- Status quo or "do nothing" appears in the alternatives list.
- Every differentiator has a value statement and at least one piece of proof, or is flagged as unproven.
- The target customer is described by situation, not only firmographics.
- The category choice is explained, including what was rejected.
- The statement fails the competitor swap test.
- No superlatives ("best", "leading", "world-class") without proof attached.
Common mistakes
- Starting with the category you were built in. Founders often default to the frame they had in mind on day one. The best frame is the one where your strengths matter most to buyers today.
- Listing features as differentiators. "AI-powered" or "easy to use" describes a property, not a reason to buy. Push through to the outcome.
- Positioning against the competitor you fear rather than the one you meet. Use loss data, not market maps.
- Trying to appeal to everyone. A broad target hides your strongest value. Narrow positioning tends to win more deals, including some outside the target.
- Confusing positioning with messaging. Positioning is the strategic choice; taglines and headlines come after and should be derived from it.
- Inventing a category to sound visionary. Category creation is slow and costly. Default to an existing frame unless the evidence forces you out of it.
Example prompts
- "Here are notes from 8 customer interviews and our last 10 losses. Draft our positioning."
- "Our homepage says we're an 'all-in-one revenue platform'. Help us position more sharply."
- "Should we position as a subcategory of CRM or as something new? Walk me through it."
- "Write a positioning statement for our consulting offer and run the competitor swap test."
- "We sell to both startups and enterprises. Help us pick which one to position for first."
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- positioning-basics by BrianRWagner · 450
- positioning-and-story by AIDevGTM · 331
- crafting-positioning by GTM-Strategist · 275
- competitive-positioning by louisblythe · 195
- brand-messaging-and-positioning by manojbajaj95 · 109
- positioning-icp by chadboyda · 85
- positioning-map by pmalliance · 77
- positioning-strategy by mia-ppp · 71
Need help setting it up?
This page tells you what positioning-statement does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.