Messaging Framework: A Template for Startups
A messaging framework is a one-page document that tells a company what to say about itself: the core promise, three or four message pillars, the proof behind each pillar, and how the wording shifts by buyer and channel. It sits under the positioning statement and above every page and pitch. Once it's written down, a company's AI tools can write from it too.
Picture a band hired for a wedding, where each player learned the first-dance song from a different recording. The guitarist learned the album version. The singer learned a live one with an extra verse. Everyone's good, and the song still falls apart at the bridge.
Plenty of startups sound like that band once a few people start talking to customers. The founder pitches one promise on sales calls, and the website makes another. A new sales rep improvises a third from an old deck. Each version is defensible on its own. A buyer who hears two of them starts to wonder which one is true.
A messaging framework is the chart the whole band reads from. Two questions decide whether yours works. Does everyone pull the same promise from it, and can each person change the wording without changing the song?
What a messaging framework holds
A chart doesn't tell the drummer every beat, and a messaging framework doesn't script every sentence. It fixes the parts that must stay the same and leaves room for the rest. A complete one holds five parts:
- Promise: the value proposition, one sentence a buyer could repeat back, naming who you help and the result they get.
- Pillars: three or four reasons the promise is true. Each one should persuade a buyer on its own.
- Proof: two or three pieces of checkable evidence under each pillar, such as a number or a customer quote.
- Variants: which pillar leads for each buyer and channel, from a sales call to the founder's LinkedIn posts, with a sample line.
- Vocabulary: the words you use for your customer, your category and the problem, each paired with the word you avoid.
The framework sits one level below positioning. Your positioning statement decides where you stand against the alternatives, and only your team reads it. The messaging framework turns that decision into the words customers hear. Write the positioning first. Messaging built without it asserts value instead of earning it.
Messaging framework template
All five parts fit on one page, and the template keeps them in order.
POSITIONING (copy it in, don't rewrite it here) For [target buyer] who [need], [company] is the [category] that [benefit]. Unlike [main alternative], we [key difference]. PROMISE (one sentence, in the buyer's words) [Company] helps [buyer] [result they care about]. PILLARS (three or four, each convincing on its own) 1. [Pillar name]: [one sentence on why it's true] Proof: [number, feature, or customer quote] Proof: [second piece of evidence] 2. [Pillar name]: [one sentence] Proof: [evidence] Proof: [evidence] 3. [Pillar name]: [one sentence] Proof: [evidence] Proof: [evidence] VARIANTS (which pillar leads, by buyer and channel) [Buyer] | [Channel] | Leads with [pillar] | "[Sample line]" [Buyer] | [Channel] | Leads with [pillar] | "[Sample line]" [Buyer] | [Channel] | Leads with [pillar] | "[Sample line]" Everyone | Homepage | Leads with the promise | "[Sample line]" VOCABULARY Our customer: say [term], avoid [term] Our category: say [term], avoid [term] The problem: say [term], avoid [term] The result: say [term], avoid [term] Competitors: say [term], avoid [term] OWNER: [name] LAST REVIEWED: [date]
Fill it in from the top down, because each part leans on the one above it:
- Positioning: copy in your positioning statement as it stands. If you don't have one, stop and write it first.
- Promise: write it the way a buyer would say it, then read it to someone outside the company. If they can't say it back, rewrite it.
- Pillars: test each one alone. Cover the others and ask whether this one would still make a buyer lean in. A pillar that needs the others is a feature riding along.
- Proof: use only evidence you could defend under a direct question. Leave a blank rather than invent one.
- Variants: map them to your real deals. The person who signs and the person who uses the product every day usually need different pillars up front.
- Length: keep it to one page. If it runs to two, you have too many pillars.
A worked example
Filled in, the variants show how one promise travels. Take Kennelwise, a hypothetical scheduling tool for veterinary clinics, whose promise is "Kennelwise keeps a clinic's day full without the phone tag."
| Buyer | Channel | Leads with | Sample line |
|---|---|---|---|
| Practice owner | Sales call | Fills cancellations | "A cancelled slot gets rebooked from the waitlist before it sits empty." |
| Front-desk lead | Product tour | Easy to learn | "Your team can run it by lunch on day one." |
| Office manager | Follow-up email | Syncs with your records | "Bookings land in your practice software. Nobody types them twice." |
| Everyone | Homepage | The promise | "A full schedule, without the phone tag." |
Every row is a different arrangement of the same song. The owner hears revenue, and the front desk hears an easier morning. Neither one hears a different company.
When it's too early: if you can't yet name the buyer who says yes fastest, a messaging framework will only polish a guess. Sell for a while longer, then write it.
Messaging mistakes
Most frameworks that fail were written well enough and then broke in use. Five failures come up most often:
- No proof: pillars a sales rep can't defend when a buyer asks "how do you know?"
- One buyer only: messaging built for the person who signs can lose the person who uses the product, and that person quietly stalls adoption after the contract.
- A shelf document: the framework lives in a slide deck nobody opens while writing, so it never changes what gets written.
- Too many pillars: past four, nobody remembers them, and each one gets thinner.
- Swapped jargon: replacing "streamline" with "optimize" fixes nothing. Name the concrete thing instead.
Where the framework lives
AI tools make the shelf document a bigger problem. Your team now drafts with them, and a tool that has never read your framework invents a promise of its own every time someone asks it for copy. That's one more player who learned the song from a different recording.
Put the framework where those tools can read it, and every draft starts from the same chart. I built Cadence for this: it keeps a company's positioning, voice and approved claims in one governed source, wired into the AI tools the team already uses. What an AI operating system is covers the rest of that setup.
Getting everyone saying the same thing
A band's players can each sound like themselves, as long as they all read from the same chart. Write the promise, back each pillar with proof, and decide which pillar leads for which buyer. Then keep the page where your people and your AI tools both write from it.
If you'd rather have it built, the messaging is part of the brand and strategy work in my Marketing Foundations. A company that only needs its story fixed can hire me for a positioning and brand project instead.
Hand out the chart before the next gig.
Common questions
What's the difference between a messaging framework and a positioning statement?
The difference between a messaging framework and a positioning statement is who reads it. A positioning statement is an internal decision about who the company serves and how it differs, and customers never see it. A messaging framework turns that decision into the promise and the lines customers actually read and hear.
Who should own the messaging framework at a startup?
The owner of a startup's messaging framework is usually the founder, until a marketing leader arrives to take it over. One person decides what changes, and sales gets a say because reps hear the objections first. A framework with no owner drifts as each team edits its own copy.
How often should a messaging framework be updated?
A messaging framework should be updated when the positioning changes or a new kind of buyer starts showing up in deals. A quarterly read-through catches drift in between. A startup that rewrites its framework every month usually hasn't settled the positioning underneath it.
Is a messaging framework the same as a brand voice guide?
A messaging framework and a brand voice guide answer different questions. The messaging framework decides what the company says. The voice guide decides how the company sounds, which stays constant while the tone shifts from channel to channel. Many startups keep the two on one page.