Machine-Verified Demand: When a Signed Webhook Is the Proof

Ask a founder how many paying customers they have and you will get a number. Ask them to prove it and you will get a screenshot. The gap between those two answers is where most launch platforms live - and it is exactly the gap machine verification exists to close.

The evidence tiers ladder runs from a founder's word to a machine's observation. This piece is about the top rung: what it actually means for a number to be machine-verified, and why it is rare enough that a board displaying it is telling you something no vote count ever can.

What machine-verified actually means

The phrase gets used loosely. Here is the strict version, as one board implements it (R-52):

1. The fact is observed, not reported. A "paying" count that comes from the founder typing a number is self-reported, whatever the dashboard looks like. A paying count that comes from a payment event the machine received and recorded itself is observed. The difference is who produced the number: the person with an incentive, or the system with no opinion.
2. The event is signed by the payment processor. The founder wires their own payment webhook - the endpoint their processor already calls when money moves - to the board, along with the endpoint's signing secret. Every payment event arrives with a cryptographic signature, which the board verifies server-side. A forged or tampered event fails the signature and is refused. The board never holds the founder's processor keys; the signature is the whole point.
3. The record is idempotent. Payment processors redeliver events - retries, dashboard replays. A verification system that counts redeliveries double-counts revenue. The correct behavior: the same event arriving twice is acknowledged and recorded once, forever.

One more detail that separates observation from theater: the launch gate. Only paying relationships that started after the founder joined the board count. A customer from before is the founder's past, not the board's evidence - their renewals arrive forever and are received, but never recorded. A cancellation notice changes nothing either. The machine counts one thing honestly: people who started paying while the record was live. The system reports what is true, not what flatters.

Why the receipts matter now

Traction-faking went from scandal to business model. Bought upvotes are a priced market on the big boards, revenue screenshots are routinely rendered rather than captured, and at least one prominent founder has publicly admitted lying about revenue after the fact. The response from most platforms has been pattern detection - statistical screens that catch campaigns but cannot tell you whether the specific number you are reading is real.

Signature verification ends the argument instead of profiling it. When a board displays a paying count marked machine-verified, the claim is not "the founder says" or "we checked and it looks fine" - it is "the payment processor signed this, and here is the tier that proves how we know." A buyer comparing platforms should treat the absence of that mark as data: if a number does not say how it is known, it is marketing.

The same discipline applies to votes, incidentally - the cheap currency of launch day. A vote count anyone can buy tells you about a wallet; a verified join tells you about a product. The metric that survives manipulation is the one that requires a real person to do the real thing.

What it is not

Machine verification is deliberately narrow, and the narrowness is the honesty:

• It is not a gate. Tiers are labels, never gates (R-52): a startup with only self-reported numbers is not hidden or ranked down - its numbers simply wear the tier they earned. The reader decides what each tier is worth.
• It is not the board processing money. The board never takes a cut of pilots, never touches a subscription, never holds processor keys - money never touches the seat machine (R-18). The webhook records facts; commerce lives elsewhere.
• It is not an endorsement. A verified payment says the payment happened - by the stated method, signed by the stated processor. It says nothing about whether the product is good. What it proves is demand; whether the demand is deserved is still your judgment.

How to do it yourself

If you are a founder: declare your activation event before you need it, wire your webhook, and let the numbers land where they land - the same pre-registration logic as a commitment clock. If you are building your own product and want credible numbers without a board: the pattern is the takeaway. Do not report what you can observe. Report what a system you do not control has already confirmed, label everything else as your own word, and make the label impossible to miss.

The uncomfortable version: if your numbers only look good when they are self-reported, machine verification is not the thing to fix first.

launchduels runs the top tier on every listing - the paying facts are signed, and the tiers are public. Put your real numbers on the record →