The problem with "Can you write us a testimonial?"
Every guide on collecting testimonials tells you to "just ask." And they're not wrong — you do need to ask. But what you ask matters far more than whether you ask.
Send a customer "Hey, could you write us a quick testimonial?" and you'll get back something like:
"Great product. Easy to use. Would recommend!"
That quote could be about literally anything. A toothbrush. A spreadsheet app. A dog grooming service. It tells your visitors nothing, it builds no trust, and it takes up space on your landing page that could be doing actual conversion work.
The fix isn't complicated: replace the vague ask with a specific question. The right question steers your customer toward the details that make a testimonial persuasive — the problem they had before, the result they got after, and the reason they'd recommend you over the alternatives.
Most guides throw 25–40 questions at you and call it a resource. You don't need 40 questions. You need 7 good ones, and you need to understand what each one is designed to produce.
Question 1: "What was going on in your business before you started using [product]?"
What it produces: The "before" state — the frustration, the inefficiency, the pain.
This is the most important question on the list. It gives you context that makes the testimonial relatable. When a visitor reads about someone who had the same problem they currently have, the connection is instant: "That's exactly my situation."
What a generic ask produces:
"We needed a better solution."
What this question produces:
"I was copy-pasting customer quotes from emails into a Google Doc, then manually formatting them in HTML on our landing page. Every time we got a new testimonial it took 20 minutes to add it. I kept putting it off, so our page had the same three quotes for eight months."
The second version is a real testimonial. The first is filler.
Question 2: "What specific result have you gotten since using [product]?"
What it produces: Concrete outcomes — numbers, time saved, conversions increased.
This is the "money question." It nudges customers away from vague praise and toward measurable impact. Even if the result is small, specificity makes it credible.
What a generic ask produces:
"It's really helped our business."
What this question produces:
"We went from zero testimonials on our landing page to a full wall of love in one afternoon. Our trial signup rate went from 2.1% to 3.4% in the first month."
If your customer can't point to a specific result, that's useful feedback too — it might mean your product's value isn't landing clearly enough.
Question 3: "What would you tell a friend who was considering [product]?"
What it produces: Authentic, conversational language that sounds like a recommendation, not marketing copy.
This question reframes the ask entirely. Instead of "write marketing material for me" (which is what "write a testimonial" really means), you're asking them to give advice to someone they care about. The tone shifts. The language becomes natural and persuasive in exactly the way marketing copy tries to be but rarely achieves.
What a generic ask produces:
"I would highly recommend [product] to anyone looking for a solution."
What this question produces:
"Just try it. Setup takes five minutes, your customers don't need to create an account, and it genuinely looks good on your site without any CSS hacking. I wish I'd found it six months earlier."
That second version sells your product better than anything you could write yourself.
Question 4: "Was there anything that almost stopped you from trying [product]?"
What it produces: Objection handling from the mouth of a peer.
This is the question most founders are afraid to ask. It feels risky — what if they say something negative? But that's exactly the point. When a customer names a hesitation they had and then explains why it was unfounded, they're doing the most valuable sales work possible: addressing the exact doubts your prospects have.
What a generic ask produces:
(Nothing — nobody volunteers objection-handling without being asked.)
What this question produces:
"I wasn't sure if I needed a dedicated tool — I thought I could just hardcode testimonials in HTML. But after the third time I put off updating them because it was annoying, I realised the friction was the problem. Tarvio made it so easy that I actually keep my social proof up to date now."
A testimonial that acknowledges and overcomes a real objection is worth ten "love this product!" quotes.
Question 5: "How would you describe [product] to someone who's never heard of it?"
What it produces: A customer-voiced positioning statement.
This is a product marketing goldmine disguised as a testimonial question. Your customers will describe your product in ways you'd never think of — and their framing often resonates better with prospects than your own copy because it's in their language, not yours.
What a generic ask produces:
"It's a testimonial tool."
What this question produces:
"It's like having a tiny social proof machine. You send a link, people say nice things, and it shows up on your site automatically. Takes about five minutes to set up."
Pay attention to these descriptions. If multiple customers describe your product the same way — and it's different from how you describe it — consider updating your homepage headline.
Question 6: "What's one thing you didn't expect about using [product]?"
What it produces: Surprise and delight moments that highlight value you haven't marketed.
Customers often discover benefits you didn't predict. Maybe your collection form turned into a customer feedback channel. Maybe the wall of love became a team morale booster. These unexpected use cases make for compelling, authentic testimonials because they can't possibly be manufactured.
What a generic ask produces:
"I didn't expect it to be so easy!"
What this question produces:
"I didn't expect customers to actually enjoy recording video testimonials. I thought I'd get maybe one or two, but people seem to like the little recording flow. I've got seven video testimonials now and I only have 30 customers."
The surprise element makes these quotes naturally interesting. Visitors read them and think "huh, I wouldn't have expected that either" — which is a form of curiosity that moves them toward trying the product.
Question 7: "Would you recommend [product], and if so, to whom?"
What it produces: A direct endorsement with built-in audience targeting.
This question does double duty. The first half captures an explicit recommendation. The second half — "to whom" — gets your customer to name your ideal customer profile in their own words. That's incredibly useful for both your testimonials and your positioning.
What a generic ask produces:
"Yes, I'd recommend it."
What this question produces:
"Definitely. I'd recommend it to any solo founder who's building a SaaS and wants social proof on their landing page without spending $50 a month on it. If you're technical enough to paste a script tag, you can set this up."
That response is a testimonial, a customer profile, a positioning statement, and a competitive differentiation — in three sentences.
How to use these questions in practice
You don't need to ask all seven. Pick two or three that match the kind of testimonial you need most right now.
If your landing page has no testimonials yet: Start with Questions 1 (the before state), 2 (specific results), and 3 (friend recommendation). These three alone will give you testimonials that cover the full persuasion arc: problem → result → endorsement.
If you have testimonials but they're generic: Send Questions 4 (objection handling) and 6 (unexpected value) to customers who already gave you a weak quote. Frame it as a follow-up: "Thanks again for the testimonial — I had one quick follow-up question if you have a minute."
If you're building a comparison page or competitor-alternative content: Question 5 (how they describe the product) and Question 7 (who they'd recommend it to) will give you language you can use to position against alternatives.
Where to put the questions: Include them directly on your testimonial collection form. When a customer opens your form and sees a specific prompt instead of a blank text area, they'll write something specific. The question itself does the heavy lifting. This is how Tarvio handles it — you customise the prompt question on your collection form, your customer sees it alongside a simple text input and optional video recorder, and the result is a testimonial that's actually usable. No login required for your customer, takes under a minute.
The before-and-after difference
Here's what the same customer might submit depending on how you ask:
Prompt: "Write a testimonial"
"Great tool! Really easy to use and has helped our business a lot. Highly recommend."
Prompt: "What was going on before you tried us, and what changed after?"
"Before Tarvio, I had exactly zero testimonials on my landing page because collecting them was such a hassle. Now I have a wall of love with 14 real quotes and 3 video testimonials, and my trial conversion rate is up 40%. The whole thing took maybe 15 minutes to set up."
Same customer. Same product. Completely different testimonial. The only thing that changed was the question.
TL;DR
The questions you ask determine the testimonials you get. Stop asking "can you write a testimonial?" and start asking specific questions that steer toward the details that actually convert.
The seven questions, in order of importance:
- What was going on before you started using [product]?
- What specific result have you gotten since?
- What would you tell a friend who was considering it?
- Was there anything that almost stopped you from trying it?
- How would you describe it to someone who's never heard of it?
- What's one thing you didn't expect?
- Would you recommend it — and to whom?
Pick two or three. Put them on your collection form. Watch the quality of your testimonials transform overnight.