Nobody wakes up thinking: “I’m going to buy a new SaaS today!” What they’re really thinking (besides coffee): “How do I make this pain go away?”. Too many people in tech pitch what their product does—instead of what it means for the person using it. The real value of your product isn’t just in its features, but in how it transforms the user’s life:
When you focus only on features, people won’t see the transformation. And transformation is what people are really buying. Here’s what happens when you sell features instead of outcomes:
The Reason This HappensPeople in tech take genuine pride in their technical achievements. We want to showcase our hard work rather than “dumbing it down” to benefits. We worry that using “marketing talk” will make us look less competent. Some even view emotionally-driven messaging as manipulative. Listing features feels like the logical, objective path. Here are other reasons why this happens:
How to Fix ItYou must be thinking: “Benefits over features—got it. But how do I do that?” First, let’s clear the air. I know this shift can feel…icky. Like you’re turning into a dodgy car salesman. But here’s the thing:
Storytelling sticks because it shows change — a clear before and after. That’s why the most iconic stories follow this arc of transformation. Just look at these stories:
Transformation is what closes the loop after building up tension from conflict (problems) and consequences (stakes) in your story. When you give people a clear “before and after,” your message sticks. Let’s say you’re building a tool that automates customer feedback collection:
Same tool. But the second version shows transformation. Don’t make people connect the dots—draw the whole picture for them. Here are other ways to frame your solution as transformation: 1. Use tangible examplesPeople in tech often give accurate—but intangible—examples. Imagine if Steve Jobs only explained the technical specs of the iPod: “A 5GB MP3 player with USB connectivity and 10-hour battery life.” That’s technically correct. But the audience might be thinking:
Now compare that to what he actually said: “1000 songs in your pocket.” The audience would think:
See the shift? When the benefit is vivid and concrete, people can see the transformation—and they get curious. You’ve earned their attention. Hook them with the promise → Explain the specs after. 2. Ask “so what?”Technical language informs. Emotional language persuades. Let’s say your product “automates reporting.” That sounds useful but dry. It doesn’t tap into how your customer feels before and after. Ask yourself “so what” to unpack the real benefit of the solution.
Feature: “This tool automates reporting.”
Ask: “So what?”
Benefit: “No more last-minute scramble before leadership reviews.”
You’re not changing what the product does—you’re changing what it means. You can see this in how some of the best brands speak:
People might forget a feature. But they remember how you made them feel. 3. Anchor to identityPeople don’t just buy products—they buy better versions of themselves. Apple used this approach masterfully with the Mac vs. PC campaign. The Mac wasn’t just “less prone to viruses” or “better at graphic design.” It was cool, creative, and easygoing. The PC? Uptight, corporate, and clunky. They weren’t just selling specs. They were selling who you were if you chose a Mac. You weren’t just buying a computer—you were declaring your identity. You can see more examples from other brands:
Even in SaaS, identity framing works. If your tool helps engineers write cleaner code, you’re not just saving time—you’re making them feel like pros who ship with confidence. 4. Show the differenceI want you to ban the word “better”. It’s vague. It leaves people guessing. When you use the word “better”, it makes people ask:
Instead, you should show what makes your solution different. This helps with your positioning in the market. It helps people know if your product is for them—or not. And this makes it easier for your solution to stand out. One way to do this is to tell your audience who this product is NOT for, just like how Basecamp does it: Or like how Hey.com compares screening emails like screening calls: You get the idea. Here’s my favourite quote on this topic: “Different is better than better.” — Sally Hogshead TakeawayIf you want your message to stick (and your product to sell), remember:
Don’t just tell people what your product does. Show them what it does for them. P.S. I’m working on something special—a course on storytelling for people in tech. To make sure it’s as useful as possible, I’d love your input: Which of these is your biggest struggle right now?
Looking for something else? Reply and let me know! Adam |
Get exclusive, weekly insights and case studies rooted in 10+ years of product management and 5+ years of content marketing expertise.
What separates click-worthy content from clickbait? One backs up its claims. The other exaggerates them. Even in tech, the same rule applies: if people can’t see the proof, they won’t buy the promise. It’s not enough to say your product or idea is amazing—you have to prove it’s worth believing. Without credibility, even the best story falls flat. Imagine all the 20-year-old self-proclaimed business gurus on Instagram selling you $10k coaching programs on how to be rich. Sure, maybe the top 1%...
I don’t care how disciplined you are—even Navy Seals deal with procrastination. When someone flags a problem at work, my default reaction is: “That’s something for future Adam to deal with.” (And just to be clear: I’m not a Navy Seal—just making a point). Of course, I don’t just ignore it. I’ll analyze the issue, weigh it against the backlog, and decide if it’s worth tackling now or later. This goes to show that if a problem doesn’t feel painful or urgent enough, it’s easy to: Delay Forget...
It’s frustrating when nobody understands you despite having the most accurate explanation. For years, I struggled to explain what I do as a product manager in social settings. Whether it’s family, friends, or other professionals, I’d get nervous when they ask: “So what do you actually do?”. I’d try to sound impressive by cramming in as much detail as possible. I’d throw out Agile/Scrum buzzwords like: “Outcomes over outputs” or “Leading without authority”. The result? People stared at me with...