Ask a GP what kills deals and the answer is always the same. “Seller expectations were too high.”
That is the number one deal obstacle in the 2026 Bain/StepStone GP survey. Inflated seller expectations. The seller wants 9x. The buyer sees 7x. The gap cannot be bridged. The deal dies.
But the number two obstacle is more interesting because it is more fixable.
Diligence red flags. Earnings quality. Customer churn. The metrics that looked solid in the CIM but did not hold up when the buyer started pulling the threads.
Both obstacles, the first and the second, come down to the same question. Can the numbers survive scrutiny?
What a diligence red flag actually looks like
The term “diligence red flag” sounds dramatic. In practice, it is usually mundane. It is a discrepancy that creates doubt.
The CIM says revenue grew 15% last year. The audited financials show 13%. The difference is a timing adjustment that is perfectly legitimate, but it was not disclosed. The buyer now wonders what else was not disclosed.
The management presentation says customer retention is 92%. The billing data shows 86% when measured by the same methodology the buyer uses. The definition was different. Nobody intended to mislead. But the buyer’s diligence team now adjusts every other metric for potential definitional variance.
The EBITDA bridge shows $3 million in add-backs. Two of the three are well-documented, one-time expenses with clear supporting evidence. The third is a $900K adjustment for “operational restructuring” with a one-paragraph description and no supporting schedule. The buyer marks it as a risk item. The adjustment may be entirely valid. But the lack of documentation makes it a liability.
Each of these red flags, individually, is manageable. Deals survive individual discrepancies. What kills deals is the pattern. When the diligence team finds three or four discrepancies in the first week, the conclusion is not “this company has a few documentation gaps.” The conclusion is “we do not have confidence in these numbers.”
That conclusion changes the deal structure. Or it kills the deal entirely.
The confidence framework
Buyers do not make decisions based purely on the numbers. They make decisions based on their confidence in the numbers.
Two companies with identical EBITDA, identical growth rates, and identical margins will receive different bids if one generates buyer confidence and the other generates buyer doubt. The confident bid is clean. Full price. Simple structure. Fast close. The doubtful bid is discounted. Earnout-dependent. Extended timeline. Additional diligence requests.
GF Data’s analysis of 360 mid-market transactions since Q3 2024 shows this directly. Sellers with a quality-of-earnings analysis plus a data quality assessment achieved 7.4x EBITDA multiples. Sellers without the data quality component achieved 7.0x. A $2 million difference on a $50 million business.
That gap is not a function of operating performance. It is a function of buyer confidence. And buyer confidence is a function of how quickly and cleanly the seller can answer the buyer’s questions.
The questions that matter
Diligence teams have hundreds of questions on their checklists. But in practice, most red flags stem from a small number of high-impact areas.
Revenue quality. Is the revenue real? Is it recurring or one-time? Does it reconcile across systems? Can you show it by customer, by segment, by time period, tied to the general ledger? Revenue quality is the single most scrutinized area in diligence because it is the foundation of the valuation model. Any inconsistency here cascades through the entire analysis.
Customer concentration. What percentage of revenue comes from the top five customers? Is the concentration increasing or decreasing? What is the churn rate by cohort? Buyers want to know whether the revenue base is diversified enough to survive the loss of a key customer. If the answer requires a week of analysis because the data is not organized for this question, the buyer’s assumption will be unfavorable.
EBITDA adjustments. Every add-back in the EBITDA bridge needs to be documented, one-time, and defensible. The quality of the documentation matters as much as the legitimacy of the adjustment. An add-back that is real but poorly documented creates the same diligence friction as an add-back that is questionable.
Margin sustainability. Can the current margins be maintained post-transaction? Are they dependent on cost reductions that have already been fully captured? Are they being supported by one-time factors that will not recur? The diligence team will model margin scenarios. If the supporting data does not enable clean scenario analysis, the buyer defaults to conservative assumptions.
Customer and revenue trends. Is the growth trajectory real? Is it accelerating or decelerating? What does the cohort data show? Revenue trend analysis requires consistent data over 24-36 months. If the methodology changed partway through, or if the data requires manual reconstruction, the trend analysis is unreliable and the buyer adjusts for the uncertainty.
Why these flags are fixable
The encouraging reality is that most diligence red flags are not fundamental business problems. They are data and documentation problems.
The revenue discrepancy between the CIM and the financials is a timing adjustment that was not disclosed. The fix is disclosure and documentation. The customer retention definitional gap is a methodology mismatch. The fix is using the buyer’s standard methodology and providing a reconciliation. The EBITDA add-back without supporting documentation is a legitimate expense that was not properly recorded. The fix is creating the supporting schedule.
None of these fixes require changing the underlying business. They require investing in the data infrastructure that makes the business legible to a buyer.
This is the distinction that matters. Diligence red flags are not business problems. They are communication problems. They are the gap between what the company knows about itself and what the company can prove to someone who has never seen the business before.
The 48-hour test
There is a simple test that predicts how diligence will go.
Ask your finance team this question. “Can you show me MRR by customer segment, reconciled to the general ledger, for the last 36 months?”
48 hours means you are ready. The data exists, it is organized, and the team can produce it quickly. Diligence will be smooth. Buyer confidence will be high.
“Give me a week” means you are not ready. The data exists but requires manual assembly. The team can produce it, but the process will be slow enough that every follow-up question from the buyer creates a bottleneck.
“Depends which system” means you have a real problem. The data exists in multiple versions that do not agree. The team does not know which version is authoritative. The reconciliation that should take 48 hours will take weeks and may not produce a definitive answer.
Most mid-market companies fall into the second or third category. Not because the management team is incompetent. Because nobody invested in making the data ready for the question.
The timing problem
The worst time to discover you have a diligence red flag is during diligence.
When the buyer’s team flags an inconsistency, the seller has limited time to respond. The management team is simultaneously running the business, supporting diligence, and managing the emotional dynamics of a transaction. Adding a data reconciliation project to that workload is the worst possible timing.
The right time to discover your red flags is nine to twelve months before the exit process begins. At that point, the company has time to investigate, fix, and document. The CFO is not under transaction pressure. The data team can do the work properly rather than rushing.
The even better time is in the first 100 days after acquisition. Companies that establish data infrastructure early build the foundation that prevents red flags from accumulating. The data is reconciled continuously, not in a pre-exit sprint. The definitions are agreed upon when the systems are implemented, not when the buyer asks why they differ. The EBITDA adjustments are documented as they occur, not reconstructed from memory three years later.
The seller’s diligence
The firms that exit cleanly and at premium multiples are increasingly running their own diligence before going to market.
This is not a legal diligence or a financial audit. It is a data diligence that asks the same questions a buyer would ask and tests whether the company can answer them quickly, consistently, and defensibly.
Can we reconcile revenue across all systems within 48 hours? Can we produce customer cohort analysis going back 36 months? Can we document every EBITDA adjustment with supporting evidence? Can we separate organic growth from acquired growth at the entity level?
The companies that can answer yes to these questions go to market with confidence. The data room tells a consistent story. The buyer’s diligence confirms rather than challenges. The process moves at the buyer’s speed rather than the seller’s.
The companies that cannot answer yes have a window to fix it. But only if they ask the questions early enough.
Inflated seller expectations is the number one deal obstacle. Diligence red flags is number two. Both are symptoms of the same root cause. The company cannot prove what it claims to be worth. The first is about the number. The second is about the evidence. Fix the evidence and you do not just prevent the red flags. You earn the right to the expectations.