You're the owner. One card pays for the scheduler. Another pays for an old scheduler. An AI subscription was useful during a trial, but its extra seats are still renewing. Start with the bills and the work each tool supports. Do not start by cancelling the cheapest thing you recognize.
You will build a one-page stack map, check real use, name safe cuts, and track savings only when they actually post. The Three Outcomes Filter helps you choose what earns a place: money, time, or customer experience. This audit finds the recurring cost behind those choices.
What you get when done
A stack map, a dependency check, a keep/cut/consolidate decision for each tool, named cancellation owners and dates, verified spending controls where supported, and a quarterly review. The first ninety minutes produces the decision list; migrations or annual-contract changes may take longer.
Safety & data
Use the shop's approved business AI workspace, ideally a shop-owned account. Do not upload card statements, account numbers, transactions containing customer details, payroll information, staff HR records, passwords, API keys, or billing-console screenshots. Make a small table with vendor and amount only. Keep the source documents and any identifying details in your approved accounting system.
A vendor name can still reveal sensitive business context. Review the list before sharing and use category placeholders where necessary. Patient data and privileged matter information are not needed here. A business plan is not blanket approval for those records. The owner reviews the analysis and authorizes every cancellation, access change, or budget setting; AI never executes them. Any customer communication about a transition is reviewed and sent by the named account owner. Use the AI Use Policy and read the customer-data Field Note.
Step 1 — Pull three months, then make a smaller table
Review three months of card and accounts-payable statements locally. Extract vendor names and total amounts paid. Check annual invoices and upcoming renewals too; a quarterly sample can miss an annual bill. Do not export card numbers, bank details, invoice attachments, customer descriptions, or individual employee purchases to AI.
Keep a local working register with billing cadence, next renewal, notice period, owner, and contract link. Those are facts you verify, not facts a model can infer from a charge. Label currency and whether tax is included when comparing amounts.
Done: a reconciled local register and a separate vendor-plus-amount table safe for analysis. Unknown charges go to the bookkeeper before they become “waste.”
Step 2 — Group by function and flag questions
Review these vendor names and amounts only: [sanitized table].
Group likely functions: phones, scheduling, CRM/FSM, marketing, AI, automation, storage, or unknown.
Flag possible overlap, but do not assume similar vendors provide the same service.
Return: vendor, supplied amount, likely function, possible overlap, uncertainty, and questions for the owner.
Do not infer seat counts, annual/monthly terms, cancellation rights, or savings from names alone.
Provide blank fields for verified billing cadence, seat count, renewal date, and dependency owner for me to fill locally.
Do not cancel anything or recommend shutting down a customer-facing service before dependency review.
Now add the verified billing and seat facts in the local register. An HVAC field-service platform may include scheduling that looks redundant but drives dispatch and invoicing. A law office's storage tool may hold records under retention duties. An agency's unused login may be a service account powering a client workflow. “Overlap” means investigate, not delete.
Step 3 — Check seats against real work
In each approved admin panel, have the authorized administrator review seat use and the last-login or activity report if available. Flag seats unused for more than thirty days as candidates for removal. Confirm whether the seat is seasonal, a backup administrator, a service account, on leave, or needed for record ownership before acting.
The manager approves the cut. Transfer required records and ownership through supported tools, preserve retention obligations, and confirm a backup administrator still works. Do not use last-login data as a staff performance score. If the vendor cannot show reliable usage, ask the team what work the seat supports and label the answer as unverified until checked.
Done: each unused-seat candidate has a retain reason or an approved removal plan, including data ownership and recovery.
Step 4 — Review AI and automation usage
Read the billing and usage reports for AI seats, API/model spend, automation task runs, agents, and CI jobs. Identify the business owner and intended output of each recurring run. A successful run that nobody uses can still be waste.
For each provider, verify what its controls actually do. Some budgets only alert; some stop usage; some allow overage or delayed accounting. Set a monthly cap and alerts where supported, with a named owner who receives them. If a hard cap is unavailable, document that limit and the manual stop procedure. Test controls safely with a provider-supported method, not by running a paid workload to exhaustion.
Use a cheaper available model tier for routine drafting only after it passes your actual quality checks. Reserve higher-cost tiers for tasks that justify them. Do not hard-code a model version or assume the cheapest option is acceptable for sensitive work. Quality and permitted data use still matter.
If an agent or CI workflow repeats without a useful output, have its owner inspect the trigger, retry limit, and schedule. Pause only the identified nonessential workflow after checking dependencies. Do not disable every automation because one bill looks large.
Step 5 — Decide keep, cut, or consolidate
| Tool | Decision | Work it supports | Dependency/export check | Owner | Renewal/notice date | Action date |
|---|---|---|---|---|---|---|
| [vendor] | [keep / cut / consolidate] | [specific work] | [verified / pending] | [name] | [date] | [date] |
Before cancellation, export required records into an approved system and verify they open. Check contract terms, retention duties, integrations, number ownership, and customer impact. A phone system in peak season needs a transition plan, not an impulsive cancellation. Do not remove the only copy of customer data or the only administrator.
For consolidation, prove the replacement handles the critical workflow before ending the old service. Name the person who approves the switch and the person who can roll back. The owner schedules any needed customer notice; that named person reviews and sends it. AI does not email vendors to cancel or negotiate on your behalf.
Step 6 — Publish the one-page stack map
Use one row per tool: function, business owner, monthly-equivalent committed cost, renewal date, critical dependencies, decision, and next action. For an annual contract, show the annual commitment beside the monthly equivalent so nobody mistakes an accounting comparison for a cancellable monthly bill.
Hypothetical: if a verified unused monthly seat costs [amount] and cancellation takes effect on [date], the estimated future reduction is [amount] per month. It becomes realized savings only after the lower bill or credit posts. Subtract migration costs, replacement subscriptions, and unavoidable contract charges when comparing options. Do not count a proposed cancellation twice.
The AI budget Field Note helps connect tools to the full operating cost. Review the map quarterly and before a major renewal. Use Security Week to verify access removal after changes.
Operator Standard check
- Trace: reconcile vendor spend and usage with the work each tool supports.
- Choose: assign keep, cut, or consolidate decisions based on outcomes and dependencies.
- Build: schedule approved changes, verify exports, and configure supported spend controls.
- Prove: check posted bills and continuity of critical workflows after the changes.
Failure modes
Do not cancel the only system holding customer records before a verified export. Do not cut the phone line while dispatch depends on it. Do not assume an alert is a spending cap. Do not treat every inactive seat as disposable. Do not spend the whole review chasing a tiny charge while ignoring a large verified overlap. Do not call estimated savings money recovered. Do not auto-send cancellation or customer-transition messages.
If it goes wrong (kill switch)
The owner can stop the cancellation queue before the next action. The administrator pauses the specific planned change and follows the recorded rollback or vendor recovery procedure. Keep the old service active during a migration until the critical workflow is verified, where contract terms allow. If a service already stopped, contact the provider through its official support route; do not assume restoration is guaranteed.
For affected customers, the named account owner sends a reviewed factual notice: “We are resolving an issue with [service]. Please use [verified alternative] while [name] handles it.” Do not invent a recovery time. If records or access may have been exposed, follow the incident process in the AI Use Policy.
Prove it: 4-week scoreboard
| Metric | Baseline | Week 1 | Week 4 | Keep-Kill decision |
|---|---|---|---|---|
| Verified recurring committed spend | [ ] | [ ] | [ ] | Compare same scope and billing period |
| Posted savings, net of replacement costs | [ ] | [ ] | [ ] | Keep only verified reductions in the result |
| Unused seats awaiting owner decision | [ ] | [ ] | [ ] | Resolve exceptions before removal |
| Tools with verified cap/alert and named recipient | [ ] / [ ] | [ ] / [ ] | [ ] / [ ] | Document controls the provider lacks |
| Critical workflows disrupted by changes | [ ] | [ ] | [ ] | Pause cuts and fix the transition |
Save it as a skill
Save the approved analysis prompt and never-list in a Project or skills/tool-stack-audit.md in the shared drive. The billing register stays in its approved location.
SKILL: Tool Stack & AI Spend Audit
Owner / bookkeeper / authorized administrator: [ ]
Input: sanitized vendor names and amounts only. No statements, credentials, personal data, or customer records.
Task: group functions and flag possible overlap using the approved prompt. Treat cadence, seat use, renewal rights, and dependencies as unknown until verified by a person.
Never-list: [paste the shop's complete never-list]
Never cancel, change access, alter budgets, or send messages. Do not call hypothetical savings realized.
Before action: owner approves; administrator verifies exports, dependencies, recovery, contract terms, and customer impact.
Stop: missing records, unclear owner, critical service at risk, or an unavailable rollback.
Output: one-page map and decision list with owners and dates.
Review date / version / changes: [ ]
Definition of done
The stack map is complete. Every proposed cancellation has an owner, date, contract check, and verified data/dependency plan. Supported spend caps and alerts are configured and their limitations recorded. Changes are scheduled rather than assumed complete. The next quarterly audit is on the calendar. At four weeks, record posted results and any service impact.
FAQ
Should I remove every seat unused for thirty days? No. Flag it, then check its purpose, record ownership, seasonality, and recovery role before an authorized person removes it.
Can I call annual savings realized today? No. Keep them hypothetical until the relevant cancellation and lower charges take effect. An annual commitment may not be refundable.
What if the tool is cheap but nobody uses it? It may still be worth removing after a dependency check. Prioritize by verified cost, risk, and attention required, using the Three Outcomes Field Note.