1. Start with a decision inventory, not a cancellation list
Make one row for every tool, plan, AI add-on and paid workspace that can create a renewal or expansion decision. Record the owner, monthly or annual cost, renewal timing, primary workflow, active users, critical integrations and the cost of switching. The purpose is visibility. Do not mark a product as “waste” merely because usage is imperfect.
2. Annualize the real spend
Monthly pricing hides the size of many decisions. Convert monthly plans to annual spend, add paid AI features, seat growth, support tiers and predictable usage charges. For variable tools, use a recent baseline rather than the most optimistic month. This gives you the amount actually exposed to renewal and expansion decisions.
The free AI & SaaS Waste Calculator is designed for this first pass. It does not claim savings; it simply makes the spend selected for review visible.
3. Separate six different leak surfaces
| Surface | Question | Possible decision |
|---|---|---|
| Unused | Has meaningful use disappeared? | Review / cancel |
| Duplicate | Are two tools serving the same workflow? | Consolidate / keep both with reason |
| AI add-on | Did price increase without a baseline for value? | Test / remove / justify |
| Oversized | Are seats or tiers above current need? | Reduce plan or seats |
| Renewal timing | Is the organization deciding early enough? | Move review date forward |
| Economics | Does the workflow value still exceed full operating cost? | Keep / redesign / stop |
4. Measure utilization in the workflow, not only logins
A login count is a signal, not a business case. Ask what the tool actually changes: handling time, delay, error exposure, capacity, handoffs, response speed or quality. A tool with frequent logins can still be operationally weak. A tool used by only two people can be essential if those two people own a high-value bottleneck.
What to capture
- Which recurring workflow would break or slow if the tool disappeared?
- Which other tool could perform the same function?
- What human review or exception handling still exists?
- What would migration, retraining or integration replacement cost?
- What evidence will you use at the next renewal to confirm the decision?
5. Make renewal timing part of the system
A renewal audit performed one day before the contract date is mostly paperwork. Set the internal decision date earlier than the vendor deadline. That gives the team enough time to test alternatives, collect usage evidence, reduce seats, export data or decide that switching cost makes renewal rational.
Spend, usage, overlap, workflow dependency and contract constraints.
Keep, resize, consolidate, replace or stop — with an explicit reason.
Update the baseline so the next renewal starts from observed reality.
6. Know when self-service is enough
If the stack is small, ownership is clear and the team can challenge its own assumptions, a checklist plus a lightweight business case may be enough. The AI Value Realization Kit exists for that middle layer: make baseline, value, cost and decision threshold reviewable without paying for a custom audit.
A deeper review becomes easier to justify when multiple tools interact, renewal exposure is material, ownership is fragmented, or a wrong consolidation decision could cost more than the review itself. The AI & SaaS Spend Waste Audit is fixed-scope and should not be the default route for every stack.
7. Close the loop after the decision
A spend audit is incomplete if it ends at “cancel these tools.” After the team acts, run the free measurement layer again. Did annualized spend change? Did workflow friction increase? Did a consolidation create a new bottleneck? Did a cheaper plan remove a feature the team actually needed? This is how a one-time cost review becomes a reliable operating habit rather than a short-lived savings exercise.
Use the smallest route that fits the decision.
Start with free evidence. Move to self-service or specialist review only if the decision is material enough to justify more depth.
Decision support only. No guaranteed savings, vendor outcome or implementation result.