A SaaS messaging framework that turns your feature list into a story a buyer can follow

Why a feature list fails a stranger

The first problem is that a feature list makes the buyer do your job. They have to guess what each feature is for, and then work out what it would be worth in their own business, before they can care. You can do that translation in your head because you built the product. A stranger can't, and they won't stay long enough to try.

The second problem is that a feature is a claim without a consequence. "Automated reminders" tells a buyer what exists. It doesn't tell them that nobody at the front desk has to pick up the phone when a patient cancels. Until you say the consequence, the feature is just a word, and the buyer has no way to compare it to what they do today.

The last problem is the order you say things in. Before a buyer will read anything about your product, they need to know whether this page is for them. If the page opens with a feature, the visitor has to read about your product before they know whether the page is for them, and most visitors leave instead. So the product has to come after the part that tells them they're in the right place.

What is a SaaS messaging framework?

A SaaS messaging framework is a fixed order for the things you say about your product, and every page, email, and sales call follows it. The order I use has four parts: the problem the buyer already has, what that problem costs them, the change your product makes possible, and the proof that it's real. The product itself shows up in part three, not part one.

You can think of the four parts as a short story. Something is wrong, it's costing the reader, there is a different way to do it, and here is evidence it works. A buyer won't think about a solution until they agree there's a problem, and they can't judge your proof until they know what you're proving, so the page has to go in that order.

1. The problem, in the buyer's words

Open with something true about the buyer's day, said the way they would say it. Not the way you'd describe the market, and not the way your product solves it. If a clinic owner reads your first line and nods, you've done it. If they have to translate it into their own words first, the line isn't there yet.

A clinic owner would never say "inefficient scheduling workflows." They'd say "Four patients no-showed on Tuesday and we couldn't find anyone to take their slots." Write the second one, or something as plain as it.

To find the words, go back to what buyers already said. Pull up your last five sales calls and your last twenty support tickets, and write down the exact words buyers used to describe the problem. On a sales call, that's how they answer "what made you take this call?" before you start pitching. In a support ticket, it's the first sentence they type. Those phrases are your opening. A line lifted from a buyer's mouth always beats a line you composed, because the next buyer recognizes it.

Here's one test for whether the problem is specific enough. Could you film it? "Operational inefficiency" can't be filmed. "A receptionist calling eight patients in a row to offer a slot that just opened up" can. Write the one you could film.

2. The stakes, as a cost they can feel

Once the buyer recognizes the problem, tell them what it costs. Founders skip this part because the cost feels obvious to them, and it's what makes a buyer decide to keep reading instead of bookmarking the page for later.

Stakes are money, time, or risk, and the more specific you can honestly be, the better. When a patient no-shows, the clinic still pays the therapist for that slot and bills nobody. If the owner knows their per-visit revenue, they can do the math from there, and you can help them by spelling out what that looks like, an empty 45-minute slot that goes unfilled four times a week. You don't need a made-up industry statistic, and you shouldn't invent one. You need the reader to picture the cost in their own numbers.

Say what happens if nothing changes, too. The waitlist keeps getting longer and the front desk burns out, or the clinic across town that fills its schedule keeps hiring. Name the one your buyers actually bring up, not the one that sounds most dramatic.

3. The change, and then the product

Most founders don't know this part exists, and it's what makes a message persuasive instead of just clear.

Before you show the product, show the buyer a different way to think about the problem. The clinic owner believes no-shows are a fact of life and the job is to remind people harder. The change is that a no-show is only a loss if the slot stays empty, so the job is to fill it in the hour after it opens, from a list of patients who already asked for an earlier appointment. Once the owner sees the problem that way, describing your product is the natural next thing to write.

Then the product arrives, described by what it lets the buyer do, not by what it is. "When a patient cancels, the tool texts the next three people on your waitlist, and the first to reply gets the slot." That's a workflow the owner can picture, and it describes the same feature as "automated waitlist management" while meaning something.

The reason this order works is contrast. You show how the buyer works today, then how they'd work with your product instead, and the reader understands what your product is by understanding what it replaces. A product with no contrast is a product the buyer has to evaluate from scratch, and buyers don't do that for a stranger.

4. The proof, and how to start collecting it

Last comes evidence, and this is the part founders worry about when they only have a handful of customers and not much to point to yet. Use what you honestly have, whether that's one clinic's name next to one specific result, a number from your own product data, a founder who owned a clinic for ten years and built this because of it, or one early clinic that agreed to let you measure its numbers before and after it started using the product. Any of these beats a line about being trusted by leading providers, which nobody believes.

I cover how to get more proof with almost no customers later in the course. What you should do today is start collecting it, because the proof you'll want in six months has to be measured now. For every customer who starts, write down where they stand on the day they onboard. For a clinic, you'd record its no-show rate, how many cancelled slots it refilled last month, and how many hours the front desk spent on the phone. Six months from now you'll be able to say what changed, in their numbers, with their permission. If you don't record the starting point, you'll never be able to prove the change, no matter how real it was. Your future self will thank you for starting this early.

Your homepage hero is where the four parts either work or don't

The first screen of your homepage is where you find out whether a stranger can follow the order, because it's the only part most visitors read. Three kinds of headline show up over and over, and they're worth comparing on the same product.

The worst kind describes an industry change. Something like "Reimagining the future of patient care." It's the error I see most often on early SaaS sites, and it says nothing. It doesn't describe the product, so the visitor doesn't know what you sell, and it doesn't name a benefit, so they don't know what they'd get. The line is about the industry, not about them, so there's no reason to keep reading. A visitor who lands on that line has to scroll to find out what the company does, and the ones who don't scroll are gone.

The bad kind names your category. "Scheduling software for physical therapy clinics." This one at least tells the visitor what you are and who it's for, which is why founders reach for it. The problem is that naming your category invites a comparison. The visitor now knows you're scheduling software, so they compare you to the scheduling software they already have, on the features they already know, and you've lost the chance to change how they see the problem.

The good kind names the benefit. "Fill the appointments your no-shows leave open." Now the headline is about a problem the clinic owner has every week, it names what changes, and it implies the product without describing it. The visitor who has that problem keeps reading. The visitor who doesn't leaves, which is fine, because you weren't going to close them anyway.

The category still needs to be on the page, because a visitor should never have to guess what kind of thing you are. Put it in the subheadline, right under the benefit. "Scheduling software that texts your waitlist the moment a slot opens, built for physical therapy clinics." Benefit first, category second, and the two together tell a stranger what you sell and why it matters before they scroll.

Words that empty a message

Some words show up in SaaS copy so often that buyers no longer read them. Seamless. Effortless. AI-powered. Streamline. All-in-one. Next-generation. Robust. Revolutionize. Each one felt like it meant something the first time someone used it. Now they're filler, and a buyer's eye slides past them the way yours slides past fine print.

The problem with these words isn't that they're overused. It's that they carry no picture. "Seamless integration" doesn't tell the buyer what happens, so they can't compare it to their current tool, so it doesn't move them. "Your therapists' schedules update in the clinic system the moment a patient books" tells them exactly what happens, and it's the same claim.

"AI-powered" deserves its own mention, because founders reach for it hoping it signals sophistication. To a buyer it signals nothing, because every product says it now. If the AI does something useful, say the useful thing. "The tool learns which patients tend to accept last-minute slots and texts them first" is a benefit. "AI-powered scheduling" is a label.

Here is the test for every line on your site. Could a competitor paste it onto their homepage without changing a word? If yes, it's not saying anything about you, and it needs to be rewritten until it could only be true of your product.

How to write it this week

Block a morning, and bring whoever has heard the most customers talk.

1. 1.Collect the buyer's words. Go through your last five sales calls and your last twenty support tickets. Write down every phrase a buyer used to describe the problem in their own words. Circle the three that came up most.
2. 2.Write the problem in one or two sentences using those phrases. Check it with the filming test.
3. 3.Write the stakes in one paragraph. Money, time, or risk, in the buyer's own units. No invented statistics.
4. 4.Write the change in one paragraph, then the product in one paragraph. The change is the different way to see the problem. The product is what makes that way possible, described as a workflow the buyer can picture.
5. 5.List every piece of proof you honestly have, and start writing down where every new customer stands on the day they start.
6. 6.Rewrite your homepage hero. Benefit in the headline, category in the subheadline.
7. 7.Read the whole thing to someone outside the company. Then ask them to tell you what the product does and who it's for. If they can't, go back to step one, because the problem is almost always that you slipped back into your own words.

Once the four parts are written down and agreed on, they become the source for everything else. The homepage follows the order top to bottom. A cold email is the problem and the stakes in two sentences, then the change, then a link to proof. A sales deck is the same four parts with slides. You write the story once, and every page, email, deck, and sales call repeats it instead of each one inventing its own version.

Keep going

I publish a new lesson of this free course every week. Sign up for the newsletter and I'll email you each one the day it's published.

The next lesson takes the four parts you just wrote and compresses them into one sentence a stranger can repeat, which is the test every page and ad you write from then on has to pass.

If you'd like a second set of eyes on your messaging before you rewrite the site, this is the kind of work I do with early-stage SaaS companies, and I've written up how I approach positioning and messaging. If you'd rather have someone look at your whole marketing setup and tell you what to fix first, I offer a two-week review where I look at everything from how buyers find you to why they don't convert, then hand you a plan for the next 90 days.