To prepare ARR and pipeline data for due diligence, fix one written ARR definition, then rebuild a monthly, customer-level ARR bridge that ties to invoices, deferred revenue and cash. Add monthly cohorts and CRM field history so every ARR and pipeline number can be re-derived from raw exports before a buyer’s quality-of-earnings team does it for you.
Illustrative example built by JayOh, not client data.
Committed, contracted, recurring, active. Dated churn rule. One page, versioned.
Opening + new + expansion − contraction − churn = closing, tied to invoices, deferred revenue and cash.
By signup month, fixed denominator, gross and net retention split.
Timestamped stage, amount and close-date history. Start now: it can’t be backdated.
A buyer’s quality-of-earnings team does not take the deck. It requests raw exports and rebuilds the numbers. Prepare for these five tests and you have prepared for diligence.
Is ARR contracted, recurring, subscription and active? ARR has no GAAP definition, so buyers re-derive it under their own rules.
Does opening ARR plus movements equal closing ARR, and does each dollar trace to an invoice, the deferred revenue roll-forward and cash collected?
Do monthly cohorts hold up? Newer cohorts retaining worse than older ones, or strong NRR masking weak GRR, are the usual findings.
Top-customer share plus change-of-control, assignment, most-favored-nation and termination-for-convenience terms.
Can stage moves, amount edits and close-date pushes be shown with timestamps, and do closed-won deals match billing?
Every test asks one question: can this number be rebuilt from source data by someone who wasn’t in the room?
Most ARR problems are classification problems. Walk reported ARR down to committed ARR yourself, log every adjustment, and the buyer’s number matches yours. Example below is illustrative (same figures as the hero).
| Adjustment | Illustrative $M | What buyers do | Your fix before diligence |
|---|---|---|---|
| Pilots and POCs annualized | −0.5 | Remove until converted to a signed subscription | Flag pilots in the CRM and billing; exclude until the contract starts |
| Month-to-month annualized as permanent | −0.6 | Treat as non-committed | Report committed ARR and M2M ARR as separate lines |
| Usage overage run-rated | −0.3 | Count only committed minimums | Split committed from uncommitted usage in the billing export |
| Services bundled into subscription | −0.4 | Re-map to non-recurring | Separate SKUs for implementation, training and subscription |
| Notice-given customers still counted | −0.2 | Drop from active ARR | Pick one churn-dating rule (at notice or at service end) and apply it everywhere |
| Ramp deals at end-state value; stale FX rates | 0.0 (not in example) | Re-state to current-period contract value and current rates | Record ramp schedules and FX policy in the definition memo |
| Reported $12.0M → defensible $10.0M | −2.0 (−16.7%) | At an illustrative 6x revenue multiple, $1M of reclassified ARR is $6M of headline price, so $2.0M is $12M. | |
Types of adjustment follow what buyer-side guides from Peony, Papermark and DualEntry describe. Dollar amounts are JayOh-constructed for illustration.
ARR is a non-GAAP run rate; revenue is recognized under ASC 606. Both can be right and still disagree, which is why buyers insist you can bridge one to the other.
| Item | In ARR? | In GAAP revenue? |
|---|---|---|
| $120K annual contract signed July 1 | $120K immediately | About $60K in that calendar year |
| 3-year contract worth $300K | $100K (annual rate) | Recognized ratably over the term |
| Implementation, onboarding and professional services | No | Yes, on delivery or at milestones |
| Uncommitted usage overage | No | Yes, as consumed |
| Customer who gave notice | Removed per your churn rule | Recognized until service ends |
watch this Timing gaps are normal. Buyer-side guides treat an ARR-versus-revenue growth divergence that persists across four or more consecutive quarters as a definitional problem rather than a timing one. That is a practitioner heuristic, not a standard. Reconcile monthly and write the explanation down.
Examples: DualEntry and OnlyCFO ARR-versus-GAAP explainers (2025–2026). A common error flagged by Baker Tilly: extrapolating monthly GAAP revenue ×12 to report ARR.
SaaS Capital’s 2025 survey (14th annual; 1,000+ private B2B SaaS companies; under $1M ARR excluded) puts median net revenue retention at 101% and gross revenue retention at 91%, with median growth of 24%.
Source: SaaS Capital 2025 B2B SaaS Retention Benchmarks.
| Segment (SaaS Capital 2025) | Median NRR | Median GRR |
|---|---|---|
| All companies | 101% | 91% |
| Bootstrapped | 104% | 92% |
| Equity-backed | 101% | 90% |
| Multi-year contracts | 103% | 94% |
| Annual contracts | 101% | 90% |
| Month-to-month | 100% | 89% |
| ACV above $250K | — | 95% |
| ACV below $250K | — | about 91% |
Sapphire Ventures’ 2025 KeyBanc Capital Markets & Sapphire Ventures SaaS Survey lands in the same place: gross retention near 90% and net retention above 100%. Treat these as sanity checks for your cohort, not targets to assume. Full sources: SaaS Capital and Sapphire Ventures. Related: how we measure net revenue retention.
Score yourself on seven tests. Anything weak should be fixed before launch. These bands are JayOh’s synthesis of what buyer-side guides describe; concentration and divergence thresholds are practitioner rules of thumb, not standards.
| Test | Weak | Acceptable | Strong |
|---|---|---|---|
| ARR definition | WEAK Unwritten; Finance, Sales and CS differ | OK Written, mostly applied | STRONG One memo, committed basis, versioned |
| ARR bridge | WEAK Annual, hand-built spreadsheet | OK Monthly, ties to billing | STRONG Monthly by customer, 8–12 quarters, ties to billing, deferred revenue and cash |
| ARR vs GAAP gap | WEAK Unexplained for 4+ quarters | OK Explained, undocumented | STRONG Documented monthly reconciliation |
| Cohorts | WEAK One blended NRR | OK Annual cohorts | STRONG Monthly cohorts, fixed denominator, GRR and NRR split |
| Concentration | WEAK Top customer above ~15–20% with change-of-control terms | OK Top customer ~10–15%, clauses reviewed | STRONG Top customer under ~10%, clauses catalogued |
| Pipeline history | WEAK Current-state report only | OK History on some fields | STRONG Field history on stage, amount, close date; monthly anomaly review |
| CRM-to-billing match | WEAK Unexplained gaps | OK Gaps explained quarterly | STRONG Automated match; exceptions logged |
Finance guides cover ARR well and skip pipeline. Buyers still ask whether your forecast was honest. Give them history, not a current-state report.
| Export | What it proves | Red flag a buyer looks for |
|---|---|---|
| Opportunity field history (stage, amount, close date, timestamped) | Numbers weren’t edited after the fact | No field history, or edits after close |
| Stage-to-stage history for every opportunity in the period | Stage discipline | Deals jumping from early stage to closed-won; abnormal time in stage |
| Close-date push log | Forecast hygiene | Same deals pushed month after month, never removed |
| Win rate and cycle time by segment and rep, rolling | Pipeline quality | Win rate flattered by a shrinking denominator |
| Quarter-start pipeline snapshots vs outcomes | Coverage and forecast accuracy | No snapshots, so coverage can’t be proven |
| Closed-won to billing match | Bookings are real ARR | Bookings with no invoice; large “miscellaneous” ARR adjustments |
Field history and snapshots cannot be created retroactively. Switch them on now, and tell buyers honestly when history starts. See our guides on pipeline forecasting hygiene and forecasting pipeline accurately.
Checklist items reflect request lists published by Peony, Papermark and FE International for software targets, plus JayOh’s CRM-side additions. For the full commercial view, see our GTM due diligence checklist.
Sell-side preparation commonly starts 3 to 6 months before launch (Papermark). Buy-side review typically runs 4 to 10 weeks (Papermark) or 4 to 6 weeks after LOI (FE International).
Write definitions. Turn on field history. Start quarterly pipeline snapshots.
Build the ARR bridge and three-way tie-out. Build monthly cohorts.
Apply adjustments. Reconcile ARR to GAAP. Run a buyer-style self-review.
Assemble the data room pack. Dry-run the questions with Finance, RevOps and the CRO.
Buyer diligence. Answer from raw exports, not slides.
Finance: ARR bridge sign-off, GAAP reconciliation, deferred revenue. RevOps: CRM field history, stage definitions, cohort data, CRM-to-billing match. CRO: pipeline narrative and snapshots. Customer Success: renewal and notice dates.
Rebuilding ARR from monthly GAAP revenue ×12. Sending a spreadsheet instead of raw exports. Reporting only blended NRR. Turning on field history after launch. Fixing numbers inside the data room. Changing definitions mid-process.
JayOh is a GTM systems engineering firm, a HubSpot Platinum Partner and an Anthropic partner, building revenue systems through embedded growth pods since 2016. The Revenue Diligence-Readiness Package is built for the 60 days before a data room opens: clean ARR reporting, defensible funnel metrics, reconciled cohort data and documented systems.
Clients on JayOh’s reporting methodology have seen forecast accuracy improve by about 28%.
We standardized RevOps and built GTM infrastructure across five Samsung Next portfolio companies. Read the case study.
A diligence scoring system for OpenView cut time spent on low-potential deals by roughly 30%.
Billing and CRM have to tell one story, whether the stack is HubSpot, Salesforce or a billing platform like Chargebee. Related: our data cleanup methodology, private equity support and post-acquisition CRM consolidation.
In diligence, ARR is the annualized value of contracted, recurring subscription revenue from active customers at a point in time. It is a management metric with no GAAP definition, so buyers rebuild it from billing exports, contracts and cash instead of accepting the number you report.
ARR is a point-in-time run rate; GAAP revenue is recognized over a period under ASC 606. A $120K annual contract signed July 1 adds $120K to ARR immediately but about $60K to calendar-year revenue, and services, onboarding fees and uncommitted usage sit in revenue but not in ARR. Keep a monthly reconciliation between the two.
Plan for an ARR bridge covering the last 8 to 12 quarters and a customer-level monthly ARR schedule covering at least 24 months, with term and status flags on every customer.
Buyers typically strip them out of committed ARR: pilots annualized before conversion, month-to-month contracts annualized as permanent, and usage overages projected as steady state. Remove them yourself, log each adjustment, and show the committed number alongside the reported one.
Expect requests for timestamped opportunity history on stage, amount and close date, stage-to-stage movement, win rate and sales-cycle length by segment and rep, and a match between CRM closed-won deals and billing records. Quarter-start pipeline snapshots let you prove coverage and forecast accuracy.
Sell-side preparation commonly starts 3 to 6 months before launch, and buy-side diligence typically runs 4 to 10 weeks. Field history and pipeline snapshots cannot be backdated, so turn them on first.
There is no formal standard. Practitioner rules of thumb flag a single customer above roughly 10 to 20 percent of ARR, especially when its contract has change-of-control, assignment or termination-for-convenience terms.
SaaS Capital’s 2025 survey of more than 1,000 private B2B SaaS companies found median net revenue retention of 101 percent and median gross revenue retention of 91 percent. Companies with NRR above 130 percent grew at a median of 50 percent, versus 21 percent for those at 100 to 110 percent.
Finance should sign off on the ARR bridge and its reconciliation to GAAP revenue and cash. RevOps owns the CRM field history, stage definitions, cohort data and the CRM-to-billing match that feed it.
Sources (2023–2026): SaaS Capital, 2025 B2B SaaS Retention Benchmarks. Sapphire Ventures with KeyBanc Capital Markets, 2025 SaaS Survey. Peony, SaaS due diligence guides (2026). Papermark, SaaS due diligence (2026). FE International, SaaS due diligence checklist (April 2026). DualEntry, ARR vs revenue (2026). OnlyCFO, ARR vs GAAP revenue (2025). Baker Tilly, ARR reporting in diligence (2023). Buyer-side timelines, thresholds and ARR adjustment categories are vendor and advisor guidance, not regulatory standards; the weak/acceptable/strong bands and the ARR example are JayOh synthesis. Last updated November 5, 2026.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
