The Cost of "Good Enough" Software

“Good enough” is the most expensive phrase in business software. It’s how teams justify keeping tools that don’t quite fit. It’s how procurement closes a deal on a product that’s almost right. It’s how the same friction year after year becomes invisible — not because it stopped costing, but because it stopped being measured.

Good-enough software has a compounding cost. Every quarter you keep it, the cost grows, and the cost of replacing it grows too. The math is rarely on the side of staying.

Three compounding costs

Compounding labor. Each workaround built around a not-quite-fitting tool requires maintenance. The spreadsheet that bridges two systems needs updating when either system changes. The Slack channel where deal context lives needs to be searched, summarized, re-summarized for new team members. New hires inherit the workarounds as if they were normal. The labor cost grows with team size.

Compounding institutional knowledge. As people leave, the knowledge of “why we do it this way” leaves with them. The replacement doesn’t know which workaround exists for what reason. They re-invent the wheel, introduce subtle errors, or propose tearing it all out without understanding what’s there. Either way, the cost of the not-quite-fitting tool grows every time someone new joins.

Compounding switching cost. Each year you keep the tool, you encode more processes around it. The replacement project gets bigger, not smaller. By year three, “we should replace this” has become a multi-quarter project nobody wants to start.

The hidden balance sheet

A simple way to see good-enough cost: imagine you had to write a check today for everything you’ve spent on the tool over its lifetime. Not just license fees. Include:

• Every hour your team has spent on workarounds
• Every error caused by gaps the tool doesn’t handle
• Every training session new hires have needed to learn the workarounds
• Every integration paid for to make the tool talk to the rest of the stack
• Every consultant or implementation partner involved

The number is rarely small. It’s also rarely tracked. That’s the problem — good-enough cost lives in lots of small places, so it never gets totalled.

When good enough becomes too expensive

There’s a specific threshold where good-enough crosses into wasteful. It’s when the three-year total cost of keeping the tool exceeds the three-year total cost of replacing it with something that fits.

That threshold used to be high, because custom software was expensive. (See Why Custom Software Is No Longer Just for Enterprise.) Now it’s lower than most teams realize. The math has shifted enough that workflows that didn’t qualify for replacement two years ago do now.

The honest question

Look at your stack. Pick the tool you’re most likely to defend as “good enough.” Now ask:

• If we were starting today, would we pick this tool?
• How many workarounds exist around it?
• What does it cost us over three years if we change nothing?

If the answer to the first question is no, you’ve already made the build-vs-stay decision. The team just hasn’t acknowledged it yet. (For how to act on that acknowledgment, see When Off-the-Shelf Software Stops Fitting Your Business.)