Positioning and Messaging Frameworks That Stick

Most positioning docs are 14 slides nobody reads. The deck wins deals. The doc rots in Notion. A PMM spends six weeks on a "messaging framework," presents it to leadership, gets nods, posts it in a Slack channel, and three months later a rep on a Tuesday discovery call is still saying "we're like Salesforce but easier" because that's what came out of their mouth before the new positioning ever reached them.

That's not a writing problem. It's a shipping problem. And it starts with how you build the thing in the first place.

This is a working playbook. It assumes you're a PMM IC or lead who has to actually deliver positioning your sales team uses, your website reflects, and your founder stops rewriting on Sunday nights. We'll walk April Dunford's framework, the 1-page doc that survives a slide, the messaging hierarchy that keeps headlines from masquerading as positioning, the validation loop with sales, the committee trap, the rewrite-vs-refine call, and a 30-day rollout plan with named owners.

The Real Deliverable Isn't the Doc

Before any framework, get this straight: the deliverable that changes revenue is the slide and the rep's first 90 seconds of a discovery call. Everything else is scaffolding.

If your positioning can't survive being compressed to one slide, sales will compress it for you. Badly. They'll cut your nuance, drop your category frame, and reach for whatever competitor name the buyer recognized last quarter. So write for the slide first, then back into the doc.

April Dunford's Five Inputs

Dunford's framework, laid out in Obviously Awesome, has five inputs. Treat them as the worksheet you fill out in a working session, not the deliverable you ship. The deliverable comes later.

1. Competitive alternatives. What does your buyer use today if you didn't exist? Not "the market." The actual alternatives a real prospect named in a discovery call last week. For a mid-market revops platform, the honest answer is usually "Salesforce plus three spreadsheets plus a part-time ops contractor," not "Gainsight" or whatever Gartner put in the same quadrant.

2. Unique attributes. What does your product have that those alternatives don't? Be specific. "Easy to use" is not an attribute. "Native lead distribution by territory and round-robin with SLA timers, configurable in 10 minutes by a non-admin" is an attribute. If a competitor can claim it with a straight face, it's not unique.

3. Value those attributes unlock. The "so what." Native lead distribution + SLA timers means leads don't sit unworked for 48 hours, which means your win rate on inbound MQLs goes up 8-12 points based on what we've seen in deployments. Attributes without value are trivia. Value without attributes is a headline.

4. Who cares the most. Not your TAM. The customers for whom that value is urgent and obvious. The mid-market revops platform's "who cares most" is a 100-300 employee B2B SaaS company with inbound demand, a 4-8 person sales team, and a head of revops who's two months into the job and getting pressure on inbound conversion. That specificity is the point.

5. Market category. The frame the buyer puts you in when they describe you to their boss. If you don't pick one, the buyer picks one for you, and they almost always pick the wrong one (cheaper, smaller, last-decade). For revops, you might frame as "revenue operations platform" instead of "CRM" because CRM puts you next to Salesforce in the buyer's head and the comparison kills you.

A working session that runs all five inputs with three people from product, sales, and customer success (not a survey, not async edits) takes about four hours and produces 80% of the answer. The other 20% comes from validation.

The 1-Page Positioning Doc

Once you have the inputs, compress them to one slide. If it doesn't fit, you haven't decided yet.

Here's a filled-in example for a fictional B2B SaaS — call it PipelineLens, a revops analytics tool.

Category: Revenue operations analytics platform

Who it's for: Heads of RevOps at 100-500 person B2B SaaS companies with inbound-led GTM, 4-12 reps, and a Salesforce instance that's been customized into a swamp.

The named alternative being displaced: Salesforce reports + a BI tool + a part-time analyst.

Three unique attributes:

Pre-built revops models (pipeline waterfall, conversion by stage, rep loading) that work on day one with a Salesforce-only setup, no data engineer required.
Native pipeline forecasting that ties to rep-level activity data, not just opportunity stage.
An ops-team-shaped UI: dashboards built for the person running the QBR, not the AE checking their commission.

The value those attributes unlock: Forecast accuracy goes from "gut + Excel" to within 5% of plan, the head of revops gets two days a week back from manual reporting, and the CRO walks into board meetings with a number instead of a story.

That's the slide. Sales can read it in 20 seconds. The rep can paraphrase it in their own words on a discovery call. The website hero writes itself off the "who it's for" + the value line. Anything longer and you're back in Notion.

The Messaging Hierarchy

Positioning is the foundation. Messaging is what people actually read and hear. They get conflated constantly, and that's how you end up with a website hero that says "Pipeline that wins" and a positioning doc that says nothing useful.

The hierarchy has four layers. Each answers a different question.

Positioning answers: who is this for and why is it different? It's the 1-page doc above. There's one. It doesn't change weekly.

Value props answer: what does the buyer get? Three of them, max. Each tied directly to one of your unique attributes. For PipelineLens: "Forecast within 5% without a data team." "Get your QBR back to a one-day prep, not a one-week fire drill." "See rep-level pipeline health in real time, not at month-end." Value props are not features. "Pre-built revops models" is a feature. "Forecast within 5% without a data team" is a value prop.

Proof points answer: why should I believe you? Numbers, named customers, or specific outcomes. "Customers cut forecast variance from 22% to 4% in the first quarter." "Used by RevOps teams at [Named Customer 1], [Named Customer 2], [Named Customer 3]." Adjectives are not proof points. "Industry-leading" is not a proof point. It's a tell that you don't have one.

Headlines answer: will the buyer click or keep scrolling? They're the surface. They depend on channel. The website hero, the LinkedIn ad, the cold email subject line, the demo slide title. Each is a different headline expressing the same value prop. For "Forecast within 5% without a data team," you might run three variants:

"Forecast within 5%. No data team required."
"Stop guessing your number. Start defending it."
"RevOps analytics that work the day you turn it on."

Headlines are not positioning. If the headline changes and the positioning has to change with it, you don't have positioning, you have a tagline.

Validate With Sales Before You Ship

Here's the part most PMMs skip. They write the doc, present to leadership, and ship. Then they're confused when the field doesn't use it.

Validate before the rollout, not after.

Ride along on five discovery calls and five demos. Not as a coach. As an anthropologist. Listen for the words reps use when the buyer asks "so what do you do?" and "how are you different from [competitor]?" Write down their actual phrasing.

Run structured win-loss interviews. Ten wins, ten losses. Same script. Ask buyers what they almost bought instead, what made them pick you (or not), and what phrase a colleague would use to describe what you do. Buyers are bad at telling you what to build. They're surprisingly good at telling you what category they put you in.

Mine objections from Gong or Chorus. Search your call recordings for the top five objections of the last 90 days. If your positioning doesn't have a clean answer to each, you have a gap.

The signal you're looking for: are reps already saying something close to your positioning in their own words? If yes, sharpen it and amplify it. If no, you have a rollout problem, not a writing problem, and no amount of redrafting fixes that.

The Messaging-by-Committee Trap

Every PMM has lived this one. The CEO wants the hero to mention AI. The CRO wants the deck to lead with ROI. The founder-engineer wants the proof points to highlight the architecture. The head of design wants fewer words on every page. You take it all in, redraft, send it around, and what comes back is mush. Nothing wrong, nothing right, nothing memorable.

Name one decision-maker. Usually the CMO or VP of Marketing. If you don't have one, the PMM owns the call and the founder backs them.

Give everyone else structured input windows, not edit access. A 30-minute review session where they raise concerns, and the decision-maker arbitrates on the spot. No async redlines on the doc. No Slack threads relitigating word choices. The decision-maker hears the input, makes a call, moves on.

This sounds harsh. It is. The alternative is shipping mush, and mush doesn't win deals.

Rewrite vs. Refine

Don't rewrite on a hunch. Rewriting is six months of internal churn, sales confusion, and a website refresh that competes with three other priorities. Do it when the input has actually changed.

Rewrite when:

Your category has shifted (the buyer now puts you in a different bucket)
Your ICP has shifted (you're selling to a different role or segment than 12 months ago)
Your competitive set has shifted (a new entrant is reframing the conversation, or an old competitor exited)
Your product has shifted enough that the unique attributes are different

Refine when:

Win rates are healthy but the language feels stale
A new proof point is available and you want to thread it through
You're A/B testing headlines, not the underlying value prop
Sales is using the positioning but the hero copy is getting clicked at a low rate

If you can't name which of those triggered the rewrite, you're rewriting on vibes. Stop and refine instead.

The 30-Day Rollout Plan

Positioning that doesn't ship to web, sales, deck, and enablement in 30 days isn't real. Here's the plan, with owners.

Days 1-7: Surfaces drafted.

Web hero + 3 follow-on sections (PMM owns, web designer drafts)
Deck slides 2-4 (PMM owns, sales ops reviews)
One-pager (PMM owns)
Battlecard updates for top 3 competitors (PMM owns, top reps review)

Days 8-14: Internal review.

30-minute leadership review with the named decision-maker (CMO or VP Marketing)
Top 5 reps walk through the deck and battlecards live, give feedback in the room
Customer success reviews the one-pager for accuracy

Days 15-21: Enablement.

30-minute live enablement session for the full sales team
A 5-minute Loom from the CRO or a top rep called "here's the new pitch." This matters more than the deck. Reps imitate other reps, not PMMs.
Battlecards updated in the enablement tool of record (Highspot, Seismic, Showpad, or wherever your reps actually look)
Updated demo script with the new opening 90 seconds

Days 22-30: Ship and check in.

Web hero goes live
New deck deployed to all reps
One-pager added to the standard follow-up email template
30-day check-in: spot-check 5 discovery calls, listen for the new language, identify what's sticking and what isn't

If a surface isn't owned by a name, it doesn't ship. "Marketing owns the website" is not an owner. "Priya owns the hero copy and Diego owns the three follow-on sections, both due Friday" is an owner.

What to Watch After Launch

The leading indicator that positioning is working isn't pipeline. Pipeline lags. The leading indicator is rep language. Pull 10 discovery call recordings from week 4. If reps are using the new framing in their own words (not reciting the deck, but paraphrasing the value prop with their own examples), you've shipped. If they're still saying the old thing, you have an enablement gap, not a positioning gap, and the fix is more reps and more reinforcement, not another rewrite.

The lagging indicator is win rate against the named alternative. If the alternative was Salesforce-plus-spreadsheets and your win rate against that profile moves up 5+ points over 90 days, the positioning is doing work. If it doesn't, look at the messaging hierarchy: are the value props specific enough? Do the proof points exist? Or is the buyer hearing the new positioning and still not believing it?

Positioning is never finished. It just gets sharper or duller. Keep listening to calls. Keep updating proof points as customer outcomes accrue. And resist the urge to rewrite every time a board member says they don't love the website hero. That's a refine call, not a rewrite call. Save the rewrite for when the inputs actually change.

Product Marketing Manager Guide