Private equity buyers evaluating a SaaS target should focus their diligence on four areas: the quality of recognized revenue, the stability and retention of the customer base, the technology stack and its integration burden, and the retention risk carried by key people. Formal due diligence typically begins after an NDA and letter of intent, and in FE International's experience, drawn from more than 1,500 completed transactions, this confirmatory phase spans roughly four to six weeks — the stage where deals are either confirmed or abandoned. Below is a framework for working each of the four areas, the metrics that matter in each, and the red flags that should change the price or the decision.
Area 1: Financial Health and Revenue Quality
SaaS-specific financial diligence goes beyond the baseline statements every deal team reviews. Kruze Consulting, which has guided hundreds of venture-backed SaaS companies through diligence, emphasizes that the checks that "catch most issues" are revenue recognition and deferred revenue — reconciling the contract, the cash, the deferred revenue schedule, and the metrics in the board deck so they all agree with each other.
Two checks deserve particular attention. First, confirm that revenue recognition follows GAAP or IFRS standards, particularly for annual and multi-year contracts, a step Thomas Smale's due diligence checklist for buyers at FE International singles out. Second, scrutinize deferred revenue carefully: FE International's guide on the subject warns that this is "where many buyers underestimate the impact on valuation and deal terms." Also verify gross margins by reviewing hosting costs, third-party API expenses, and support overhead, since infrastructure costs can quietly erode the margin profile a pitch deck presents.
The valuation context matters as much as the accounting. As Smale cautions, a public SaaS company trading at 7x revenue does not mean a comparable private company with $3M ARR should command the same multiple. Separately, watch for aggressive pro-forma add-backs: Hebbia's overview of private equity due diligence notes that sellers often use them to inflate EBITDA, forcing deal teams to separate genuine adjustments from management optimism.
Area 2: Customer Stability and Net Revenue Retention
Recurring revenue is only as good as the customers generating it. FE International's checklist advises requesting a full customer list with contract start dates, plan types, and revenue contribution, then calculating net revenue retention, gross churn, and logo churn by cohort. Cohort-level analysis matters because aggregate numbers can mislead: Hebbia warns of a "more dangerous variation" in which a few large, expanding accounts mask a high churn rate — top-line revenue looks stable or growing while the business rapidly loses smaller customers, a pattern indicating poor product-market fit and heavy exposure if primary clients pull back.
Net revenue retention is the metric to weigh most heavily. It measures whether existing customers' spending grows or shrinks on its own — upsells and expansions minus churn and downgrades. As Iron Meadow Holdings puts the priority: "Net revenue retention, because it tells you whether the existing customer base grows or shrinks on its own. Everything else — growth, CAC, even churn — is easier to fix than a product customers quietly abandon."
Benchmark churn against the right population before drawing conclusions. Iron Meadow reports that healthy annual churn for an established B2B SaaS business sits roughly between 6% and 10%, while smaller SMB-facing tools often run 3–7% monthly, because small businesses churn tools quickly. Neither figure is automatically disqualifying — but the price must reflect it. Customer concentration is the other classic pitfall; Ben Murray's preparatory guidance at The SaaS CFO underscores that buyers will expect monthly historical tracking of bookings — new, expansion, and downgrades — plus churn in both dollar and logo terms.
Area 3: Technology Infrastructure and Integration Complexity
Technology diligence covers systems architecture, cybersecurity posture, technical debt, and integration costs, and it typically runs in parallel with the other workstreams during the confirmatory phase. The red flags to surface, per V7's Casimir Rajnerowicz, are legacy system dependency, data privacy exposure, and integration costs — risks that rarely appear on a balance sheet but shape what the buyer can actually do with the asset after closing.
Assess infrastructure at the component level: network diagrams, firewalls, firmware currency, server and cloud hosting arrangements, and software licensing. Long-term hosting, telecom, or software contracts deserve specific scrutiny because they can limit integration flexibility, constraining the growth plans that justified the acquisition in the first place.
Technical debt deserves its own line of inquiry because it is, in Iron Meadow's framing, "the least visible and most expensive surprise." Their guidance is blunt on when to bring in outside help: for financial and legal review above roughly $250K in deal size, professional support is warranted, and for technical review, an independent audit is worth it at any size. Automation can carry part of the load — document ingestion, metric reconciliation, dependency and security scanning, and risk scoring are systematic tasks — but judgment on price and structure remains human.
Area 4: Talent Retention and Operational Stability
Operational diligence examines the team, its processes, and its scalability. The documents to request are organizational charts, process documentation, HR data, and management biographies, with key person risk, supply chain fragility, and process gaps as the red flags to surface. Key person risk is the one that most directly threatens a SaaS thesis: if a founding engineer or a product leader holds institutional knowledge that no documentation captures, the asset's value can walk out the door with them.
For a private equity buyer, the talent question extends past the target itself. Integrating the acquisition into the portfolio is a known quantity of work: IT practitioners describe defining a baseline IT standard for the platform company, assessing each acquisition against it, agreeing on a remediation plan, and moving the company onto shared support, security, and Microsoft 365 — with tenant integration usually the first major post-close project. Whether key engineers and product managers stay through that transition is a diligence question, not a post-close assumption, and the retention plan belongs in the deal terms rather than in hope.
SaaS Acquisition Due Diligence Framework
Use the table below as a working checklist: for each of the four areas, it pairs the metrics to analyze, the questions to press, and the red flags that should alter price or structure. The comparison shows how the workstreams interconnect — a deferred revenue discrepancy undermines the revenue base, cohort churn undermines the customer base, and lock-in contracts or key person flight undermine the post-close plan.
| Diligence Area | Key Metrics to Analyze | Critical Questions to Ask | Potential Red Flags |
|---|---|---|---|
| Financial Health | Revenue recognition (GAAP/IFRS), deferred revenue schedule, annual prepayments and contract terms, gross margins (hosting, third-party APIs, support) | Do billing terms and recognized revenue agree? Can metrics be recalculated from underlying data rather than only a pitch deck? Is the recognition policy applied consistently across all customers? | Discrepancies between billing terms and recognized revenue; aggressive pro-forma EBITDA add-backs; assuming a public company's revenue multiple applies to a private target with different ARR |
| Customer Stability | Net revenue retention, gross dollar retention, logo churn by cohort; new/expansion/downgrade bookings; revenue contribution per customer | Is NRR above or below 100%? What does cohort-level churn reveal that aggregate revenue hides? How does churn compare to benchmarks for this customer segment? | A few large expanding accounts masking high small-customer churn; churn above the 6–10% annual B2B norm (or 3–7% monthly for SMB tools) without price adjustment; customer concentration |
| Technology Infrastructure | Systems architecture, cybersecurity posture, technical debt, integration costs; network diagrams, firewalls, firmware currency, hosting, software licensing | What will integration into the portfolio platform cost? Do long-term hosting, telecom or software contracts limit flexibility? Has an independent technical audit been run? | Legacy system dependency, data privacy exposure, unmeasured technical debt, lock-in contracts that constrain integration and growth plans |
| Talent / Operational Stability | Team structure and scalability from org charts, process documentation, HR data, management bios | Which individuals hold knowledge no documentation captures? Who is staying through the transition? Is there a retention plan in the deal terms? | Key person risk, process gaps, and departures that would destabilize the business during integration onto shared systems |
Read row by row, the framework also ranks urgency by area. Financial and customer checks validate the price; technology and talent checks validate the plan. A target can pass the first two and still fail the investment thesis if technical debt or a key person dependency makes the post-acquisition roadmap unexecutable.
Making Informed Investment Decisions
Private equity firms should integrate findings from financial, customer, technology, and talent due diligence to form a holistic view of a SaaS target's value and risks, informing both the final investment decision and the post-acquisition strategy. The four areas are not independent verdicts: a churn problem reshapes the revenue model, a licensing lock-in reshapes the integration budget, and a key person risk reshapes what any of the other findings are worth.
The measurable test of whether diligence did its job is concrete: successful integration of the due diligence findings into the investment committee memo, paired with a clear post-acquisition value creation plan. If the memo cannot state, from evidence, why revenue recognition holds, why NRR supports the growth case, what integration will cost and when, and who is staying to execute — the diligence is not yet finished. The confirmatory window of roughly four to six weeks is the buyer's opportunity to surface exactly those gaps while the deal can still be repriced or declined.
Sources
- SaaS Due Diligence Checklist for Buyers in 2026 | FE International — Feinternational
- SaaS Due Diligence Checklist for Startups — Kruzeconsulting
- Private Equity Due Diligence: What You Need to Know — Hebbia
- Logistics & Supply-Chain Software Acquisitions — Iron Meadow Holdings
- How to Prepare for Preliminary SaaS Due Diligence - The SaaS CFO
- Private Equity Due Diligence Process: AI vs Traditional — V7LABS




