The FNDRS Elements™Element 24Risk

Tech Debt

Tech debt, the accumulated cost of technology that has not kept up, lowers the offer because a buyer treats it as a bill they will pay after closing and subtracts it. It covers aging servers, unsupported software, custom code only one person understands, and spreadsheets doing the job of systems.

Family
Risk
Position
H4
Scored
Control: higher is safer
Table 1. Entry 24 in the Exit Elements™ specification, version 1.4.
SymbolTdNumber24FamilyTd RiskPositionH4
Scored asControl: higher is saferCompoundsNoneWorked inBuildPillarDeal readiness

§1 Definition

What is tech debt?

Tech Debt is the accumulated cost of technology that has not kept up: aging servers, unsupported software, custom code only one person understands, spreadsheets doing the job of systems, and security or data gaps. A buyer treats it as a bill they will have to pay after closing and subtracts it from what they offer. It is scored as control, so a high score means the debt is low and the systems are sound.

Aging systems, custom code, and unsupported tools a buyer would have to replace. Scored as control: higher is safer.

A manufacturer running its shop floor on a 15-year-old ERP with no vendor support, or a services firm whose billing depends on a spreadsheet macro written by a former employee, carries Tech Debt whether or not it is visible on the balance sheet.

Use cases

Inventorying every system with its age, owner, and support status, replacing or documenting anything that depends on one person, closing basic security gaps such as backups and access control, and estimating the remediation cost yourself before a buyer does.

The risk family

Exposures that cause a buyer to discount the multiple or walk away. Risk elements are scored as control: a higher score means the risk is contained.

The discount. Buyers subtract for owner dependence, documentation, concentration, key people, compliance, and tech debt, each scored as control, so a higher score is safer.

Meet the family

§2 Measurement

How is tech debt measured?

Age and support status of core systems, share of custom code without documentation or maintainers, known security or data gaps, and the estimated cost for a buyer to remediate.

Figure 1. Sample assay for Acme Industrial: tech debt scores 40 today (leaking value) against a target of 70 (developing). Sample scores, not a client. Your own assay comes from the exit score and the valuation.

How the scale reads

  1. Every element is scored from 0 to 100 against what a sophisticated buyer expects at close.
  2. Risk elements are scored as control: higher is safer.Applies here
  3. Inputs are recorded, not targeted.
  4. Outcomes are derived from their feeding families.
feedsdiscountsTdTech DebtRisk6 elementsEvEnterprise Value
Figure 2. Reaction pathway for Td: element, family, outcome. The risk family discounts the multiple.

§3 Pathway

The path from tech debt to enterprise value

Every element feeds a family, and every family feeds an outcome. The chain below is the route this element's score takes into the number a buyer pays.

Figure 3. Tech Debt at H4 in the standard table: column H, row 4. Columns group the families; the wealth series runs beneath.

§4 Position

The risk series

6 elements share the family. Read them together: a buyer prices them as a group.

  1. Od19 · Owner DependenceG2
  2. Dd20 · Documentation DebtH2
  3. Cc21 · Customer ConcentrationG3
  4. Kp22 · Key-Person RiskH3
  5. Lc23 · Legal & ComplianceG4
  6. Td24 · Tech DebtH4

§5 Compounds

Tech Debt stands alone

This element is not part of a named compound. It is priced on its own, through the family it belongs to.

§6 In the FNDRS journey

Where tech debt gets worked

The assay scores it. The process, the pillars, and the platform move it. Table 2 lists every place this element is on the agenda.

Table 2. Where element 24 appears in the FNDRS journey.
WhereWhat happensAlongsideGo
StageBuildBuild the right foundation. Establish a company capable of becoming valuable rather than merely producing founder income. Baseline valuation, health check, constraint inventory, and the first roadmap.TmTlCpDmCfPdOdDdKpLcAc
Pillar of valueDeal readinessPreparation is leverage. A company that can answer a buyer's first twenty questions on day one closes faster, at the agreed price, with nothing surfacing in diligence that was not already disclosed.DrLcScEvOp
trackTechnology auditThe whole footprint and topology, mappedIpDd
trackTechnology overhaulA plan for custom software, AI automation, and integrationsTaIpOe
The elementTech DebtBuyers and diligencedeal structurePrice and proceedsset at the table
Figure 4. The route tech debt takes: buyers, diligence, and the deal itself set its effect; the FNDRS valuation does not compute it.

§7 In the valuation

How does tech debt affect a sale?

Priced by buyers Not modeled

Buyers price it as a bill they will pay after closing.

The FNDRS valuation does not compute this element, either by design or because it is not yet measured. Its effect shows up in what a buyer will pay, in diligence, or in the structure of the deal and the proceeds.

What FNDRS reads

Not measured by the valuation today. The capital-expenditure question covers physical assets only.

How the table meets the number

Find out how tech debt scores in your business

The exit score is the first assay: fifteen minutes, six pillars, and a first read on the elements that matter most.