How to Get Testimonials When You Have No Customers

Your landing page has a section for testimonials. It has had one for four months. It currently holds three grey placeholder cards, or you deleted it and the page has a gap where trust was supposed to go.

You are stuck in a loop that every founder hits exactly once: you need social proof to convert customers, and you need customers to produce social proof. The loop is real, and it is also breakable — because "testimonial" is a much narrower word than "proof", and you are almost certainly sitting on proof you have not recognised as proof.

Who this is for

You have shipped. You have somewhere between zero and five paying users. Maybe a few dozen people have tried the free tier and said nothing.

You are not short of evidence — you are short of the specific artefact you have seen on other companies' websites: a headshot, a name, a job title, and two sentences of praise. Because that is the only shape you recognise, you have concluded you have nothing.

You also have not asked anyone. Asking feels like begging, and the one time you drafted the message it read as needy, so you closed the tab.

Why this feels harder than it is

Two things are happening at once.

The first is a definition problem. Trust on a web page does not come only from quoted praise. It comes from any signal that other humans have been here and it went fine. A named customer quote is the strongest of those signals, and it is one of about eight — the rest of which do not require a single paying customer.

The second is a timing problem, and it is the expensive one. The moment a person is most willing to say something nice about your product is roughly ninety seconds after it solves their problem. Not at the end of the month. Not when you finally get round to building a testimonial-request flow. Founders miss that window over and over, then conclude their users do not like the product enough to say so.

Both problems have the same fix: know what counts as proof, and ask at the moment it exists.

The proof you can collect this week

Not all social proof is the same strength, and — usefully — the weakest kinds are the ones available at zero customers. Start at the bottom of this table and work up as you get users.

Three rows deserve a note.

Screenshots of unsolicited praise are underrated and you already have some. Search your inbox, your Discord and your GitHub issues for "thanks", "this is great" and "exactly what I needed". Most founders find two or three within ten minutes. Ask that person for permission to quote them; they said it publicly already, so the ask is small.

A number from your own logs is proof and costs nothing. "Processes 40,000 webhooks a day" is a verifiable fact about your system. It is not a claim about anyone's results, which is what makes it safe to publish. Be careful to source anything you write down — an unsourced multiple like "3x faster" reads as measured and is the easiest sentence to be held to.

Being your own case study is legitimate when you say so. You built the thing because you had the problem. Write up what your own numbers looked like before and after, label it clearly as your own use, and you have a specific, honest story where you previously had a grey placeholder.

How to ask, and when

The ask itself is four lines. The timing is the whole game.

1. Instrument the moment of success. Whatever "it worked" means in your product — first deploy, first import, first report — that event is your trigger. You do not need a system for this at five users. You need to notice.
2. Ask within a day, referencing the specific thing. Not "would you mind leaving a testimonial". Try: "You got your first deploy running on Tuesday. Would you be up for two sentences on what it replaced? Happy to write a draft for you to correct."
3. Offer the draft. This is the line that changes reply rates, and it is not manipulation — it is removing work. Most people want to help and do not want to write. A draft they edit is faster for them and more specific than what they would have written cold.
4. Ask for one concrete detail rather than praise. "What were you doing before?" produces a usable quote. "What do you think of the product?" produces "it's great".
5. Get permission in writing, and record what you were allowed. Name, role, company, and whether the logo is allowed are four separate permissions. Assume none of them until told.

Step 5 is the one that quietly matters later. A quote you cannot attribute because you never asked is a quote you cannot use on the page, and by the time you need it that user may have moved jobs. The Mark Platform stores each piece of social proof against the product it belongs to with the attribution attached, so the quote and its permission never drift apart — which also stops one client's proof appearing on another's page if you are running marketing for several products.

Where the proof goes once you have it

Collecting is only half of it. Proof placed below the fold is proof nobody sees.

Put your strongest single piece near the headline, not in a testimonials section three screens down. The visitor deciding whether to keep reading never reaches the section — this is one of the seven questions a landing page has to answer in order, and it is question five, not question nine.

Then put a second piece next to the price. That is the other moment doubt spikes.

Why we are telling you this

The Mark Platform treats social proof as a step in the 8-step journey rather than a page section, because the collection is a process and the page is just where it ends up. Every quote is stored against a product with its source and permission, and the website audit checks whether trust signals appear on your site at all — it is one of the seven categories it scores.

We are also being careful about what we claim here. Nothing in this post says testimonials will lift your conversion rate by some multiple, because we would have to source that number and it would still be someone else's product. What we can tell you is what the audit repeatedly finds: early pages have a trust-signal gap, and the founders who fill it are the ones who asked at the right moment rather than the ones who waited to have something impressive.

This will not help if nobody has used your product yet. Zero users is a distribution problem, not a proof problem — start with cold email or the communities your buyers already read and come back when someone has a win worth quoting.

Common questions

Is an anonymous testimonial worth anything? Yes, and it is much better than a placeholder. "A solo founder running a Postgres-backed side project" carries real information. Never invent one — a fabricated quote is the single fastest way to lose the trust you are trying to build.

Can I offer a discount in exchange for a testimonial? You can, but the quote gets weaker and you have to disclose it in most jurisdictions. Ask first without an incentive; most people say yes.

How many do I need before the page looks credible? Two specific ones beat six vague ones. Stop collecting once you have two that name a concrete before-and-after, and spend the time on distribution instead.

What if someone gives me a lukewarm quote? Do not publish it, and do read it carefully. A lukewarm testimonial from a real user is a product signal — it usually means the value landed somewhere other than where you think it does.

Your next step

Spend fifteen minutes today searching your inbox and Discord for "thanks". Ask the two people you find for permission to quote them. That is a page with real proof on it by Friday.

The Mark Platform gives every quote a home with its source and permission recorded, and checks your site for the trust signals it is missing. Start your marketing journey — free.