Watch your own thumb for a week. You scroll past the polished brand announcement without slowing down, and then you stop on a blurry screenshot of someone's actual results, or a customer complaining that a product ruined their excuse for not exercising. Claims from companies bounce off. Evidence from people lands.
That is the entire case for proof content: UGC, testimonials, reviews, and the other artifacts your customers create. It is the cheapest content you are not publishing, and most businesses sit on a pile of it without noticing.
I will add my own disclosure early, because it shapes this whole post. Planpost, my scheduling product, is pre-launch. I have no wall of customer logos and no folder of glowing quotes. Writing this guide is partly me building the collection system before I need it, and the last section covers what to do when you are in that same position.
What counts as proof
The word "testimonial" makes people picture a formal quote next to a headshot, which is the least interesting version. The full inventory is wider:
- Public UGC: posts where a customer mentions you unprompted, tags you, or shows your product in use.
- Reviews on platforms you do not control: app stores, G2, Google, Trustpilot, Amazon.
- Private messages: the email that says "this saved my week," the support ticket that ends in a thank you, the DM reply.
- Replies and quote posts on your own content, where someone adds their experience to your claim.
- Results artifacts: screenshots, before-and-after shots, numbers a customer is willing to share.
- Renewals and repeat behavior you can describe honestly, even without naming anyone.
Two of these arrive in public and the rest arrive in private, which is why proof piles up unseen. The email inbox of your support address probably contains more usable testimonials than your marketing folder does.
What does not count: anything paid or traded that gets presented as spontaneous. Paid creator content can work fine as content, but the moment you dress it up as an unprompted customer opinion, you are one screenshot away from a very bad week. Label what needs labelling.
Ask at the moment of the win
The biggest reason companies lack testimonials is not that customers are unwilling. It is that the ask comes at a dead moment, in a dead format. The quarterly "we'd love your feedback!" survey email produces nothing quotable because nothing just happened.
Ask when something just happened. The customer hit a milestone, renewed, got a result, or told support their problem is solved. That is the moment their goodwill and their memory are both at a peak, and a one-line reply is easy for them.
The question matters as much as the timing. "Any feedback?" produces "great product, thanks!", which is useless. Specific questions produce sentences with texture:
- What almost stopped you from buying?
- What were you doing before, and what happened when you switched?
- What would you tell someone who is on the fence?
- What surprised you?
The first question is my favorite, because the answer is an objection-handler written in a customer's voice. Nothing you write yourself will ever be as convincing as "I thought this would be too complicated for our team, and it wasn't."
Get permission like an adult
The permission rule
If it arrived in private, ask before you publish it. If it was posted in public, ask before you reuse it outside its original context. Keep the yes in writing, credit the person the way they want, and show them the final post if they ask. No exceptions for "they probably won't mind."
This is not just courtesy, though it is that too. Reposting someone's photo or words without permission can violate platform rules and copyright, and the reputational cost of one annoyed customer screenshotting your unauthorized repost exceeds the value of every testimonial you have.
The ask can be tiny. "This made my day, could I share it on our LinkedIn with your first name?" covers consent, attribution, and scope in one sentence. Keep the reply. A folder of screenshots of people saying "of course, go ahead" is boring, and that is exactly what legal boredom should look like.
One more habit worth building: when someone tags you in public UGC, engage with it where it lives before you think about reusing it. Reply, share it to your own audience through the platform's native mechanics, and thank them. Most of the value of UGC is captured right there, in public, at zero cost.
Turn the raw material into posts, gently
The most common way proof gets ruined is over-production. A customer writes "honestly I expected to cancel after the trial and now the whole team uses it," and marketing turns it into a gradient graphic where the sentence has been shortened, capitalized, and drained of blood.
The customer's words are the asset. Your job is framing, not rewriting:
- The plain screenshot with one line of context above it outperforms elaborate design in most feeds, because it reads as evidence rather than as an ad.
- Keep their phrasing, including the imperfect bits. "Honestly I expected to cancel" is the hook. A copywriter would never write it, which is why it works.
- Write the setup, then let their line land. Your text explains the situation; their words carry the verdict.
- For video UGC, clip to the moment of the actual reaction or result. The first eight seconds are the whole game.
- Before-and-after formats need the "before" to be specific. "We were spending Friday afternoons copy-pasting posts" beats "our process was inefficient."
One strong piece of proof is also a campaign, not a post. The same testimonial can run as a plain-text post on X, a longer story with context on LinkedIn, and a visual on Instagram, spaced across weeks. The mechanics of doing that without publishing identical copies everywhere are in my guide to repurposing one piece of content.
Make it a slot, not a burst
Proof content fails as a binge. Eight testimonials in one week reads as desperation, then silence for a quarter. The fix is a standing slot: one proof post per week, or every two weeks, mixed in between your educational and product content like seasoning rather than served as the whole meal.
A recurring slot also forces the collection habit. When Thursday's proof slot exists, someone has to fill it, which means someone is finally reading the reviews and the support threads for material. The calendar creates the demand that makes collection happen.
And measure these posts like everything else. Proof content often looks mediocre on reach and surprisingly good on clicks and conversions, because it persuades the people who were already close. If you can, track them through to outcomes; the setup for that is in how to track revenue from social posts. A testimonial post that quietly produces trials every time it runs is a rerun candidate, and reruns of proof are entirely legitimate. New audiences have not seen it, and the old audience forgot.
When you have no customers yet
Here is my own situation, and maybe yours. Pre-launch, or early enough that the review pile is thin. Two honest moves and one dishonest one.
The dishonest move first, to name it: inventing testimonials, or paraphrasing "what customers would probably say" into quote marks. Beyond the ethics, it is strategically stupid. Fabricated proof is a liability that sits in your feed forever, waiting for the moment your real early customers notice that "Sarah from Ohio" does not exist.
The first honest move is documentation instead of testimony. You cannot quote customers, but you can show the thing working, show the problem it removes, and publish the build as it happens. Proof of work is a real substitute for proof of satisfaction, and audiences read it as evidence because it is evidence. This is most of what I post about Planpost right now.
The second honest move is borrowed specificity. Early users, beta testers, even friends who genuinely use the thing can say true things about it, as long as you label the relationship. "One of our beta users told me" is honest and still concrete. The label costs you almost nothing; the specificity is what persuades.
Collect from day one, even so. The first unprompted "this is great" that lands in your inbox is a future post. Ask for permission the day it arrives, file it, and by the time you have twenty of them you will have a proof engine instead of a scramble.
An invented testimonial is not a shortcut. It is a liability with a caption. The real ones are sitting in your support inbox, and they are better written than anything you would have made up.
