← All writing

Product Marketing

How to build a B2B messaging house: the framework PMMs actually use

By Nick Pham6 min read

TL;DR

Four descriptions of one product, all published this week. The copy is fine and nothing sits underneath it. A messaging house holds six parts. One value proposition, three pillars, proof under each, an unlike line, segment variations, and objection responses. Most teams finish the document and stop there. The house only counts when someone who didn't write it says a line out loud without looking it up.

Four descriptions of the same product went out this week. The agency's copy. A deck the field rebuilt on Sunday night. A product page someone rewrote in a hurry. A blog post.

None of them wrong. Four different promises, made to four slightly different customers.

We call that a copy problem and hand it to whoever writes best. But the sentences are fine. Nothing sits underneath them.

A messaging house is what sits underneath. It's the document that says what we claim, what proves the claim, and how the claim bends for each buyer without breaking.

Positioning decides who we're for and why we win. The house decides how we say it, the same way, in every room.

Most companies operate without one, and the cost stays quiet. Buyers hear a different story depending on who picks up the phone, and nobody files a ticket about that.


What the house holds

Six parts. The whole thing fits on five pages.

The one sentence

We help [specific audience] [achieve outcome] by [differentiated approach].

Spend longer here than feels reasonable. This sentence goes on the homepage, at the top of every deck, in the first line of every sequence. Wrong here means wrong everywhere downstream.

Two ways we get it wrong. "We help teams work better" is generic enough to belong to anyone, and "the only platform with X and Y" names no outcome at all.

There's a third failure that hides better. If the thing takes two sentences to say, we've written a paragraph and hoped nobody would notice.

The test is whether a new salesperson can say it unprompted after one read. Not read it off a card. Say it, to a stranger who asked what we do.

The pillars

Three things we need every buyer to believe by the time the conversation ends.

Three because three is what a person carries out of a meeting. Four is a list. Two undersells.

Each pillar answers a distinct buyer concern rather than describing a feature, and each one has to be provable. If a competitor could say it word for word, it isn't a pillar yet.

Most pillars hold up in this shape. "[Benefit] because [mechanism]. Unlike [alternative], we [difference]."

A customer support platform might land on speed, adoption, and evidence. Features live under pillars, never inside them.

The proof

Every pillar carries evidence, and evidence comes in four forms.

Numbers we can defend under questioning, because a vague stat does more damage than no stat. Customer evidence with a name attached, since one real story outruns twenty anonymous ones. Third-party validation from analysts, review sites, and industry bodies.

And mechanism, which is the one teams forget. Sometimes the most persuasive proof is a plain explanation of why the approach works at all.

Organize the library by pillar, then tag each item by segment, by deal stage, and by competitor. Different proof lands against a different rival. That tagging is what turns a document into something sales actually opens.

The unlike line

"Unlike [alternatives], we [difference that matters to this buyer]."

The word alternatives is doing more work than it looks.

For one buyer the alternative is a spreadsheet. For another it's the suite they already paid for. For plenty of them it's doing nothing, which closes more of our deals than any competitor does.

Write one line for each of the matchups that come up most, and put them in the battlecards.

The variations

One value proposition. One set of pillars. The language moves.

A CFO and a support director are buying the same product for different reasons. The CFO is managing risk. The director is managing a queue.

For each segment, lead with the pillar that matters most to them, use their words instead of ours, and answer the objection that always comes up.

The objections

This is the part most houses skip, which is why reps improvise.

  • "We already have an incumbent."
  • "You're too expensive."
  • "Not this year."
  • "How is this different from the other one?"

Every one of those is a messaging problem before it becomes a sales problem. For each, write the reframe, the proof point, and the next question to ask. It belongs here rather than in a Notion page nobody opens.


Positioning first

Positioning is the decision. Messaging is the expression of it.

Build the house on a validated positioning statement, never alongside one that's still moving. Language can't rescue an unclear decision. It just distributes it faster.


Where the language comes from

Not from us.

Open the win/loss transcripts, the call recordings, the ticket themes. We're hunting for the exact words buyers use for the problem, for why they went looking, and for why they chose us or didn't. The phrases that repeat are the raw material.

Good messaging gets harvested more than it gets written. What we're assembling already exists in the market, scattered across a hundred calls, said badly by people who were mid-thought.

Then pressure-test. Take the draft value proposition to the three people who sell the most and ask whether it's what they actually say when a prospect asks what we do. "Sort of" is a no.

Then pull the last ten wins. If the pillars don't match what those buyers said decided it, rewrite the pillars.

Keep the finished thing to five pages. Twenty pages is a research document. Useful, and a different object.


The half nobody does

And here's where it comes apart. We treat the house as a writing project, so we celebrate the day the document is done.

The document was never the deliverable.

A messaging house is finished when someone who didn't write it says a line out loud, in their own voice, without looking it up. Everything before that is a file.

So launch it the way we'd launch anything else:

  • Thirty minutes, live, with room for questions. A Slack link doesn't do it.
  • A one-page reference for sales.
  • Website, deck templates, and outbound sequences moved to the new language in the same week.
  • A check-in thirty days later to hear what broke.

The signals come from outside the team.

Reps stop winging it and start pulling language from the doc. Inbound gets less noisy, because when the story is precise the wrong people stop raising their hands. Customers start handing our own sentences back to us in discovery calls.

Then keep it alive. A quarterly calibration against the last quarter's deals is enough, and it beats the annual ground-up rebuild that everyone dreads and nobody schedules.

Call that second one the borrowed sentence. A line someone repeats without attribution and without looking it up, because it says the thing better than they could say it themselves.

That's the only unit of measure the house has. Four descriptions of one product means nobody has borrowed anything yet.

Write the sentence worth borrowing.


What to do next

If the deck, the homepage, and the last agency draft each make a different promise, the gap is architectural and more copy won't reach it.

That's a messaging sprint, and it starts with the buyer language already sitting in transcripts nobody has read. If that's where you are, start here. The first conversation is free.


Frequently asked questions

A brand guide covers visual identity, voice and tone, and design standards. A messaging house covers the claims, the proof, and the narrative structure that should show up in buyer-facing content. The brand guide governs how we say things. The house governs what we say. Both matter, and they solve different problems.

For a mid-stage B2B SaaS company with one or two PMMs, four to six weeks done properly, including research, validation, and the internal launch. Under two weeks means something got skipped. Past three months means the scope grew into a different project.

Product marketing owns it. It gets built with input from sales on win patterns and objection language, from customer success on retention drivers, and from product on capability limits. PMM owns the synthesis and the final document.

Start with one for the core product. As the portfolio grows, build product-level houses underneath the company-level house. The company house defines the category and the brand promise. Product houses define what each product is worth inside that promise.

Related reading

The author

Nick Pham

Founder of Bare Strategy. Twenty years in B2B marketing, the last decade in product marketing inside enterprise software.

More about the operator →

If this is where you are

Bring the problem, not a brief, and you'll leave the first conversation with something useful either way.

Start a conversation