Ask five people at a B2B company to describe what the product does and you will get five different answers. Ask to see the messaging and you will be pointed at ten decks, each with a slightly different version, none of them canonical. Product marketing says it one way, sales another, demand-gen a third. There is no single source of truth, so every asset re-litigates the positioning from scratch, and the message drifts a little further with each rewrite.
A messaging framework is supposed to be the fix. In most orgs it is a static document that was accurate the day it was approved and out of date the day after, because nothing downstream is actually bound to it. It sits in a drive while the real messaging evolves, uncontrolled, across a thousand assets.
We think a messaging framework should be a living block that every asset inherits from, not a PDF that drifts. Here is how to build one.
The real problem: positioning without a spine
The core issue is not that teams lack messaging. It is that they lack one authoritative version of it, in a form other work can actually reference.
When the framework is a file, "inheriting" from it means a human remembers to open it and copy the right sentence. That never scales. So the value pillars mutate, the boilerplate exists in four incompatible lengths, and the proof points get quietly dropped whenever someone is in a hurry. The message is not wrong anywhere in particular. It is inconsistent everywhere in general, which is worse, because inconsistency is what erodes trust with a buying committee that sees your content across a dozen touchpoints.
Our take: distill one source of truth, grounded in what you own
A messaging framework is the canonical Message in the way we think about marketing: Audience times Message times Channel. It is the medium-neutral spine every downstream asset should inherit, the reusable unit of meaning that a blog post, a sell sheet, and an ad are all just channel expressions of.
So the opinion is direct: distill one source of truth, ground every claim in what you actually own, and make it a live block others build from.
A messaging framework is the Message every downstream asset should inherit from, not a static file that drifts the day it ships.
The Build a Messaging Framework Job takes your positioning notes, product information, research, and existing messaging, and composes them into a canonical, sectioned document with a deliberate structure:
- A positioning statement: the one sentence the whole org can agree on.
- Three value pillars: the load-bearing claims, in priority order.
- Proof for each pillar: the evidence that makes each claim credible, not just asserted.
- Boilerplate at 25, 50, and 100 words: ready to paste into any asset, at any length, without a rewrite.
The tone is pinned to crisp and canonical, the audience to your ideal customer profile and buying committee, and the hard constraint is one source of truth with consistent terms throughout, every claim grounded in the source.
How the Job keeps it honest and consistent
Two mechanics do the quiet work.
First, when you supply a structure, it is treated as authoritative. The engine turns each named section into a heading, in order, and does not revert to the source's own shape. You get the positioning-pillars-proof-boilerplate framework you asked for, every time, not whatever structure the input happened to have.
Second, the framework gets smarter as your library grows. When it composes, the engine retrieves your other relevant content, not just the source you handed it, and grounds the framework in that accumulated organizational knowledge. Importantly, this is retrieval and grounding, not model fine-tuning: the platform injects what it knows about your org as context, per-org and tenant-safe, so the framework reflects your actual positioning rather than a generic template.
The output is a real block, provenance-linked to its sources, editable, and, crucially, available for every other Job to ground on.
Why this belongs in Plan
Positioning is a Plan-stage decision, and getting it into a canonical, machine-referenceable form is what makes the rest of the workflow coherent. When your blog posts, sales collateral, and carousels are all grounded in the same framework block, consistency stops being a thing you police on every asset and becomes a property of the system.
Build the spine once. Let everything inherit it. That is how a message stays canonical across a thousand assets instead of drifting across ten decks.
Related: research the market that your positioning has to win in, and turn the framework into a campaign brief with real KPIs.
