Brand Messaging Framework: A One-Page Version That Sales and Marketing Can Both Use, With a Fill-In Table

A brand messaging framework is a short shared document that turns a positioning decision into usable language: who you are talking to, the problem you solve, what you promise, the proof, how you differ, how you answer objections and how you sound. A new rep, a freelancer and a web designer can all say the same thing from it.

Positioning and messaging are different jobs, and mixing them is why many frameworks stall. Positioning is a decision about where you stand in the buyer's mind relative to the alternatives. Messaging is the language that expresses that decision to different readers in different places. We cover how to write and test the decision in our post on the positioning statement template, and we do not repeat it here. If you have no position yet, the framework below will expose that quickly: the differentiation row will be blank or generic.

Keep it to one page. In our view a twenty-page brand book is a document people read at launch and then stop opening. A page that sits open on a rep's second monitor and in a writer's brief gets used. Length is also an honest test of clarity. If you cannot say it on one page, you probably have not decided it.

Eight rows are enough. The first seven carry the substance and the last keeps the language consistent. For each row the table gives the question it answers, a prompt to fill in, and the test the line must pass before it stays. Write for the reader of the sentence, not for the person who approves it.

Start with what buyers have already told you. Four sources cost little: notes from sales calls, the lost-reason field in the CRM, reviews of your business and of competitors, and a handful of customer interviews. Our posts on customer interview operations, win-loss analysis selection bias and customer review mining cover how to do each without fooling yourself. Treat the phrases you find as raw material. Copying a customer's words into the problem row is research. Quoting them publicly as a testimonial needs their permission.

Write the problem row before the promise row, and write both before the differentiation. It is easier to claim an outcome you have not yet tied to a problem, and the result is a promise nobody was asking for. Then have a rep and a marketer fill in the page separately and compare. Where the two sheets disagree, you have found the places the teams currently tell different stories. That comparison is often more valuable than the finished page.

When the evidence for a row is thin, leave it thin on the page. A short, honest promise beats a long one that you cannot back up. It is also easier to build on. If the proof row is empty, the next job is to gather proof, not to write around the gap.

Proof is the row most often padded, because it is the row that sells. The FTC's policy statement on advertising substantiation says that advertisers need a reasonable basis for objective claims before they make them. Whether a particular sentence is advertising is a legal question for counsel, but the discipline is good practice for any claim a buyer might rely on. Every number needs a source, a period and an owner. Every superlative needs something behind it or should go.

Testimonials and endorsements carry their own rules. The FTC's Endorsement Guides, revised in 2023, say that a connection between an endorser and a marketer that a significant minority of consumers would not expect, and that would affect how they weigh the endorsement, should be disclosed clearly and conspicuously. A customer who was paid, discounted or related to someone at your company is a connection to disclose. Check current rules with counsel before you publish endorsements.

A simple ladder keeps the proof row honest. Use the strongest rung you actually have, and say which rung it is. Do not borrow the strength of a higher one.

Differentiation fails when it is a list of virtues. Fast, reliable, customer-focused: every competitor says them. The test in the table, whether a competitor could say the identical sentence, removes most candidates. What survives is usually specific: a process you run, a constraint you accept, a type of customer you decline. In our view, saying who you are not for is often the most believable line on the page.

The objection row works best when each entry has five parts: what the buyer says, what they probably mean, a short answer, a pointer to proof, and a question you can ask back. The question matters. An answer closes a point, and a question keeps the conversation moving and tells you whether the objection was real. We cover this from the sales side in our sales enablement post. The framework page holds the answers. The enablement work turns them into something a rep can use mid-call.

The table below fills in a few rows for an invented business, a bookkeeping service for independent dental practices. It is illustrative. The business, the entries and the wording are made up to show the level of specificity to aim for, and the proof row is left as an instruction because we hold no evidence for a fictional firm.

Adjectives such as friendly, professional and bold describe nothing a second writer can reproduce. Positions on dimensions can be reproduced. The Nielsen Norman Group describes four dimensions of tone of voice: funny versus serious, formal versus casual, respectful versus irreverent, and enthusiastic versus matter-of-fact. It notes that a product's tone can be expressed as a point in that four-dimensional space. Mark each dimension on a simple scale, and write one example sentence in that tone and one that is too far in either direction. A writer can check a draft against it.

Distinguish voice from tone, as Mailchimp's public content style guide does. Voice is the steady character of the writing, and tone changes with the situation: a billing error calls for a different tone from a product launch. Write the voice once on the page and give tone a short note on how it moves with context. The same guide describes valuing clarity over hype, which is the right instinct for most small businesses.

Plain language belongs in this row. The Nielsen Norman Group argues that even expert readers prefer plain language, and that clear, direct writing is not talking down. For a framework that sales will use aloud, it is also a practical test: if a rep stumbles reading a line out loud, the line is wrong.

Roll it out by using it. A shared page is how a shared vocabulary happens in practice. Have a rep read the page aloud on a real call, have a writer use it on a real brief, and change what breaks. Give the page one owner, a version and a review date at the top, and put it in the one place both teams already look. A framework that lives in a slide deck dies in the slide deck. If your team already keeps one canonical home for sales material, add the page there.

Review it on a schedule, and sooner when the evidence changes. A lost deal that lands on an objection the page does not hold is a prompt to add it. A proof entry that loses permission or goes out of date should come off the same day. Cut rows that nobody uses. The aim is not a complete document but a current one. If the page is still true in a year, you have probably been too vague. If it has changed every month, you may still be deciding the position, which is the work to finish first.