Messaging House Template for a Web3 Startup, Filled In

A messaging house is a one-page document with three layers: a roof (the single sentence that says what you are and why it matters), three pillars (the reasons someone should believe it), and proof points under each pillar (facts you can verify and show). A foundation underneath holds the boilerplate, tone and the words you avoid. For a startup, the template's value comes from what pulls from it: your website, press materials and KOL briefs should all quote the house rather than invent their own version.

Below is the template I use, filled in for a fictional Web3 company so you can see every box with real-looking content, followed by how each team takes from it.

Why does a Web3 startup need a messaging house?

Because in crypto, many people speak for you at once. Founders post on X, the BD lead talks at side events, KOLs write threads, community mods answer questions in Telegram and Discord, and journalists quote whatever they can find. Without one shared source, each of them builds a slightly different version of the company, and the market hears noise.

comms is so underrated in web3 but that's everything! how you communicate w your community, stakeholders, customers, retail users, airdrop hunters, journos is literally everything! Shilika Jain on X, 3 Jun 2025

That list of audiences is the reason the house exists. Each audience needs a different emphasis, but all of them should hear the same core claim. The messaging house is how you keep emphasis flexible and the claim fixed.

It also changes what PR work starts with. Most teams think PR begins at the pitch. It begins earlier:

most projects think that PR is asking a media to publish an article about their company what it actually is - creating a storyline, working on the messaging & narrative, pitching to targeted journalists, reaching out to them with well-curated pitches, following up & more! Shilika Jain on X, 13 Apr 2023

The messaging house is that "working on the messaging" step, written down.

What goes in each part of the house?

A few rules I hold each layer to.

The roof names an outcome for a person, not an architecture. If it contains a protocol name or an acronym, it isn't finished. It should also name an enemy, something the company is against, because a claim with no tension gives a journalist nothing to write about.

The pillars are three, not five. Five pillars means nobody will remember any. Each pillar should be something a competitor couldn't easily say about themselves with a straight face.

Proof points must be checkable. A number with a date, a named partner, a public dashboard, an audit report, a published survey. "Industry-leading security" isn't a proof point. "Audited by [named firm], report public since [month]" is.

The foundation is the boring part teams skip, and then regret. It holds the approved boilerplate, the one category word you'll own, and a short list of terms to never use in mainstream copy. My crypto jargon cut list is a good starting point for that last section.

What does a filled-in Web3 messaging house look like?

Here's a full house for a fictional company, Harbourline, a stablecoin payroll app for small remote teams. Harbourline isn't real and the figures in brackets are placeholders, so treat the structure as the lesson, not the content.

Roof "Harbourline lets small remote teams pay contractors anywhere in digital dollars, in minutes, without a bank in the middle. We're against the week-long, fee-heavy international wire."

Pillar 1: Paid in minutes, not days Support line: contractors receive dollars on the same day the invoice is approved. Proof points: - Median payout time, published monthly on a public status page [placeholder figure] - Number of countries where contractors have been paid [placeholder figure] - A named customer case study with the before and after timings

Pillar 2: Costs you can see before you send Support line: the fee is shown up front, in dollars, before you confirm. Proof points: - Fee schedule published on the pricing page - A side-by-side cost comparison against a standard international wire, with the method explained - An owned data report: a survey of remote team founders on what cross-border payments cost them [to be commissioned]

Pillar 3: Your money stays yours Support line: funds sit in accounts the company controls, not on Harbourline's balance sheet. Proof points: - Third-party security audit, named auditor, report link - Custody model explained in a public one-page doc - Incident history page, kept current even when there's nothing to report

Foundation - Category word: "stablecoin payroll." Glossed on first use as "paying people in digital dollars." - Boilerplate (40 words): written once from the roof and pillar headlines, reused verbatim everywhere. - Tone: plain, specific, calm. No price talk, no token talk in customer channels. - Avoid in mainstream copy: bridge, gas, non-custodial, onchain, L2.

Notice what's missing. There's no token, no chain name and no "revolutionary." Those may exist in Harbourline's docs and investor materials. They don't belong in the house, because the house is for every audience.

Where do strong proof points come from?

From things you own and can show again next quarter. The best proof points I've seen in client work fall into three types:

1. Usage numbers with a public source. GAIA's node count did this job: "400K nodes" appeared in a Binance Square headline in April 2025, and node count worked as proof for the decentralised AI agents narrative across a steady run of founder interviews.
2. Owned research. Tangem's self-custody survey, with its two-thirds-of-users-support-self-custody stat, gave journalists a number to lead with, and it travelled across English, Korean, Japanese and Dutch editions.
3. Named partners. Web3Auth's Google Cloud partnership, paired with an adoption report, gave two separate news hooks in one quarter.

What these share: a reporter can verify them, and each one makes a pillar concrete. If a pillar has no proof point yet, mark it "to be built" in the house. That gap becomes your next quarter's PR plan.

How do PR, website and KOL briefs pull from the house?

This is the part that makes a messaging house worth the afternoon. Each output takes a specific slice. I call it the pull map:

Two things follow from the map. First, no output gets to invent its own roof. If the homepage, the boilerplate and the KOL brief describe the company differently, one of them is wrong, and the house tells you which. Second, each output uses one pillar at a time. A press release that tries to prove all three pillars proves none of them.

For KOL work specifically, the house saves a lot of rewriting. The brief pulls the roof as a must-say line and the avoid list as must-not-say. My KOL brief template shows the full brief format, and the KOL marketing service runs on the same source document.

How do you build the house in one working session?

I do it in about three hours with the founder, one product lead and whoever owns the data.

1. Collect every current description. Homepage, deck slide one, X bios, the last release's boilerplate. Read them aloud back to back. The differences usually make the case for the exercise on their own.
2. Write the roof first, and argue about it. Most of the session goes here. Use plain words and name the enemy.
3. List every reason to believe, then cut to three. Group the long list into themes. Keep the three that competitors can't easily claim.
4. Attach proof to each pillar. Mark gaps honestly.
5. Write the foundation last. Boilerplate comes straight from the roof and pillar headlines.
6. Ship it to everyone who speaks for you. Team, investors, KOLs, community mods. A house nobody else reads is just a nice document.

if your brand lacks story, it lacks everything! Shilika Jain on X, 28 Nov 2022

The house is how a story becomes something a whole team can actually tell.

When is a messaging house not the right tool?

It has limits. Pre-product-market-fit teams often don't know their real user yet, so a detailed house locks in guesses. In that case, write a roof and a one-line enemy, skip formal pillars, and revisit every month.

Teams that pivot often can end up maintaining a house that describes last quarter's company. Put a review date on it, quarterly at most.

And the house doesn't replace a sharper positioning exercise. If you haven't decided who you're for and what you're against, start with a positioning statement and come back to the house afterwards. A house built on an unclear roof just spreads the confusion more consistently.

When the roof is settled and you're ready for it to show up in coverage, that's where Web3 PR campaigns take over.

FAQ

How is a messaging house different from a positioning statement?

A positioning statement defines who you're for, what category you're in and how you differ. The messaging house takes that decision and turns it into language and evidence different teams can reuse. You need the positioning first, and the house is what you hand to everyone else.

How often should a startup update its messaging house?

Review proof points monthly, since numbers go stale fast. Revisit pillars quarterly. Change the roof only when the strategy changes, such as a new primary user or a new category, because every change to the roof means rewriting every output that pulls from it.

Should the token appear in the messaging house?

Usually not in the roof or pillars. Token details belong in investor and community materials with their own disclosure rules. Keeping the token out of the house stops price talk leaking into customer and press copy.

Who should own the messaging house?

One person, usually the comms or marketing lead, with the founder signing off on the roof. Shared ownership tends to mean nobody updates it. The owner's job is to keep it current and to flag any output that drifts from it.

If your homepage, deck and boilerplate each tell a different story, let's build your house together in one working session.