Costing the option of doing nothing
Every business case compares products to each other. The comparison that matters is against changing nothing at all.
Selection processes compare candidates. What they rarely do is compare the winner against the baseline of carrying on exactly as now, which is always available, always free of implementation risk, and sometimes the correct answer.
Including it as a genuine option changes the quality of the decision, because it forces the benefit to be stated as a number rather than assumed. To see how a vendor frames attendance-tracking software in practice, employee attendance tracking software is useful as an example to translate into neutral requirements.
What doing nothing actually costs
- Time spent on the manual process, at real hourly cost, per month.
- Errors and rework — how often, and what each one costs to fix.
- Delay: revenue or decisions that arrive later than they could.
- Risk that is currently being carried: a compliance gap, a single spreadsheet only one person understands, a system that is no longer supported.
- Staff cost — whether the friction is a factor in anybody leaving.
Adding these up usually produces one of two useful outcomes. Either the number is large, and the business case writes itself. Or it is small, and you have discovered that the irritation is real but not expensive, which is worth knowing before spending a year replacing something.
Plenty of processes are annoying and cheap. Software is frequently bought to remove an annoyance at a price far above what the annoyance was costing.
Compare against the improved status quo, not the current one
The fair comparison is not against today. It is against what today would look like after the cheap fixes: the naming convention nobody agreed, the template nobody made, the two steps that could be dropped, the report that could be scheduled.
This is the comparison vendors never suggest and it regularly closes a large part of the gap. Where it closes all of it, you have saved the purchase price. Where it does not, the remaining gap is the real benefit of the product, and it is the number the business case should use.
Count the cost of the change itself
Doing nothing has one large advantage that shows up in no feature comparison: it consumes no implementation effort, no migration, no training, no period of reduced productivity while people learn.
Those costs are real, they land on people who are already busy, and they are systematically excluded from business cases. A product that saves ten hours a month and costs two hundred hours to implement does not break even for nearly two years, before anyone has counted the subscription.
Set the bar high enough to be worth it
Given implementation cost and risk, a marginal improvement is not a reason to change. A useful discipline is to require the projected benefit to exceed the total cost by a clear margin rather than merely beating it, because both sides of that comparison are estimates and the error is not symmetric — implementation costs overrun far more often than benefits overdeliver.
Write it down either way
If the decision is to do nothing, record why, with the numbers. The question will come back in a year, and having the previous analysis means revisiting it rather than starting again — and if the cost of the status quo has risen since, that is itself the argument.
When requirements involve personal data, the NIST Privacy Framework is a useful independent reference.