agentleFS
erickdronskierickdronski/gtm-skills/skills/positioning/SKILL.md

positioning

Skill0 starsChanged 27 days agoMITView on GitHub

Establish product positioning and a messaging hierarchy grounded in competitive alternatives, differentiated capabilities, and the value those capabilities enable for a specific segment. Use this whenever the user asks about positioning, messaging, value proposition, how to describe or explain their product, what makes them different, homepage or category copy, an elevator pitch, a narrative, or says their messaging is not landing. Also use it when a description of the product is full of adjectives and short of contrast.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tov-guidelines, icp-research and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • matteotittaSkill

    tov-guidelines

    Analyzes existing client content (website, blog, social, docs) to extract voice patterns, vocabulary preferences,

    Also in 4 projects that use this

  • growthack88Skill

    icp-research

    Scrapes case studies, testimonials, and solutions pages from a target website to build structured ICP documentation. Produces TAM analysis, firmographic segments, champion and economic buyer personas, use case mapping, customer proof points, and voice-of-customer synthesis with normalized attributes. Requires website URL as primary input. Upstream: recommended company-context. Downstream: feeds positioning, product-messaging, landing-page-copy, content-strategy, and outreach-emails.

    Also in 4 projects that use this

  • dachi-jp3Skill

    level

    表示レベル(auto / low / medium / high)を切り替える。

    Also in 3 projects that use this

  • YepAPISkill

    competitor-research

    Competitive analysis between domains using YepAPI.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user which of these actually shows up in lost deals.

    line 44
  2. Distinctive:

    If yes, delete it. What survives is usually shorter and much more specific than what the team started with — and that specificity is the …

    line 55
  3. Distinctive:

    Stop at the point where the buyer would nod without needing your product explained.

    line 67
  4. Distinctive:

    The "compared to what" test: Read the copy to someone unfamiliar.

    line 133
  5. Distinctive:

    The lost-deal test: Do lost deals cite reasons your positioning claims to address?

    line 139
  6. Distinctive:

    Leading with the category you wish you were in: If buyers put you in a category, you are in it.

    line 148
  7. Distinctive:

    Positioning against a competitor buyers have never heard of: If the buyer does not know the competitor, the contrast is invisible and you …

    line 158

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Positioning

Positioning is context-setting. It is the answer to a question the buyer asks before any of your features matter: what kind of thing is this, and compared to what?

Get it wrong and every downstream asset works against you. Buyers evaluate you on criteria that belong to a different category, your strengths read as irrelevant, and your team writes increasingly elaborate copy to compensate for a frame that was wrong at the start.

The single most useful reframe: you do not position against a competitor, you position against the alternative — which is very often a spreadsheet, an intern, or doing nothing at all.

The sequence

This follows April Dunford's method, which is the most reliable framework available for this, and its steps must run in order. Each one constrains the next, and skipping ahead to "what makes us different" without first establishing "different from what" is the failure mode this sequence exists to prevent.

1. Competitive alternatives

What would the customer do if you did not exist? Not "who are our competitors" — what would actually happen. Interrogate this hard, because it is where the real information is:

  • A named competitor
  • An in-house build or an existing internal process
  • A spreadsheet, a shared doc, a person doing it manually
  • Nothing — living with the problem

"Nothing" is the most common alternative and the hardest to beat, because it has no procurement cycle and no switching cost. If it is the primary alternative, the entire positioning has to be about the cost of inaction, and messaging built around beating a named competitor will miss.

Ask the user which of these actually shows up in lost deals. If they do not know, that is the first research task, and it is worth more than the rest of this exercise.

2. Unique attributes

What do you have that the alternatives do not? Capabilities, not adjectives. "Powerful", "intuitive", and "enterprise-grade" are things every competitor also claims, which means they carry zero information.

The test: could a competitor say this sentence about themselves without lying? If yes, delete it. What survives is usually shorter and much more specific than what the team started with — and that specificity is the entire asset.

3. Value those attributes enable

For each surviving attribute, ask "so what" until you reach something the buyer cares about independent of your product.

We index the codebase as a graph → so what → queries resolve across files → so what → the agent stops making changes that break callers three files away → so what → review time drops and fewer regressions ship.

Stop at the point where the buyer would nod without needing your product explained. Going further reaches generic business outcomes — "increase revenue" — that no longer distinguish you.

4. Who cares a lot

Which customers care disproportionately about that value? Not everyone who could buy — the segment for whom this is urgent.

Characteristics that make a segment care disproportionately are almost always structural: they have the problem at unusual scale, they have been burned by it recently, or they are regulated into caring. Find the structural reason and the targeting writes itself.

5. Market category

What context makes your value obvious? The category sets buyer expectations — what they compare you to, what they expect to pay, what checklist they evaluate against.

Three moves are available:

Play in an existing category. Easiest. Buyers already have budget and a frame. You have to win on their established criteria.

Position in a subsegment. "Observability, for agent workloads." Inherits budget while shifting the comparison set. Usually the right answer.

Create a category. Enormously expensive — you fund the education of the entire market. Correct only when no existing category makes your value legible, and you have the capital and the years. Most category creation attempts are subsegment plays that would have worked better labeled honestly.

6. Relevant trend, optionally

A trend can make the positioning feel urgent, but only if it is genuinely connected. Bolting a trend onto positioning it does not fit reads as opportunistic, and buyers are unusually good at detecting it.

Turning it into messaging

The positioning is internal. Messaging is what ships. Build the hierarchy in this order and keep it in one document:

One-line positioning statement — internal, precise, not customer-facing:

For [segment] who [situation], [product] is a [category] that [key value]. Unlike [primary alternative], it [key differentiator].

Value pillars — two to four, each stating a differentiated capability and the value it enables. Each pillar needs proof: a metric, a customer outcome, a demo moment. A pillar without proof is a claim, and claims are free.

Proof points — the specific evidence under each pillar. This is where the value case belongs.

Objection handling — the three objections that actually kill deals, and the honest response to each. Not rebuttals; responses. An objection you cannot answer honestly is a product roadmap item, and pretending otherwise wastes everyone's time.

Testing it

Positioning is testable, and most teams never test it:

  • Sales call test. Does a rep get further with it than without? The fastest signal available.
  • The "compared to what" test. Read the copy to someone unfamiliar. Ask what they think the alternative is. If they cannot say, the positioning is not doing its job.
  • The competitor test. Take your homepage headline, swap in a competitor's logo. Does it still read as true? If so, you have written a category description rather than a position.
  • The lost-deal test. Do lost deals cite reasons your positioning claims to address? If so, the positioning is not reaching them, or is not true.

Common failures

Positioning for the team instead of the buyer. Internal language, internal architecture, internal priorities. Buyers do not care how it works until they care what it does.

Leading with the category you wish you were in. If buyers put you in a category, you are in it. Fighting the frame from inside it never works; subsegmenting does.

Feature lists as positioning. A list of capabilities tells the buyer nothing about whether it is for them.

Changing it every quarter. Positioning compounds. Frequent changes reset the compounding to zero and confuse everyone who was starting to understand you.

Positioning against a competitor buyers have never heard of. If the buyer does not know the competitor, the contrast is invisible and you have spent your best sentence on nothing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.