If you're running finance or operations at a 50 to 200-person Indian company, there's a good chance your SaaS stack has quietly grown past what anyone has a clear picture of. Tools get added fast, removed slowly, and no one owns the full list.
The result: you're probably paying for 30 to 60 tools, a meaningful chunk of which are either unused, duplicated across teams, or renewing automatically without a single person noticing. That's not a judgment, it's just what happens when companies grow faster than their procurement habits.
This plan breaks a SaaS audit into 90 days of manageable weekly effort. You won't need a dedicated IT team or a procurement department. You'll need one owner, a few hours a week, and a willingness to make some uncomfortable calls with department heads.
Why Quarterly Is the Right Cadence for a SaaS Audit
Annual reviews sound thorough until you realize that most SaaS renewals don't wait for your year-end. A tool you signed up for in March auto-renews in September. If you're only looking at the stack once a year, you've already missed it.
Growth-stage companies add tools faster than they remove them. A 100-person company that grew from 40 employees in 18 months has almost certainly added 15 to 25 new SaaS tools in that window, and retired maybe 3. The stack drifts in 90 days, sometimes significantly.
A quarter also maps naturally to the rhythms Indian companies already operate on: OKR reviews, quarterly budget check-ins, and GST filing deadlines. Running a SaaS audit on the same cycle means the findings feed directly into decisions that are already being made, rather than sitting in a spreadsheet waiting for the right meeting.
The average Indian SMB renews 60% of its SaaS stack on autopilot, with no utilisation review in between.
SaaS spend management Indiaartments, zombie subscriptions from tools the team stopped using six months ago, and SaaS license rightsizing audit seats but are now absurdly overprovisioned for 80 actual users. Each of these is a quiet, repeating drain.
Key takeaway: A quarterly audit cadence isn't bureaucracy — it's the minimum viable habit that keeps SaaS spend from compounding silently against you.
Before You Start: What You Actually Need to Run This Audit
SaaS audit checklist India one data source means your inventory will have gaps that undermine every decision downstream.
You'll need access to:
- Corporate card statements for the last 6 months, including any shared or departmental cards
- UPI transaction logs from accounts used for vendor payments — more relevant than most finance teams expect
- Admin access to Google Workspace or Microsoft 365 for OAuth-based inbox discovery
- A list of any expense accounts where teams self-reimburse for SaaS (Zoho Expense, SAP, or even a simple Google Sheet)
SaaS vendor review processes conflicts between department heads, and is accountable for the full 90 days. It's usually the CFO, an ops lead, or a senior finance manager. The role doesn't require technical skills. It requires business judgment and some authority.
Build a tracker before anything else. One row per subscription, with columns for: tool name, department owner, monthly cost, billing cycle, renewal date, number of licensed seats, and estimated active users. This tracker is the output of the first 2 weeks and the working document for the rest of the audit.
Action: Before Day 1, confirm you have view access to every payment method the company uses — corporate cards, UPI, and reimbursed expenses. A single missed card will leave shadow IT invisible throughout the entire audit.
If setting this up manually feels like 3 days of work before the real work starts, that's because it is. The free SaaS spend audit at Easexpense connects to your work inbox and surfaces the full subscription list in under 30 minutes, including tools that never showed up in any expense report.
Run a free SaaS spend audit — find every hidden subscription
Days 1 to 14: Discovery — Find Everything You Are Paying For
Discovery is the heaviest phase, and most companies underestimate how many tools they'll find. The typical outcome for a 50 to 200-person company is a SaaS inventory that runs 20 to 40% larger than anyone assumed going in.
Start with the work inbox. Connect it to a mail discovery tool that reads recurring invoices and flags subscriptions. This surfaces tools that never went through a formal approval process — the Figma seat someone added, the Notion team plan a designer signed up for, the Loom subscription from two product managers ago.
Cross-reference card statements line by line. International SaaS vendors frequently appear as generic merchant names on statements, so you'll need someone who can recognize "Atlassian" as the Jira charge and "SFDC" as Salesforce. This step is tedious and non-negotiable.
Flag shadow IT explicitly as a separate category in your tracker. Shadow IT is any tool signed up for on a personal card, a shared team card, or a departmental budget without central visibility. It isn't necessarily wasteful — sometimes teams find genuinely useful tools this way. But it needs to be brought into the central inventory before any rationalisation decisions are made.
By the end of Day 14, you should have a complete list with every subscription categorised by department and owner. If you're a 100-person company and your list has fewer than 25 tools, you've missed something. Go back and check the expense reimbursements.
Key takeaway: Discovery always surfaces more than expected — treat a larger-than-anticipated inventory as a sign the audit is working, not a sign something went wrong.
Days 15 to 30: Rationalization — Cut, Consolidate, or Keep
With a complete inventory in hand, the work shifts from finding to deciding. Apply a simple 3-bucket framework to every tool on the list.
- Actively used: 40% or more of licensed seats active in the last 30 days, no equivalent tool elsewhere in the stack
- Occasionally used: Some legitimate usage but seat count, tier, or plan is probably overprovisioned
- Unused or redundant: Fewer than 20% active seats, or a duplicate of a tool already in another bucket
The unused or redundant bucket is your immediate win. Cancel unused trials that converted to paid without anyone noticing. Find the department running 3 project management tools simultaneously (it's almost always product or engineering) and pick one. Downgrade the Slack Pro plan your 12-person marketing team has been on when the free tier would cover their actual usage.
When you bring these decisions to department heads, lead with utilisation data, not cost arguments. "You're paying ₹18,000 a month for 50 Asana seats and 9 people logged in last month" is a conversation. "We need to cut SaaS spend" is a negotiation that goes nowhere.
Action: In Week 3, action the no-friction cuts first: unused trials, tools with zero logins in 60+ days, and duplicate categories. These require no department approval and typically recover 8 to 12% of total SaaS spend immediately.
Calculate cost-per-active-seat for every tool in the occasionally-used bucket. A ₹500/month tool with 2 active users out of 20 licensed seats is costing you ₹5,000 per actual user. That figure changes how the conversation with the team owner goes.
Days 31 to 60: Renewal Intelligence — Stop Getting Surprised
Surprise renewals are one of the most avoidable ways companies lose money on SaaS. A tool auto-renews for another annual cycle, the invoice arrives, and by the time anyone notices it's already past the cancellation window. That's a full year of spend locked in for something the team stopped using in month 4.
Map every renewal date from your tracker and flag anything renewing in the next 90 days. For each of those, assign a decision: cancel, renegotiate, or renew. That decision needs to be made at least 30 days before auto-renewal, not after the invoice arrives.
Centralise renewal ownership. One person — or one system — receives every upcoming renewal alert. The worst version of this is renewal reminders scattered across personal email inboxes of whoever originally signed up for the tool. That person may have left the company.
Most SaaS vendors will offer meaningful concessions — additional seats, price holds, or discounts — if you approach the conversation 45 days before renewal rather than the week it's due. Vendors know their churn rate is highest at renewal; a proactive customer who signals they're evaluating alternatives is worth retaining on adjusted terms. Our team at Easexpense has seen vendors extend discounts of 15 to 25% in negotiated renewals for customers who initiated the conversation early.
For customers on AI CIO, renewal dates surface automatically from the payment layer — we process the transactions, so we see renewal timing before the invoice hits your inbox.
Book a 15-minute call — we'll show you what's renewing in your stack this quarter
Days 61 to 75: Compliance and Invoicing Cleanup
This section gets skipped most often, and it's the one that quietly costs Indian companies the most money over time.
Every SaaS subscription from an Indian vendor should carry a GST-compliant invoice with your company's GSTIN. That invoice lets you claim input tax credit at 18% on the subscription cost. If the invoice doesn't include your GSTIN, or if it's been going to the wrong entity, you can't claim the ITC — and you're effectively overpaying by 18% on every renewal.
International SaaS vendors are a separate case. Under the reverse charge mechanism, your company owes GST to the government on these subscriptions, even though the vendor doesn't collect it. Many Indian companies are either unaware of this obligation or inconsistent about meeting it. An audit is the right moment to reconcile what's been paid and what's outstanding.
Watch out: International SaaS invoices — AWS, Slack, Notion, Figma, and others — fall under reverse charge at 18%. If your company hasn't been self-assessing and remitting this GST, your CA needs to know during this audit phase.
Use this phase to consolidate billing. Move as many vendor invoices as possible to a single procurement email address and a single billing entity. This makes future audits significantly faster and makes ITC reconciliation something your finance team can do in a few hours rather than a few days.
The output of Days 61 to 75 is a clean vendor register: one row per active vendor, with confirmed pricing, contract terms, invoice delivery details, and GSTIN status. Build this once and maintain it going forward. It's the single document that makes every future audit start from a much better baseline.
Key takeaway: ITC on SaaS subscriptions is real money — a 100-person company spending ₹40 lakh a year on Indian SaaS vendors could be leaving ₹7.2 lakh in unclaimed tax credit on the table.
Days 76 to 90: Build the Process That Survives the Quarter
The audit itself is a one-time project. The goal of the final 2 weeks is to set up the lightweight systems that mean you never have to do a full audit from scratch again.
Write a one-page SaaS procurement policy. It doesn't need to be comprehensive — it needs to answer: who can approve a new SaaS tool, at what cost threshold does it escalate, and what information is required before any new subscription goes live. A tool costing under ₹2,000 a month might only need a manager sign-off. Something over ₹10,000 a month should go through finance.
Set up an intake workflow so teams request tools rather than self-subscribe. A simple Google Form that feeds a shared sheet works for most companies at this size. The point isn't bureaucracy — it's visibility. Shadow IT exists because the path to self-subscribing is easier than the path to asking for approval. Make the intake process genuinely fast (24 to 48 hours to a decision) and teams will use it.
Block a 15-minute monthly SaaS review on the calendar for the audit owner. That's it — 15 minutes a month to check what's renewing, flag anything new that appeared outside the intake workflow, and confirm the tracker is current. This is the maintenance cadence.
Before the quarter closes, assign renewal ownership for every active subscription. Every tool should have a named person who receives the renewal alert and is responsible for the cancel/renegotiate/renew decision. Not "the team" — a named person.
Define 4 KPIs to track next quarter: total SaaS spend, active tool count, average seat utilisation rate, and ITC recovered vs. prior period. These four numbers tell you whether the audit held or whether the stack drifted again.
The Lazy-Mode Version: Let AI CIO and the Marketplace Do Most of This
Not every company has the bandwidth to run a 90-day manual audit. If you're a 60-person company with no dedicated ops or IT headcount, the person who'd own this audit is the same person doing three other jobs. That's fine — there's a shorter path.
AI CIO handles continuous discovery, renewal alerts, and utilisation monitoring without manual effort. It connects to your Google Workspace or Microsoft 365, reads the payment layer, and surfaces what's active, what's renewing, and what looks underused. The categories that took 2 weeks to build manually in Discovery phase happen in a single onboarding session.
The Easexpense marketplace covers the rationalisation side. When you identify a tool that's overpriced or underused, you can compare alternatives with India pricing in INR, check which ones issue GST-compliant invoices, and switch without losing the vendor discount we've negotiated at the account level. That's meaningfully different from shopping comparison sites where the listed price is the retail price.
Combined, these two compress the 90-day manual process into something closer to an afternoon. The judgment calls still sit with you — what to keep, what to cut, how to handle a department head who's attached to a tool with 12% utilisation. But the mechanical work is largely handled.
This approach suits companies with no dedicated IT or procurement staff particularly well, which describes most Indian SMBs at the 50 to 150-person stage.
What a Realistic Outcome Looks Like After 90 Days
Be honest about expectations going in. The first audit is the heaviest. After that, maintenance is genuinely light — a few hours a quarter once the tracker and processes are in place.
For a 50 to 200-person company, the typical outcome is 15 to 30% savings on annual SaaS spend. For a 100-person startup spending ₹40 lakh a year across all SaaS tools, that's ₹6 to 12 lakh recovered. Some of that comes from cancellations, some from plan downgrades, some from ITC previously left unclaimed, and some from renegotiated renewal pricing.
The non-financial outcomes are worth noting too. A clean vendor register means your next audit starts from a real baseline. Renewal alerts mean finance stops getting surprised by invoices. ITC fully claimed means your effective SaaS cost is 18% lower than the sticker price on every compliant Indian vendor invoice. And a procurement intake process means the stack stops growing invisibly.
What to do with recovered budget: put it into tools where utilisation is high and the team is constrained. The audit tells you not just where money is wasted, but where it's genuinely being used — that's where incremental investment pays off.
The second quarter is easier. The third is almost automatic.
Frequently asked questions
How long does a SaaS audit actually take for a 100-person company?
Discovery is the heaviest phase and typically takes 1 to 2 weeks if you're doing it manually — pulling card statements, scanning inboxes, and building the initial tracker. With inbox-connected tools like the Easexpense spend audit, the initial inventory surfaces in under 30 minutes, though you still need to cross-reference card statements for charges that don't generate email invoices. The full 90-day plan is designed so the total active work per week stays under 4 hours for one person, with most of that concentrated in the first month. After the first audit, the quarterly maintenance cycle drops to 2 to 3 hours per quarter.
What is shadow IT and how do I find it during a SaaS audit?
Shadow IT is any SaaS tool a team member signed up for using a personal card, a shared team card, or a department budget without central approval or visibility. It's not always malicious — people sign up for tools because they need to get work done and the approval process feels slow. In most 50 to 200-person companies, shadow IT accounts for 20 to 35% of total SaaS spend, which makes it one of the highest-value things to surface in an audit. You find it by scanning email inboxes for recurring invoices (look for anything with "invoice", "receipt", or "subscription confirmed" in the subject) and cross-referencing card statements line by line for recurring charges. Connecting your Google Workspace or Microsoft 365 inbox to a discovery tool automates most of this work.
How do Indian companies handle GST on SaaS subscriptions during an audit?
Every SaaS subscription from an Indian vendor should carry a GST-compliant invoice with your company's GSTIN, allowing you to claim input tax credit at 18%. During an audit, the task is to reconcile which vendors have been issuing compliant invoices and which haven't — if invoices were going to a personal email or a billing entity without the correct GSTIN, those ITC claims are effectively lost. International SaaS vendors fall under the reverse charge mechanism, meaning your company is responsible for self-assessing and remitting GST directly to the government on those subscriptions. Many Indian SMBs are unaware of this obligation for international tools, or have been inconsistent about it, which is a liability your CA should be looped in on during this audit phase. The audit should produce a clear summary of ITC claimed, ITC missed, and any reverse charge obligations outstanding.
Which SaaS subscriptions should I cancel first when cutting spend?
Start with tools where active users are below 20% of licensed seats — these are the clearest cases where you're paying for capacity no one is using. Follow that with duplicate categories: two or more tools doing the same job for the same team. Free trials that converted to paid without anyone noticing are usually safe immediate cuts because there's no team dependency to manage. After those quick wins, move to plan downgrades — tools where the team is on a Pro or Enterprise tier when a lower plan covers their actual usage. Avoid cancelling anything touching customer data, finance workflows, compliance, or security tools without a confirmed replacement already in place, because the cost of a gap in those areas typically exceeds the savings.
How often should a growth-stage startup run a SaaS audit?
Quarterly is the practical answer for companies growing headcount faster than 20% per year, because tool sprawl compounds quickly and annual reviews simply can't keep pace with how fast tools get added. If you have a continuous monitoring tool in place — one that's connected to your inbox and payment layer — you can reduce formal audits to every 6 months, with automated alerts handling the month-to-month hygiene. The first audit is always the hardest because you're starting from incomplete data; subsequent audits start from a maintained tracker and take significantly less time. Companies that treat SaaS spend as a recurring operational review rather than a once-a-year finance project typically find that their stack size stabilises and per-employee SaaS cost drops over time.
Can I run a SaaS audit without dedicated IT or procurement staff?
Yes, and most Indian SMBs do exactly this. The audit is designed to be owned by a CFO, ops manager, or senior finance executive with no IT background — the skills required are business judgment and enough authority to make or push through decisions, not technical skills. Automated discovery tools handle the heavy lifting on inventory, and the tracker framework is simple enough to run in a Google Sheet or Notion table. The manual judgment calls — keep, cut, or renegotiate — require someone who understands how the team actually works, which is a business skill. The main risk of running this without IT support is missing some infrastructure-level tools (cloud instances, DevOps platforms) that finance may not have visibility into, so it's worth a quick check with an engineering lead before closing the discovery phase.
What is a reasonable SaaS spend benchmark for a 50 to 200-person Indian company?
A rough benchmark is ₹8,000 to ₹15,000 per employee per month across all SaaS tools, depending on the company's profile — a product company with heavy AWS and infrastructure spend will sit higher than a services firm running mostly productivity tools. Companies above ₹18,000 per employee per month are usually carrying significant redundancy, overprovisioned enterprise plans, or infrastructure spend that hasn't been optimised. The benchmark also varies by stage: early-stage startups often overspend on tools that made sense at 20 people but haven't been reassessed at 80. If your company is above ₹20,000 per employee per month, a structured audit is almost certainly going to find savings that more than justify the time invested.