# Technology Due Diligence for M&A: What Acquirers Actually Need to Know

A field guide to technology due diligence in acquisitions: architecture, code, security, team, licensing, and the findings that change deal terms.

Technology due diligence is the investigation of a target company's technology — its architecture, code, security posture, data, intellectual property, team, and operations — conducted before an acquisition closes. Deals die on technology findings more often than deal teams expect: the platform that cannot scale to the acquirer's volume, the codebase held together by two engineers who are about to leave, the open-source license violation that taints the core product, the security posture that would fail the acquirer's own standards on day one. Financial diligence tells you what the company earned; technology diligence tells you what you are actually buying and what it will cost to own.

This guide is written for acquirers, their advisors, and the target-side teams preparing for scrutiny. It covers each diligence workstream, what to look for, how findings translate into deal terms, and how to plan the post-merger integration reality. It assumes a technology or technology-enabled target; a pure brick-and-mortar acquisition needs a lighter touch, but the security, data, and IP workstreams still apply.

## Why technology diligence changes deals

Technology findings change deals in three ways. First, they **reprice**: discovering that the platform needs a full rebuild within two years, or that infrastructure costs will triple under the acquirer's load, changes what the asset is worth. Second, they **restructure**: key-person risk becomes retention agreements; security gaps become pre-close remediation commitments or post-close escrows; IP problems become representations, warranties, and indemnities with real teeth. Third, they occasionally **kill**: not usually from one catastrophic finding, but from the accumulation — the architecture is fragile, the team is flight-prone, the security posture is years behind, and the integration cost exceeds the strategic value.

The findings that move price are rarely the ones in the pitch deck. Founders present architecture diagrams; diligence reads the code, the incident history, and the infrastructure bill.

One structural note: diligence quality depends on access. Negotiate deep technical access early — repository access, architecture documentation, incident histories, infrastructure bills, and interviews with working engineers, not just the CTO. A target that resists technical access is itself a finding.

## Architecture assessment

Architecture diligence answers one question: **can this system do what the investment thesis needs it to do?** If the thesis is "acquire the customer base and migrate them to our platform," the target's architecture matters less than its data model. If the thesis is "acquire the platform and scale it tenfold," architecture is the whole bet.

Assess against the intended future, not the present. A system handling its current load comfortably may collapse at the acquirer's volumes. Key areas:

- **Scalability profile.** Where are the bottlenecks? Single-database architectures, synchronous call chains, unpartitioned data, missing caching layers — identify what breaks first as load grows and what it costs to fix. Ask for load test results; if none exist, that is a finding.
- **Coupling and modularity.** How entangled are the components? A modular system can be integrated, replaced, or scaled piece by piece; a monolith with deep coupling must be absorbed whole. Map the dependency graph between services, and between the target's systems and third-party services.
- **Single points of failure.** Identify them at every layer: the one database with no replica, the one engineer who understands the billing system, the one vendor whose outage would halt operations, the one data center or region everything runs in.
- **Technology stack coherence.** A stack assembled from five frameworks across three eras suggests accreted development without architectural governance. It is not disqualifying, but it predicts integration cost and hiring difficulty.
- **Integration surface.** APIs, event streams, data exports — the seams where the acquirer's systems will connect. Undocumented, inconsistent, or fragile integration surfaces are where post-merger timelines go to die. (For the acquirer-side view of connecting systems, see our [enterprise integration strategy guide](/guides/enterprise-integration-strategy-guide/).)

Produce an architecture risk register: each risk, its likelihood, its impact on the investment thesis, and a rough remediation cost. This register becomes an input to price negotiations and integration planning.

## Code and technical debt review

Nobody can read an entire codebase during diligence, and nobody needs to. The goal is a **representative sample** that reveals engineering discipline: the practices that produced the code predict the code you have not read.

Sample deliberately: the highest-revenue code paths (billing, checkout, core transactions), the most-changed modules (churn correlates with pain), the security-sensitive surfaces (authentication, authorization, payment handling), and a random selection to check whether quality is consistent or concentrated. For each sample, assess:

- **Readability and structure.** Could a competent new hire understand and safely modify this code? Naming, modularity, and separation of concerns are leading indicators of maintenance cost.
- **Test coverage — real coverage.** Not the percentage on a dashboard, but whether the tests cover the paths that matter and whether they actually run in CI. A suite that is red, skipped, or ignored is worse than no suite, because it signals that quality gates are decorative.
- **Dependency hygiene.** Outdated libraries, unmaintained dependencies, known-vulnerable versions. Generate a software bill of materials (SBOM) or equivalent and check it against vulnerability databases.
- **Technical debt markers.** TODO comments referencing years-old dates, disabled tests, copy-pasted modules, "temporary" workarounds that are load-bearing. Some debt is normal; debt with no repayment plan and no ownership is a liability.
- **Development practices.** Code review discipline, CI/CD maturity, deployment frequency, rollback capability, observability. The practices tell you how the team works; the code tells you what those practices produced.

Translate findings into economics: estimate the remediation investment required to bring the codebase to the acquirer's standards — typically expressed as engineering-years or as a percentage of the purchase price. A codebase needing a full rewrite is not necessarily a dealbreaker, but it must be priced as one.

## Security posture

Security diligence protects the acquirer from inheriting breaches, vulnerabilities, and practices that would fail its own standards. It has three inputs: **artifacts** (policies, audit reports, penetration test results, certifications), **evidence** (vulnerability scan results, access control configurations, incident history), and **practice** (how the team actually handles security day to day).

Cover at minimum:

- **Known vulnerabilities.** Scan the infrastructure and applications; review the patch cadence for critical vulnerabilities. A backlog of unpatched criticals is a finding about process, not just software.
- **Access control and identity.** Who has production access, how it is granted and revoked, whether secrets are managed or scattered, whether former employees retain access. Excessive standing access to production is one of the most common findings.
- **Data protection.** Encryption at rest and in transit, key management, PII handling, data retention and deletion practices. Map these against the regulatory regimes the combined company will face.
- **Incident history.** Every material incident in the last two to three years: what happened, how it was detected, how long it took to contain, what changed afterwards. A target with no incident history has either been lucky or is not detecting — ask which.
- **Third-party and supply-chain risk.** Vendor access to systems and data, dependency vulnerabilities, the blast radius if a key vendor is compromised. (Our [vendor security review guide](/guides/vendor-security-review-guide/) covers the assessment method in depth.)

Security findings map to deal terms more directly than most: specific vulnerabilities become pre-close remediation requirements; systemic gaps become post-close investment commitments; undisclosed incidents become warranty and indemnity issues. And note the acquirer's own exposure: on day one, the target's security posture becomes the acquirer's headline risk.

## Data and intellectual property

For many acquisitions, data and IP are the actual assets being purchased. Diligence must verify that the acquirer will own what it thinks it is buying.

- **IP ownership and chain of title.** Was the core IP developed by employees under proper assignment agreements? Contractor-developed code without IP assignment is a classic finding — the company may not own its own product. Review employment and contractor agreements for the key creators.
- **Open-source compliance.** Inventory open-source components and their licenses. Copyleft licenses (GPL and its variants) in distributed or SaaS products can create obligations to disclose source code — a finding that can reprice a deal or require expensive remediation. Permissive licenses are generally fine but still require attribution compliance. An SBOM with license analysis is the standard artifact; its absence is itself a finding.
- **Patent and trademark position.** What is owned, what is licensed, what is merely claimed. Verify that trademarks cover the marks that matter and that patent claims read on the actual product.
- **Data rights and privacy.** Does the target have the rights to use its data the way the investment thesis requires? Customer contracts, terms of service, and privacy policies may restrict data use, combination with the acquirer's data, or cross-border transfer. Privacy diligence is especially critical where the thesis involves merging customer datasets.
- **Litigation and claims.** Pending or threatened IP litigation, cease-and-desist history, employee IP disputes. Even meritless claims cost money and management attention post-close.

IP findings are legal-diligence territory, but technology diligence supplies the technical facts — what code exists, where it came from, what licenses govern it — that legal analysis depends on.

## Team and organization

In technology acquisitions, the team is often a large part of the purchase price — sometimes explicitly, in acqui-hires. Even when it is not, the acquirer needs the target's engineers to keep the systems running and execute the integration.

- **Key-person risk.** Identify the engineers without whom critical systems cannot be operated or changed. Interview them. Understand their motivations and flight risk — acquisition announcements trigger departures, and the people most able to leave are usually the ones you most need to stay.
- **Retention planning.** Which roles are critical for the first twelve to twenty-four months, and what retention instruments (stay bonuses, equity, role guarantees) will keep them? Price retention into the deal economics; it is not free.
- **Organizational health.** Team structure, reporting lines, decision-making culture, remote versus colocated norms. A team that ships through informal hallway coordination will struggle inside a process-heavy acquirer, and vice versa.
- **Hiring and attrition data.** Offer acceptance rates, regretted attrition, time-to-fill for key roles. These predict whether the team can grow to meet the integration plan.
- **Compensation alignment.** Gaps between target and acquirer compensation bands create immediate retention risk on close. Map them early.

Treat the "people findings" with the same rigor as technical findings: named risks, mitigations, costs. "The team seems good" is not diligence.

## Infrastructure and operations costs

Read the bills. Infrastructure diligence verifies the **run-rate cost** of the target's operations and how it changes under the acquirer's plans:

- **Current infrastructure spend**, broken down by compute, storage, data transfer, and managed services. Unexplained growth trends are a finding.
- **Cost efficiency.** Over-provisioned resources, unused reservations, missing cost controls — the standard cloud waste review. (The method is the same as any cloud cost assessment; what matters here is the forward number.)
- **Cost at acquirer scale.** Model infrastructure cost under the combined company's volume. Architectures that are cheap at startup scale can be brutally expensive at enterprise scale — per-transaction managed-service costs, data egress, and unpartitioned databases are the usual culprits.
- **Operational maturity.** On-call practices, incident response, deployment safety, disaster recovery posture, backup testing. You are inheriting the operations, not just the code.
- **Vendor contracts.** Terms, renewal dates, termination rights, change-of-control clauses — some vendor contracts allow termination or repricing on acquisition, which can be either a cost or a savings.

The output is a forward operating cost model: what it costs to run the target's technology for the next three years under the integration plan, including remediation investment. This number belongs in the deal model.

## Integration planning: the post-merger reality

Most technology diligence stops at "what are we buying" and never reaches "what will it take to combine." The integration plan is where acquisition value is created or destroyed, and diligence should produce its first draft:

- **Integration thesis.** Which systems survive, which are retired, which are merged — and in what sequence. Every "migrate the customers to our platform" thesis needs a data-migration plan with a realistic timeline; every "keep both platforms" thesis needs an integration-layer plan with a realistic cost.
- **Identity and access.** Unifying identity is usually the first technical integration and the prerequisite for everything else. Plan it early.
- **Data integration.** Combining customer, product, and operational data across different models is consistently underestimated. Budget for data mapping, cleansing, and dual-running.
- **Timeline realism.** Integration timelines in deal models are almost always optimistic. Diligence should produce an independent estimate grounded in the architecture findings — the coupling, the data model differences, the team capacity — not in the synergy presentation.
- **Interim operating model.** Who runs the target's systems between close and integration, under whose standards, with what incident escalation? The gap between close and integration complete is where operational risk concentrates.

If the target's systems resemble the legacy estates acquirers often inherit, our [legacy modernization playbook](/guides/legacy-modernization-playbook/) covers the assessment and sequencing discipline that applies equally to post-merger platform consolidation.

## How findings translate to deal terms

Technology findings are only useful if they change the deal. The translation mechanisms:

- **Purchase price adjustments.** Quantified remediation costs — the rebuild, the security program, the infrastructure uplift — reduce what the asset is worth. Bring engineering-year estimates and vendor quotes, not adjectives.
- **Escrows and holdbacks.** A portion of consideration held back against specific technology risks: unresolved IP questions, security remediation milestones, key-person retention periods.
- **Pre-close remediation.** Specific fixes the target must complete before close — critical vulnerability remediation, IP assignment cleanup, access revocation. Define acceptance criteria, not just effort.
- **Representations, warranties, and indemnities.** The target warrants the state of its technology — IP ownership, license compliance, absence of undisclosed incidents — with indemnities sized to the risk. Technology diligence defines what is being warranted.
- **Retention and incentive structures.** Key-person risk becomes stay bonuses, earnouts tied to integration milestones, or role commitments.
- **Walk-away triggers.** Define in advance which findings kill the deal: GPL contamination of the core product with no remediation path, a material undisclosed breach, loss of the key technical team. Deciding the triggers before diligence prevents sunk-cost pressure from overriding judgment later.

Document every material finding with its evidence, its estimated cost or risk, and its proposed deal-term treatment. The diligence report is not an academic exercise — it is a negotiating instrument.

## Putting it into practice

Good technology diligence is fast, senior, evidence-driven, and honest about what it cannot verify.

If your organization is evaluating an acquisition — or preparing for one — independent technology diligence keeps the assessment honest and the findings actionable. Our [technology advisory engagements](/engagements/) include M&A technology diligence and post-merger integration planning, and our [capabilities](/capabilities/) cover enterprise architecture and technology strategy. To discuss an upcoming transaction, [contact us](/contact/).
