What 'verified' should mean in diligence

“Verified” is becoming startup land’s most abused word. Marketplaces verify profiles, platforms verify metrics, badges verify everything — and almost nowhere does anyone finish the sentence: verified against what? Here is a working standard worth holding every use of the word to, whichever side of the check you sit on.

The standard: claims traced to sources

A claim is verified when it’s been checked against something that would be hard or consequential to fake — and when the checking is specific: this claim, that source, this date. Three tiers of source, in descending strength:

Executed documents. A signed stock purchase agreement, a countersigned SAFE, a board consent. Strongest, because the document is the fact — the shares exist because the paper exists.

Systems of record. A payment processor’s ledger, a bank feed, a state registry. Strong for exactly what they measure: Stripe knows revenue that moved through Stripe; it knows nothing about the side deal invoiced by PDF. Good verification names its system and its scope.

Public filings. A Form D, a certificate of incorporation, a franchise-tax status. Attested under legal consequence, free to check, and chronically underused.

Below the line: decks, screenshots, data-room PDFs of dashboards, and the founder’s memory. These are claims — the inputs to verification, never its output.

Verified ≠ vetted — and the difference is load-bearing

Verified says: this factual claim matches its source. Vetted says: someone judged this company worth your attention. The first is checkable, automatable, and honest about its limits. The second is an opinion in a process costume — and when a platform’s “vetted” badge turns out to mean “we had a call with them,” the word did the damage.

The distinction cuts both ways. A verification-first read can tell you a cap table ties out to its documents, that revenue is source-traced, that the IP chain is complete. It cannot tell you the market is real or the founder is exceptional — and any system that implies otherwise has quietly crossed from fact into advice. Knowing where verification ends is part of using it.

The practical test, for each side

Angels: for any claim that would move your decision, ask one question — “what would I look at to check this?” If the answer is a source document, ask for it (a founder with a real data room produces it in minutes). If the answer is “you’d have to trust me,” you’ve learned where the claim actually sits. The pre-check routine is this test, systematized.

Founders: the standard is your friend, because meeting it is a moat. “Verified” claims cost you nothing when the paper exists — and the raise-time difference between asserting your numbers and demonstrating them is measured in weeks of diligence and points of trust. The companies that make verification effortless are making a statement no deck can: check anything; it holds.