Why self-reported metrics kill small acquisitions

A founder wants to sell a small software business. A buyer is interested. Both are acting in good faith. The deal still takes four months, or dies — and the reason is almost never price. It is that the buyer cannot cheaply establish that the numbers are real.

What gets offered as evidence is a screenshot of a dashboard. The buyer cannot tell whether it is filtered, whether refunds are netted out, whether one customer is 40% of it, or whether the date range was chosen. So they ask for more. The founder sends a spreadsheet. The buyer asks for the export behind the spreadsheet. Weeks pass, and the momentum that makes deals close leaks away.

Verification is a product feature, not a service

The instinct is to solve this with people: an analyst reviews the books and writes a report. That works and it does not scale to deals of this size — the diligence costs more than a fraction of the transaction.

The alternative is to make the seller connect the source instead of describing it. Read-only access to the payment processor and the analytics property, pulled by the platform, reconciled, and presented identically for every listing. The seller is no longer asserting a number; they are authorising the platform to go and read it.

This changes the negotiation completely. Every listing is measured the same way, so a buyer can compare two businesses without re-doing the work each time, and a seller with genuinely good numbers is no longer penalised for the fact that liars also make claims.

What has to be built alongside it

• Staged disclosure. Sellers will not connect their Stripe account to a public listing. Verification has to happen behind an NDA gate, with aggregate signals public and detail released to qualified buyers.
• Consistent definitions. 'Monthly revenue' must mean one thing platform-wide, including how refunds, trials, annual plans and taxes are handled — and it must be stated on the listing.
• Settlement. Verified numbers get a buyer to yes; escrow gets them to paid. A marketplace that stops at introductions has solved the easy half.
• Honest gaps. Some businesses cannot be verified — cash revenue, a homegrown billing system. Say so on the listing rather than quietly treating unverified as verified.

The general lesson

Wherever your product asks a user to assert something another user must rely on, you have a choice: police the assertion, or remove the need for it by reading the source. The second is more work up front and it is the one that compounds, because it holds as the marketplace grows and the incentive to misrepresent grows with it.