The Messaging Framework document

The deliverable. This is what the four stages produce, and it is the only artifact the team should need to write on-message copy without asking anyone.

Contents

• Design principles
• The three-layer structure
• Full annotated outline
• The evidence standard
• Quote and proof handling
• What to leave out
• Maintenance
• Failure modes

Design principles

Written to be used, not to be admired. Dunford's argument against the traditional positioning statement applies to the whole document: the test is whether a salesperson can act on it. If the artifact cannot be used by someone who did not attend the workshop, it failed regardless of how good the thinking was.

Three readers, three depths. The same document serves a rep with five minutes before a call, a marketer writing a landing page, and an executive interrogating the choice. Structure for all three by ordering from most-used to least-used, not from most-foundational to most-applied. The rationale goes at the back.

Decision and expression are separate. The positioning decision is short and stable and changes rarely. The expression is long and applied and changes constantly. Mixing them means nobody can tell what is settled and what is a draft — which is how a framework accumulates three competing versions of the same claim.

Every claim carries its evidence. A claim without a source is a claim a rep cannot defend and a lawyer cannot approve. Sourcing is not an appendix concern; it belongs inline.

Retirement is part of the document. New language does not displace old language on its own. The document has to say what is being dropped, or the old terms live on in decks forever.

The three-layer structure

Layer 1 — THE DECISION        short, stable, front-loaded
          Everything settled. Changes only when the market moves.

Layer 2 — THE EXPRESSION      applied, living
          Copy, proof, objections, per-surface guidance.
          Changes as the product and market change.

Layer 3 — THE EVIDENCE        reference, appended
          Research, customer language, sourcing, competitive scan.
          Supports the other two. Read when challenged.

Order the document this way. A reader who stops after Layer 1 should still be on-message.

Full annotated outline

# [Company] Messaging Framework
Version · Date · Owner · Next review

────────────────────────────────────────
## The one page
────────────────────────────────────────

Everything a rep needs, on one screen. If it doesn't fit, cut until it does. Contains:

• The one-liner — the Fletch sentence in plain form
• The category — what kind of thing this is
• Who it's for — the best-fit segment and the disqualifier
• The three things we claim — no more than three, each in under ten words
• The real alternative — what they do today if we don't exist
• Our strongest proof — one number or one named result

This page is what gets memorized, pasted into team chat, and put on the back of a badge. Write it last, from everything below.

────────────────────────────────────────
# LAYER 1 — THE DECISION
────────────────────────────────────────

## The problem we solve

One paragraph, in customer language, from the demand brief. The struggling moment — concrete, dated, recognizable. Not a market trend. A reader in the segment should see themselves.

Follow with the three or four most common ways it shows up, using customers' own nouns.

## Competitive alternatives

What customers actually do today, ranked by how often it appears on real shortlists. Include the status quo and internally built tools explicitly — usually the most common alternative and the one most often omitted.

For each: what it's good at (state this honestly, it builds credibility with sales) and where it breaks.

## What only we can claim

The differentiators that survived the table-stakes test, with the date the test was run and who was checked.

For each, in this order: the attribute (a fact), the mechanism (how it works), the value (laddered to money, risk, or time), and the proof.

Include a short, explicit list of table stakes — true things competitors also claim. Reps need these to stay in the consideration set, and they need to know not to lead with them. Labeling them prevents a rep building a pitch on a claim the competitor's homepage also makes.

## Who this is for

Best-fit characteristics as situational triggers, not demographics. Then the disqualifying signals — who this is not for, and what to say when they show up. Sales trusts a framework that tells them when to walk.

## Where we compete

The market category and one paragraph on why this frame makes the value obvious. If a category was considered and rejected, say which and why. This is what stops the question being reopened every quarter.

## What we are not

Explicit boundaries. The most-read section in practice, because it settles arguments.

────────────────────────────────────────
# LAYER 2 — THE EXPRESSION
────────────────────────────────────────

## The narrative

The Raskin arc in prose — the shift, winners and losers, the promised land, capabilities, proof. Half a page. This is the spine of the deck and the keynote, and it should read as the same decision as Layer 1 at a different altitude.

Include the shift statement as a standalone quotable line, since that is the sentence a champion repeats internally.

## Messaging by surface

Not by audience first — by surface, because that is how the team works. For each: website, outbound email, social, the deck, and the demo.

Give the headline, the subhead, the opening line, and one worked example. Examples are what get copied; principles are what get ignored.

## Messaging by audience

Only where audiences genuinely need different value, not a different tone. Over-segmentation here is how frameworks bloat into documents nobody reads.

For each audience: their version of the struggling moment, the value that lands, the proof they need, and the objection they raise.

## Proof library

Every usable proof point in one table:

Proof	Claim it supports	Source	Date	Clearance

Clearance matters — whether a customer name can be used, whether a figure is one account's result or a benchmark, whether a number is an internal estimate. A single number presented as typical when it belongs to one customer is the most common proof failure.

## Quote bank

Verbatim customer quotes, each with role, company type, source, date, and clearance status. State the attribution policy once, at the top of the section, so nobody has to guess: named accounts only where cleared, otherwise role and company type.

## Objection handling

One per real objection from the demand brief's anxiety and habit forces — not invented objections. Each gets the objection in the buyer's words, the response, and the proof that backs it.

Cover the four that appear in almost every B2B deal: "we already have [incumbent]," "how is this different from [the free thing bundled in our stack]," "what about security and our data," and "what do we have to migrate or give up."

## Words we use / words we don't

Two columns, from the language inventory.

Third section: retired language — terms being deliberately dropped, what replaces them, and why. Without this, old vocabulary survives in decks indefinitely.

────────────────────────────────────────
# LAYER 3 — THE EVIDENCE
────────────────────────────────────────

## Demand evidence

The demand brief in summary: interviews run, dates, the Four Forces with ranked verbatims. This is what someone reads when they want to challenge a claim.

## Competitive scan

What each alternative currently claims, with the date checked and links. Dated, because it decays fast — and dating it is what triggers the next review.

## Sources

Every statistic with full citation and date. Internal estimates labeled as estimates. If a number cannot be sourced, it does not go in the document.

## Decisions and change log

What was decided, when, by whom, and what was considered and rejected. This is what prevents a settled question being reopened in six months by someone who wasn't there.

The evidence standard

Apply consistently:

• Statistics — source, publication, date. Internal data labeled as internal.
• Customer results — which customer, over what period, whether typical or a single account.
• Quotes — role, company type, date, clearance status.
• Competitive claims — the date checked, since competitor pages change without notice.
• Security and compliance claims — the exact scope of what is certified or attested, and what is not. Where the legal wording is narrower than the marketing instinct, use the legal wording and say why in a note to the team.

That last one prevents the most expensive class of messaging error, where confident older collateral makes an absolute promise the contract does not.

Quote and proof handling

Sales will use the strongest number in the document regardless of caveats, so put the caveat inside the claim rather than beside it. "One customer reclaimed 25–30% of their team's time" travels safely. "25–30% time saved" does not, because the qualifier falls off the first time it is repeated.

Where a proof point is strong but uncleared, include it and mark it clearly as internal-only. Reps need to know it exists so they can pursue clearance, and they need to know not to say it yet.

What to leave out

• Strategy rationale at length. A paragraph per decision, not a memo. Long rationale belongs in a separate strategy doc.
• Buyer journey maps, funnel diagrams, campaign plans. Different artifacts with different owners.
• Product roadmap. It dates the document and invites the framework to be rewritten every release.
• Aspirational capability. Only what the product does today. A framework that describes the product you are building is the fastest route to a sales team that overpromises.
• More than three audiences unless the value genuinely differs.

Maintenance

Put version, date, owner, and next review on the first page, and set a review trigger rather than only a date — "review when a major competitor ships or bundles a comparable capability, when the ICP changes, or in six months, whichever comes first."

Keep the change log at the back. When a claim is retired, log it rather than deleting it silently, so anyone who finds old collateral can see it was a decision.

Distribution beats polish. A document nobody opens has no value. Ship the one page separately, walk the team through it live, and put the full framework where the team already works.

Failure modes

• Front-loading the philosophy. If page one is the narrative and the claims are on page fourteen, reps read page one and improvise the rest.
• No one page. The single highest-leverage section, and the most commonly missing.
• Uncleared proof presented as usable. Creates legal exposure and destroys trust in the document.
• Aspirational claims mixed with current ones, unlabelled.
• No retirement list. Old language persists indefinitely.
• Audience sprawl. Six personas, each a paragraph, none actionable.
• Undated competitive claims. The scan looks authoritative long after it stopped being true.
• Written once, never revised. A framework with no owner and no review trigger is a snapshot, not a system.