By Mehdi HassanEvery founder hits the same wall: the landing page needs proof, and there are no customers to quote yet. The usual responses are to skip proof entirely or to stretch the truth. Neither works. This guide lists twelve honest sources of proof early startups already have, and how to present each. It's part of our wider guide to social proof on landing pages.
What counts as social proof for startups with no customers?
Social proof for startups with no customers is any credible, third-party or verifiable evidence that the team can deliver and that people want the product. Before revenue, visitors aren't asking 'did it work for others?' because they know you're new. They're asking whether you're serious, whether you'll be around, and whether anyone else cares.
That shifts the type of proof. Instead of results, you show credibility (who's building it), backing (who has bet on it), and demand (who's waiting for it or trying it). These are weaker than a case study, but they're honest and they answer the doubts early visitors actually have. A clear message matters even more at this stage; our guide to explaining AI products covers this for technical startups, where vague promises are the default.
What are the 12 honest proof sources early startups have?
The twelve honest proof sources early startups have fall into four groups: the team, the backers, early demand and the work itself. Most startups have several of these on day one, even before launch.
Proof source | Doubt it answers | How to show it |
|---|---|---|
1. Founders' track record | Can this team build it? | Previous companies, roles and relevant expertise |
2. Investors | Will they be around? | Named funds or angels, with permission |
3. Advisors | Do experts back the approach? | Named advisors with a one-line reason they joined |
4. Design partners | Is this built with real users? | Company names or roles, with permission |
5. Beta or pilot usage | Is anyone actually using it? | A precise, current count of teams or users |
6. Waitlist size | Does anyone want it? | A real number, updated, without rounding up |
7. Pilot feedback | Does it work in practice? | Short attributed quotes from beta users |
8. Open-source activity | Is the code real and maintained? | Stars, contributors and recent commits |
9. Integrations | Does it fit my stack? | Logos of platforms you genuinely integrate with |
10. Accelerator or program | Has someone vetted them? | Named program, if it's recognized by your buyers |
The final two are less obvious. 11. Public building: a changelog, demo videos or a founder's posts about what shipped this week prove momentum. 12. Credentials and compliance work: if you've started a security certification or follow a known standard, saying so honestly, including that it's in progress, answers a risk question enterprise buyers will ask anyway.
How should you present team, investors and advisors?
Present team, investors and advisors as short, specific facts tied to the product's problem, not as a résumé. 'Built payments infrastructure at a fintech for six years' tells a buyer why this team can solve their payments problem. A list of famous former employers without context reads as name-dropping.
- Team: one line per founder linking past experience to this product's problem. Real photos, not illustrations.
- Investors: a short 'Backed by' line with fund names, placed low on the page or in the footer area. Buyers care less than founders think, but it signals runway.
- Advisors: only include advisors whose expertise a buyer would value, with one line on what they contribute.
- Permission: confirm every name in writing. Some investors and advisors prefer not to be listed.
This kind of proof belongs on the about page as well as the landing page, since serious evaluators check it there. It's one part of a wider set of brand trust signals for early-stage startups, along with a consistent visual identity and clear contact details.
How do you show early demand before launch?
You show early demand before launch with precise, current numbers and named early users: waitlist signups, beta teams, design partners and pilot feedback. The rule is precision. A specific, modest number that's true reads as more credible than a big round one that sounds invented.
Waitlist pages are the most common place to show this. A line like 'Join [exact number] product teams on the waitlist' is persuasive if the number is real and updated. Our guide to waitlist landing pages covers how to build pre-launch demand, and our pre-launch and waitlist page examples show how other startups present early numbers.
For example, suppose a pre-seed startup has a beta and three design partners
For example, suppose a hypothetical pre-seed analytics startup has 40 teams on a closed beta, three design partners and one advisor who ran data teams at a known company. Its landing page hero says what the product does, with a line underneath: 'In beta with 40 product teams.' Midway down, a 'Built with' section names the three design partners with their permission, and one short quote from a design partner's head of product describes a report they now build in minutes. The team section explains the founders' background in one line each. Nothing is inflated, and every claim can be checked.
Can you use pilot feedback as testimonials?
Yes, you can use pilot and beta feedback as testimonials if the person approves it and the quote is clearly about their real experience. Label it honestly where it matters, for example 'Beta user, Head of Ops at a logistics startup'. Early feedback quotes are often more specific than later ones, because beta users pay close attention.
Ask early. The moment a beta user tells you the product saved them time is the moment to ask for a 15-minute call and turn their words into a quote. Our guide to getting testimonials that sell has the interview questions and the approval email. If a company won't allow its name, a quote attributed by role and industry is still better than none.
What social proof should startups avoid?
Startups should avoid any proof that would embarrass them if a visitor checked it: logos of companies that never became customers, testimonials from friends or investors posing as users, fake review counts, invented usage numbers, and 'as seen in' bars for outlets that only republished a press release.
Pros
- Honest early proof sets a standard you can keep as you grow.
- Precise numbers and named partners are checkable, which makes them more believable.
- Team and expertise proof is strong for complex products where buyers bet on the builders.
Cons
- Early proof is weaker than customer results and won't close large deals alone.
- Small honest numbers can feel underwhelming, so the message has to carry more weight.
- Proof like waitlist counts needs regular updating, or it goes stale.
There's also a legal side. Consumer protection rules in many regions, including the FTC's in the US, treat fake reviews and undisclosed endorsements as deceptive. That's reason enough, but the commercial reason is stronger: a trust problem at launch follows a startup for years.
When should a startup replace early proof with customer proof?
A startup should start replacing early proof with customer proof as soon as its first users get real value, which is usually during the beta. Swap waitlist numbers for usage numbers, design-partner mentions for quotes, and the 'Backed by' line for a first case study page.
Plan for it from the start: ask for logo and quote permission when a pilot begins, track a simple before-and-after metric with each early customer, and review the page every month. Once you have a handful of customers in one industry, a focused logo wall becomes useful. If the page itself needs rebuilding for the new stage rather than just new proof, our guide to fixing just the homepage explains when one page is enough.
