Diligence does not test whether your numbers are impressive. It tests whether they are true.
Founders walk into a data room thinking the investor is judging growth rate, ARR, runway, and margins. They are, but only after they decide the numbers can be trusted. A diligence team starts by looking for the one thing that does not lie. Once one number breaks, they stop adjusting that number and start questioning the system that produced it.
This field guide covers the finance and accounting layer of diligence: the numbers, schedules, reconciliations, and hidden liabilities that turn a clean raise into a retrade, a cleanup sprint, a reserve, or a long delay.
It was created by Punch Financial, our Bookkeeping & Accounting partner. Punch runs CFO and accounting operations for venture-backed startups across every stage and business model, from seed-stage SaaS to usage-based AI, so they have watched diligence teams work from the inside and know exactly where the numbers break. This guide is that experience, condensed into a self-check you can run before the room opens.
What's inside
Eight landmines, each with the founder's mental model, the diligence mechanic that exposes it, what it costs you, a 60-second self-check, and a fix list:
- Your ARR is built on cash, bookings, or Stripe, not earned revenue
- Prepaid credits and annual contracts are booked as revenue too early
- Your ARR includes revenue that is not actually recurring
- Your gross margin is not tied to the real cost of serving customers
- Retention and customer concentration do not support the growth story
- You have sales tax exposure in states where you never registered
- Your financial statements do not tie to the source systems
- Your equity records do not reconcile to the balance sheet
Plus two bonus checks sophisticated founders should run early: worker classification exposure, and whether your QSBS clock and qualification are actually documented.
How to use it
Read each landmine and tick the box if it is true of your books. Checking a box is not a reason to panic. It is a reason to clean the issue up while you still control the process. Before diligence, you can fix it, document it, and explain it. During diligence, the same issue becomes a reason to slow down, widen scope, or re-underwrite the deal.
