Imagine a Gulf trading group approaching its software renewals. Dubai finance has the invoices, Riyadh operations has another user list, and a former project manager still owns several automated reports. Procurement asks IT to remove every account without a recent login. The proposed saving looks tidy. The dependency map does not exist. SaaS licence optimisation should begin by proving which subscriptions the business can change without interrupting useful work.
The obvious response is a licence dashboard. That can expose assignments and activity, but it cannot decide whether a rarely used account supports a quarterly close, whether a cheaper tier removes an essential control, or whether releasing a seat changes the next invoice. The operating decision needs three kinds of evidence: what is used, what depends on it and what the contract allows.
SaaS licence optimisation needs a commercial baseline
Start with one application approaching a genuine decision window. Record the purchasing entity, subscription, product tier, paid quantity, assigned quantity, price basis, commitment end and notice deadline. Include the reseller where one exists. A UAE parent and Saudi subsidiary may have separate purchases for legitimate reasons; do not treat matching product names as proof that the agreements can be combined.
Separate seat charges from storage, transactions, messages, AI credits and other consumption. The FinOps Foundation's SaaS guidance distinguishes licence-based and consumption-based models and explains how contract commitments constrain optimisation. A smaller user list can leave a minimum commitment untouched or move spending into a different charge.
Preserve the original invoice and entitlement record before making changes. Finance needs a baseline with consistent scope, currency and billing period. Otherwise a credit, exchange-rate movement or delayed invoice can be mistaken for an operational saving. Keep one accountable application owner beside the financial owner so the review can reach a decision.
1. Replace the inactive list with a decision list
Join the licensed-user list to current employment or contractor status, team ownership and application activity. Mark unexplained records for investigation. Look for duplicate assignments, accounts created for abandoned projects and premium features assigned by default. An unclear identity is a reason to verify ownership, not an instruction to delete it.
Be precise about the activity signal. Microsoft's sign-in activity documentation distinguishes attempted interactive sign-ins from successful access, and successful access can be interactive or non-interactive. A login timestamp is therefore evidence about access, not a complete measure of productive use or feature value.
Check a period that covers the application's work cycle. A monthly reporting tool, seasonal campaign platform and daily customer-service system need different windows. Account for leave, temporary assignments and staff moving between business units. Ask the manager to confirm the required job, rather than simply approving another year of the same licence.
2. Find what a person-shaped account is carrying
For each proposed removal, inspect owned documents, dashboards, shared workspaces, scheduled exports, integration credentials and approval responsibilities. A departed employee's account may still be carrying a live workflow. That dependency needs a supported owner and access model; keeping an unnecessary personal subscription forever is not a solution.
Write the transfer action before the removal action. Name the new owner, the records that must remain available, the method for moving them and the business test afterwards. Ask the operational team to run the report or complete the approval using the replacement arrangement. An administrator seeing the files does not prove ordinary staff can continue.
Retention and recovery also need a decision before an account or entitlement changes. Check the exact product's terms and your organisation's requirements. The SaaS recovery testing field note explains how to prove that useful records and relationships can be recovered. Use that discipline where a licensing change could affect access to important business history.
3. Choose the smallest entitlement that completes the job
Give every candidate one proposed outcome: keep, downgrade, reassign, remove or investigate. Attach evidence, an owner and a review date. “Keep” is a valid result when an infrequently used capability matters. “Investigate” should expire into a decision rather than becoming a permanent holding area for uncomfortable questions.
For a downgrade, list the features the role actually needs. Test the lower tier against a complete task, including exports, collaboration, authentication and required controls. A user may rarely open an administration screen while still benefiting from a centrally managed feature. Ask the system owner to confirm those dependencies before equating low feature clicks with low value.
Consolidation deserves the same test. Two overlapping tools may support different workflows, languages or customer channels. Compare the cost of maintaining both with migration, training, integration changes and disruption. The goal is lower total cost for the required capability, not the smallest possible number of vendor logos.
4. Separate released seats from reduced commitments
Microsoft's business subscription guidance separates unassigning licences from removing them from a subscription. It also describes reduction windows that depend on the billing agreement and purchase circumstances. Confirm the terms for the actual subscription and purchasing channel before announcing an immediate reduction in spend.
Google Workspace's billing guidance says suspended users remain billable and that deleting a user on an Annual Plan does not reduce the commitment before renewal. These are examples of why access cleanup and commercial savings need separate records. They are not universal rules for every SaaS product.
Classify the financial result as a realised reduction, avoided future purchase or possible renewal reduction. Reassigning an already-paid seat can avoid another purchase without lowering today's bill. A planned renewal change remains a forecast until accepted. Record the effective date and confirm the supplier's revised quantity or order, then reconcile the invoice when it arrives.
5. Run a bounded renewal cycle
Begin early enough to transfer dependencies and meet notice deadlines. Pilot changes with a small, approved group, keep a practical restoration path and monitor the affected work. Connect leaver and role-change events to entitlement reviews through the existing business automation process. Automate the evidence collection first; retain judgment where removing access could interrupt operations.
The renewal decision should show the current commitment, approved changes, effective dates, preserved capabilities and verified financial effect. SaaS licence optimisation is complete when the business pays less for the capability it still needs, or demonstrably avoids buying it twice. A shorter account list alone has not earned the saving.