Blog · August 26, 2026

How to turn a support message into a testimonial

A few weeks after I shipped one of my apps, someone emailed me. Two sentences. “This just saved me an hour on the first day. Thank you for making it.” I wrote back “so glad it helped”, felt good for about ten seconds, and archived it.

That was a testimonial. I threw it away. I did the same thing dozens of times before it clicked: the social proof I kept saying I did not have was arriving in my inbox every week, and I was filing it under “nice, moving on”.

The proof is already in your inbox

When you launch with a handful of users, the advice to “add testimonials to your landing page” feels like a joke. You have no testimonials. You barely have users.

But you almost certainly have messages. A support email that ends with “by the way, I love this”. A reply on X. A line in a Discord. A thank-you DM. None of it looks like a testimonial because it is not on a landing page in a nice font. That is the only thing separating it from one.

So the first move is not to go collect testimonials. It is to stop deleting the ones you already get. Make a folder, label it “kind words”, and drop every one of those messages in it the moment it lands. In a month you will have more proof than you thought you had in a year.

Ask, at the right moment

Some of the best proof needs a small nudge. The trick is when you ask, not how.

Ask right after a win. Someone tells you the app fixed their problem, or you helped them through a support thread, or they hit a milestone using your product. That is the moment they feel it. Reply with a real thank-you, and then, honestly: “Would you mind if I quoted that? One line is perfect, and I am happy to link back to you.” Most people say yes, because you are asking at the exact moment they are glad they found you.

Do not send a cold “please write me a testimonial” email to your whole list. It puts the work on them and it arrives when they feel nothing in particular. A specific ask, tied to a specific moment, in reply to something they already said, converts far better and costs them almost nothing.

Specific beats glowing

The instinct is to want the shiniest quote. “Amazing app, five stars, life changing.” That kind of praise reads as filler, and readers skim right past it. It could be about anything.

The testimonials that actually work are specific. They name the problem and the result. “I stopped dreading my Monday reporting” says more than “great app”. “Set it up in five minutes and shipped my first invoice the same day” beats “so easy to use”. When someone sends you a vague compliment, it is fine to ask a gentle follow-up: “What did it replace for you?” or “What were you doing before?” The answer is usually the quote.

You are not putting words in their mouth. You are helping them say the useful part. And you never invent one. A made-up testimonial is the fastest way to lose the trust the real ones are supposed to build, and people can smell it.

Get permission, keep it honest

Two rules, and they matter more than any of the design.

Ask before you post, every time. A private message is not public consent. A quick “ok if I share this with your name and handle?” keeps you honest and often gets you a better, on-the-record version.

And keep it real. Use their actual words. If you trim for length, do not change the meaning. Credit them the way they want to be credited, first name, full name, handle, or anonymous if they prefer. The whole value of proof is that it is true, so protect that.

Turn it into something people see

Here is where most of these die. The quote is real, you have permission, and then it sits in a doc because turning it into something worth posting means opening a design app and fighting with fonts. So it never goes out.

This is exactly the wall I wrote about in 8 things to post as a developer: the content is ready, the design is the blocker. The fix is to decide once what a testimonial looks like in your world, and then reuse it. One quote card, your colors, your type. From then on, a new testimonial is a two minute job, not a design project.

That is the whole reason the Text card in Monocards exists: paste the quote, add who said it, and it comes out on-brand and ready to share. When you want it to read like a real reply from the platform, the Social card mocks it up as a post or a message. You lock in the look one time, and every kind word after that becomes a card you can drop into a launch thread or the top of your landing page. The app is optional here. The habit is the point: make sharing a testimonial cheap enough that you actually do it.

Where to put them

Once you have a few, put them where decisions happen. Near your download or sign-up button, not buried at the bottom. In your launch posts, one strong quote per post. On the pricing page, right where the hesitation is. And keep sharing single ones as you get them, the same way you share a milestone, so the stream of proof is public, not just parked on one page.

You do not need a hundred reviews to look trusted. You need three specific, real, well-placed ones, and a habit of not deleting the next one.

The work is not getting testimonials. It is noticing that you already have them, asking at the right moment, and making them cheap to show. Start with your archive folder. There is probably a testimonial in there you filed under “nice” last week.