Technical debt
Definition
Technical debt is the accumulated cost of shortcuts in a codebase and its infrastructure, meaning the work that has to be done before the product can change without breaking. At $50k–$150k, buyers rarely walk away over it. They quantify it in developer days and take it off the price.
Technical debt is the accumulated cost of shortcuts in a codebase and its infrastructure, meaning the work that has to be done before the product can change without breaking. Every shipped product carries some. The question a buyer asks is how much, and whether it is the kind that compounds.
At a $50,000 to $150,000 deal, the buyer is often a solo operator or a small team who will maintain the code themselves. Architecture opinions barely feature. What they are working out is how many days of work stand between them and their first release, and what happens if something on the billing path fails at two in the morning while paying customers watch.
Debt that blocks change gets priced. Untidy code that runs quietly usually does not.
Where it bites
In technical diligence, where the specifics are predictable. Unsupported framework or language versions, dependencies with open security advisories, no test coverage on the billing path, manual deploys from one machine, and infrastructure configured by hand with no record of how. Any one of those is survivable. Together they turn a two week handover into a three month rebuild, and buyers who have been through that once never forget it.
Worked example
A SaaS at $3,500 MRR and $42,000 of trailing annual profit, on a framework version that went out of support two years ago, with no automated tests and deploys run from the founder's laptop. The buyer's developer scopes the upgrade at roughly 30 days of work. At contractor rates that is $18,000 to $24,000 of unavoidable spend before a single feature ships.
The offer arrives at 2.3× rather than 3×, about $97,000 against $126,000. The debt was not hidden. It was simply never repaid.
Technical debt is one of the few discount items a seller can remove on a known budget. Upgrade the runtime, put tests on anything that touches money, automate the deploy, and write down how the infrastructure is built. Doing that work yourself costs less than letting a buyer price it.
Related: stack-transfer, due-diligence, transferability
See what a business at this level is listed at.
Everything on sale between $50,000 and $150,000, on the same fields.