Why your SaaS product isn't getting recommended (and how to fix it)

Good product. Decent retention. Zero word-of-mouth.

That's the silence most SaaS companies can't explain. Real users, fine NPS, a handful of case studies that say nice things. And almost nobody talking about us unprompted.

So we improve the product. More features, smoother onboarding, a redesign. The referral number doesn't move, because we diagnosed the wrong organ.

Word-of-mouth is not a product outcome. It's a narrative outcome.

A product gets recommended when the recommendation makes the recommender look smart, well-informed, or early. A product that carries no social signal won't spread however good it is.

Jonah Berger, a marketing professor at Wharton, opens Contagious with social currency, the idea that people share what makes them look good. His 2013 framework has aged well because the thing it describes is status, and status hasn't moved.

It's the first of his six drivers and the one B2B software teams skip. Products that spread do so because using them says something about the person doing the sharing.

Products that don't spread are often excellent. They just don't say anything.

---

The tool that spreads

Slack was not a uniquely better chat tool when it launched.

HipChat existed. Campfire existed. Email was fine.

Slack spread because using it signaled something. "We run a modern, psychologically healthy team." Choosing it was a statement, and recommending it made you the person who knew what good looked like before everyone else did.

Linear, the tracker engineering teams use, spreads by referral in a way its feature list can't account for. Recommending Linear says you care about how engineering work actually gets done. It makes the recommender look like a thoughtful practitioner.

Neither signal happened by accident. Both were built into the positioning, the aesthetic, the community, and the language each company used to describe who the product was for.

---

The intimacy trap

Teams live inside their products. We know every feature, every integration, every edge case, and that intimacy becomes a trap.

When it's time to talk about the thing, we describe what it does. It's the natural instinct. We built it, we know it best, so we lead with what we know.

Buyers work differently. They evaluate by the relief they get and the identity they pick up, whatever the feature grid says.

"AI-powered workflow automation" means nothing. "Your ops team finishes the week without a backlog" means something.

"Faster ticket routing" is forgettable. "You're the support lead who never gets surprised by an escalation" is a signal.

Feature-centric products get used. Identity-conferring products get recommended.

And this isn't a soft channel we can afford to leave to chance. Wynter's January 2026 survey of 101 B2B SaaS CMOs found that 42% ranked word-of-mouth as the number one factor in getting a vendor onto their consideration list, ahead of brand, review sites, and AI recommendations.

The companies that crack it don't buy pipeline the way their competitors do. They don't have to.

---

The sharer's ledger

Social currency is the value the person sharing gets from the act of sharing. What the recipient gets is a separate ledger entirely.

When a support lead recommends our help desk to a peer at another company, what does she get out of it? If the answer is "nothing, she's being helpful," we have no social currency.

If the answer is "she looks like the person who solved a problem before her peers knew it was solvable," we have something that can spread.

Two signals do most of the work in B2B.

The first is expertise. "I use X" becomes shorthand for "I've thought hard about this and found the answer." The recommender gets to be the expert by having found the right tool first.

The second is belonging. "We use X" means "we're the kind of company that does this properly."

Slack worked at the team level and Figma did it for design teams. The product stops being a utility and becomes a membership marker.

Pick whichever is more natural for the product and build it in on purpose.

---

Building the signal in

This is positioning work, and it starts with one question. What does a buyer say about herself when she tells a peer about us?

The identity it confers

Outcomes and identity do different jobs. "Saves you 10 hours a week" helps someone decide to buy. "You're the kind of ops lead who runs a tight machine" gives them something to repeat.

Outcomes convert. Identity refers.

So write the sentence out. "Using [product] signals that you are [identity]." If we can't finish that sentence, neither can our users, and they certainly can't finish it on our behalf in a hallway conversation.

Then look at the best customers. What did they have in common before they found us?

The identity usually already exists inside the group we've attracted. Name it and hold it steady.

Visible to non-users

Social currency only fires if somebody else can see it.

The Slack notification in a screenshot. The Linear link in a GitHub comment. The Figma file in a design review.

If the product is invisible to a user's peers, the signal never leaves the building.

So find the moment where using it is visible to someone who doesn't. Shared outputs. Reports that reach stakeholders outside the core team.

If no such moment exists, design one into the workflow instead of bolting on a separate growth program.

One moment is enough. A non-user sees something our product made and wonders what it is and how that team runs like that. The logo on every exported PDF tries much harder and signals much less.

Who goes first

Where a product shows up shapes what it signals. Notion became the thoughtful productivity tool partly because it spread through the personal productivity community long before it reached the enterprise.

So ask who the first fifty reference customers are, and what it means to belong to that group. Early adopters write the identity that later adopters inherit.

They're writing it whether we direct them or not. If the first customers are price-sensitive small businesses, that's the identity the product carries into every market after. If they're craft-obsessed practitioners at companies other people admire, that's what travels.

---

The peer sentence

Here's the diagnostic, and it takes an afternoon.

Ask five of your best customers one question. "What would you say if a peer asked why you use us?"

Whatever comes back is the peer sentence. It's the version of us that exists when nobody from our company is in the room, and it's the only version that ever gets repeated.

Listen for two things.

Does she lead with features or with identity? "It has a great API" and "the dashboards are solid" mean the product solves a problem without conferring anything. "It means we don't cut corners" is the answer we're listening for.

And does it sound like her, or like our website read back to us? A customer reciting our copy has no story of her own yet. She needs a shorter, sharper one she can hold in her head.

The distance between the peer sentence we heard and the peer sentence we wanted is the distance between our positioning and positioning that spreads.

Most SaaS copy is written for the buyer reading it. The best is written for the buyer quoting it to someone else. That takes being more specific and more opinionated than feels safe, because the version everyone agrees with is the version nobody repeats.

Build the product, then build the sentence. The referral curve lags the positioning work by a year or more, so what we do this quarter shows up in a pipeline nobody will review for a long time.

The companies waiting for word-of-mouth to happen naturally are waiting on a machine nobody built.

---

What to do next

If retention is healthy and referrals are flat, the gap sits in the positioning rather than the product. That's a positioning audit. We go find the peer sentence your customers already say, then rebuild the messaging so it's the sentence you wanted.

If that's where you are, start here. The first conversation is free.

---