Back to field notes
Playbooks 7 min read

Turn customers into your best sales reps: a playbook for video testimonials at scale

Getting one video testimonial is luck. Getting twenty is a system. Here's the repeatable process we've seen work across hundreds of SaaS teams on Proofly — from the first ask to a library of customer evidence that compounds over time.

TL;DR

Scale comes from systematizing three things: trigger (the right moment), format (direct recording link, three specific prompts), and destination (a wall that compounds over time). Teams that embed this into their existing customer communication rhythm collect 10–15 testimonials per quarter without a dedicated campaign.

Most SaaS founders think testimonials are something you collect during a campaign — a big push every six months where you email twenty customers, get four responses, and publish two videos. Then you're done until the next push.

That mental model produces a wall that stagnates. The same six testimonials from two years ago, slightly outdated, featuring customers who may have churned.

The teams that end up with a library of 30+ strong, current video testimonials don't do campaigns. They have a system that runs every week, in the background, without anyone owning it as a project.

Here's the system.

The three trigger categories#

Systematic testimonial collection starts with identifying the moments in your customer lifecycle when asking is most likely to succeed. There are three categories that work across nearly every SaaS product:

Milestone triggers. The customer crosses a metric threshold that matters to them. This might be their hundredth user, their first paying customer, a revenue milestone, or hitting a benchmark they told you about in onboarding. Many products can fire these automatically — a webhook, a usage event, a Stripe event — so the testimonial request goes out without anyone manually watching for it.

Success event triggers. The customer does something they came to your product to do: launches a campaign, ships a feature, solves a specific problem. These are often visible in your Slack community, in support tickets ("this worked perfectly"), or in NPS responses. A simple Zapier automation that fires when someone gives you an NPS of 9 or 10 can send the recording link within minutes.

Relationship triggers. The customer reaches out positively — a thank-you email, a kind reply to your newsletter, a mention on social media. These are the highest-conversion asks because the customer has already volunteered their positive sentiment. Reply in the same thread: "That means a lot — would you be up for a quick 60-second recording? I built a link so it takes no setup: [link]"

Set up monitoring for all three. You don't need automation for all of them. Manual scanning of your support inbox and Twitter mentions twice a week, looking for the relationship triggers, is enough to capture most of the high-conversion opportunities.

The request format that scales#

At volume, the personalization in your request matters more than the polish. Customers can tell the difference between a request that references something specific about their experience and a templated ask that uses their first name as a mail-merge field.

The format that consistently outperforms:

Line 1: Reference the specific thing. "Congrats on the launch / saw you hit 500 users / glad the integration issue got sorted."

Line 2: One direct ask. "Would you record a 60-second video about what changed? Here's the link — no signup, no app: [link]"

Line 3 (optional): The three prompts, if they're a customer who needs more direction. "The link will show you three questions: what the problem was before, what changed, and who you'd recommend this to."

That's the whole message. No explaining what Proofly is, no apologizing for asking, no "whenever you get a chance." The directness signals that you respect their time and know what you want.

The link goes to a page that shows the recorder immediately — no account, no app download, no instructions beyond the three prompts you wrote when you created the request. The customer clicks, grants camera permissions, sees the questions, and records. The whole flow from click to upload takes under three minutes.

The three prompts drive everything:

  1. "What was the situation before you found [product]?" — This produces the before story. Customers will say things like "we were pasting everything manually into a spreadsheet" or "I had no idea if any of my customers were actually happy." These before stories are what your target visitors recognize themselves in.

  2. "What specifically changed — any numbers you can share?" — The word "specifically" does a lot of work. Without it, customers say "it made things easier." With it, they say "our team spends about 20 minutes a week on this instead of four hours."

  3. "Who would you recommend this to?" — This turns the testimonial into qualification copy. A customer saying "anyone running a subscription product with 50–500 customers" is doing audience targeting for you.

The approval and publication workflow#

Every submission lands as "pending" in your Proofly dashboard. Your job is to review and approve within 24 hours. Approving quickly matters because:

  • The customer may be watching for their testimonial to appear (and it will if they visit your wall)
  • The sooner it's approved, the sooner you can share it on social and send it to the customer to retweet
  • Quick turnaround signals to the customer that you valued their time

After approving, the testimonial automatically appears on your Wall of Love and becomes available for the embed on your landing page. No manual step needed.

The next action: within a few hours of approval, tweet the quote (or a still from the video with a quote overlay). Tag the customer. They'll almost always like or retweet, which puts the testimonial in front of their audience — a leverage effect that cold outreach can't replicate.

The compounding math#

This is why the weekly habit beats the bi-annual campaign.

If you send three thoughtful recording requests per week and convert at 35% (roughly what we see for personalized, triggered asks in the data from Proofly users), you collect one testimonial per week. In a year, that's 50 testimonials — a library that covers every customer type, use case, and stage.

ApproachAsks/yearConversion rateTestimonials/year
Bi-annual campaign (40 asks)8010%8
Weekly habit (3 asks/week)15635%54

The conversion rate difference (10% vs 35%) comes entirely from timing and personalization. Campaign emails go to a broad list at a random time. Triggered, personalized asks go to a customer at the moment of highest positive emotion, with context that makes the request feel specific to them.

Repurposing the library#

A library of 50 testimonials is more than a wall. It's a content bank.

Sales sequences: Attach three relevant testimonials to your cold outreach. Match the testimonial customer profile to the prospect's profile. A solo founder testimonial for a solo founder prospect. An agency testimonial for an agency prospect.

Case study source material: The transcripts of video testimonials are first-draft case studies. The customer's "before" description is the problem section. Their "what changed" answer is the results section. A case study is two emails and a transcript away.

Ad creative: A video testimonial in a paid ad converts 40–60% better than a produced explainer in most B2B SaaS categories (per our customers' data). You have the video. The customer already consented to it appearing on your website. Check whether the consent language covers ads; if not, a quick email confirmation is a few minutes of work.

Newsletter content: A monthly "what customers are saying" section in your newsletter, featuring two or three testimonials from the past month, builds social proof with your email list while also giving you a repeatable content format that costs nothing to produce.

Objection handling: Tag testimonials by the objection they address. "Too expensive" → find the testimonials that mention ROI. "Takes too long to set up" → find the testimonials that mention getting started quickly. When a sales prospect raises an objection, you can forward a specific testimonial that addresses it.

The wall as a living document#

The Wall of Love should be updated regularly — not just when you have a burst of new testimonials, but as a conscious curation exercise. Every quarter:

  • Remove testimonials older than 18 months (or archive them to a secondary wall)
  • Move the strongest recent testimonials to the top six visible positions
  • Check whether the mix of customer types still reflects who you're targeting
  • Retire testimonials from customers who have churned (not mandatory, but good practice)

A wall with recent testimonials — customers from the last six months — converts better than a wall with impressive-but-dated testimonials. Recent proof signals that people are using and loving your product right now, not that they did two years ago when your product was different.

Frequently asked

Quick answers

How many testimonials do you need before the Wall of Love starts driving conversion?+

Three is enough to ship. Two video and one written quote is a credible wall. The diminishing returns start around fifteen — after that, adding more testimonials moves the needle less than improving the quality and relevance of what you already have. Most teams over-index on collecting and under-index on publishing and placing what they have.

What if you're pre-revenue and have no customers to ask?+

Ask beta users and pilot customers even if they're not paying. Ask anyone who gave you positive feedback during discovery calls — 'would you be willing to record that for our website?' converts at around 35% when asked immediately after a good call. Early testimonials from pre-revenue users are valid social proof; be transparent that they were beta customers if the context is relevant.

Should testimonials be gated behind an approval workflow?+

Yes, always. In Proofly, every submission lands in 'pending' and requires explicit approval before it appears on the wall. This gives you editorial control, protects against spam or fraudulent submissions, and lets you contact the customer before publishing if you want to verify anything. Never auto-publish customer-submitted content to a public surface.