Prove your startup's numbers without exposing them

2026-08-29·Launch and early traction·2 min read·by Sourabh Singh

Prove your startup's numbers without exposing them

What you can verify about traffic and revenue, what stays private when you do, and why a banded verified figure beats an exact self-reported one.

Prove your startup's numbers without exposing them

You can prove traffic and revenue with read-only connections that expose only aggregate totals - never customer records. Publish figures as dated bands rather than exact numbers: a verified band is more credible to a reader and less useful to a competitor.

Every landing page claims something. "Trusted by 10,000 teams." "Join 50,000 makers." None of it is checked, everyone knows none of it is checked, and so it all carries roughly zero weight.

The interesting question is what you can actually prove without handing over your business.

The three things worth proving

Domain control

The weakest claim and the easiest to check: that you control the site you are pointing at.

How: a DNS TXT record, or a verification file, or a badge served from your own HTML. All three prove the same thing - someone with write access to that domain agreed to this.

What it exposes: nothing. A DNS record is already public.

What it is worth: it stops the entire class of listings that point at someone else's product.

Traffic

How: a read-only connection to your analytics. The verifier reads aggregate session counts for the property and nothing else.

What it exposes: aggregate totals. Not individual visitors, not their identities, not what they did. There is nothing personally identifying in a session count.

What it is worth: a lot, because traffic is the most inflated number in software marketing and the easiest to disprove once someone can actually look.

Revenue

How: a read-only connection to your payment processor, reading totals only.

What it exposes: a total. Not customer names, not email addresses, not individual transactions, not what anyone paid.

What it is worth: most of all, precisely because nobody does it.

Publish bands, not exact figures

This is the part people get wrong when they decide to be transparent.

An exact figure - "$4,312 MRR" - is a gift to competitors, a target for anyone who wants to undercut you, and no more informative to a reader than a band.

"$2–5k MRR, verified 29 August 2026" tells a prospective customer everything they wanted to know: this is a real business at a real scale, and someone checked. It tells a competitor almost nothing actionable.

Bands plus dates plus a named source. That combination is what makes a claim citable - by a reader, and by an AI answer engine deciding whether your number is quotable.

What verification must never do

  • Read customer records of any kind.
  • Require write access to anything.
  • Be irrevocable. If revoking is hard, the connection is too broad.
  • Publish anything you did not agree to publish.

If a verification process wants more than aggregate totals, that is a data-collection exercise wearing a badge.

The staleness problem

A verified number is only true on the date it was checked. A badge from eighteen months ago proves nothing about today.

Anything claiming to verify has to re-check on a schedule and let levels fall, publicly, when the evidence stops supporting them. A verification that only ever goes up is a marketing programme.

The test for any verification scheme: what happens when the number gets worse? If the answer is "nothing, the badge stays", the badge never meant anything.

Launch it where the numbers are checked

RankCert ranks products on domain control we verify ourselves. Listing is free and the link stays dofollow whether or not you display the badge.

Submit a product - free

Tools from this guide