Messaging

For a long time, whoever needed a sentence about the product simply wrote one. A designer wrote the homepage headline, a sales rep wrote the deck, a recruiter wrote the job post. Everyone knew the product, so nothing was wrong exactly, but the three sentences didn't match. The homepage said "document collaboration tool," the deck said "meeting productivity solution," and the job post said "knowledge management platform."

The damage shows up because customers see all three. In one meeting Sofia was describing the product when the customer turned a laptop around, pulled up the website, and asked whether that was even the same thing she was talking about. She said yes, and the answer was true, but trust dropped a notch anyway. From the other side of the table it looked like the company selling the product couldn't say what it was.

The same friction ran inside the company. Every time an ad needed new copy, someone reopened the question of what to call the product, and whatever got decided stayed in that one ad and reached nobody else. Messaging exists so those sentences get settled once and written down instead of being invented again each time.

A messaging document usually holds five blocks, and they run from general at the top to specific at the bottom.

1. The one-line description. This is what you hand someone who has never heard of the product. Pagedeck uses "the collaboration doc tool where the meeting notes are done before the meeting ends." Descriptions built on the change the customer experiences age better than descriptions built on features.
2. Three core benefits. Three lines on why someone buys this. A benefit is not a feature: "real-time co-editing" is a feature, and "nothing is left to write up after the meeting" is a benefit. The limit is three because a list of six leaves the listener remembering none of them.
3. The evidence behind each benefit. Next to every claim goes a reason to believe it — a feature name, a number, a result an actual customer got. A line like "time spent writing up meetings dropped from six hours a week to one" sits in this slot.
4. Variants by customer type. The same benefit gets said differently depending on who is listening. To a product manager it's "you stop digging for what was decided," to engineers it's "decisions land on the ticket directly," and to a founder it's "you spend less payroll on meetings."
5. Words not to use. The banned list is part of the document too. Pagedeck dropped "innovative" and "all-in-one" because ten competing products use the same two words, so they separate nothing.

Above the first block, teams often place a positioning statement — a single sentence naming who the product is for, what category it belongs to, and what makes it different. With that sentence on top, there's a fixed point to return to whenever the wording below it starts drifting.

The writer is the product marketer. At Pagedeck that's Ravi. It isn't a document one person produces alone, though. What the team actually built comes from Mia, and what customers respond to in meetings comes from Sofia. Ravi's job is less about inventing facts than about choosing which of the existing ones go outside and shaping them into sentences.

The readers are everyone who has to write or say something about the product: whoever owns the website copy, whoever builds the ads, the sales reps introducing the product in meetings, the support agents answering tickets. The point is that they copy from it rather than take inspiration from it. If each reader leaves feeling inspired and writes something fresh, the company is back where it started.

Other materials descend from this one. A battlecard is a one-page sheet of counterarguments for competitive deals, and those arguments start from the core benefits here. A customer story narrates the results a real customer got, and which result gets featured follows the benefit messaging picked. Writing the document and getting people to actually use the words are two different jobs, so sales enablement carries the second one — staying with reps until they can say these lines in their own voice.

"Is this phrasing actually in the messaging doc?"

Checking whether a line headed for an ad or landing page is the agreed wording.

"Let's fix the messaging first and then redo the landing page."

A proposal to edit the source document rather than patch copy screen by screen.

"We decided not to use that phrase in the messaging."

The word is on the document's banned list.

Two weeks before Pagedeck shipped automatic meeting summaries, Ravi opened the messaging document and rewrote one of the three core benefits. It had been "edit together from anywhere," and it became "the write-up is finished when the meeting is." The new feature made that promise something the product could actually keep.

Pushing that one line downstream took another week. Sofia swapped the cover sentence on the sales deck, and support cleared the old phrasing out of their saved replies. The messaging change isn't finished until that spread is finished. Stop at the document and the company ends up running two different descriptions of itself at the same time.

The most common mistake is treating messaging as a slogan or ad copy. Both are short sentences about a product, so the confusion is understandable. But copy is a finished line that goes outside, and messaging is the raw material you consult while writing that line. Lift a sentence straight out of a messaging document onto a billboard and it usually falls flat, because it was written for accuracy and gave up rhythm to get there. Teams that conflate the two start optimizing the document for how it sounds, and end up with lines no rep can use in a meeting.

Treating it as a write-once document is the other one. After a few weeks of work up front there seems to be no reason to open it again. But products change, competitors change, and the customer type you mostly sell to changes, so a sentence that was accurate last year is wrong this year. Messaging nobody has touched in six months quietly stops getting used, and at that moment everyone goes back to writing their own. A quarterly review, plus an update whenever the product shifts significantly, is the normal rhythm.