Off-the-shelf software is rarely expensive to buy. It gets expensive to use.

The price of an off-the-shelf solution is clear: a license per user, the rollout, maybe a maintenance contract. It's on the quote, so it gets compared, negotiated and budgeted.

What the quote leaves out are the costs that come afterward. You only see them once you've worked with the software for a while — and by then, they no longer feel like costs. They're just how things are.

You notice it in small things. A colleague keeps a spreadsheet on the side because the system can't handle a certain case. An order is entered twice because two tools don't talk to each other. A process that could take three steps takes seven, because that's what the software dictates.

Each of these seems harmless on its own. Together, they're a tax your business pays day after day. A quick calculation: if five employees each spend half an hour a day on workarounds, that adds up to about 550 hours a year over 220 working days. Then there are the errors where the pieces meet: the record that's up to date in the spreadsheet but not in the system, the call back to the customer because two versions don't match.

And often it's not just the cost. Whatever makes the workaround necessary usually can't be changed in an off-the-shelf product. You depend on what the vendor anticipated, and the vendor didn't anticipate your case. So the workaround isn't temporary. It's permanent.

The second kind of cost is more visible but rarely budgeted up front: customization. To make off-the-shelf software fit your business, you need customizing, and for that you need consultants who know that particular product. Every customization has to keep working after the next update. Companies that customize heavily start postponing updates — and eventually end up with a version nobody wants to touch.

With larger systems, the rollout alone takes months or years. During that time, the software doesn't adapt to the company; the company adapts to the software. Processes that worked well get rebuilt because the tool expects them to work differently. And a few years later, the next migration is due, because the vendor discontinues the version or the company has outgrown it.

These costs are invisible, so they're rarely weighed against the seemingly low purchase price. An honest comparison doesn't start with the quote. It starts with everyday work. Ask three employees which lists they keep outside the system, which data they enter twice and which steps they consider pointless. Estimate how much time that costs per week. And ask which customizations caused problems during the last few updates.

Add it all up and the picture often shifts considerably. What looked inexpensive at purchase turns out to be the more expensive option over the years. And what seemed expensive at first, because it's built to fit, turns out to cost less in the end.

That doesn't mean off-the-shelf software is wrong. For a standard problem, it's exactly right — nobody should build their own accounting or payroll software. But the better question isn't “What does the solution cost?” It's “What does it cost to work without the right solution?”