Finding tech debt is half the work; converting it into a defensible price adjustment is the other half, and it's where buyers most often fumble. Present the finding too late, conflate deferred maintenance with normal upgrades, or fail to document it, and a legitimate $76,000 liability gets dismissed as a buyer chipping at the price. Done right — tiered, quantified with vendor quotes, and framed as deferred maintenance — the same finding is an evidence-backed retrade the seller can accept without feeling cheated.
§ 01 · The four urgency tiersAnd what belongs in the retrade.
| Tier | What it covers |
|---|---|
| Tier 1 — Day 1 | MFA, end-of-life hardware, license compliance |
| Tier 2 — First 90 days | AMS migration, VoIP, initial training |
| Tier 3 — First year | Full system utilization, workflow automation, software consolidation |
| Tier 4 — Ongoing | Normal operating cost — NOT included in the retrade |
Tiering by urgency does two things: it builds the buyer's post-close roadmap, and it disciplines the retrade. Tier 1 is the Day 1 requirements — MFA, end-of-life hardware, and license compliance — the items that can't wait. Tier 2 is the first 90 days — the AMS migration, the VoIP install, and initial training. Tier 3 is the first year — full system utilization, workflow automation, and software consolidation. Tier 4 is ongoing normal operating cost. The crucial discipline is the Tier 4 exclusion: only Tiers 1–3 belong in a retrade, because Tier 4 is normal capital expenditure that every agency carries, not deferred maintenance the seller let accumulate. A buyer who tries to retrade Tier 4 items hands the seller a fair reason to reject the whole adjustment.
§ 02 · The productivity-loss formulaThe cost the seller's number ignores.
The direct costs aren't the whole bill — the migration itself costs output. The formula: annual revenue × estimated productivity decline × (migration months ÷ 12). A $1.5M agency at a 15% decline over three months forgoes roughly $56,000 of output. That productivity loss is real money the seller's asking price never accounts for, and it belongs in the buyer's total alongside the direct vendor costs.
The productivity-loss formula captures the cost that hides behind the vendor invoices. A system migration doesn't just cost the migration fee — it costs the 10%–20% output drop while staff relearn workflows and clean dirty data, and that drop is quantifiable: annual revenue times the estimated decline percentage times the fraction of the year the migration spans. On a $1.5M agency, a 15% decline over three months is about $56,000 of forgone output — a number that often exceeds the direct vendor costs and that the seller's price never reflects. Adding it to the direct costs produces the real total: for a moderate 10-person agency, roughly $36,000 in direct costs plus $40,000 in productivity loss equals about $76,000 all-in. The full range runs from $5,000 for a turnkey operation (current cloud system, modern hardware, MFA already in place) up to $100,000+ for a severely outdated one.
§ 03 · Four retrade structuresHow the adjustment gets made.
Once quantified, the tech-debt total can be applied through four structures, each fitting a different deal dynamic. A direct price reduction is the cleanest — the headline number drops by the tech-debt total. A closing credit leaves the price nominal but credits the buyer cash at close, which can preserve a seller's reported headline figure. An escrow holdback sets the funds aside and releases them as the remediation is actually completed, which works when the cost is uncertain. And an adjusted earnout baseline bakes the remediation cost into the earnout's starting point, so the seller's earnout isn't credited for output the buyer's investment created. The structure choice follows the same logic as any other price-affecting finding — it's the operational counterpart to the risk adjustments that move the multiple, covered in risk-adjusted multiples. The tech-debt total is the input; the structure is how it reaches the price.
§ 04 · The four mistakes and the framingPresenting it so it lands.
Four mistakes sink an otherwise-valid retrade. Conflating tech debt with normal capital expenditure — retrading Tier 4 items — gives the seller a reason to reject everything. Presenting too late — raising it after the diligence-findings summary rather than as part of it — makes it look like a tactic rather than a finding. Failing to document — no vendor quotes, no line items — leaves the number arguable. And ignoring the seller's perspective — framing it as fault rather than fact — turns a negotiation into a fight. The framing that works is specific and neutral: a technology assessment identified a quantified investment to bring the infrastructure to the buyer's operating standard, itemized, requested as a price reduction or closing credit, and explicitly characterized as deferred maintenance rather than improvements. Presented that way — tiered, documented, timely, and framed as fact — the retrade reads as the fair adjustment it is, and the seller can accept it without feeling the deal was sprung on them. The audit that produces these numbers is in AMS due diligence.
◆
Terminology on this shelf
- Four urgency tiers
- Day 1, first 90 days, first year, and ongoing — only the first three belong in a retrade.
- Tier 4 exclusion
- Ongoing normal capital expenditure — excluded, because it isn't deferred maintenance.
- Productivity-loss formula
- Annual revenue × decline % × (migration months ÷ 12) — the cost the seller's price ignores.
- All-in total
- Direct costs plus productivity loss — ~$76K for a moderate 10-person agency.
- Four retrade structures
- Price reduction, closing credit, escrow holdback, or adjusted earnout baseline.
- The four mistakes
- Conflating with CapEx, presenting late, failing to document, ignoring the seller's view.