The Communication Playbook for B2B SaaS
Your marketing, sales and support teams are all describing a different product. Here's how to fix that, for good, with one page.
Here's an uncomfortable question. If you asked your marketing person, your top salesperson, and your support lead to each describe your product in one sentence, right now, without checking notes, would you get the same answer three times?
Almost nobody does. Marketing writes the website. Product writes the changelog. Sales writes their own decks because the official one is "outdated." Support writes the help centre in whatever language customers actually use. Four teams, four descriptions of the same product, and none of them match anymore.
This isn't a communication problem. It's an ownership problem. Nobody decided, in writing, what the damn product actually is. So everyone's guessing, and everyone's guess is a little different.
A playbook fixes this. Not a rebrand, not a new tagline, just one page that everything else has to agree with.
Step 1: get to one sentence
Every company needs one sentence a customer could repeat to a coworker, with zero help from you. The formula: for [this specific person], [your product] is the [category] that [does this thing], unlike [the alternative].
Think about how you'd explain Slack before everyone already knew what Slack was: "it's like email, but faster and actually organized." That's a category (email, sort of) plus a twist. You don't need to invent a new noun. You need to borrow one people already understand and improve on it.
Test your sentence two ways. Can a brand-new hire say it from memory on day three? Can a customer repeat it back to you after one demo? If either answer is no, you don't have a sentence. You have a slogan, and slogans don't help anyone understand what you sell.
Step 2: pick three things and stop
Under that sentence, you get exactly three main points. Three, because that's what a human brain actually keeps. Not five. Not seven, because your VP of Product insisted. Three.
For each one, nail down:
- The claim, in the customer's words, not yours.
- The proof. A number, a real customer story, something concrete. Not a vibe.
- The picture. A diagram, a screen recording, a little animation. Something for people to actually look at.
- The doubt it kills. What's the objection this point answers?
Write the whole thing on one page. If it doesn't fit on one page, you haven't actually decided yet. You're still negotiating with yourself.
Step 3: map every place your product gets explained
Make a list of everywhere your product shows up and gets described, and be honest about which ones are actually saying the right thing today:
| Where | Who owns it | Where it comes from |
|---|---|---|
| Homepage | Marketing | The one sentence |
| Product pages | Marketing | The three points |
| Launch videos | Marketing + studio | This quarter's point |
| Sales deck | Sales | The three points |
| Demo script | Sales | The three points |
| Onboarding | Product | The "aha" moment |
| Docs intro | Product/DevRel | The one sentence |
| Help centre | Support | Whatever words customers actually use |
| Release notes | Product | The three points |
| Investor deck | Founders | The one sentence |
Two rules make this actually work. One: nobody gets to freelance their own description of the product. Two: every single row has one named human who owns it. The second someone says "we all sort of own that," nobody updates it, and it rots.
Step 4: ban some words
This part is boring and it changes everything. Make a banned list and a preferred list.
- Banned: leverage, robust, seamless, best-in-class, next-generation, empower, unlock, revolutionize. If it sounds like it came out of a keynote at a conference nobody wanted to attend, cut it.
- Banned: internal codenames anywhere a customer might see them. Nobody outside your building knows what "Project Falcon" is.
- Preferred: verbs your customer already uses. "Fix the broken payment" beats "resolve the transaction anomaly."
- Preferred: actual numbers over adjectives. "Loads in under a second" beats "blazing fast."
Whoever writes your help centre articles probably already does this instinctively. Steal their voice and give it to everyone else.
Step 5: get your visuals to agree with each other
Words alone can't carry a complicated product, especially if what you sell is invisible, like infrastructure or data or security. So decide, once, at the company level:
- One diagram. The single picture that explains how your thing works. Every deck, every video, every doc uses the exact same shapes and colors for the exact same ideas.
- One way of showing your product. Same zoom level, same highlight color, simplified screens. Never a busy, cluttered raw screenshot.
- One motion style. How things move when you animate them: how a number counts up, how a step happens, how you show something is fast. This is the stuff that makes a company look like it has its act together, even if nobody consciously notices why.
When the diagram in the sales deck matches the one in the video which matches the one in the docs, your customer learns your product once. Not three separate, slightly-different times.
Step 6: put it on a calendar
None of this survives without a recurring meeting. Sorry.
- Weekly, 30 minutes: review anything new that's about to go out. Marketing plus product.
- Monthly: spot-check three random surfaces from the map above. Are they still accurate?
- Quarterly: pull the actual words from five deals you won and five you lost. Compare them to your three points. Adjust.
- Yearly: revisit the one sentence itself, but only if you've got real evidence it's wrong. Don't change it because someone's bored.
How you'll know it's working
- Sales cycles get shorter because people show up already getting what you do.
- Support tickets that start with "wait, I thought this did X" start disappearing.
- New hires hit their targets faster because there's one story to learn, not four.
- Press and analysts start using your words instead of making up their own, worse ones.
If you've got nothing right now
Do this in a week. Monday: call five customers and write down, word for word, how they describe you. Not how you'd like them to. How they actually do. Tuesday: write your sentence and your three points. Wednesday: check the homepage, the deck, and onboarding against them. Thursday: fix the homepage and the first onboarding screen, since those get the most traffic. Friday: assign owners and put the recurring meeting on the calendar.
That one week does more for your company than most rebrands do.
If you get to the visual step and realize you don't actually have "one diagram" or "one motion style," that's normal, and it's also literally what we do all day. [Book a call with us](/contact) and we'll help you build the picture that finally makes your product make sense.
Want this applied to your product?
Book a positioning call. You leave with a clear read on what is unclear in your product story and what would fix it.