How to Get Your First 10 Testimonials Before Launch

Photo by Kelly Sikkema on Unsplash

You get your first ten testimonials by giving ten specific people the product early, watching what they do with it, and then asking a narrow question about a moment you already witnessed. Not by broadcasting a request. Not by trading discounts for praise — which, since October 2024, is regulated in ways most founders don't realize. The first ten are a manual, one-at-a-time job that looks nothing like the automated review flows you'll run later, and the constraint isn't finding willing people. It's that a stranger cannot write a specific sentence about a product they haven't actually used for anything.

TL;DR

• Ten early users who each did one real thing with your product will produce better testimonials than a hundred people on a waitlist.
• Specificity is the whole game. "Great product" is worthless; "it took me 40 minutes instead of the weekend I'd blocked out" sells.
• The FTC's Consumer Reviews and Testimonials Rule took effect October 21, 2024. You may not condition an incentive on positive sentiment, and civil penalties run to $53,088 per violation.
• Employees, friends, and family can write testimonials, but the relationship must be disclosed clearly and unavoidably — a hyperlink doesn't count.
• Testimonials on your own site are discounted by readers. Getting a few onto third-party platforms is worth more than doubling the count on your landing page.

Before going further: I'm a founder, not a lawyer, and the regulatory section below is a plain-English summary of published FTC guidance rather than legal advice. Read the primary sources I link, and talk to an attorney about your specific situation.

What actually counts as a testimonial?

A testimonial is an advertising message that consumers are likely to believe reflects the opinions, beliefs, or experiences of someone who has used your product. That's essentially the FTC's own definition, and it's worth internalizing early because it draws a line most founders blur.

The FTC distinguishes testimonials from consumer reviews. A review is submitted to and published on a platform dedicated to receiving and displaying evaluations — an app store, a review site, a product page. A testimonial is an advertising message you put in your own marketing: your landing page, your launch post, your onboarding email. Most reviews aren't testimonials and most testimonials aren't reviews, though incentivized reviews count as both.

The practical consequence: when you quote a happy user on your landing page, you are advertising. The FTC's guidance is direct that a business putting testimonials on its own website "is disseminating them and is not merely hosting them" — so the merely-hosting exemption that protects retailers displaying customer reviews does not protect you.

This matters for what you should be collecting. You don't need star ratings before launch. You need three or four sentences from a named human describing something concrete that happened when they used the thing. That's a testimonial, it's the highest-leverage asset a pre-launch product can have, and it cannot be manufactured — which is exactly why it works.

One useful side effect of the definition: it tells you what a good testimonial contains. The FTC cares about representations of the endorser's experience — what actually happened when they used the product — as distinct from their opinion of it. Opinions aren't regulated the same way and, not coincidentally, they don't persuade anyone either. "I loved it" is an opinion. "I had the Stripe webhook working before lunch" is an experience. Collect experiences.

Where the first ten actually come from

There is no channel that produces testimonials for a product nobody has used. There are only people, ranked by how likely they are to do something real with early software. Here's the honest ordering, from my own launch and from watching other indie founders run the same play.

| Source | Typical yield | Quality | Effort per testimonial | Main risk | | --- | --- | --- | --- | --- | | People who described the problem to you first | 3-5 of 10 asked | Highest | Low | Small pool; you have to have been listening | | Founders in your niche you've actually helped | 2-4 of 15 asked | High | Medium | Feels transactional if the relationship is new | | Beta group from a waitlist | 2-3 of 50 signed up | Mixed | High | Most never open the product | | Community members (Discord, Slack, subreddit) | 1-3 of 20 asked | Medium | Medium | Rules against promotion; easy to get banned | | Friends and family | 1-2 | Low | Low | Requires disclosure; readers discount heavily |

The first row is where nearly all of my usable material came from, and it's the row that requires work you should already have done. Every person who ever complained to you about the problem you're solving is a candidate, because they can articulate the before state without prompting. That's the half of a testimonial founders always forget to collect.

The waitlist row deserves a caution. A big waitlist feels like a testimonial pipeline and mostly isn't. People sign up for waitlists in a moment of mild curiosity and forget within a week. Hand-selecting 20-30 people from a list and personally onboarding them will outperform emailing a thousand, because the binding constraint is usage, not willingness.

The sequence that works looks like this:

flowchart TD
    A[Pick 10-15 named people who have the problem] --> B[Personal message: offer early access, no ask attached]
    B --> C[Onboard each one manually; watch where they stall]
    C --> D{Did they complete something real?}
    D -->|Yes| E[Note the specific moment and the date]
    D -->|No| F[Fix the blocker; do not ask]
    F --> C
    E --> G[Ask a narrow question about that moment]
    G --> H[Draft a tightened version; send for approval]
    H --> I[Publish with name, role, and any required disclosure]

The step founders skip is the diamond. Asking someone who stalled at step two for a testimonial produces a vague sentence, because vague is all they have. It also burns the relationship, since you've made them say something they don't believe. If they didn't get anywhere, that's product feedback, and it's worth more than the quote would have been.

This same manual-first logic drives everything else about early distribution — it's why the first hundred customers come from conversations rather than channels, and why shipping before you feel ready is the only way to have real usage to point at.

The ask: timing, wording, and the question that works

Most testimonial requests fail because they ask the person to do the writing. "Would you mind writing a few words about your experience?" hands a blank page to someone with a job. Weeks pass. Nothing arrives.

Ask a narrow question about a specific moment instead.

Timing. Ask within 48 hours of the moment they got value. Memory decays fast and specificity decays with it. If someone messages you "ok this actually worked," that's the window — not next month.

The message. Here's roughly what I send, adapted per person:

Hey [name] — you mentioned Tuesday that you got billing working in an afternoon after putting it off for weeks. I'm putting together the launch page and I'd love to quote you on that.

Two questions, one sentence each is plenty:

1. What had you tried before, and what was annoying about it?
2. What specifically happened when you used it — how long did it take, what did you end up with?

If you'd rather not, genuinely no problem, and it changes nothing about your access. If you're up for it I'll draft something from your answers and send it back for approval — you can change or kill any of it.

Four things are doing the work there. It references a specific moment, so they're recalling rather than composing. It asks two narrow questions, which is a two-minute job. It makes declining costless and explicitly decouples the ask from their access, which matters both ethically and legally. And it offers to do the writing, with approval — most people are happy to be quoted and reluctant to draft.

The before question is the important one. Question 1 produces the half of the testimonial that makes it credible. "This saved me so much time" is unfalsifiable. "I'd been putting off payments for three weeks because I didn't understand webhooks" is a person. Readers who share that before state recognize themselves, which is the entire mechanism by which social proof works.

Editing. You may tighten for length and clarity. You may not write the sentiment for them. The FTC's guidance is pointed here: a business "shouldn't provide the text for a testimonial without a reasonable basis to conclude that the text is truthful about the testimonialist's experience." Sending a draft built from their own answers and getting explicit approval is the clean version. Sending a flattering paragraph you invented and asking them to sign off is not.

Ask for attribution. Name, role, company, photo, and a link if they have one. An anonymous testimonial is worth a fraction of an attributed one, and asking at the same time avoids a second round of email. If they'd rather stay anonymous, use it anyway and accept the discount.

If your first ten need to come from people you haven't met, the same specificity rules apply to the initial contact — the cold outreach script for solo founders covers that part.

The incentive question, and what changed in 2024

This is the section most founders skip, and it's the one with actual downside.

The FTC's Rule on the Use of Consumer Reviews and Testimonials went into effect on October 21, 2024. It authorizes courts to impose civil penalties for knowing violations, with the Commission citing penalties of up to $53,088 per violation. There's no private right of action, so you're not going to get sued by a competitor over this — but "no one has sued me" is not the standard you want for the copy on your homepage.

Three provisions matter for a pre-launch founder.

You may offer incentives. You may not condition them on sentiment. The rule does not prohibit giving people something in exchange for a review. What it prohibits is any express or implied requirement that the review express a particular sentiment. The FTC's own examples of implied requirements are instructive: "Tell us how much you loved your visit to John's Steakhouse and get a $5 coupon" violates it. So does "tell your friends about all the fun you had." Read your own draft email with that lens — most founder testimonial requests contain a smuggled assumption that the answer will be positive.

Insiders can participate, but the relationship must be disclosed. Employees, contractors, officers, and their immediate relatives may write reviews and testimonials, provided they clearly and conspicuously disclose the connection. The FTC's guidance says a small business owner can ask family members to write reviews, as long as they disclose the relationship. "Clear and conspicuous" is defined strictly: the disclosure must be unavoidable, meaning a consumer can't be required to take any action — clicking a hyperlink, hovering over an icon — to see it. A disclosure in the first line of the review qualifies. An asterisk leading to fine print does not.

Free access is a material connection. Under the FTC's Endorsement Guides, a material connection includes a financial relationship or the gift of free or discounted products or services. The need to disclose isn't limited to situations where money changes hands. If your ten beta users got lifetime free accounts, that's a material connection, and the disclosure belongs with the endorsement rather than on an About page.

The compliant version of all this is not onerous. It looks like:

• Give early access freely, with no strings and no expectation stated.
• Ask about their experience without signalling the answer you want.
• Note "early access user" or "received free access" next to the quote.
• If it's your cousin, say so in the first line.
• Never pay for a specific sentiment, on your site or anywhere else.

One more thing worth knowing, because founders do this instinctively: asking only the customers you think are happy is not prohibited by the rule itself, but the FTC notes it could violate the FTC Act under the Endorsement Guides. The safer habit is to ask everyone who completed something real, and then decide what to publish — selective publication of genuine testimonials is normal advertising, while a collection process rigged to surface only praise is a different thing.

Where to put them (and why your landing page isn't enough)

Having ten testimonials and putting all ten on your homepage is a mistake, because readers apply a discount to anything a company chose to display about itself.

Nielsen Norman Group's usability research is blunt on this. In studies of how people evaluate company websites, participants regarded quotes and case studies displayed on company sites with skepticism, reasoning that the site would of course only include the positive ones. NN/g's guidance on communicating trustworthiness concludes that having a presence on external review sites matters more than on-site testimonials, and that linking out to those sources signals transparency and confidence.

So the placement strategy for ten testimonials is roughly:

Three or four on the landing page, positioned next to the specific claim each one substantiates rather than herded into a wall of quotes. A testimonial about setup speed belongs beside the setup-speed claim. A wall of five-star cards reads as decoration; a quote in context reads as evidence.

One or two on the pricing page, ideally addressing the objection that shows up right before purchase. That's usually "is this worth it" or "will I be able to use it." Placement near the decision point is doing most of the work — the same logic as the rest of the pricing page anatomy.

Two or three pushed to third-party platforms. Product Hunt comments, a relevant subreddit thread, an Indie Hackers post, a G2 or Capterra listing if your category has one. These carry more weight than anything on your own domain, and they're the ones you should be asking for explicitly rather than hoping for. This is worth folding into the pre-launch checklist rather than treating as an afterthought.

The rest go into onboarding email. A relevant testimonial in day-two of a welcome sequence reaches people at the moment of doubt, which is where it does the most good in the onboarding flow.

And keep the raw material. The full transcript of what someone told you — before you tightened it — is the best source of landing page copy you will ever have. Most of the phrasing on my own site came from users describing the problem in their words, not from me trying to write marketing.

Frequently asked questions

How many testimonials do I actually need before launching?

Three specific, attributed testimonials outperform fifteen vague ones. If you have three people who can each describe a concrete before-and-after with their name attached, you have enough to launch. Ten is a comfortable target because it gives you material for the landing page, the pricing page, and third-party platforms without reusing the same quote everywhere.

Can I offer a discount in exchange for a testimonial?

You can offer an incentive for a review or testimonial, but you cannot condition it on the review being positive — including by implication, which is where most founder emails go wrong. You also need to disclose the incentive. In practice, giving free early access with no strings and asking afterward is simpler and produces better material than any incentive structure.

What if my only early users are friends?

Use them, disclose the relationship clearly and unavoidably in the first line of the testimonial, and treat them as a bridge rather than a destination. Readers heavily discount testimonials from people connected to the founder, which is appropriate. Replace them with customer testimonials as soon as you have any.

Do I need written permission to quote someone?

Get it in writing — an email or chat message approving the exact text is enough. It protects you if they later object, and it forces the useful step of showing them the tightened version before it goes live. Ask for approval of the wording, the attribution, and the photo together.

Can I edit a testimonial for length?

Tightening for length and clarity is normal, as long as the edited version still accurately reflects what the person said about their experience and they approve it. What you can't do is supply the sentiment yourself. The line the FTC draws is about having a reasonable basis to believe the text is truthful about the testimonialist's actual experience.

What if someone gives me negative feedback instead?

That's a better outcome than a weak testimonial, and it usually means you asked too early. Fix the thing they hit, tell them you fixed it, and ask again after they've used it successfully. Don't offer them anything to soften or withdraw criticism — beyond being a bad idea, paying to remove truthful negative reviews can itself run afoul of the FTC Act.

Start with ten conversations, not ten requests

The reason first testimonials feel impossible is that founders think of them as a marketing asset to be acquired, when they're a byproduct of watching real people use the thing. If ten people have genuinely used your product and you were paying attention while they did, you already have ten testimonials — you just haven't transcribed them yet. If nobody has used it yet, no amount of asking will conjure specificity that doesn't exist.

So the work is upstream. Get ten named people using it, onboard them one at a time, note the exact moment each one got value, and ask about that moment within two days. Keep the incentive out of it, disclose every relationship, and put a few of them somewhere that isn't your own website.

If you're at the stage where you're hunting for those first ten users, Coding Capybaras is the free boilerplate I built so non-technical founders can get to a working product fast enough to have something worth testifying about.