If you're the IT lead or CTO at a 100-to-200-person Indian company, you're almost certainly paying for SaaS seats nobody's using. Not a few. Dozens. Spread across Slack, Zoom, Figma, Jira, Notion, and whatever else your teams signed up for over the past 3 years of rapid hiring and tool sprawl.
The problem isn't that people are wasteful. It's that no single system watches utilization continuously. Procurement lives on one credit card, cloud billing on another, and the HR team quietly offboards someone without triggering a single license review. The result is a quiet, compounding drain on your SaaS budget that nobody notices until a CFO asks why software costs went up 40% while headcount grew 20%.
SaaS audit checklist India unused seats, reclaim the money, and set up a process so it doesn't silently creep back. We'll use real INR figures throughout, because the math only becomes uncomfortable when you see it written down.
Why Unused Seats Are a Silent Budget Leak
Let's put a number on it before anything else. A 150-person company running Slack Business+ at ₹685 per user per month with 55 inactive users is burning ₹4.5L per year on nothing. Not on a bad tool. On accounts that haven't been opened in months. Multiply that across 30 tools and you're looking at a problem that funds a mid-level engineer's annual salary.
shadow IT signupsing checklist. Role changes that moved someone off a tool but left the seat live. Tool consolidation that got half-done. And shadow IT signups — tools bought on a personal card that IT never knew existed.
SaaS vendor review processcurement policy Indiae of glass. Procurement is scattered: some tools bill to the company card, some go through an AWS Marketplace invoice, some are on the founder's personal Amex from 2021. Without a unified view, you're doing tribal knowledge archaeology every quarter instead of running a clean report.
Watch out: Attrition is your single biggest license leak trigger. Every employee who leaves without a formal SaaS offboarding step costs you, on average, 2.3 active licenses sitting idle at full price.
Step 1: Build Your SaaS Inventory Before You Reclaim Anything
SaaS license rightsizing audit discovery layers working together before you can confidently say "this seat is safe to kill."
Layer one: SSO and IdP logs. If you're on Okta or Azure AD, you have last-login timestamps for every SSO-connected app. Pull a 60-day report filtered to zero logins. That's your first pass. The gap in this approach: not every tool is SSO-connected, especially the ones that were shadow IT to begin with.
Layer two: bank and card transaction feeds. Cross-reference your recurring charges against your approved tool list. Anything that appears in the bank feed but not in the IT inventory is a discovery candidate. This catches the tools that were bought outside IT's visibility entirely.
Layer three: inbox invoice parsing. This is where significant volume hides. AI reads invoice emails in Gmail or Outlook, extracts vendor name, amount, billing cycle, and maps each invoice to the user or team that received it. For Google Workspace shops, you get richer signals because Gmail's API gives you invoice metadata at scale. For Microsoft 365 shops, the same logic applies through Exchange/Outlook connectors. Different signals, same output: a complete inventory with monthly cost in INR, seat count purchased versus provisioned, and last-login date per user.
A complete inventory looks like a single spreadsheet row per tool: name, monthly INR cost, seats purchased, seats provisioned, last-login date, billing owner. You can't start reclaiming until you can see all of that in one place.
Run a free SaaS spend audit — find every hidden subscription
Key takeaway: Discovery has to come from three layers — SSO logs, payment feeds, and inbox invoices — because no single source catches everything your company is actually paying for.
Step 2: Define 'Inactive' With a Defensible Threshold
This is where most reclamation projects go wrong. IT sets "90 days no login" as the default threshold across every tool, flags 80 accounts, gets pushback from 6 team leads, and quietly shelves the whole effort.
The right thresholds are tool-specific. Slack: 14 days of no activity is a reasonable flag — it's a daily communication tool. Zoom: 30 days. Jira: 45 days, because sprint-based teams might not log in during planning cycles. Figma: 60 days, because design reviews are project-gated and a designer might not edit files for two months without being inactive. Applying 90 days to Slack means you're leaving obvious waste on the table. Applying 14 days to Figma means you're flagging active designers.
Pulling last-active data directly from vendor APIs is more reliable than SSO alone, because SSO only tracks logins, not actual usage. Slack's SCIM API gives you message activity. Microsoft Graph gives you Teams meeting joins, file edits, mail activity. Google Admin SDK gives you Drive, Meet, and Calendar signals. The combination of login event plus actual activity signal is what separates a defensible reclamation list from one that gets challenged in the first team meeting.
Document your exceptions before you start sending notifications. Employees on maternity or paternity leave, bench employees between projects, seasonal contractors who'll return in Q4. A reclamation workflow that accidentally flags a senior engineer on parental leave creates trust problems that outlast any budget savings.
Action: Build a simple exceptions register before your first reclamation run. HR sends you a list of any employee on leave or bench status. Filter them out of your inactive list before a single notification goes out.
The output of this step is a prioritized reclamation list: tool name, inactive seat count, monthly cost per seat, and estimated annual INR recovery if those seats are cancelled. Sort by annual recovery descending. Start at the top.
Step 3: The Reclamation Workflow — From Flag to Downgrade
Once you have the list, the process has two stages. First, an automated email goes to the flagged user: "We've noticed you haven't used [Tool] in 45 days. If you still need access, click here to confirm within 7 days. If we don't hear from you, your seat will be released." That 7-day window filters out anyone who was on vacation or heads-down in a sprint.
If there's no response, the notification escalates to the user's manager. Manager confirms or overrides. This two-step approach means you're not making unilateral calls about someone's access, and you have a documented trail if anyone questions the decision later.
Deprovisioning isn't just clicking "remove user." You need a checklist per tool. For Slack: transfer channel ownership, export DM history if legally required, check if the user owns any paid Slack apps or workflows. For Jira: reassign open tickets. For Google Workspace: set a mail delegate for 30 days before deleting. Skipping these steps creates operational breakage that's worse than the cost of the idle seat.
Vendor-specific downgrade mechanics matter here. Notion's flex billing adjusts monthly — you can drop seats immediately and the next invoice reflects it. Google Workspace suspends vs. deletes — suspend first, wait 30 days, then delete to avoid losing data. Microsoft's license reassignment portal lets you move a license to a new user without buying a new seat, which is useful when you're reclaiming from a leaver to onboard a joiner.
On the finance side, every reclamation event needs documentation. When a vendor issues a credit note mid-cycle, that credit note must be GST-compliant to correctly reverse the input tax credit your finance team already claimed. Vendors outside India often issue credits in USD with no IGST breakdown, which creates reconciliation headaches. Build the habit of requesting proper documentation upfront.
Key takeaway: Reclamation is a workflow, not a one-time delete action — two-stage notifications, deprovisioning checklists, and GST-clean credit notes are all part of doing it properly.
Step 4: Shadow IT Is the Hidden 30% You Almost Missed
Shadow IT is software purchased by employees or individual teams without going through IT or finance. In Indian SMBs it's remarkably common. Your data team bought Notion individually. Three designers each have personal Canva Pro subscriptions. Half the leadership team is on ChatGPT Plus on their own credit cards.
In a 100-person Indian company, shadow IT routinely adds 20–30% to the true SaaS bill — and carries zero SSO, zero offboarding, and zero visibility for IT.
Detection is straightforward if you've done inbox invoice parsing. Cross-reference every vendor that shows up in invoice emails against your approved tool list. Anything not on the approved list is a shadow IT candidate. Common culprits we find across Indian SMBs: Canva Pro at ₹4,999/year per user with 8 individual subscriptions running in parallel, Loom on 6 department cards, ChatGPT Plus on 12 separate accounts at $20/month each (roughly ₹1,670/month per account, so ₹2.4L/year total just on AI tools no one centralized).
The consolidation play here is obvious but the math makes it stick. Canva Teams costs ₹16,900/year for up to 5 users. Eight individual Canva Pro subscriptions cost ₹39,992/year. Consolidating saves ₹23,092/year on one tool, you get central billing, SSO, and brand kit controls. Repeat this pattern across 4-5 shadow IT tools and you're looking at ₹1-2L in annual savings without reclaiming a single enterprise seat.
The security argument is worth making to your leadership team, not just the finance one. Shadow IT means company data living in tools with no SSO and no automatic offboarding. When someone leaves, their personal Notion account doesn't get deactivated with their Google Workspace account. That's a data governance problem that compounds over time.
Explore our SaaS Marketplace to see consolidated team plans for the tools your company is likely running as shadow IT — with negotiated pricing that beats what individuals pay on Canva or Loom's website.
Action: Pull every vendor from the past 6 months of inbox invoice parsing and check each one against your approved tool list. Any vendor appearing on 3 or more individual cards is a consolidation candidate.
What AI CIO Automates That You Cannot Do Manually at Scale
Manual reclamation works once. You run the audit, recover ₹5-6L, present the savings to your CFO, and everyone feels good. Then 3 months later you've onboarded 15 new employees, 3 senior people left without a proper offboarding, and the drift has already started again. Without a continuous process, you're back to where you started within 2 renewal cycles.
This is exactly the problem AI CIO is built to solve. New hires trigger automatic license provisioning reviews — you don't over-buy at the start. Leavers trigger immediate reclamation workflows. Role changes flag tools that are no longer relevant to the new function. All of this runs as a background process, not a quarterly manual effort.
The alerts engine combines renewal signals with utilization signals. 45 days before your next Jira renewal, AI CIO surfaces a reclamation recommendation that includes current seat utilization, cost per active user, and a one-click approve or defer action from the admin hub. You're not reacting to a surprise invoice. You're making a deliberate decision with data in front of you.
The utilization data goes deeper than login events. AI CIO reads activity signals from vendor APIs: Jira issues created and closed, Figma files edited, Zoom meeting minutes hosted. A user who logs into Jira weekly to check their notifications but hasn't closed a ticket in 90 days is a different reclamation candidate than someone who's actively managing a sprint board. That distinction matters when you're deciding whether to reclaim or reassign.
The ROI framing is simple. One IT lead at ₹18L/year CTC cannot monitor 40 tools monthly while also managing infrastructure, security, and onboarding. AI CIO does the monitoring as a background process and surfaces only the decisions that need a human. That's the right division of labor.
Book a 15-minute call — see your own SaaS savings with a quick walkthrough
Real Numbers: A 120-Person SaaS Audit Breakdown
Here's a composite example based on actual Easexpense customer data. A 120-person product company, 34 active SaaS tools across engineering, design, sales, and operations.
Audit findings: 18 tools with inactive seats, 6 duplicate tools where two teams were running parallel subscriptions for the same use case, and 4 shadow IT apps spending ₹2.1L/year on individual subscriptions that could be consolidated.
The top 5 reclamation wins by annual INR recovered:
- Slack Business+: 32 inactive seats at ₹685/month — ₹2.6L/year recovered
- Zoom Business: 18 inactive hosts at ₹1,250/month — ₹2.7L/year recovered
- Figma Organisation: 11 inactive seats at ₹4,500/month — ₹5.9L/year recovered (Figma's per-seat cost is high)
- Jira Premium: 22 inactive users at ₹710/month — ₹1.9L/year recovered
- Notion Team: 14 inactive members plus 3 individual plans consolidated — ₹1.1L/year recovered
The full audit took 3 hours with automation. Our internal estimate for doing the same audit manually across 34 tools, pulling admin reports, cross-referencing HR data, and building the reclamation list: roughly 3 weeks of part-time effort by someone who knows what they're doing.
At renewal: 2 vendors (Zoom and Zoho) offered mid-cycle prorated credits. 3 required waiting for the annual renewal date. Total first-year savings: ₹5.8L. In subsequent years, with the continuous monitoring in place, the drift rate dropped significantly because license reviews now happen automatically at offboarding rather than quarterly by hand.
Setting Up a Recurring License Review Process
A reclamation audit is a one-time recovery. A recurring review process is what keeps the savings compounding year over year.
The cadence that works: monthly automated scans for new inactive flags, a quarterly human review where the IT lead and finance approver sit down and confirm the reclamation queue, and an annual full audit timed 60 days before your largest renewal (usually Microsoft or Google, which are often Q1 or Q4 events). The 60-day buffer is important because it gives you negotiating room. If you discover you only need 80 seats instead of 120, you want that conversation to happen before auto-renewal processes, not after.
Ownership structure: IT lead is the directly responsible individual for the reclamation list. Finance is the approver for any spend change above ₹50,000. This keeps the process moving without requiring finance sign-off on every 3-seat Loom cancellation, while ensuring material decisions have visibility.
The metrics worth tracking quarter over quarter: license utilization rate per tool (seats used divided by seats purchased), cost per active user (total tool spend divided by active user count), and reclamation rate (INR recovered divided by INR spent on SaaS). These three numbers tell you whether your process is working or whether the drift is returning.
When you present to leadership, frame it as INR recovered versus cost of the process. If Easexpense's platform costs ₹X/month and you recovered ₹5.8L in year one, the ROI calculation writes itself. CFOs understand that framing far better than "we cleaned up our SaaS stack."
Check out the Easexpense pricing page to see what the platform costs relative to the recoveries a company your size typically sees in year one.
Key takeaway: Monthly automated scans plus a quarterly human review creates a self-sustaining process — the one-time audit becomes a continuous margin improvement, not a project you repeat from scratch every year.
Frequently asked questions
How do I find unused SaaS licenses in my company?
Start by pulling last-login data from your SSO provider or directly from each vendor's admin console. Cross-reference that against your active employee list and set tool-specific inactivity thresholds — 30 days for Zoom, 45 for Jira, 60 for Figma. Inbox invoice parsing catches tools that were never provisioned through IT at all, which is often where the biggest surprises hide. Easexpense's free spend audit does this across your entire stack in under 30 seconds by connecting your work inbox and cross-referencing against known vendors. The output tells you every tool you're paying for, the seat counts, and first reclamation candidates sorted by annual INR impact.
What is SaaS license reclamation and why does it matter for Indian SMBs?
SaaS license reclamation is the process of identifying paid seats that are no longer actively used and either reassigning or cancelling them before the next billing cycle. For Indian SMBs paying in USD or through resellers with 18% GST on top, even 10-15 reclaimed Slack or Zoom seats can save ₹1-2L annually. The pain is higher in India because most companies have no dedicated procurement function watching utilization month to month — IT is stretched across infrastructure and security, and finance sees a consolidated card statement, not a per-seat utilization report. The result is that unused licenses quietly renew for years before anyone investigates.
Can I reduce SaaS seats mid-contract or do I have to wait for renewal?
It depends on the vendor. Zoom, Zoho, and Google Workspace allow seat reductions mid-cycle with prorated credits applied to your next invoice. Microsoft 365 and Adobe Creative Cloud typically lock seat counts until the annual renewal date — you can remove users from the admin console but the billing doesn't adjust until renewal. Notion's flex billing adjusts monthly, so any change you make this month appears on next month's invoice. Knowing which vendors allow mid-cycle changes and which don't tells you whether to act immediately or queue the reduction for renewal — and Easexpense surfaces this vendor-specific policy as part of every reclamation recommendation so you're not finding out after the fact.
How much money do companies typically recover through a SaaS license audit?
Based on Easexpense customer data, a 100-150 person Indian company with 25-40 active SaaS tools typically recovers ₹3-8L annually through a first reclamation exercise. Shadow IT consolidation adds another ₹1-2L in many cases, because individual subscriptions almost always cost more per seat than a consolidated team plan. The range varies by industry — product and tech companies tend to have higher per-seat costs and more tool sprawl than services firms, which means higher absolute recovery amounts. ₹5L is a reasonable conservative floor for a company of that size; the ceiling is higher once shadow IT is fully counted.
What is shadow IT and how does it inflate our SaaS spend?
Shadow IT refers to software purchased by employees or individual teams without going through IT or finance — often on a personal card or a department credit card that never appears in the central software inventory. Common examples include personal Canva Pro subscriptions, individual ChatGPT Plus accounts, and Loom plans bought without a purchase order. In a 100-person company, shadow IT routinely adds 20-30% to the true SaaS bill. It also creates security and compliance gaps because those tools have no SSO, no centralized access control, and no automatic offboarding when the employee leaves — meaning company data can persist in third-party systems long after the employment relationship ends.
How does AI automate SaaS license reclamation?
An AI layer like Easexpense's AI CIO continuously monitors usage signals from vendor APIs — not just login events but actual activity like Jira tickets closed, Figma files edited, or Zoom meeting minutes hosted. When utilization drops below a tool-specific threshold and a renewal date is approaching, it surfaces a reclamation recommendation to the IT lead with a one-click approve or defer action. This replaces a monthly manual review process that most IT leads simply don't have bandwidth to run across 30-40 tools. The system also triggers reclamation automatically when an employee is offboarded through your HR system, which is the biggest leak point in most companies that rely on manual quarterly reviews.
Does SaaS license reclamation affect GST input tax credit claims?
Yes, and this is an area Indian finance teams often overlook until it creates a reconciliation problem. When you downgrade a plan mid-cycle and receive a vendor credit note, that credit note needs to be GST-compliant to correctly reverse the ITC you already claimed on the original invoice. Vendors outside India — which covers most SaaS tools — often issue credits in USD without IGST or CGST/SGST breakdowns, which creates a mismatch in your books. Your CA will flag it; best to handle it at the source. Easexpense generates GST-clean documentation for every reclamation event processed through its platform, so your finance team gets a properly structured credit note they can actually use for ITC reversal without a manual adjustment entry.