voice + messaging · 24 jun 2026 · 3 min read
how to build a messaging framework (that sales will actually use)
marcus · voice + messaging

most companies do not have a messaging problem. they have a messaging surplus. ten true things about the product, said in random order by different people, until the market hears nothing in particular. a messaging framework exists to fix that: it decides which true things lead, which support, and which stay in the drawer.
here is the structure we build, and why each layer earns its place.
one core message
the single idea the market should associate with you. one sentence, no commas doing heavy lifting. this is the hardest part and the reason frameworks fail, because choosing one idea means demoting nine others, and committees hate demoting. but a core message that contains everything communicates nothing. pick the claim that is most true, most different and most valuable to the buyer, in that order of tiebreak.
three supporting pillars
the reasons to believe the core message, grouped into three themes at most. three because humans retain three, and because forcing the cut exposes which arguments are actually strong. each pillar gets a plain statement and the proof behind it: the mechanism, the number, the story, the named customer.
proof, not adjectives
every claim in the framework needs evidence attached or it gets cut. "fastest onboarding in the category" survives if you can say "live in four days against an industry average of six weeks". "world-class support" dies on contact. a framework full of unproven claims is just a tone of voice document with ambitions.
audience translations
the same pillars, restated for each audience that matters: the buyer, the user, the investor, the journalist. not different messages, the same message in their language and against their alternative. this is the layer that makes sales decks, pr pitches and landing pages stop contradicting each other.
the usability test
hand the framework to a salesperson and ask them to open a cold call with it. hand it to whoever writes the website and ask for a homepage hero. if both can do it in minutes without interpreting, it works. if they ask "but what do i actually say", you have written strategy theatre.
a good framework is short, sounds like the brand, and gets used because using it is easier than improvising. that last part is the design constraint most agencies miss.
messaging is the core of our story sprint: positioning, voice and the framework built together by one team, then pressure-tested on the real assets, the site, the deck, the pitch.
saying ten things and being heard saying none? let's talk.
related posts
thought leadership without the cringe
the phrase is embarrassing but the asset is real: a founder with a known point of view makes every other channel cheaper. here is how to do it without becoming a linkedin caricature.
ux writing is brand voice at the smallest scale
buttons, error messages, empty states: the smallest words in your product carry the brand more often than your homepage ever will.
one idea a fortnight.
the thinking we use on real brands, written down. no filler, no funnels.