Most brand messaging skips straight to solutions and features. This is the ladder that puts conviction first, and the reason it changes what everything downstream sounds like.
Ask a marketing team what their company does and you'll get a competent answer. Ask what the company believes and you'll usually get a pause, then a value prop restated more slowly.
That gap is why so much B2B messaging is interchangeable. It's accurate. It describes real capabilities for real buyers. And a competitor could sign it without changing a word, because it never took a position anyone could disagree with.
The fix is a layer that most frameworks leave out entirely.
What does my prospect need to believe in order to buy?
Billy Broas · Simple Marketing for Smart PeopleA conviction is something the company believes that its buyers already suspect but nobody has said out loud. It's what makes an audience say exactly, turning a silent frustration into a shared belief. That belief is what earns the right to present a solution at all.
Nine levels, each one constraining the next. Read top to bottom, it's a derivation: by the time you reach feature language, every word is traceable to a belief.
| Level | The question it answers | Failure tell |
|---|---|---|
| Corporate Strategy | What is the company actually trying to become? | Marketing invents its own strategy because nobody wrote this down. |
| Elevator Pitch | What do we say in one breath, without hedging? | It needs a second sentence to make sense. |
| Audience | Who is this for, by responsibility rather than title? | A persona doc nobody could use to recognize a real person. |
| Problems | What is going wrong in their week? | It's the category's problem, not theirs. |
| Convictions | What do we believe to be true that they'd agree with? | A competitor could say it. This is the gate. |
| Perceptions | What should they now believe about us? | It restates the conviction instead of following from it. |
| Solutions | What do we offer that acts on the conviction? | The solution existed before the conviction and got retrofitted. |
| Use Cases | Where does this show up concretely? | Generic scenarios that fit any vendor in the category. |
| Feature Sets | What specifically does it do? | Feature language that doesn't trace up the ladder. |
Most messaging work starts at Solutions and reasons outward. That produces something defensible and forgettable, because the argument is running backward: here is what we built, therefore here is why you need it.
Running it forward inverts the burden. Here is what's going wrong. Here is what we believe about why. Here is what follows if that's true. By the time the product appears, the reader has already agreed to the premise, and the product reads as the natural consequence rather than a pitch.
It also does something structural: it gives every downstream team the same source. Campaign copy, sales talk tracks, executive bylines, and product launch narratives all derive from one ladder instead of each inventing a position and drifting apart.
This runs parallel to PMM's product positioning, not on top of it. The distinction is altitude. Product positioning answers what the product does and who it beats. Brand-level architecture answers what the company stands for and why anyone should care that it exists.
Both are necessary. They fail differently: a company with positioning but no conviction competes entirely on features. A company with conviction but no positioning can't close a deal.
The test is a single question, and it's brutal enough that most first drafts don't survive it.
Put a competitor's logo on the sentence. Is it still true and sensible? If so, you've written category education, and you're spending your budget teaching the market to buy from anyone.
Three failure modes come up repeatedly:
Using a manufactured brand, Meridian, a hypothetical platform for field service operations, to show the derivation without exposing anyone's live messaging.
| Level | Meridian |
|---|---|
| Problem | Work gets approved by whoever happens to be looking at their phone, and the record of why is scattered across texts, email, and memory. |
| Conviction | Losing control of spend is what happens when the decision and the record live in different places. Control should be a property of the workflow rather than of somebody's vigilance. |
| Perception | Meridian makes the disciplined choice the default one, so nobody has to be heroic to keep spend clean. |
| Solution | Approvals, documentation, and payment in one workflow, with the record produced automatically as a byproduct. |
Notice what the conviction does that the solution can't: it reframes the reader's situation from a personal failing into a structural one. That reframe is the thing they'll remember, and it's the reason the solution lands as relief rather than as a sales pitch.
This front-loads work into a phase that used to feel optional, and the first campaign built this way will feel slower. The payoff is that the second one starts from a shelf instead of a blank page, and every campaign after that inherits an argument nobody has to relitigate.
The Ad Modules framework handles the compression problem: how to write an argument once at every length it will ever need, so a designer assembles placements from a shelf instead of rewriting the argument thirteen times.