§ Guide

Software Debt: The Invisible Tax on Mid-Size Industrial Ops

Why your team is stitching together six tools, three spreadsheets, and one heroic operator—and how to surface the cost before it shows up as turnover or margin loss.

Short answer: software debt is the tax your team pays—every week, in hours—because the tools don't fit the work. It's invisible on the P&L until it shows up as the twenty-year operator who finally quits.

What it actually looks like

Software debt rarely looks like bad software. It looks like six tools pretending to be one: the ERP for records, a spreadsheet for the stuff the ERP doesn't handle, email for approvals, a shared drive for drawings, a paper form for the shop floor, and one heroic operator who keeps it stitched together in her head.

Every day you operate that stack, you pay a little tax. Re-keying. Second-guessing the number on the screen. Waiting for the one person who knows where the spec actually lives. None of it shows up on an invoice. All of it shows up as fatigue.

Three places it hides

Onboarding time — a new hire can't build a quote without a veteran on standby for two weeks. The knowledge lives in someone's head, not in the system.
Shift-change friction — every handoff costs 10–20 minutes because the receiving shift has to reconstruct what happened from email threads.
The “ask the veteran” pattern — if your best answer to “how do we do X?” is a person's name, you have software debt there.

How to measure it

Don't start with tools. Start with roles. Interview the five people closest to the friction for fifteen minutes each and ask three questions:

What task do you do every single day that nobody upstairs seems to notice?
Which system fights you?
What would you stop doing if you could?

Their answers stack-rank faster than any audit. This is the same method CIRQL uses in the first week of every engagement—see the field diagnostic.

How to pay it down

One tool replaces two. Don't add a seventh system to the stack; collapse two into one that covers the workflow.
Custom where it pays, standard where it doesn't. Accounting and inventory can be commodity software; your quoting and fulfillment workflows probably can't.
Own the code. If the fix is custom, make sure your business still runs when the vendor doesn't.