If you're running finance or ops at an Indian company with 50 to 300 people, you probably already know that your SaaS stack is out of control. The question isn't whether there's waste. It's whether you have a process that can actually surface it, get the right people in a room, and produce decisions that stick.
Most vendor reviews fail not because the team doesn't care, but because the process is built on a stale spreadsheet, has no single owner, and produces a list of "recommendations" that quietly die in someone's inbox. Finance stops trusting the output after the first cycle, and the whole exercise gets deprioritized.
90-day audit plan process that finance teams will actually respect — with the right data inputs, a clear stakeholder map, a decision framework, and a meeting structure you can run in 90 minutes. If you implement even half of what's here, your next renewal conversation with a vendor will feel very different.
Why Most Vendor Reviews Fail Before They Start
AI SaaS license monitoring is stale data. Someone pulls a spreadsheet that was last updated six months ago, vendors have been added or cancelled since then, and the numbers don't match what finance sees in the bank statements. The CFO spends the first 10 minutes of the meeting pointing out discrepancies instead of making decisions.
reclaim unused SaaS licenses's responsibility" are no one's responsibility. IT thinks finance is tracking it. Finance thinks IT is tracking it. Department heads assume someone else is on top of renewals. By the time a ₹6 lakh annual contract auto-renews for a tool that half the team stopped using eight months ago, it's too late to do anything about it for another year.
shadow IT SaaS audit get talked about enough: GST invoice mismatches. Many smaller SaaS vendors, and a surprising number of international ones billing Indian entities, issue invoices without a valid GSTIN or without capturing the buyer's GSTIN. This makes the input tax credit unclaim able. Finance discovers this at year-end when the CA asks for invoice details, and suddenly an otherwise clean review process has a compliance hole in it.
The average Indian SMB renews 60% of its SaaS stack on autopilot, with no utilisation review and no finance sign-off.
Pre-agreeing on decision criteria is the fix most teams skip. Without a defined threshold — say, "any tool with utilisation below 60% gets flagged for renegotiation" — the review becomes an opinion contest. The department head argues the tool is strategic. Finance argues it's too expensive. Nothing gets decided. Building the criteria before the meeting keeps the conversation grounded in data rather than politics.
Watch out: If your vendor list lives in a shared Google Sheet that anyone can edit, you don't have a source of truth. You have a hypothesis. Lock down a single system of record before you run your first review cycle.
What a Quarterly SaaS Vendor Review Actually Covers
A quarterly review isn't the same as an annual contract renewal review. The annual review is about whether to renew at all. The quarterly review is a portfolio health check. You're asking: is our stack working the way it should, are we paying for what we're using, and are there signals we should act on before the next renewal cycle?
The scope for each quarter should be clearly defined in advance. Which vendors fall into this review window? Which contracts are renewing in the next 60 to 90 days? Are there tools that have had a significant change in usage since the last check? You don't need to review every vendor every quarter. A rolling coverage model works well: tier your vendors by spend and criticality, then review Tier 1 every quarter, Tier 2 every 6 months, and Tier 3 annually.
The review itself covers 3 layers. First, cost accuracy: are you being billed what you contracted for, in the right currency, with correct GST treatment? Second, utilisation: how many of your licensed seats are actually in active use? Third, strategic fit: does this tool still solve the problem it was bought to solve, or has the team's workflow changed?
Escalate a vendor from the quarterly cycle to an urgent review if you see a sudden spike in billing, a significant drop in usage (below 40% of seats active), or an upcoming auto-renewal of more than ₹2 lakh that hasn't been reviewed in 12 months.
Run a free SaaS spend audit — find every hidden subscription
The Metrics That Finance Cares About (and How to Pull Them)
Finance doesn't want a feature comparison. Finance wants numbers that map to budget lines. Here's what to bring into the room.
Cost per active seat. Take the total annual spend on a tool and divide it by the number of users who logged in at least once in the last 30 days. If you're paying ₹7,20,000 per year for 60 Slack licenses but only 40 people are active, your real cost per active user is ₹18,000, not ₹12,000. That ₹6,000 gap per person is your renegotiation leverage.
Renewal date vs. last usage date. Any tool where the last active login predates the upcoming renewal by more than 60 days is a cancellation candidate. This sounds obvious, but most teams don't track it. They find out only after the auto-renewal fires.
Duplicate tool detection. How many tools in your stack solve overlapping problems? A 150-person company running both Zoom and Google Meet, both Notion and Confluence, and both HubSpot and Zoho CRM in different departments is paying for the same capability multiple times. The review should surface these pairs explicitly.
GST credit eligibility. For each vendor invoice, check whether it carries a valid GSTIN, whether your company's GSTIN is captured, and whether the service qualifies for input tax credit under GST rules. International SaaS vendors are a particular pain point here. Many don't issue GST-compliant invoices at all, which means you can't claim the 18% credit. Over a ₹50 lakh annual SaaS spend, that's ₹9 lakh of tax you're leaving on the table.
Spend trend over 3 quarters. Is a particular tool's bill growing quarter-on-quarter without a corresponding headcount or usage increase? That's a signal that you've drifted into a higher pricing tier without realising it, or that seat creep is happening without formal approval.
Key takeaway: Finance earns trust when the data is clean, current, and tied to INR figures. Bring utilisation numbers and GST status into the room, not just a vendor list.
Who Belongs in the Room: Stakeholder Map for a Vendor Review
Four roles need to be represented. You don't need four separate people if your company is small, but each role needs a human accountable for it.
The CFO or finance lead owns the budget decision. They need a clean, reconciled number to approve a renewal, cut a tool, or authorise a renegotiation. Don't make them dig through raw data in the meeting. Send them the summary 48 hours ahead.
The department head or tool owner vouches for business value. They're the person who can say "if we cancel this, our support team loses X capability" or "honestly, we switched to a different workflow six months ago and no one uses this anymore." Their input is essential, but they should not have veto power over cost decisions.
The IT or ops lead flags security, integration, and compliance issues. They know which tools have SSO set up, which ones store sensitive data, and which contracts have SLA clauses that matter. In companies without a dedicated IT lead, this role often falls to the CTO or a senior engineer.
The procurement or vendor manager brings the contract terms, SLA history, and renewal leverage. If you've had support issues with a vendor, this is where that history gets used. If you're approaching renewal, this person knows whether the contract has an early-exit clause.
A lot of Indian SMBs at the 50 to 200 employee stage don't have a dedicated IT lead. That gap is real, and it's one of the things our AI CIO is built to fill. It surfaces the data that an IT lead would bring into the room: active user counts, renewal dates, integration dependencies, and shadow IT subscriptions that nobody officially sanctioned.
Building a Decision Framework: Keep, Renegotiate, or Cut
Every vendor in your review gets scored on 3 dimensions: utilisation rate, business criticality, and cost vs. available alternatives. Score each one on a simple 1 to 5 scale. The combined score tells you which bucket the vendor falls into.
Set your thresholds before the meeting. A reasonable starting point: utilisation above 70% and criticality of 4 or 5 means keep. Utilisation between 40% and 70% means renegotiate at renewal. Utilisation below 40% with a criticality of 3 or less means either cut now or put it on a 60-day usage watch with a cancellation trigger.
Vendor pushback on mid-term renegotiation is common. The most effective approach is to come with data, not with a general complaint about the price. "We have 60 licenses and 22 active users in the last 90 days. We'd like to reduce to 25 seats at renewal and we're open to a 2-year commitment at that seat count." That's a conversation most account managers will engage with, because the alternative is a cancellation.
A practical example: a 120-person product company we work with ran this framework for the first time last year. They found ₹4.2 lakh in annual waste across 4 tools with utilisation below 35%, plus 2 duplicate tooling pairs. The CFO approved all 6 decisions in a single 90-minute session because the data was clean and the decision criteria were pre-agreed.
Action: Score every vendor in the review on utilisation, criticality, and cost vs. alternatives before the meeting. Pre-agreed thresholds turn the meeting into a decision session, not a debate.
Document every decision and the rationale behind it. "We kept Zoom at 80 seats because the sales team dependency is high and the cost per active user is ₹9,800 per year" is a sentence that takes 10 seconds to write and saves you 20 minutes of re-litigation at the next review.
Book a 15-minute call to see your SaaS savings data before your next vendor review.
Key takeaway: A scoring matrix with pre-agreed thresholds turns vendor review from a political debate into a structured decision. Document the rationale or you'll relitigate it next quarter.
Using Easexpense Analytics as the Data Layer for Your Review
The hardest part of running the first vendor review is pulling the data. If your SaaS subscriptions are spread across 6 team credit cards, 3 departments, and a handful of invoices buried in someone's inbox, assembling a clean vendor list manually can take a week. That's usually why the review never happens.
Connecting your Google Workspace, Microsoft 365, AWS, Slack, or Zoho account to the Easexpense platform surfaces every active SaaS in your environment in minutes. The spend analytics dashboard shows live license utilisation, billing trends across 3 quarters, and renewal dates — all in one view, without needing to export a CSV from each vendor's admin panel.
Shadow IT is the data gap most reviews miss. A team member signs up for a project management tool on their personal card and expenses it monthly. Another department runs a separate video conferencing subscription because they didn't know the company already had one. These don't show up in your official vendor list. Our mail discovery scans connected inboxes to surface these subscriptions before your review starts, so the vendor list you bring into the meeting is actually complete.
Renewal date alerts built into the dashboard mean you're not relying on a calendar reminder someone set 11 months ago. If a ₹3 lakh contract is renewing in 45 days, it surfaces in the review queue automatically. The team gets notified before the auto-renewal fires, not after.
Run a free SaaS spend audit — find every hidden subscription
The 90-Minute Quarterly Review Meeting: A Practical Agenda
Send the spend summary and utilisation data 48 hours before the meeting. Anyone walking in cold will slow the session down. The pre-read should be one page: total SaaS spend this quarter, top 10 vendors by cost, and a flagged list of tools with upcoming renewals or utilisation below your threshold.
First 20 minutes: triage. Walk the flagged list. Mark each vendor as "needs discussion," "straightforward keep," or "straightforward cut." This sorts the agenda for the rest of the meeting and avoids spending 40 minutes on a ₹8,000/year tool when a ₹12 lakh decision is waiting.
Next 40 minutes: deep dives. Work through the top 5 vendors by spend or renewal proximity. For each one, the department head states the business case, the finance lead states the cost position, and the group applies the scoring framework. A decision or a clear next step comes out of each discussion before moving to the next vendor.
Final 30 minutes: decisions, owners, timelines. Log every decision in writing during the meeting, not afterwards. Assign a named owner for each action — renegotiation outreach, cancellation processing, invoice consolidation for GST claims. Set a date for each action. If a decision can't be made in the room (usually because a key stakeholder is absent or a piece of data is missing), assign someone to get the missing input and schedule a 30-minute follow-up within the week. Don't let it drift.
Turning Review Outputs Into Procurement Actions
A renegotiation email works best when it leads with data. Don't open with "we'd like a discount." Open with your utilisation numbers: "We currently have 50 licensed seats. Active usage in the last 90 days was 31 users. We'd like to align our seat count and pricing to actual usage at renewal." Vendors respond to this kind of specificity because it signals you're prepared and you have options.
Getting finance sign-off on cancellations is easier than most ops teams expect, if the decision is documented with rationale and the utilisation data is attached. What kills the process is going back to the CFO with a verbal summary three weeks after the meeting. Send the decision log by email the day after the review, get a written confirmation, and the cancellation becomes a straightforward admin task instead of a reopened debate.
After the review, consolidate your invoices and check which ones qualify for GST input tax credit. Group them by GSTIN-compliant vs. non-compliant. For the non-compliant ones, contact the vendor or switch to a procurement channel that handles GST-compliant invoicing, which is something our marketplace handles automatically for vendors in our catalog.
Action: Within 48 hours of your vendor review, send the decision log to all stakeholders with named owners and deadlines. Reviews that don't produce written actions within 2 working days rarely produce any actions at all.
Set up renewal alerts before you close the current cycle. If your next quarterly review is in 3 months, you want to know about any contracts renewing in that window at least 45 days before they fire. That's the working time you need to renegotiate or cancel without being held hostage by a 30-day notice clause.
Key takeaway: The review output only matters if it produces written actions with named owners. A well-run 90-minute meeting that generates a clean decision log is worth more than a 3-hour discussion that ends with "let's follow up."
Making the First Review Stick: Common Mistakes to Avoid
Don't try to review every vendor in the first session. Trying to cover a 40-tool stack in one meeting produces fatigue, poor decisions, and a team that won't show up for the next one. Start with the top 10 by spend. Build the habit before you expand the scope.
Assign a single DRI (directly responsible individual) for follow-through. This is the person who tracks whether the renegotiation email went out, whether the cancellation was processed, and whether the next review is scheduled. Without a DRI, actions drift.
Don't skip the finance sign-off step to save time. Getting written approval from the CFO for cuts and renegotiations takes 5 minutes if you've done the meeting right. Skipping it and acting unilaterally might save you a conversation today and cost you the credibility to run future reviews.
Frame the review as a portfolio health check, not a cost-cutting exercise. The goal is to make sure every rupee you're spending on SaaS is working. Some tools will get renewed at the same price because they're genuinely valuable. Others will get cut or renegotiated. Both outcomes are good. The team needs to feel that the process serves them, not just that it exists to justify cancellations.
Finally, before you close the current review, put the next one in the calendar. Set the date, book the room or the video call, and assign the pre-read owner. Reviews that end without scheduling the next one have a very low survival rate past the second cycle.
Frequently asked questions
How often should a company conduct a SaaS vendor review?
Quarterly is the practical standard for companies running 20 or more SaaS tools. A quarterly cadence catches renewals before they auto-fire and keeps utilisation data fresh enough to act on. Annual reviews are too slow for a stack that changes every few months — tools get added, team sizes shift, and spending patterns drift in ways that an annual snapshot simply won't catch in time. For Tier 1 vendors (your highest-spend, most business-critical tools), a quarterly review is non-negotiable. Tier 2 and Tier 3 vendors can follow a 6-month or annual cadence once your process is mature.
What data do I need before starting a SaaS vendor review process?
At minimum: a complete list of active subscriptions, the monthly or annual cost for each, the renewal date, and a usage or login report from the last 90 days. If you can't pull this data quickly, a tool like Easexpense can surface it by scanning your work inbox or connecting to Google Workspace or Microsoft 365. You'll also want GST invoice status for each vendor — whether invoices carry a valid GSTIN and capture your company's GSTIN. Missing that data means you can't do a proper credit eligibility audit as part of the review.
How do I calculate cost per active user for a SaaS tool?
Divide the total annual spend on the tool by the number of users who logged in at least once in the last 30 days. If you're paying ₹6,00,000 per year for 50 licenses but only 30 people actually used the tool, your real cost per active user is ₹20,000, not ₹12,000. That gap of ₹8,000 per inactive seat, multiplied across 20 seats, is ₹1,60,000 in annual waste from one tool alone. This is the renegotiation lever. Bring this number to the vendor at renewal, and most account managers will engage on a seat reduction rather than risk losing the account entirely.
What is shadow IT and how does it affect a vendor review?
Shadow IT is any software a team member subscribed to without going through IT or procurement, often on a personal or departmental card. It doesn't show up in your official vendor list, so it gets skipped in reviews entirely. The risk is twofold: you're paying for capabilities you already have through an official tool, and you have no visibility into data storage, security, or compliance for these subscriptions. Tools like Easexpense surface these subscriptions by scanning invoices in connected inboxes, giving you a complete picture before the review starts so you're not working from a vendor list that's missing 20% of actual spend.
How do I get CFO buy-in for a SaaS vendor review process?
Come to the CFO with numbers, not a proposal. Show the current total SaaS spend, the estimated waste from unused licenses, and a one-page view of upcoming renewals in the next 90 days. When the CFO can see that an unreviewed auto-renewal will charge ₹8 lakh next month for a tool with 40% active utilisation, the case for a structured review process makes itself. Frame the first review as a diagnostic, not a commitment to a new process. Once the CFO sees the output — decisions made, savings identified, invoices cleaned up — the second review practically sells itself.
Can I claim GST input tax credit on SaaS subscriptions in India?
Yes, provided the vendor issues a GST-compliant invoice with your company's GSTIN and the software is used for business purposes. The common failure point is that many international SaaS vendors, or smaller Indian vendors, issue invoices without a valid GSTIN or without capturing the buyer's GSTIN, making the input tax credit unclaim able. At an 18% GST rate, this matters significantly at scale — on a ₹50 lakh annual SaaS spend, that's ₹9 lakh you either claim or leave on the table. A vendor review is the right time to audit which of your invoices actually qualify and to put pressure on vendors who aren't issuing compliant invoices.
What is a reasonable SaaS licence utilisation rate before renegotiating?
A utilisation rate below 70% is generally a strong signal to renegotiate the number of seats at renewal. Below 50% warrants a conversation mid-term if the contract allows it, particularly for high-spend tools where the waste in INR terms justifies the vendor call. Above 90% utilisation suggests you may need to negotiate an expansion, and you should ideally do that before the vendor knows how dependent you are on the product — because that's when you have leverage to lock in a better per-seat rate for the additional licenses. Track this metric quarterly so you're never in a renewal conversation without a clear utilisation baseline to anchor on.