Positioning messaging framework

This one is long. Copy it, then paste it into your AI.

<!--
COMMUNITY SKILL — included under its original MIT license.
Source: https://github.com/adam-lagerhausen/b2b-marketing-skills by Adam Lagerhausen (MIT).
License text: ../LICENSE-b2b-marketing-skills.txt
Curated into Growth Marketing OS by Mahmoud Omar (mahmoudomar.com) — this file
is NOT original work by the repo author; see /skills/community/README.md.
-->


# Positioning Messaging Framework

## When to use

Use this skill when you need to turn product, customer, market, or voice-of-customer inputs into a usable B2B positioning and messaging framework.

Use it for:

- New product or feature positioning
- Repositioning an existing product
- Homepage or campaign message strategy
- Launch messaging foundations
- Sales narrative inputs
- Reviewing whether existing positioning is sharp enough

Do not use it to produce generic copy before the strategic choices are clear. Positioning comes first. Messaging turns that positioning into everyday English. Copywriting is the clear wording that gets the message across.

## Required inputs

Ask for or infer these inputs. If an input is missing, state the assumption and mark confidence as low.

- Product or company name
- Product category or current market frame
- Target segment and persona
- Company attributes that make the segment specific
- Customer economic goal
- Customer qualitative or emotional goal
- Current alternative, status quo, or vendor class
- Pains and consequences of the current approach
- Job to be done
- Differentiated capabilities or model
- Proof points, reasons to believe, or customer evidence
- Business outcomes the product can credibly support
- Words, phrases, or stories customers actually use

## Core principles

- Positioning is how you want customers to perceive the product and frame the decision versus a competitor, status quo, or alternative.
- Messaging translates positioning into everyday English: the messages to get across, not just slogans.
- The product is the tool. The thing customers buy is usually uptime, safety, reliability, revenue, efficiency, confidence, or the ability to say yes.
- Always define a clear segment. Curate for the attributes you are optimizing for, and explicitly decide what you are not optimizing for.
- If you can remove the company logo and replace it with a competitor, the positioning is not sharp enough.
- Stories beat claims. Use concrete situations, consequences, and before/after change.
- Avoid jargon, inflated claims, category mush, and copy that sounds like every SaaS homepage.

## Workflow

### 1. Clarify the segment

Define the narrowest useful target:

- Who are the buyers, users, and influencers?
- What company attributes matter? Size, industry, maturity, workflow complexity, risk profile, regulation, growth stage, or operating model.
- What are they optimizing for?
- What are they not optimizing for?
- Who is intentionally out of scope?

Push back when the segment is too broad. "B2B companies," "revenue teams," or "enterprises" is usually not enough.

### 2. Name the real alternative

Identify what the customer would do if this product did not exist:

- Keep using spreadsheets, email, meetings, manual review, or internal tools
- Use a horizontal platform
- Hire more people
- Accept the risk or delay
- Choose a better-known vendor
- Do nothing until the pain becomes urgent

The real alternative is often the status quo, not the named competitor.

### 3. Diagnose pains, consequences, and JTBD

Separate:

- Pain: what is broken or frustrating
- Consequence: what that pain costs the business
- Job to be done: the progress the customer is trying to make
- Emotional stakes: what the buyer wants to feel or avoid feeling

Translate feature problems into business problems. Do not stop at workflow annoyance if the real issue is missed revenue, risk, downtime, churn, delay, or lost trust.

### 4. Define differentiated value

Connect capabilities to outcomes:

- What does the product let the customer do that they could not do before?
- Why is that better than the alternative?
- What is the differentiated model, mechanism, data, workflow, integration, or expertise?
- What business improvement does this create?
- What emotional outcome does it enable?

Avoid claiming "faster," "easier," or "smarter" unless you can say faster than what, easier for whom, and smarter because of what.

### 5. Build the positioning statement

Use this template, then tighten it:

For [people/role/attribute] at [company attributes], who want [economic goal] while [qualitative goal], [Company] is [superlative/product] that lets you [business improvement] so you can [economic goal]. Unlike [alternative/status quo/vendor class] that [causes problem] because [flaw], [Company] helps you [differentiated goal] with [differentiated capability/model] so you can [specific business goal] and [emotional outcome].

The final version should be specific, credible, and plain-spoken. It does not need to be ad copy.

### 6. Turn positioning into messaging

Create exactly 3 messaging pillars that express the position in buyer language.

The 3 pillars must be unique and differentiated. Each pillar should make a distinct strategic point, not restate the same value in different words. If two pillars would appear together on a homepage and feel interchangeable, merge or rewrite them.

Use this split unless the evidence strongly suggests another structure:

1. Primary pain / urgent buyer problem
2. Differentiated mechanism / why this works differently
3. Business or emotional outcome / why the buyer should care now

For each pillar, include:

- Message
- Buyer pain it addresses
- Business outcome
- Reason to believe
- Plain-English copy direction

Messages should be useful in sales conversations, website sections, launch copy, and enablement.

### 7. Pressure-test and sharpen

Run the output through the pressure tests below. If it fails, revise before finalizing.

## Output format

Produce the framework in this structure:

1. Executive summary
   - One-paragraph readout of the recommended position

2. Target segment and persona
   - Segment
   - Persona
   - Company attributes
   - Optimizing for
   - Not optimizing for
   - Out of scope

3. Real alternative
   - Status quo or competitor/vendor class
   - Why customers choose it today
   - Why it breaks

4. Pains, consequences, and JTBD
   - Pains
   - Business consequences
   - Job to be done
   - Emotional stakes

5. Differentiated value
   - Core value proposition
   - Differentiated capabilities or model
   - Business outcomes
   - Emotional outcome

6. Positioning statement
   - Template version
   - Tightened version

7. Messaging pillars
   - Exactly 3 pillars
   - Each pillar must be unique and differentiated, not a near-duplicate of another pillar
   - For each: message, pain addressed, outcome, reason to believe, copy direction

8. Reasons to believe
   - Evidence, proof, mechanism, customer quotes, data, demos, or stories

9. Plain-English copy direction
   - Homepage headline direction
   - Subhead direction
   - Sales talk track direction
   - Words to use
   - Words to avoid

10. Pressure-test notes
   - What is sharp
   - What is still weak or unproven
   - What customer evidence would improve confidence

## Quality bar

A strong output:

- Names a specific customer segment, not a vague market
- Frames the decision against the real alternative
- Connects product capabilities to economic outcomes
- Includes the qualitative or emotional reason the buyer cares
- Uses plain English that a customer would recognize
- Makes explicit tradeoffs about who the positioning is and is not for
- Provides credible reasons to believe
- Produces exactly 3 messaging pillars that are unique, differentiated, and useful in a real sales conversation
- Avoids interchangeable SaaS language

## Pressure tests

Before finalizing, check:

- Logo-swap test: If the company name were replaced with a competitor, would the statement still sound true?
- Segment test: Is the target specific enough that some potential customers are excluded?
- Alternative test: Is the real alternative named clearly?
- Outcome test: Does the value ladder up to revenue, cost, risk, uptime, safety, reliability, speed, trust, or ability to say yes?
- Proof test: Can the company prove the claim with evidence, mechanism, demo, customer story, or data?
- Plain-English test: Would a buyer say, "Yes, that is exactly the problem"?
- Story test: Is there a concrete before/after situation, not just an abstract claim?
- Jargon test: Could the message be understood without category buzzwords?

## Anti-patterns

Avoid:

- Starting with taglines before positioning choices are made
- Targeting everyone who could technically buy the product
- Treating the named competitor as the only alternative
- Confusing features with value
- Claiming generic speed, efficiency, AI, automation, or productivity without a mechanism
- Writing copy that could fit any SaaS company
- Writing four or more pillars because every benefit feels important. Force the three strongest, most differentiated messages; move supporting points into proof, copy direction, or sales talk track.
- Over-optimizing for cleverness instead of clarity
- Hiding weak differentiation behind adjectives like modern, seamless, powerful, unified, or intelligent
- Ignoring emotional stakes such as confidence, safety, trust, control, or the ability to say yes
- Making claims without proof or a path to proof

Fill in anything in [brackets] or {braces} with your own details first.