The FNDRS Elements™Element 24Risk
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.
| Symbol | Td | Number | 24 | Family | Td Risk | Position | H4 |
|---|---|---|---|---|---|---|---|
| Scored as | Control: higher is safer | Compounds | None | Worked in | Build | Pillar | Deal readiness |
§1 Definition
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
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.
How the scale reads
§3 Pathway
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.
§4 Position
6 elements share the family. Read them together: a buyer prices them as a group.
§5 Compounds
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
The assay scores it. The process, the pillars, and the platform move it. Table 2 lists every place this element is on the agenda.
| Where | What happens | Alongside | Go |
|---|---|---|---|
| StageBuild | Build 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 | The process |
| Pillar of valueDeal readiness | Preparation 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 | The pillar |
| trackTechnology audit | The whole footprint and topology, mapped | IpDd | |
| trackTechnology overhaul | A plan for custom software, AI automation, and integrations | TaIpOe |
§7 In the valuation
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.
The exit score is the first assay: fifteen minutes, six pillars, and a first read on the elements that matter most.