Blog→PE/VC

PE/VC8 min read

Calculating Technical Debt's EBITDA Impact in Private Equity Due Diligence

A financial framework for Private Equity operating partners to translate legacy code maintenance burdens directly into EBITDA compression forecasts.

By Richard Ewing·April 10, 2026

Share:

The Hidden Cost of Legacy Integration

During technical due diligence, evaluating software architecture is standard practice. However, translating those architectural findings into financial models is where most Private Equity firms fail. When a target company's engineering team spends 45% of their time keeping legacy systems running, that isn't just an engineering inefficiency—it is a direct drag on EBITDA margins.

Every dollar spent on maintenance is a dollar not spent on growth. If you are modeling a 3x enterprise value expansion based on aggressive feature shipping, but the target holds massive undocumented liabilities, those feature roadmaps will stall. This is why establishing core technical debt principles during the diligence phase is critical. It allows operating partners to quantify the exact CapEx required to refactor the platform before it scales.

Applying the Product Debt Index

Using the Product Debt Index (PDI) framework, PE firms can convert abstract engineering complaints into a concrete $M liability on the balance sheet, adjusting the purchase price or carving out specific remediation tranches.

Like this analysis?

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

Subscribe Free →

More in PE/VC

The Coordination Tax: Why Hiring More Engineers Destroys Gross Margin

We mask operational friction with cheap capital, answering every missed deadline by hiring more developers. Here is why that fails.

5 Red Flags PE Firms Miss in Technical Due Diligence

PE firms lose millions because their due diligence stops at revenue metrics. Here are the 5 engineering signals that predict failure.

The Post-Acquisition Engineering Playbook: Day 1-100

The first 100 days after acquisition determine engineering success or failure.

Canonical Frameworks

Cost of Predictivity

The Cost of Predictivity measures the variable cost of AI accuracy. Unlike traditional software with near-zero marginal costs, AI features have significant variable costs that scale with both usage AND accuracy requirements. As AI correctness increases, cost scales exponentially — not linearly. This is the fundamental economic challenge of AI products. Traditional software follows a simple cost model: high fixed development cost, near-zero marginal cost per user. Build the feature once, serve it to millions for pennies. AI products break this model entirely. Every AI query costs compute. Every inference requires GPU cycles. Every improvement in accuracy requires either more sophisticated prompts (more tokens = more cost), retrieval-augmented generation (vector DB queries + embedding generation), or fine-tuned models (massive training costs amortized over queries). The cost structure looks more like a manufacturing business than a software business. The exponential curve is the killer. Moving from 80% accuracy to 90% accuracy might cost 2x. Moving from 90% to 95% might cost 5x. Moving from 95% to 99% often costs 10-20x. This is because the easy cases are solved by the base model, and each additional percentage point of accuracy requires increasingly sophisticated (and expensive) techniques to handle edge cases. This creates what Richard Ewing calls the AI Margin Collapse Point: the usage volume at which AI feature costs exceed the revenue they generate. Many AI features that work beautifully in prototype (low volume, don't need high accuracy) become economically devastating in production (high volume, users demand high accuracy). The AI Unit Economics Benchmark (AUEB) calculator at richardewing.io/tools/aueb helps companies calculate their Cost of Predictivity and identify their specific margin collapse point before it hits their P&L.

Read Definition →

Feature Bloat Calculus

Feature Bloat Calculus is the economic formula for determining when a feature's maintenance cost exceeds its value contribution. It quantifies the hidden tax of feature accumulation — the compounding cost that makes every new feature harder and more expensive to build. The formula considers three cost components: 1. **Direct Maintenance Cost**: The engineering hours spent maintaining the feature (bug fixes, compatibility updates, dependency management, test maintenance). This is typically 2-5% of original development cost per quarter. 2. **Opportunity Cost**: What else could those maintenance engineers be building? If 3 engineers spend 20% of their time maintaining a low-value feature, that's 0.6 FTE that could be building high-value new capabilities. 3. **Complexity Tax**: This is the compounding factor that most organizations miss entirely. Every feature in the codebase makes every other feature harder to maintain and every new feature harder to build. Adding feature #101 to a system doesn't just add feature #101's maintenance cost — it increases the maintenance cost of features #1-100. The Complexity Tax follows a roughly quadratic curve. A system with 50 features has approximately 1,225 potential interaction points (n × (n-1) / 2). A system with 100 features has 4,950 potential interaction points. Doubling features doesn't double complexity — it quadruples it. Feature Bloat Calculus quantifies this by comparing a feature's total cost (direct + opportunity + complexity) against its value contribution (revenue attribution, user engagement, strategic importance). When total cost exceeds value, the feature has "negative carry" — it's costing more to keep than it's worth. Features with negative carry should be evaluated through the Kill Switch Protocol for potential deprecation. The highest-negative-carry features should be killed first, as they free up the most capacity per removal.

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