What a diligence team actually asks for, in the order they ask for it
Diligence feels like an interrogation when you're in it. It isn't. The requests arrive in a fairly predictable order, and each one is testing something specific. If you know what each question is really asking, you can build the answer years before anyone asks it — which is the only time building it is cheap.
1. Bank statements, not dashboards
The first request is almost always raw bank statements for the trailing twelve months. Not a Stripe dashboard, not an exported CSV, not a screenshot of MRR. Statements.
This surprises founders, who tend to think of their processor as the source of truth. It isn't. The processor is a system you control and could, in principle, misrepresent. A bank statement is a third-party record. The question underneath the request is: does money actually arrive, from whom, and how regularly?
2. Processor data, to reconcile against the bank
Only after the statements does anyone want the Stripe or PayPal export. And the point of it is not the revenue number — it's whether the two agree.
This is where a lot of otherwise healthy businesses lose momentum. The numbers rarely match on the first pass, because of payout timing, refunds, chargebacks, platform fees, and currency settlement. All of that is explainable. But explaining it live, from memory, three years after the fact, reads as improvisation — and improvisation is exactly what a diligence process is designed to detect.
3. Revenue quality, not revenue volume
Next comes the breakdown: recurring versus one-time, customer concentration, churn, and contract terms. A business doing $40k a month from four hundred customers is a different asset from one doing $40k a month from three. Same number, different risk.
This is where the "$5M+ cash flow" conversation actually happens. Buyers evaluating scale are not asking whether the revenue exists — they're asking whether it will still exist after the founder leaves.
4. The gaps, and how you explain them
Every history has anomalies: the month a payment provider held funds, the customer who churned and came back, the pricing change that broke the trend line. Buyers expect these. What they're reading is not the anomaly but your explanation of it.
A founder who says "that was March 2025, we migrated processors and the payout landed on the 1st instead of the 28th, here's the record" is telling a different story from one who says "I'd have to look into that." Same underlying fact. Very different signal.
What this means for what you build
Every one of those four requests is a question about history, and history is the one asset you cannot create retroactively. You can improve your product in a quarter. You can fix your pricing in a week. You cannot go back and make last year's payments reconcilable.
That's the reasoning behind how Trust Fabric records payments: every financial event written immutably and hash-chained as it happens, so the record handed over in year three is the one created in year one. Not because cryptographic attestation is interesting on its own, but because the alternative is reconstructing three years of payment history under time pressure, during the single negotiation where you most need leverage.
The founders who do well in diligence are rarely the ones with the best numbers. They're the ones who can answer quickly, consistently, and with a record that agrees with itself.