Before you buy more software, audit what you already own
Licensed features sitting unconfigured are the most common finding in an assessment, and the cheapest thing to act on.
- June 17, 2026
- Published
- 6 min
- Read time
- Strategy
- Category
On This Page
The renewal nobody reads
Software gets bought to solve a specific problem, configured for that problem, and then renewed annually by someone comparing the invoice to last year. Nothing in that cycle prompts anyone to ask what else the licence includes.
Meanwhile the vendor ships features. Modules get added to your tier, capabilities get folded into the plan you are already on, and none of it arrives with a person whose job is to notice.
The result is completely ordinary and slightly embarrassing: businesses proposing six-figure builds for capability sitting dormant on an invoice they already pay.
What an audit actually looks like
Start with the invoices rather than the tools. Every recurring software charge, what it is for, who uses it, and what tier you are on. That list alone usually surprises people, because subscriptions accumulate without anyone holding the total.
Then, for the three or four most expensive, read the feature list for your tier against what you actually use. Not the marketing page, the documentation. Look specifically for modules that were never switched on.
Finally, look for overlap. Two tools doing the same job is common after a few years of solving problems tactically, and consolidating is usually easier than either building or buying.
Configuring is not the same as building
A dormant module is rarely a complete answer. It will do part of the job, in a way that is less tailored than something purpose-built, and it is worth being honest about that rather than overselling it.
But the comparison is not against perfect. It is against a build with a budget, a timeline, and a maintenance burden. A feature that covers seventy percent of the need and takes two days to configure usually wins that comparison decisively.
It also narrows the build if one is still needed, which makes the build cheaper and more likely to succeed.
The uncomfortable conversation
This finding is awkward to deliver, because somebody approved that subscription and somebody has been renewing it. Nobody enjoys learning they have paid three years for something unused.
The way to handle it is to make it about the system rather than the person. Nobody is assigned to audit licences, which means it is a process gap, not negligence. Assign it annually to someone and it stops recurring.
ReynoldsBuilt
AI, automation, and custom software
We audit an entire operation before building anything, then build what the business actually needs. Everything here comes out of real engagements.
About the studioKeep reading
More from the blog
Written for the person who has to make the call, not the person writing the spec.
Strategy · 8 min
The spreadsheet your team built is the best spec you have
Every business has a shadow spreadsheet holding the operation together. Most software projects throw it away. That is a mistake, and an expensive one.
ReadAutomation · 7 min
The worst automation failure is the one nobody notices
An automation that breaks loudly gets fixed the same day. One that fails quietly can corrupt six months of data before anyone asks a question.
ReadAI · 9 min
Hallucination is a design problem, not a model problem
Waiting for a model that never invents anything is not a plan. Building systems that assume it will is.
ReadFind out what should actually be built.
Start with an assessment. We walk your business end to end and show you where automation and AI pay off, ranked by what they are worth.