Tech debt in M&A due diligence: the acquirer's lens
Acquirer tech DD is a deep scan that lands on the deal team's desk with findings that feed the price and the purchase agreement. Sellers who understand the scoring rubric before the scan starts negotiate from a different position than sellers who do not.
The 90-Second Answer
No public source publishes a typical percentage that tech debt takes off a deal price. What a buyer does is estimate the bill it inherits: one-off remediation cost, plus any recurring extra running cost multiplied by the deal multiple. KPMG's 2025 Technology M&A Survey found most dealmakers see the risk (70% cite operational disruption, 60% cyberattacks) but fewer than a third treat it as a top pre-deal priority. Seller-side preparation, including in some cases a vendor-commissioned tech DD, puts the seller's own estimate of that bill on the table first.
The Acquirer's Job
What the buy-side tech DD is actually trying to answer
The buyer commissions tech DD to answer three questions in priority order. First, will the target's engineering organisation deliver the value-creation plan in the integration thesis? Second, what is the cost-of-cleanup that the acquirer will inherit on day one? Third, are there any deal-breaking risks that the financial DD cannot see? Most tech debt findings affect the first two; the third is rare but is what justifies the entire tech DD line item.
For strategic acquirers, the first question dominates. A strategic buyer is paying a premium for the target's product and customer base because they believe they can grow it inside their own platform. The DD partner's job is to assess whether the engineering organisation can execute the integration roadmap that justifies the premium. A target that looks attractive commercially but carries a debt burden that will absorb 12-18 months of engineering capacity before integration work can begin is materially less valuable to a strategic than to a financial sponsor.
For PE acquirers, the second question dominates. PE buyers operate the target standalone under the value-creation plan, so the tech DD focuses on whether the engineering opex line can be rationalised or improved. A target carrying significant debt is sometimes more attractive to PE than to a strategic, because the debt remediation becomes part of the value-creation story rather than an integration tax. The PE DD partner's language is rarely “deduct from EV” and more often “scope this into the 100-day plan”.
The Scoring Rubric
Four dimensions the DD partner scores
Each DD provider uses its own rubric, and the reports are confidential. The four dimensions below are a practical way for a seller to organise its preparation, because they map onto the questions every buyer asks. The right-hand column is what lets the buyer turn a finding into a number.
This is a preparation framework, not any one firm's scoring sheet. Survey figures on this page: KPMG, How AI can help reduce tech debt in M&A (2025 Technology M&A Survey), checked October 2026.
The Vendor DD Move
Commissioning your own tech DD before the buyer's
Sophisticated sellers in larger deals commission their own tech DD report before formal buy-side DD begins. This is the technology analogue of the vendor Quality of Earnings report familiar in financial DD. The vendor tech DD report is shared with serious bidders under NDA in the data room, and it materially shapes the buyer's DD scope.
The vendor DD has three benefits. First, the seller learns the findings before the buyer does, which gives time to remediate, reframe, or pre-disclose. Second, the buyer's DD partner often shortens scope when a credible vendor DD already exists, reducing the seller's time-tax during the DD window. Third, the vendor DD anchors the conversation: when the buyer's partner produces findings, the seller can compare against the vendor DD baseline and challenge any unexplained divergence. Fees are quoted per engagement and scale with company size and complexity. Compare the quote with your own estimate of the remediation bill a buyer could put on the table: on a $200M deal, a one-percentage-point price adjustment is $2M.
Vendor DD does not eliminate buy-side tech DD; nothing does. What it changes is the seller's position when findings emerge. A seller who can say “our own DD partner identified this six months ago and we have a remediation plan in flight” is in a different conversation than a seller who is hearing the finding for the first time from the buyer's deal team.
The Disclosure Schedule
What goes in the schedule, what stays out
The disclosure schedule attached to the purchase agreement is the formal mechanism by which the seller declares known issues. For tech debt findings, the schedule is the place to itemise material accumulated debt that the buyer is on notice of and which therefore cannot be the basis of a post-close indemnification claim. Effective disclosure scheduling around tech debt requires careful joint work between the engineering leader, the company's M&A counsel, and the CFO; the format is closer to an audit working paper than a product brief.
What goes in: material architectural decisions with known limitations (the monolith that needs decomposition, the database that is approaching scale ceiling, the dependency that is at end-of-life), material remediation plans currently in flight, and any known security or compliance debt that has not already been remediated. What stays out: opinion-level engineering judgements about code quality, general statements about “technical debt” without specifics, and any non-public engineering metrics that the seller would prefer not to be in the public record post-close.
The disclosure schedule is the seller's most important tool for managing tech debt findings in the deal. A thoroughly scheduled set of known issues converts those issues from indemnification exposure into known facts the buyer has accepted as part of the deal pricing. The seller's M&A counsel runs the schedule preparation; the engineering leader's job is to surface every material item and provide the dollar estimates the schedule entries are anchored to.
The Integration Question
Strategic acquirers ask differently
Strategic acquirers have an additional question PE buyers do not: how does the target's stack integrate into ours? Tech debt becomes material if it prevents or delays the integration roadmap. A target whose authentication system is built on a legacy framework the acquirer no longer supports, for example, becomes a 6-12 month integration problem that the deal team factors into the EV-adjustment recommendation.
The seller's preparation for the integration question is twofold. First, document the current architecture in a way that maps to the acquirer's known stack patterns (acquirer-side teams typically share their target architecture diagrams with the seller during DD; the seller's job is to provide a mapping). Second, name the integration paths that are clearly feasible and the ones that are clearly not. Acknowledging an infeasible integration path early is more valuable to the deal than pretending all paths are equivalent.
For PE acquirers, the integration question is replaced by the 100-day plan question. The DD partner produces a list of operational improvements the management team is expected to deliver in the first 100 days post-close. Tech debt remediation often features on this list; the seller's engineering leader should be ready to discuss whether the proposed 100-day items are feasible at the assumed cost and timeline. Pushing back constructively against an unrealistic 100-day plan is better than agreeing to a plan that will fail in the first reporting cycle.
Cross-Reference
The acquirer pitch in the stakeholder stack
The acquirer pitch is the M&A-specific version of the broader external-stakeholder conversations. See the VC pitch page for the fundraising version, which has overlapping but distinct DD-bank content. The EV at exit page is the strategic frame the founder uses internally before the seller-side preparation begins; the late-stage framing covers the pre-IPO cleanup variant. For the public-company variant, see tech debt at the public company, which includes the carve-out scenario where a unit is divested from a public parent.
For the engineering-deep treatment of tech-DD partner methodology, including the per-codebase scoring patterns and the static analysis tooling the partners use, see the sister site technicaldebtcost.com. The CTO who will lead the DD calls should be conversant in both views.
Field Notes
Frequently asked questions
How much does tech debt typically reduce M&A valuation?+
No public dataset publishes a typical percentage: deal terms are confidential. The price effect is best modelled as the bill the buyer expects to inherit: the one-off remediation cost, plus any recurring extra running cost multiplied by the valuation multiple the deal is priced on. KPMG's 2025 Technology M&A Survey (135 US organisations, September 2025) found 70% of respondents believe unresolved tech debt can lead to operational disruptions, yet fewer than a third deem addressing it pre-deal of utmost importance.
What does a tech DD engineer actually look at?+
Architecture diagrams against current code, dependency manifests, the last 18 months of incident postmortems, the bus factor on key systems, the build and deployment cadence, the test coverage trajectory, the senior IC retention curve, and a sample of pull requests across the most-changed files. The scan runs inside the wider diligence window, so it is measured in weeks.
Should the seller commission a pre-emptive tech DD?+
For larger deals, often yes. A seller-commissioned vendor DD report (similar to a vendor-side QofE) gives the seller advance warning of findings and an opportunity to remediate or reframe before the buyer's DD partner produces a less favourable report. Fees are quoted per engagement and scale with codebase size and scope; firms do not publish list prices.
What is the difference between strategic and PE acquirer tech DD?+
Strategic acquirers focus on integration risk and whether the target's stack will plug into the acquirer's existing infrastructure. PE acquirers focus on standalone operational efficiency and whether the management team can execute a value-creation plan that includes engineering productivity gains. The DD questions differ accordingly.
How long does the tech DD window typically last?+
It runs inside the broader diligence timetable the parties agree, usually in parallel with commercial and financial DD, with findings consolidated into the main DD report at the close-of-DD checkpoint. The deal timetable, not the codebase, sets the length.
Can findings be remediated mid-deal?+
Rarely. The deal timeline does not accommodate substantive engineering work. What can be done is a credible remediation commitment from management, captured in the disclosure schedule or in the integration plan, which sometimes softens the EV adjustment the buyer would otherwise apply.
Adjacent Reading