Blog→M&A
M&A14 min read

The Technology M&A Checklist: 50 Items Every Acquirer Needs

A comprehensive technical diligence checklist that prevents post-acquisition surprises.

By Richard Ewing·
Share:

The 50-Item Checklist

Organized in 5 categories: Architecture (10 items): scalability, modularity, dependency management, API design, database architecture, caching strategy, message queue design, service mesh, deployment architecture, monitoring stack.

Code Quality (10 items): test coverage, CI/CD maturity, documentation, code review practices, static analysis results, dependency freshness, security scan history, technical debt inventory, performance benchmarks, accessibility compliance.

Team (10 items): org structure, key person dependencies, tenure distribution, hiring pipeline, compensation benchmarks, remote/hybrid policy, engineering culture assessment, management layers, on-call practices, training investment.

Operations (10 items): uptime history, incident response, disaster recovery, backup verification, compliance status, vendor contracts, license audit, infrastructure costs, deployment frequency, change failure rate.

Economics (10 items): R&D as % of revenue, innovation ratio, cost per feature, technical debt exposure, AI unit economics, cloud optimization level, FinOps maturity, engineering efficiency trends, revenue per engineer, cost of delay.

Like this analysis?

Get the weekly engineering economics briefing — one email, every Monday.

Subscribe Free →

More in M&A

Why 60% of Technology M&A Integrations Fail

The three integration patterns and when each one leads to failure.

10 min

Technology Carve-Out Economics: The Hidden Costs of Separation

Carving out a technology business costs 2-5x what the financial models predict.

9 min

AI Due Diligence: What to Assess Before Acquiring an AI Company

AI startups have unique liabilities: model risk, data rights, and inference economics. Learn how to conduct technical due diligence effectively before you buy.

11 min

Canonical Frameworks

Innovation Tax

The Innovation Tax is the hidden cost of maintenance work that gets reported as innovation investment. It is OpEx masquerading as R&D investment, causing organizations to dramatically overestimate their effective engineering velocity and R&D productivity. Here's how it works: A VP of Engineering reports to the CEO that "65% of engineering time is spent on new features." The actual breakdown, when forensically audited, reveals that only 23% of engineering time produces genuine new capabilities. The remaining 42% is maintenance work embedded within feature sprints — bug fixes bundled into feature stories, infrastructure upgrades coded as dependencies, and refactoring disguised as feature prerequisites. This 42-point gap between reported and actual innovation investment is the Innovation Tax. It's not fraud — it's systematic self-deception enabled by the way agile teams organize work. When a sprint contains 10 stories and 4 of them are technical debt cleanup dressed as "tech stories" within a feature epic, the team genuinely believes they're spending 100% on features. The Innovation Tax is insidious because it compounds. As the maintenance burden grows quarter-over-quarter, the tax increases. But because teams don't measure it, CFOs and boards continue to believe R&D spending is generating proportional innovation output. By the time the gap becomes visible (missed deadlines, slow feature delivery, competitive lag), the organization is often approaching the Technical Insolvency Date. Benchmarks from Richard Ewing's audits show that most engineering organizations have an Innovation Tax between 30-50%. Organizations with Innovation Tax above 40% are in dangerous territory. Above 70% is terminal — the organization is approaching technical insolvency within 4-6 quarters.

Read Definition →

Kill Switch Protocol

The Kill Switch Protocol is a structured framework for identifying and deprecating "Zombie Features" — code that requires ongoing maintenance but generates zero incremental business value. Most software organizations have a dangerous bias: they add features but never remove them. Product teams celebrate launches. Nobody celebrates deletions. Over time, this creates what Richard Ewing calls "feature gravity" — a constantly growing codebase where 40-60% of the code serves no active users and generates no measurable revenue, yet still consumes engineering maintenance hours. Zombie features come in several varieties: - **Ghost Features**: features that were built, launched, and never adopted. They sit in the codebase, requiring maintenance, but have near-zero usage. - **Legacy Bridges**: compatibility layers, deprecated API versions, and backward-compatible code paths that serve a tiny percentage of users but add complexity to every future change. - **Vanity Features**: features built because a senior stakeholder wanted them, not because users needed them. Often protected by organizational politics rather than business merit. - **Abandoned Experiments**: A/B test variants that were never cleaned up, prototypes that became permanent, and "temporary" solutions that became load-bearing. The Kill Switch Protocol provides a systematic approach to identification, evaluation, and deprecation: 1. **Identify**: Flag features with less than 5% of peak usage, zero revenue attribution, or maintenance cost exceeding 10% of the feature's value contribution. 2. **Quantify**: Calculate the total cost of keeping each zombie alive (maintenance hours × fully-loaded engineer cost × opportunity cost multiplier). 3. **Assess Risk**: Evaluate deprecation risk — what breaks if this feature is removed? What customers are affected? 4. **Sunset Timeline**: Create a communication plan and graduated deprecation (warning → deprecation notice → feature flag → removal). 5. **Execute**: Remove the code with rollback capability. Monitor for unexpected breakage. The typical Kill Switch audit reveals that 30-50% of maintenance burden comes from zombie features. Removing them frees up 15-25% of engineering capacity for actual innovation.

Read Definition →
📊

Richard Ewing

The AI Economist — Quantifying engineering economics for technology leaders, PE firms, and boards.

Book Advisory →Curriculum →Free Tools →
← Back to Blog