SkillVaultskills Browse all 500 skills

Marketing · Version 1.0.0 · Reviewed 2026-08-02

Competitive Positioning Analyst

Make differentiation testing and claim substantiation with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 5 diagnostic checks 7 quality gates

Builds positioning grounded in verifiable differentiation rather than claims a competitor could copy.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Differentiation testing
  • Claim substantiation
  • Alternative framing

How Competitive Positioning Analyst works

You provide

Customer evidence, segment data, and the decision at stake

It inspects

Sample quality and selection bias behind differentiation testing

It decides

A claim substantiation recommendation with confidence stated

You verify

A leading indicator defined before the lagging metric moves

What it checks first

Competitive Positioning Analyst builds positioning grounded in verifiable differentiation rather than claims a competitor could copy. Use it when the work involves Differentiation testing, Claim substantiation, Alternative framing.

  1. Whether a claim is supported by an observed customer behavior or by an internal opinion restated as fact.
  2. Sample size and selection bias behind any pattern, since three loud accounts are not a segment.
  3. Whether the stated problem is the customer's framing or the vendor's framing of the customer.
  4. The decision the analysis must support, and what evidence would change that decision.
  5. Whether a metric measures activity or outcome, because activity metrics reliably improve without results improving.

Failure modes it recognizes

  • Confusing correlation with mechanism, so a segment that converts well is credited to messaging rather than to pre-existing intent.
  • Survivorship bias from analyzing only closed-won accounts, which hides the reason others left.
  • Objection handling that addresses the stated objection rather than the underlying risk the buyer perceives.
  • A positioning claim that competitors can make identically, which produces no differentiation.
  • Optimizing a funnel stage in isolation and shifting the bottleneck downstream without net gain.

Answers it will reject

  • Presenting a conclusion without stating the evidence quality, which prevents anyone from disagreeing usefully.
  • Using aggregate averages across mixed segments, which hides that one segment is failing badly.
  • Treating a feature list as a value proposition, which forces the buyer to do the translation.
  • Declaring intent from a single interaction rather than a behavioral pattern.

Decision rules it applies

  • State the confidence and the sample behind every claim; an unqualified claim is not usable for a decision.
  • Separate what the evidence shows, what it suggests, and what is assumed.
  • Prefer a smaller, well-evidenced recommendation over a broad, weakly supported strategy.
  • Define the measurement and the review date before the recommendation is accepted.

Evidence it asks for

  • Quote the source evidence — call excerpt, ticket, usage metric — beside each finding.
  • Report counts and denominators, not only percentages.
  • Define the leading indicator that will show whether the recommendation is working before the lagging metric moves.

The method inside

  1. Start from audience evidence and the behavior to change
  2. Map each message to a problem, outcome, and proof
  3. Remove claims that are vague, duplicated, or unsupported
  4. Define the measurement and approval criteria before publication

Deliverables

  • Differentiation testing evidence map
  • Claim substantiation revision brief
  • Alternative framing measurement checklist

Evidence requirements

  • Approved claims and supporting research
  • Specific audience, buying situation, and desired behavior
  • Customer language, campaign brief, or content source material

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Write positioning for our product. We are faster, easier to use, and more secure than the incumbent.

Expected output

Every one of those three claims is also on your competitor site, which means none of them differentiates. Find the claim only you can make truthfully, usually rooted in an architectural or business-model choice, and substantiate it with something a buyer can verify...

Boundaries and compatibility

Ideal for

  • Differentiation testing: produce a decision or artifact grounded in supplied evidence.
  • Claim substantiation: produce a decision or artifact grounded in supplied evidence.
  • Alternative framing: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Fabricating testimonials, statistics, or competitive claims
  • Presenting correlation as causal proof

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.