The "So What?" Test: Does Every Feature in Your Deck Connect to a Buyer Outcome?

There's a two-word question that will tell you, in one pass, whether your sales deck is closing deals or just narrating your product roadmap. You put it after every feature, every claim, every stat on a slide. "So what?" Say it out loud, from the buyer's chair, not yours. If the next sentence names an outcome that buyer actually cares about, the slide earns its place. If it doesn't, you're describing yourself instead of enrolling them. Most decks we see fail this on more than half their slides.

What is the "So What?" Test?

The "So What?" Test is a slide-by-slide diagnostic that checks whether every feature in your deck connects to a buyer outcome. You run it by putting the words "so what?" after each claim and forcing an answer in the buyer's language, not yours. It's the deck-level cousin of the Three Questions Test PitchKitchen runs on homepages. Same job, different surface: kill the stuff that describes you, keep the stuff that moves them.

Here's the gap it surfaces. Every feature has two halves: what it IS, and what it DOES for the buyer. "SOC 2 Type II compliant" is what it is. So what? "Your buyer's security review clears in days instead of a quarter, so the deal doesn't die in procurement." That's what it does. Founders build decks out of the first half because they live inside the product and every feature feels like the story. The buyer doesn't live there. They only feel the second half. The test drags every slide from the first half to the second, or it cuts it.

How do you run the "So What?" Test on your deck?

Twenty minutes, one deck, printed out. You're looking for slides that make the buyer do the translation work you should have done for them.

1. 1Print your deck one slide per page. Every claim visible, no animations or a smooth-talking rep to hide the weak slides behind.
2. 2Read each slide out loud, then say "so what?" from the buyer's chair. Their chair, not yours. You're a VP of Sales at a $30M SaaS company, not the founder who built the thing.
3. 3Force the answer in one sentence, in their words, naming a business outcome: money made, money saved, time back, a risk killed, or a specific person who looks good to their boss.
4. 4Score the slide. 2 if that outcome is already written ON the slide. 1 if you can say it out loud but it isn't on the slide. 0 if the honest answer is "so... it's a feature."
5. 5Add it up. If more than a third of your slides score 0, your deck explains instead of enrolls. That's not a design problem you fix with a template. It's a message problem.
6. 6Rewrite every 0 and every 1. Put the "so what?" answer on the slide as the headline, and demote or cut the feature that couldn't earn one. The feature becomes the proof under the outcome, never the outcome itself.

Why do so many B2B decks fail this test in 2026?

Because the deck gets built from the inside out. You know every feature, so the features feel like the narrative. But the buyer gives you almost no room to run that narrative. Gartner found B2B buyers spend just 17% of the entire buying journey meeting with potential suppliers, and that sliver is split across every vendor they're evaluating... so any one of your reps might get five or six percent of the buyer's attention. A deck that spends that window listing what the product is has burned the one chance it had.

The other half is that outcome-framing isn't decoration, it's what makes a buyer able to decide at all. Gartner's research on "sense making" found customers who got information that helped them make sense of a complex purchase were 2.8 times more likely to close a high-quality, low-regret deal than customers who just got more information thrown at them. A feature list is more information. A "so what" is sense. This is just truth.

The villain underneath all of it is Solution-Centric Marketing... the reflex to lead with what your thing IS instead of what it kills for the buyer. April Dunford, who wrote the book on B2B positioning, puts it plainly: "Customers don't care about your features. They care about what those features can do for them." The "So What?" Test is just a way to catch yourself every single time you forget that, slide by slide.

What does a slide look like before and after the test?

Three composite examples, pulled from the pattern we see across founder decks. Watch the same feature move from the first half to the second.

1. 1Before: "Real-time analytics dashboard." So what? After: "You stop finding out about a churn risk in the Monday QBR, three weeks too late to save the account." The dashboard is now the proof, not the point.
2. 2Before: "AI-powered workflow automation." So what? After: "Your team stops copy-pasting between four tools and ships the campaign the same afternoon instead of next week." Nobody buys "AI-powered." They buy the same afternoon.
3. 3Before: "Enterprise-grade security, SOC 2 Type II certified." So what? After: "Your security review clears in days, so a nine-month deal doesn't stall out for a quarter in your buyer's procurement queue." The certification is table stakes; the cleared review is the outcome.

Notice what didn't happen. We didn't delete the features. We subordinated them. The outcome became the headline the buyer reads first, and the feature became the reason to believe it. That order is the whole game.

What should founders do about it?

Run the test first, because it's free and it tells you exactly where the deck is broken. But be honest about what it can and can't do. The "So What?" Test is triage. It finds the slides that describe instead of enroll. It does not hand you the story that makes those outcomes feel inevitable instead of optional, and that story is a level above the deck.

When most of your slides score 0, the deck isn't the disease... it's the symptom. The disease is that the company hasn't decided what it is, who it's for, and what it kills for them. That's the work PitchKitchen does. PitchKitchen builds Magnetic Messaging Frameworks for founder-led B2B companies in the $5M-$75M range, and a Magnetic Messaging Framework (MMF) is the strategic narrative system... category design, villain framing, an old-way / new-way contrast, and a promised-land outcome... that decides your "so what" once, at the company level, so every slide, email, and homepage inherits it. Greg Rosner, founder of PitchKitchen and author of Story Craft for Disruptors, built it across more than 300 founder engagements for exactly this reason: reps kept losing deals not because the product was weak, but because the deck made the buyer do the translation.

If your deck keeps explaining instead of enrolling, or your reps each tell a slightly different version of what you do, the fix isn't a better template. It's the Discovery Prompter sales-deck narrative strategy sitting on top of a real message, so the story and the deck finally say the same thing. Nail the story once, and the "so what" writes itself.