Do not start by cancelling everything that looks unused
Start with an owner, a renewal date and the workflow each subscription supports. An inactive seat may still hold business data, run an integration, or sit inside a commitment that cannot be reduced immediately.
This checklist helps a small business review its software without mistaking credits for refunds or cutting off essential access. It is a planning process, not a claim that your business will save a particular amount.
On this page
Build one subscription inventory
Sort by business use
Check three billing traps
Protect data and dependencies
Use a decision ledger
1. Put subscriptions in one inventory
- Tool, plan and the business workflow it supports.
- Business owner and billing owner; these may be different people.
- Paid seats, genuinely needed access and recent activity.
- Invoice frequency, contractual term and renewal date.
- Required add-ons, usage charges and current annual commitment.
- Cancellation notice deadline, export options and linked systems.
Use the latest invoice and actual agreement rather than guessing from a public pricing page. Reconcile annual charges as well as monthly card payments so that prepaid tools do not disappear from the audit.
2. Give each tool a provisional decision
| Decision | When it fits | Next step |
|---|---|---|
| Keep | A necessary workflow with an accountable owner | Verify the right tier and seats |
| Resize or downgrade | The workflow matters, but the current package may exceed need | Check feature loss and effective date |
| Consolidate | Two tools appear to serve the same job | Compare missing capabilities and migration effort |
| Retire | The business no longer needs the workflow | Plan export, dependencies and contract exit |
| Investigate | No owner or unclear usage | Find the owner before removing access |
Do not equate a low login count with low value. A reporting tool used monthly can still be essential; a background automation may rarely require a login. Ask what breaks if it disappears, then verify that answer.
3. Check three billing traps
Inactive does not always mean unbilled
Billing rules differ. Slack’s Fair Billing Policy applies to specified website purchases paid by credit card or self-serve invoicing. It describes prorated credits when paid members become inactive, including an over-28-day inactivity rule. Those credits apply to future charges and are non-refundable; they are not cash returned to your bank. The policy also sets a one-member minimum if everyone becomes inactive unless the workspace is downgraded. Do not assume every Slack contract, or every SaaS product, uses this model.
Removing a user may not reduce a contract
Google Workspace’s annual-plan documentation says annual committed licenses can be reduced only at renewal. Removing access and reducing a contractual license commitment are different actions. Record when a reduction actually affects cost.
Monthly payment may still mean annual liability
Microsoft’s business cancellation guidance distinguishes billing account types and purchase routes. In its stated annual-subscription cases, paying monthly still means being charged for the rest of the term. Do not apply Microsoft 365 Personal or Family rules to a business agreement, or assume every business cancellation produces a refund.
4. Protect data and connected work before exit
- Identify integrations, scheduled jobs, shared links, forms and customer-facing dependencies.
- Confirm who owns records and files, then plan permitted export and validate that the export is usable.
- Transfer ownership and required access before deactivating a person or workspace.
- Check retention, privacy obligations and how long read access remains available.
- Have the authorised owner make and document the final change; verify the next invoice and effective date.
Microsoft’s guidance explicitly warns users to save data before cancellation and explains that effective cancellation can remove access. Treat “stop renewal”, “cancel service” and “delete subscription/account” as different actions with potentially different consequences. This article does not direct you to delete accounts.
5. Use a decision ledger
| Field | Your entry |
|---|---|
| Tool, owner and decision | Accountable person; keep / resize / consolidate / retire / investigate |
| Baseline cost and period | Actual cost before the change; explicit start and end dates |
| Post-change cost and same period | Include the replacement tool and remaining commitments |
| One-off change costs | Migration, setup, external help and internal time recorded separately |
| Contract action date | Notice deadline and effective date |
| Credit or refund | Amount, type and date actually applied or received |
| Dependency and data checks | Evidence that access, exports and workflows are protected |
| Net result and verification | Like-for-like cost difference less one-off costs; avoid counting an applied credit twice |
What counts as a saving?
Keep estimates labelled projected until the relevant evidence confirms the outcome: compare invoices for a reduced charge, payment records for a cash refund, or cancellation confirmation plus absence of a renewal charge for an avoided renewal. An unapplied credit is not yet a cash reduction. Include migration and replacement costs, use the same comparison period, and do not count a credit twice.
Use the SaaS budget worksheet to compare the remaining stack over a full year. Repeat the audit on a manageable cadence and after a staffing or major workflow change, rather than waiting for an unexplained renewal.
Sources and research notes
- Slack: Fair Billing Policy
- Google Workspace: plan commitments
- Microsoft 365 for business: cancellation, billing account types and data warnings
Checked November 3, 2026 (Asia/Seoul). AI-assisted research and drafting, with source and arithmetic checks. Documentation-based analysis, not hands-on product testing. Recheck vendor terms before purchase.