When something is not working, buying software feels like progress. It is decisive, it is visible, and there is always a vendor ready to help. It is also, frequently, the wrong move.
The accumulation problem
Very few organizations deliberately choose a sprawling application estate. It accumulates. A team needed something urgently. A tool arrived with a new hire who liked it. A trial was never cancelled. Each decision was locally sensible.
The result is an estate where nobody can confidently say what is in use, what it costs in total, or which capabilities are paid for several times over.
Four questions before buying
1. Do we already own something that does this?
Broad productivity suites in particular include far more capability than most organizations use. Forms, approvals, basic automation, shared storage, video, project tracking — these are often already licensed and simply not switched on.
2. Is the problem actually the software?
If a process is unclear, inconsistently followed or genuinely contested between teams, new software will encode that confusion rather than resolve it. It will just be more expensive confusion.
3. What is the total cost?
The subscription is the smallest part. Add implementation, integration, training, administration, the attention it takes from someone, and the eventual cost of migrating off it.
4. Who will own it in two years?
Tools adopted without a clear owner become nobody's responsibility — still paid for, half-configured, trusted by a few people and unmaintained.
When new software is the right answer
Sometimes it plainly is. The signals are reasonably clear:
- The capability genuinely does not exist in anything you own.
- The process is well understood and stable enough to be worth encoding.
- Someone specific is accountable for the outcome, not just the purchase.
- You know what you will stop doing, or stop paying for, as a result.
The goal is not to spend as little as possible. It is to be able to explain why each thing you pay for is there.