You ask the same way you will later, just from a shorter list. Before your first paying client that list is people who have seen you work rather than bought from you, and the trick is knowing which of them can vouch for the thing you actually sell. Get that right and three quotes will carry your site until real customers replace them.
The short version:
- Five sources produce a first testimonial: free work, a beta seat, a former colleague, a pilot at cost, and your first paying customer.
- Not all of them can speak to your offer. A former manager can vouch for you; only a user can vouch for the thing.
- Say how you know the person, right beside the quote. Volunteering the connection makes the quote more believable, not less.
- Ask for private permission as well as public, because favours often come with a quiet preference not to be the face of your homepage.
- A written process and one measured result from your own work outperform borrowed praise while you wait.
Who you can ask before your first customer
The list is short, and each name on it is good for something different. Sort them by what they can actually say about you, and the plan writes itself.
| Who to ask | What they can speak to | How fast |
|---|---|---|
| Someone you did free work for | The work itself, start to finish | Immediately |
| A beta or early-access user | The product, and what it replaced | Within a few weeks |
| A former colleague or manager | You — how you work, what you’re good at | Immediately |
| A pilot client at a low rate | Everything a full client could | One project |
| Your first paying customer | Everything, with nothing to explain | Slowest, best |
The bottom row is the one you want and the one you can’t have yet, which is the honest summary of this whole problem. The rows above it are how you get there: each one is real proof of something, and the job is putting each quote where what it proves matters.
Free work is the fastest route and the one most people take. Pick recipients who look like the customers you want, not whoever says yes first — a testimonial from someone in your target market is worth several from outside it, because the reader is looking for themselves in the quote.
What each one can honestly vouch for
This is the distinction that decides whether these early quotes do any work, and it’s easy to miss.
A former manager can tell the world you’re meticulous, fast, and good to work with. What they can’t tell the world is whether the thing you now sell delivers, because they’ve never bought it. Both are true statements about you. Only one of them answers the question a visitor on your pricing page is holding, which is “will this work for me?”
Position makes the claim, whatever the words say. A quote sitting in a testimonial slot under a photo and a job title reads as a customer’s verdict on the offer. So put a character reference where character is the question — an about page, a bio, a services page describing how you work — and save the proof section for people who used the thing.
That’s not a demotion. On a solo consultancy’s about page, a former manager saying you ran the hardest project on their team is stronger proof than a beta user’s line about onboarding. Match the quote to the doubt, the same way you would for any testimonial you place on a page.
Say how you know them, and say it on the page
Put the relationship beside the quote. “Beta user, free early access.” “Former colleague.” “Received the service free in exchange for feedback.” One short line, under the name.
The instinct is that this weakens the testimonial. It does the opposite, and the reason is worth understanding because it applies to everything on your proof section. A visitor can’t verify that a quote is true. What they can do is judge whether it looks like something someone would bother to fake — and nobody fabricating praise volunteers a limitation on their own evidence. Saying “this person got the work free” is a signal only an honest business sends, which is exactly why readers weigh it as one.
The alternative is worse than it looks. A reader who finds out later that your glowing testimonials came from friends discounts everything on the page, including the real ones. That’s the expensive version, and it happens after they’ve decided to trust you, which is when trust is most costly to lose.
Received the service free in exchange for feedback.
Beta user, free early access.
Former colleague, worked together at [company].
Discounted first project.Keep it to a line. The disclosure has to travel with the quote to every page it appears on, which is the practical argument for capturing it as a field on your form rather than remembering to type it each time you place a testimonial. This is the same reason real testimonials so often read as fake: the credibility lives in details that are easy to drop.
Ask for private permission, not just public
Your entire supply of testimonials at this stage is favours, and people doing favours are careful about their own reputation. The beta user happy to help is often the same person who doesn’t want to be the face on your homepage, because they’re not yet sure about the thing they’d be publicly attached to.
Asked as a yes-or-no question, that person says no and you record nothing. Asked as two options, the same person very often says yes to one: use it in a sales conversation, a proposal, a deck, anywhere unpublished. That’s a real asset, and at this stage it’s frequently your best one, because early on you’re selling in conversations rather than off a page.
A form that stores how each person allowed their response to be used keeps the two categories from leaking into each other later — in Testymo the answer lives on the submission alongside the exact words. The full case for asking at collection time is in how to get permission to use testimonials.
What goes in the proof slot meanwhile
The usual answer is a list of substitutes: trust badges, “as seen on” logos, follower counts, live pop-up notifications. Most of them prove something other than what your visitor doubts. A security badge answers a question about payment safety. A follower count answers a question about popularity. Neither answers “will this work for me”, which is the question the testimonial section exists to answer.
Three stand-ins do answer it, and you can produce all three alone.
The first is your process, written out concretely: what happens in week one, what you need from them, what they get at the end, and what happens if it doesn’t work. A specific process is evidence you’ve thought the work through, and unlike a compliment it’s checkable.
The second is a measured result from your own work. If you sell the thing you used on yourself, the numbers you produced are yours to publish, with the method stated. One honest before-and-after with the method attached beats three vague quotes.
The third is a single detailed account from one named beta user, with the free-access note attached. One specific story about what changed is stronger than five anonymous lines of praise, and a lone unattributed quote at hero size reads as invented.
Give each stand-in a retirement date when you put it up. The process block comes off the sales page once three real testimonials are live; the self-measured result moves to a methodology page rather than living in the proof slot forever.
Collect the first three so you never collect them twice
The expensive mistake here is collecting words and nothing else. A compliment in an email has no role, no company, no permission, and no answer to the question you actually needed answered — so publishing it means going back to that person three times for one missing piece each.
Ask for everything in one short form: the answer itself, their name, their role and company, whether you may use it publicly or privately, and how they came to work with you. That last field is the relationship line, captured as data at the moment it’s cheap to ask. Which questions produce which parts of a finished testimonial is worked through in testimonial questions to ask customers.
The same applies to praise you already have. An old email is a good reason to ask, not a testimonial you can publish, because it arrived without a byline or an answer about publishing — the reply to unprompted praise is the message that fixes that in one send. When the first three are in hand, adding them to your site is the short part of the job, and the timing and phrasing for every ask after that is in how to ask for a testimonial.
Frequently asked questions
How many testimonials do I need before publishing a section?
Three specific ones will carry a page. One strong, fully attributed testimonial beats a section padded with borrowed praise, so publish when you have something a sceptical reader would find credible and keep the stand-ins up until then.
Can I use a testimonial from a friend or family member?
You can, and you should say that’s who they are. In practice that tends to defeat the purpose on a sales page, because a reader who learns the endorser is a relative discounts it entirely — which is the correct outcome rather than a problem to work around. Friends are better used as a first form test than as proof.
Do I have to mention the free work if they never promised me a testimonial?
Say it anyway. The reader isn’t judging what you and the customer agreed; they’re judging what they can see, and a quote from someone who got the work free reads differently once that’s known. Volunteering it costs you a line and buys you the reader’s trust in everything around it.
Can testimonials be anonymous?
They can, and they’re weak proof that gets weaker the more prominently you place them. If someone won’t attach a full name, a first name and a real role usually gets most of the credibility with none of the exposure they were worried about — and saying the name is withheld reads better than reducing them to initials.
Should I offer free work specifically to get testimonials?
It works, and it’s how a lot of good businesses started. Two things keep it useful: pick people who match the customers you want, so the quote speaks to the right reader, and agree upfront that you’ll ask for feedback at the end, so the request isn’t a surprise landing on top of a favour.