Most landing page advice begins with social proof, logo walls, testimonials, customer counts, and badges from platforms your startup has not earned yet.
That is useful only after you have customers. Before that, it creates a different problem, a page that borrows the visual language of trust without any of the substance.
If you are pre-launch, or you have fewer than 50 customers, your landing page still has a job. It must help a visitor answer three questions, fast, can I trust this, do I understand it, and is it for me?
Why guides fail
Most SaaS landing page guides are written around established brands. They assume a visitor already recognizes the company, or can infer legitimacy from other people’s usage.
That logic breaks at zero customers. A startup with no proof cannot win by imitating Asana or Mixpanel. It has to replace borrowed credibility with direct evidence.
Good pages do this with clarity, specificity, and restraint. They do not ask a visitor to believe more than the page can support.
What visitors ask
For an unknown startup, the order matters. Visitors are not first asking about features. They are asking whether you are real, whether the product is relevant, and whether the next step is worth their time.
- What is this, exactly?
- Why should I believe you?
- Is this for someone like me?
Your page should answer those questions in that order.
Zero-proof stack
At zero customers, trust comes from a stack of smaller signals. None of them replaces customer proof, but together they make a believable case.
Named founder
Put a real human on the page. Use a name, a face, and a title. If you are the founder, say so.
This matters because unknown products are often treated as interchangeable. A visible founder reduces that distance. It tells the visitor someone accountable exists.
Keep it simple, for example, “Built by former security engineers,” or “Founded by operators who spent five years inside RevOps teams.” If you have a relevant background, use it. If you do not, do not invent one.
Show the product
Do not hide behind abstract value statements. Show the product doing the job.
A short unedited demo is better than a polished animation with no substance. If your product is software, use a screen recording, an interactive sandbox, or a narrow walkthrough of one core workflow.
Visitors want evidence that the thing exists and works. A product video should answer “what happens when I click?” not “what mood does this brand evoke?”
When you have no customers, the product itself is the proof.
Make claims testable
Avoid claims you cannot defend. Words like best, fastest, and revolutionary are weak because they ask for belief without evidence.
Prefer claims that can be checked. For example, “Set up in 15 minutes,” “Works with HubSpot and Slack,” or “Replace three manual reports with one automated workflow.”
Specificity does two things. It improves comprehension, and it limits doubt. A visitor can assess a concrete promise far more easily than a broad one.
For guidance on clarity and value proposition structure, see