Hi everyone!

Hope your Sunday is going great. I’m already in a rush to tie up loose ends with clients before the holidays, so this week was hot hot hot.

I won’t tease you — here’s a real-world problem I had with one of my B2B SaaS clients this week and how we approached it.

The Ghosted Moment

Did you know that a product with 5 reviews has a 270% higher purchase likelihood than the same product with no reviews?

Of course you did.

Even if you didn’t know the exact number, you definitely know this advice:
“Add reviews and testimonials → get more upgrades, purchases, even trial starts.”
Not rocket science.

But here’s the thing.

A lot of products I see (including teams I work with) treat testimonials as a 0/1 task: Do we have them? Good, that’s enough.

This is exactly what happened to one of my clients.

They had great testimonials… buried inside huge video chunks on the homepage that no one watched:

  • impossible to skim

  • too much effort to process

  • looked nice, did nothing

Conversion from cold traffic was low.
When we ran some user interviews, the pattern was clear:

“I don’t trust this product enough to convert and honestly, even to spend more time researching it.”

Chasing the 0/1 checkbox makes us forget why testimonials exist in the first place.

The purpose of a testimonial is to:

  • increase trust

  • give clarity

  • make people feel safe enough to take the next step (sign up, start a trial, upgrade)

But for that to work, they have to hit the right psychological triggers.
If they don’t, they won’t stop users from ghosting your website forever.

One question to ask your team if you’re battling low conversion from cold traffic:

You can literally paste this into Slack:

If I’m [our ICP] with [our core problem], what evidence do I see here that this product has already solved this exact problem for someone like me — more than once? If yes, does it take me less than 2 seconds to understand them?

What’s Behind It

If users are scrolling down to testimonials, they’re already interested enough to not bounce on the first screen.

But they’re still hesitant.
At this point, they’re trying to answer three questions in their head:

1. Did this product solve the same problem I have successfully?

What they feel:

Fear: “I’m afraid to waste time and energy on something that won’t actually fix my situation.”

Bias underneath:

Loss aversion/risk aversion – trying a new tool costs time, attention, sometimes political capital. People hate feeling they “lost” those for nothing.

Why they even have this question:

Most testimonials talk about how nice the product is (“love the UI”, “great team”) instead of what problem it actually solved. That doesn’t reduce risk.

2. Did it work for the same type of people / teams as me?

What they feel:

Doubt: “Sure, it worked for them. But I doubt they share our problems.”

Biases underneath:

Similarity bias – we trust proof coming from people who look like us, work like us, or operate at our scale.

Why they even have this question:

Most testimonial sections stack logos of huge companies or random verticals and call it a day. If you’re an early-stage startup or a tiny ops team, seeing “Fortune 500” everywhere can actually push you away: “This is not built for us.”

3. Do I believe it’s real?

What they feel:

Fear of shame: “Am I getting fooled?”

Biases underneath:

Trust / authenticity heuristic – we’re very good at sniffing out generic fluff, and when something feels off, we push back out of fear or at the risk of being shamed and embarrassed.

Why they even have this question:

AI-generated text, stock photos, vague quotes like “They changed our business!” with no context — all of this screams fake, it’s just too polished and nice, like a marketing playbook. Instead of building trust, it creates doubt.

You don’t have to trick users or rush them into conversion.
But you do need to answer these questions in a way that takes seconds, not minutes, to process.

How to Turn It Around

I’ve pulled a couple of examples from Monday. com, Amplitude, and Semrush (screenshots are below).
Let’s look at how strong testimonials answer these three questions — and how you can steal the patterns.

1. “Did this product solve the same problem I have successfully?”

What to do:

Make sure testimonials describe a clear result tied to a clear problem, not just kind words.

It doesn’t have to be a big shiny number. It can be:

  • a narrative: “We beat [competitor] on speed for the first time.”

  • a process: “Reporting that took 3 days now takes 3 hours.”

  • a feeling: “I finally feel confident about our data.”

The key: the quote should connect use case → outcome.

Why it works:

The moment you show a clear link: “This problem → this result”, you lower perceived risk and give their brain a concrete outcome to latch onto instead of a fuzzy promise.

2. “Did it work for the same type of people / teams as me?”

What to do:

Match testimonials to how you segment acquisition:

  • company size

  • industry / vertical

  • role (PM, founder, ops, RevOps, etc.)

  • maturity (early-stage vs enterprise)

If you’re selling to early-stage tech startups, putting “Google” and “Walmart” front and center can actually backfire. If your core customers are schools or non-profits, a random fintech logo is just noise.

On a landing page for a specific ICP, highlight stories from that ICP, not your entire logo zoo.

Why it works:

The moment I see “a team like mine” in the quote, I stop doing mental gymnastics. I don’t have to guess whether this could work for us — I have a direct example.

3. “Do I believe it’s real?”

What to do:

Yes, boy oh boy, this is harder with AI paranoia everywhere. But basics still work:

  • Use real photos (even if imperfect), not obviously fake stock, not generated ones, please.

  • Add name + title + company; link to LinkedIn or the company site if you can.

  • Be specific about the problem and result (“we reduced ticket backlog by 37%”) instead of “they changed everything”.

  • Video is great if you also add a short text snapshot to it, so people can skim the point without hitting play (but they will make a note of the fact that someone recorded it for you).

Why it works:

Real people, concrete details, and little bits of context are hard to fake at scale. They pass the “does this smell like a real human?” test and make the rest of your claims easier to believe.

A Share-Worthy Example

Here are some great examples of a testimonials section you can use as an inspiration or a direct reference. Go through them and think what you would change to answer those questions even better?

Amplitude

Monday.com

Semrush

If you forget everything, remember this:

Testimonials can be a growth powerhouse — but only if they answer the right questions, not just hang there and look pretty.

🎉 Woow, you finished the issue, that’s awesome!

Hi, I’m Anastasia Kudrow, and I write Ghosted.

I am also a product growth consultant. I help SaaS teams apply psychology and PLG to drive upgrades. I run my own project, Growing Pains, and also work with one of the leading PLG consulting agencies, ProductLed, led by Wes Bush.

Feel free to follow me on LinkedIn: https://www.linkedin.com/in/anastasia-kudrow/

Or check out my website, maybe we can work together: https://www.growingpains.consulting/

See you next week!