Voice of the customer

Message architecture

Message architecture is licensed CC BY 4.0. Attribution: Katafacts (katafacts.com).

1 · What it is

What it is

A message architecture is the org-wide version of a value hypothesis — the same three-level tree (buyer need, message pillar, proof point), but built once and reused across every deal and every channel instead of rebuilt fresh per opportunity. A message pillar without a real number behind it is a slogan, not a message architecture — "we help you catch risk early" isn't a pillar; "deals flagged at-risk within 48 hours, versus 3 weeks today" is. The tree tracks its own coverage the same way a value hypothesis does: any pillar with no proven measure yet is named directly, not quietly treated as ready to use in marketing copy.

2 · When to use it

When to use it — and when not to

Use it when

You have proof points that already worked in real deals (a value hypothesis, a case study, a deal A3 finding) and want to turn them into a standing message every rep and channel uses the same way.
Reps, marketing, and customer success are each describing the product's value differently, and you want one substantiated version everyone actually uses.
You want to know honestly which claims in your current pitch are backed by a real, provable number and which are still an assumption dressed up as a pillar.

Not when

You don't have any proven deals yet — a value hypothesis for a real opportunity comes first; a message architecture generalizes from proof that already exists, it doesn't invent proof from nothing.
You want a single deal's specific pitch — that's a value hypothesis; a message architecture is the standing version reused across every deal.

3 · How to fill it in

How to fill it in

Scope: What product or product line is this the standing message for?
Needs → drivers → measurable CTQs: List each buyer need this message speaks to, ideally traced to real proven deals. Pillars and proof points get drafted beneath each one — don't fill those in at intake.
Coverage: Computed for you: total needs, pillars, and proof points, and which needs still have no proven measure beneath them — nothing to enter here.
Narrative: Drafted from the tree and any coverage gaps — which pillars are proven and ready to use, which aren't yet.
Next steps: What will you do about an unproven pillar or a specific gap, ranked by impact and effort, owned and dated?

4 · What good looks like

What good looks like

The example below generalizes the value hypothesis already built and proven for the Northline Freight opportunity into Beacon Analytics' standing message — the same 48-hour visibility target and $310K reference figure, organized as the message every deal should use, with the one unproven pillar honestly held back rather than shipped as a claim.

Same example, as a downloadable xlsx workbook.

Download .xlsx

CTQ tree

Beacon Analytics — message architecture

Priya Anand, RevOps · 2027-03-01

Team: Renee Okafor, VP Sales · Sponsor: Sam Cole, Sales Enablement

Scope

Beacon Analytics' core platform message — the standing pillars and proof points every rep and every marketing channel should use, not rebuilt fresh per deal.

Needs → drivers → measurable CTQs

RevOps and sales leadership need to see pipeline risk before it shows up in the forecast, not after

Evidence: Generalized from the value hypothesis built for the Northline Freight opportunity — the same visibility gap surfaced in that deal's discovery call, and echoes Beacon Analytics' own Q1 deal A3 finding.

Real-time deal-risk visibility, without a manual pipeline review

Time from a deal going quiet to being flagged at-risk< 48 hours — the same target figure the Northline Freight value hypothesis committed to

A repeatable, named reason a deal is stalling, not just that it is

% of stalled deals with a categorized stall reason logged≥ 90%

Whoever approves the purchase needs a defensible, quantified reason to say yes without Beacon Analytics in the room

Evidence: The exact gap named in Beacon Analytics' own Q1 deal A3: 'business case never quantified' accounted for $40K of that quarter's stalled pipeline value. This pillar exists specifically to close it, standing across every deal, not rebuilt each time.

A quantified cost-of-inaction the champion can carry into a budget conversation alone

$ value of at-risk pipeline flagged 2+ weeks earlier, calculated from the buyer's own historical deal dataReference figure: $310K, from the Northline Freight trial cohort — cited as a real result, never presented as a guaranteed number for a new buyer

The team already using spreadsheets needs to trust a new system before they'll stop trusting the old oneNo CTQ yet

Coverage

Needs

Drivers

Measures

No measurable CTQ yet: The team already using spreadsheets needs to trust a new system before they'll stop trusting the old one

Narrative

Two pillars are fully specified with real, already-proven numbers: real-time deal-risk visibility (the 48-hour figure) and a quantified, defensible business case (the $310K reference figure) — both traced directly to the Northline Freight deal rather than invented for this document. The third pillar — trust over a familiar spreadsheet — has no proof yet and stays out of the standing message deliberately, rather than shipping as a claim nobody has substantiated. Every rep and every piece of marketing copy should use the same two proven pillars, in the same words, until the third one earns its place the same way the first two did.

Next steps

Run a structured pilot that actually tests whether buyers trust Beacon Analytics over their existing spreadsheet before using that as a marketing claim — right now it's an assumption, not proof.
Linked finding: The team already using spreadsheets needs to trust a new system — no measurable CTQ yet
Impact: medium · Effort: medium · Owner: Priya Anand · Due: 2027-03-28
Roll the 48-hour visibility target and the $310K reference figure into the standard sales deck and case study template, so every rep and every channel uses the same substantiated numbers instead of each inventing their own phrasing.
Linked finding: Both pillars — fully specified with proven targets
Impact: high · Effort: low · Owner: Sam Cole · Due: 2027-03-15

5 · Common mistakes

Common mistakes

Promoting a pillar into the standing message before it's actually been proven in a real deal.
A message architecture exists specifically to stop an assumption from quietly becoming "the pitch" — an unproven pillar belongs in the coverage gap, not in marketing copy, until it earns its place the same way the proven ones did.
Letting each rep or channel restate a proven pillar's number in their own words.
A pillar's whole value is a specific, checkable number — "pretty fast" instead of "under 48 hours" quietly turns a substantiated claim back into an assertion nobody can defend.
Building the message architecture before any deal has actually proven the pillars underneath it.
This tool generalizes from real, already-proven evidence — building it first and hoping deals prove it later inverts the order this catalogue's own discipline depends on everywhere else.

6 · What it connects to

What it connects to

upstream

Value hypothesis
A pillar's proof point should trace back to a real value hypothesis that actually worked in a deal — this tree is where that proven pillar gets promoted into the standing message, not invented fresh.

downstream

Value proposition canvas
The same needs and proof points organized here as a tree map directly onto a value proposition canvas's jobs/pains/gains — two complementary views of the same evidence, not two separate messages to keep in sync by hand.
Consistency audit
Once a pillar is proven and promoted here, a consistency audit is what checks weeks later whether reps and channels are actually still using it — and whether an unproven pillar has quietly crept into claims anyway.
Proof point inventory
This tree's own proven pillars are exactly the categories a proof point inventory tracks over time, as more deals add more real, checked evidence beyond the first one that proved each pillar.

7 · Where AI helps

Where AI helps

Judgement — stays yours

Deciding whether a pillar's evidence is strong enough to promote from a single deal into the standing message
Deciding which coverage gap to close before the next pillar gets promoted

Analysis — AI helps

Drafting pillars and proof points from a stated need and its supporting proven-deal evidence
Drafting the narrative from the tree and any coverage gaps

Drudgery — automated

Counting needs, pillars, and proof points across the whole architecture
Identifying which needs still have no proven measure
Exporting to xlsx in the house format

9 · Rate this kata