Social proof when you have no customers yet

List only what exists. A short, specific block beats vague claims. Put it near the top of your homepage and on /pricing.

• Your own use. Example: “We run our docs, roadmap and billing in YourProduct every day.” Link to those pages.
• Real counts. Example: “Pages indexed: current count” or “Sites checked this week: current count.” If counts are small, say “so far”.
• A public roadmap. Example: link /roadmap with dates and statuses.
• Open source parts. Example: link to github.com/yourproduct/sdk and list the licence.
• A candid comparison. Example: “YourProduct vs Spreadsheets: faster set-up, missing SSO. See /compare/spreadsheet.”

Show these as small, linked components, not empty badges. If a number updates, automate it. If it is manual, add the date captured.

Do not fake demand. Do not borrow other people’s brands. It backfires and it is risky for a small company.

• No invented quotes. If there is no name and company, do not use it.
• No customer logos without written permission. Do not copy them from a trial, a pitch or LinkedIn.
• No vague counters like “10k+ happy users” when you have none. Use real, small numbers instead.
• No “as seen in” unless you have an article to link, not an ad or a directory listing.

Trust is a set of pages, not a single badge. Ship these pages first, link them in your footer, and reference them in your product screens.

• About: real names and roles, a photo, a short line on why you built it, a postal address and a company registration.
• Security: what is encrypted, where data lives, how to delete data, how to report a bug. Example: /security.
• Status: a simple uptime page, even if manual at first. Example: /status with a feed.
• Changelog: dated entries, one line per change, with screenshots where helpful. Example: /changelog.
• Screenshots: real product images, not mockups. Label alpha features clearly.
• Support: a visible support address that reaches a person. Example: [email protected].
• Terms and privacy: plain language pages that you keep current. Link them in the footer.
• Third-party reviews: when you have them, link your G2, Capterra or Product Hunt pages from /customers.

A fixed page looks like this: /about with founders’ names, company number, and a photo in the first screen. It reads as human and current, not corporate filler.

Your hero can earn trust without quotes. Use a short claim, then a proof subline that links to evidence, and a next step in the reader’s words.

Title: Plan sprints, see delivery dates, hit your launch.
Proof subline: Built for founders, by a founder. Public roadmap since Jan 2026. Open SDK on GitHub.
CTA: See a demo project.

Place one call to action per page. Put it where the answer ends, not in a modal that interrupts. Phrase it as the next step: “see the report for your domain” or “create a sample invoice”. This matches what is documented to work on content pages.

Serve the visitor who came for the query before you sell. Interstitials that cover content on mobile are penalised as of 2026. Keep your proof visible without scrolling, keep sales secondary to the answer.

You do not need thousands of users. You need three people with a real problem your product solved, willing to be named. Here is a simple sequence.

1. 1

   Pick three reachable prospects

   Choose people you can help this month. Aim for one ideal buyer, one stretch, one friendly peer. Write their names on /customers as “in progress” only if they agree.

2. 2

   Do hands-on onboarding

   Set up the product for them. Join a call. Move their first data in. Leave with one clear success metric in their words, even if small.

3. 3

   Support like a founder

   Reply fast from your own address. Fix one bug they hit, ship one small ask. Log both on /changelog with dates.

4. 4

   Ask for a micro-quote

   After a win, ask for one or two sentences in their words, with name and company. Offer a draft, but let them edit. Get written permission to publish.

5. 5

   Publish and link

   Add the quote to /customers with a headshot, link to their site, and the context. Add the story to a short case study. Share the changelog item that enabled it.

If they cannot be named, do not publish the quote. An anonymous quote helps little. Keep the relationship warm, and ask again after the next win.

A case study has a fixed shape. Keep it tight. Even early, you can publish one per use case or integration.

• Who the customer is in two lines. Example: “Acme Labs, a 5 person biotech startup in Cambridge.”
• The problem in their words. Use their quotes or email sentences.
• What was done. Be specific: which features, which files, which settings.
• The result with the figure the customer gave. Never infer. If the result is qualitative, say so.
• A quote with a name and company.
• The product’s part named plainly. Example: “Auto-sync in /settings cut their manual export step.”

Title it for search: “Project planning software for biotech labs” or “YourProduct for biotech labs”. It can rank on the customer’s name plus your category and on “X for Y” searches.

A comparison can be social proof. It shows you know the market and where you fit. Honesty is the signal.

URL: /compare/yourproduct-vs-spreadsheet
Lead: YourProduct is faster to set up than a spreadsheet for weekly planning. It is missing SSO and budgets today.
Who should pick a spreadsheet: You need offline first. You share in email only. You will not invite teammates.
Who should pick YourProduct: You plan sprints, assign across people, and want dates without formulas.
Roadmap: SSO planned Q4. Budgets in discovery. See /roadmap.

Link to docs and to your roadmap. If a feature is missing, say it. If you have a workaround, show it. Invite readers who are not a fit to return when the roadmap item ships.

Price pages convert when they are clear. You do not need complex tiers early. One plan or two plans are fine if the difference is obvious.

• Plans are few, two to four, with one recommended.
• Each plan has one line on who it is for and the one limit that matters.
• The price is visible without a click.
• Annual and monthly are a toggle with the saving stated.
• The FAQ answers support’s objections: cancellation, card, limits, what happens at the end of a trial.
• Plan names match the app, the docs and your emails.

Do not quote industry average conversion rates. Published averages vary by source, industry and definition. The only rate that matters is your own, measured over a period long enough to hold a few hundred sessions that began on the landing page. Track signup conversion as accounts created divided by visitors of the signup path. Track trial-to-paid only within the same cohort. Free trial and freemium are different models with different rates and different support costs.

Reduce signup friction before you ask for a card. Each extra field costs you. Card before the product is seen, email verification before the first screen, a password policy that rejects real passwords, no single sign-on, or vague errors, all hurt conversion. Fix these first, then judge pricing page changes by your own rate.

A quote earns a click when it is next to the action it supports. Do not stack quotes in a carousel far from context.

• Home: one proof block under the hero, linking to /customers and /changelog.
• Features: one short, relevant quote per feature at the end of the section.
• Pricing: one quote per plan, naming the plan used.
• Signup: proof of safety, not hype. Link /security and /status. Keep the form short.
• Content pages: answer first, then one CTA that names the next step where the answer ends.

If search traffic arrives and does not convert, check three causes: the query intent is informational and the page sells, the next step is missing or below the fold, or the visitor is not the buyer. Product analytics that join the landing page to the signup event is how you tell them apart. Fix only what a page can change: answer, then offer, and place the CTA where the answer ends.

Plan a simple sequence. Update the same pages as signals land. Name dates in your changelog to show steady progress.

1. 1

   First 10 active users

   Add a small count with “so far” near the hero. Example: “Teams planning in YourProduct this week: number so far.” Link to how you count.

2. 2

   First three named quotes

   Add them to /customers with headshots and links. Place one on /pricing beside the recommended plan. Include context, not just praise.

3. 3

   First logo with permission

   Place it once, near the quotes, with a link to the case study. Do not fill a grid with unpermitted brands.

4. 4

   First third-party reviews

   Link your Product Hunt page or a G2 profile from /customers. Do not copy-paste reviews without the platform’s embed or a link.

5. 5

   First strong metric

   Add one usage metric with a date. Example: “Files synced in August: your measured count.” Keep it narrow and auditable. Remove vanity counts that no longer help.

6. 6

   As enterprise asks arrive

   Expand /security with more detail, add a short DPA, add audit logs to /features. If you add SSO, update /compare and /pricing the same day.

A fixed page at each stage looks consistent: the same plan names in the app, the docs, the emails and /pricing. Quotes always with names. Metrics with dates. Roadmap with statuses that change.