A company we spoke to had two systems for the same job. One cost a serious amount of money a year and appeared in the budget. The other was a spreadsheet on someone's laptop, cost nothing, and was where the work actually happened.
Ask which one was expensive and most people point at the invoice. It is the wrong answer, and getting it wrong is how firms end up buying a second thing that does not get used either.
The number that shows up, and the number that does not
Software has a price, and it goes in a spreadsheet somewhere with a renewal date next to it. That number is visible, comparable, and easy to argue about. It is also usually the smaller one.
The other number is what your team spends getting the work done despite the tool. It has no line item. It looks like a person who "just handles that one", a report someone rebuilds by hand every Monday, an export into a spreadsheet because the built-in view cannot answer the question anybody actually asks. None of that is in the comparison when the decision is made, because none of it existed yet.
Nobody budgets for the workaround, because the workaround is invented after the purchase.
So the comparison that gets made is licence against licence, and the comparison that matters is licence plus workaround against licence plus workaround. The second one is harder, and it is the only one that predicts what happens.
"Too expensive" is a fair question with a missing half
When somebody says a piece of work is too expensive, the honest response is not to defend the price. It is to ask: compared to what?
Sometimes the answer is a cheaper supplier, and that is a real comparison worth having. More often the answer is compared to carrying on as we are — and carrying on as you are has a cost that nobody has counted, because it is spread across a dozen people in small daily amounts nobody logs.
Twenty minutes a day of manual re-entry is two and a half weeks a year, from one person. It never appears anywhere. It is not that firms are careless about this; it is that the cost arrives in a currency the budget does not track.
Three signs you are paying the second number already
You do not need an audit for this. The evidence is usually sitting in plain view.
A shadow spreadsheet. If a team keeps its own file beside the official system, that file is a specification. It describes exactly the gap between what was bought and what the work requires, written by the people who do the work, for free. It is the most useful document in the building and nobody filed it — and it is usually the thing that settles whether to buy, build or integrate.
A person who is the integration. Somebody copies from one system into another, or reconciles two reports that should agree. They are load-bearing, they are usually good at it, and they are the reason nobody has noticed the systems do not talk.
A report rebuilt by hand. The tool produces a report. Someone exports it and rebuilds it, every time, because the built-in version answers a question nobody asked. That rebuild is the requirement.
None of these are failures of discipline. They are a team routing around an obstacle so the work still gets done, which is what competent people do. The obstacle is the point.
The objection that has weight
Here is the fair counter, and it is a good one: this reasoning can justify almost any purchase. Every vendor on earth is happy to tell you that your current system has hidden costs and theirs does not. "You are already paying for this in lost time" is the oldest line in enterprise sales, and it is usually said by somebody who has never watched your team work.
That objection holds, and it is why the argument only means something with a number attached to your situation rather than an industry average. It is also why the assessment comes first and why we will not quote before one: a claim about your hidden costs, made by somebody who has not watched your process, is a guess wearing a suit.
The test is whether anybody can name the workaround specifically. "Teams like yours are losing hours every week" is marketing. "Every Monday, Priya rebuilds the allocations report because the system reports by site and you plan by crew" is a finding. One of those you can act on.
What actually makes the second number go away
Not, usually, a better tool. The uncomfortable pattern is that replacing software often moves the workaround rather than removing it: the new system has different gaps, the team invents different spreadsheets, and eighteen months later the same conversation happens about a different invoice.
What removes it is fixing the specific mismatch the workaround is compensating for. Sometimes that is new software. Often it is a change to the existing system, an integration between two things that already work, or a process that stops needing the reconciliation in the first place. Sometimes (and this is the version nobody sells) it is deciding the current cost is acceptable and spending the money somewhere it buys more.
That last option is real. Not every workaround is worth removing. A cost you have measured and chosen to keep is a decision; the same cost unexamined is a leak.
Questions people ask
How do I estimate what the workaround is costing?
Ask the people doing it, in specifics rather than percentages: what do you do every week that the system should do, and how long does it take? You are looking for named tasks and rough durations, not a productivity study. Three or four honest answers usually make the size of it obvious.
Is the answer always to replace the tool?
No, and it often is not. Replacing software frequently relocates the workaround instead of removing it. What matters is the specific mismatch the workaround exists to bridge — the fix might be an integration, a process change, or a change to what you already run.
What if the current system is genuinely fine?
Then you have learned that cheaply, and you should spend the money elsewhere. A cost you have measured and decided to accept is a decision. That is a perfectly good outcome of asking the question, and we would rather tell you that than build something.
What to do differently
Before comparing prices, write down what your team does because the current system cannot. One line each, with a rough time on it. That list is both your requirements document and your cost of doing nothing, and it takes an afternoon to produce.
Then ask whoever is selling you the replacement to tell you which lines on that list they remove. The ones they cannot answer are the ones you will still be paying for next year.