A business owner I worked with — let's call him Diego, since that's not his real name — told me something that stuck with me: "We bought the software. We just don't really use it the way it's supposed to be used." He said it almost apologetically, like it was his team's fault for not adapting. It wasn't. Six months after rolling out a tool meant to replace their order-tracking spreadsheet, half his team was still keeping a spreadsheet. Not instead of the new system — next to it. Quietly. Because the new system didn't handle the one exception that happened on every single order: partial shipments from two different warehouses, split across two invoices, something their actual business did every day and the software had never heard of.
That shadow spreadsheet is the most honest feedback a business ever gets about the software it bought.
The tell is always a workaround, not a complaint
Nobody files a complaint when software doesn't fit. They just quietly build a workaround and keep going, because complaining takes longer than coping. That's why the real signal is never a support ticket — it's a side spreadsheet nobody officially asked for, a notebook next to the keyboard, or the phrase I hear constantly in these conversations: "oh, we just don't use that part of it."
If you hear that phrase about a feature that's supposed to be central to how your team works, that's not your team being lazy. That's your team telling you, politely, that the tool doesn't match the job.
Off-the-shelf software is built for an average business, and yours isn't average
This isn't a knock on the software itself. Most off-the-shelf tools are well built — for the business they were designed around, which is an average of thousands of businesses that all do roughly the same thing, roughly the same way. Yours doesn't do it roughly the same way. You have the one supplier who always ships late and needs a different follow-up. The one customer category with its own pricing logic. The one approval step that exists because of something that went wrong three years ago, and everyone just quietly keeps doing it.
Generic software handles the 80 percent every business shares. Your business lives in the 20 percent it doesn't, and that 20 percent is usually where the actual work — and the actual risk — sits.
The point where the workaround costs more than the fix
Workarounds aren't free, even though they feel free because nobody's writing a check for them directly. Every time someone keeps a shadow spreadsheet, they're doing the job twice: once in the system you paid for, once in the thing that actually works. Every manual reconciliation between the two is time, and every time the two disagree, someone has to figure out which one is right.
For a while, that's a reasonable price to pay — cheaper than building something custom, certainly cheaper than switching tools and retraining everyone. But past a certain point, usually once the workaround has outlived "temporary" by a year or two, the math flips. The hours spent working around the tool, every week, forever, start costing more than the one-time cost of building the specific piece that doesn't fit. I've seen teams spend four or five hours a week reconciling two systems that should have been one — that's not a rounding error, that's a part-time job nobody budgeted for, repeated every single week for years.
You don't have to throw out what you bought
This is the part people get wrong most often: fixing this doesn't mean ripping out the software you already paid for and committing to a bigger platform migration. In most of the cases I've worked on, the off-the-shelf tool is doing 80 percent of its job fine. The fix is narrower — building the one piece custom, the specific workflow the generic tool never handled, and connecting it back into the system you already have.
I did exactly this kind of work for a client running an art gallery: their point-of-sale and inventory tool handled regular retail sales well, but had no concept of artist consignment — tracking which piece belonged to which artist, what percentage they were owed, what had sold and what hadn't. Rather than replace the whole system, we built that one piece as its own tool, wired into the records they already kept. The spreadsheet that used to sit next to the real system disappeared, because the real system finally covered the part that mattered.
The fit matters more than the brand
A tool with the right features on paper can still be the wrong tool in practice, if the 20 percent it doesn't cover happens to be the 20 percent your business actually runs on. The spreadsheet sitting quietly next to your "real" system isn't a sign your team needs more training. It's a sign worth taking seriously, because it's telling you exactly where the gap is — and exactly where a small, targeted piece of custom work would pay for itself.
If your team has a side spreadsheet, a backup notebook, or a part of your paid software that "we just don't use," that's not a small annoyance to live with. That's a map someone already drew for you, for free.