Software subscriptions have become one of the fastest-growing and least-managed expense categories for small and mid-size businesses. A decade ago, most companies bought software once and ran it for years. Today, a 50-person business can easily pay for dozens of separate SaaS applications, with new tools adopted constantly by departments, managers, and individual employees who can sign up with nothing more than a credit card and a work email address.
The result is SaaS sprawl: overlapping tools, forgotten subscriptions, orphaned accounts from departed employees, and annual renewals nobody reviews until the charge hits the company card. Zylo's 2026 SaaS Management Index, based on more than 40 million licenses mostly at larger organizations, found companies leave an average of 36 percent of their SaaS licenses unused. Small businesses have smaller stacks, but the causes are the same, and the money is recoverable if you take the time to look. This guide walks through auditing your SaaS stack, eliminating waste, governing new purchases, and right-sizing the tools your team depends on.
Why SaaS Sprawl Happens, and Why It Is Getting Worse
SaaS sprawl doesn't mean your team is reckless. It's a predictable result of how modern software is sold and adopted. When a marketing manager can trial a new analytics tool for free, connect it to your website, and upgrade to a paid plan in fifteen minutes without involving IT or finance, that tool will be in your stack before anyone has compared it with what you already have. Repeat that across sales, operations, HR, finance, and customer success, and tools pile up fast.
Several trends make it worse. Remote and hybrid work, which expanded sharply after 2020, means employees provision their own tools for collaboration and productivity without the visibility of a shared office. Vendor pricing that rewards annual prepayment encourages teams to lock in before they've fully evaluated a tool. Free tiers that convert automatically to paid plans after a trial are designed to go unnoticed. And employee turnover leaves accounts active, data in place, and subscriptions renewing long after the person who signed up has left.
The costs compound. A $30-per-month tool adopted by one employee becomes a $300-per-month line item when it spreads across a team, then keeps renewing every year even as the team's use of it declines. Without central visibility, no one connects the dots.
Step One: Build a Complete SaaS Inventory
You can't manage what you can't see. The first step in any SaaS audit is a complete inventory of every application your business pays for. No single source has the full picture, so you'll need to pull from several.
Financial records are the most reliable starting point. Pull 18 months of company credit card statements and bank records and filter for recurring charges. SaaS subscriptions are easy to spot: they recur on the same date each month or year and come from vendors like "Zoom," "Notion," "Salesforce," "Adobe," or hundreds of less familiar software companies. Flag every recurring charge and build a spreadsheet with the vendor name, monthly equivalent cost, billing cycle, and the cardholder or account owner.
Accounts payable records capture annual invoices that may not appear on card statements: enterprise-tier tools, annual Microsoft 365 or Google Workspace renewals, and any vendor that invoices directly instead of charging a card. Include these in your inventory.
Email receipts and renewal notices are surprisingly useful. Search company inboxes (or ask department heads to) for "receipt," "invoice," "subscription," "renewal," and "your trial is ending." This often turns up tools employees signed up for, used briefly, and forgot, which still charge the company card every month.
Your identity provider or single sign-on platform, if you have one, shows every application employees have signed into with company credentials. Microsoft Entra ID (its application activity report lists every app with sign-in attempts), the Google Workspace admin console (its accessed apps list shows apps that reached company data and how many users each has), and Okta all provide app usage reports. This is the best way to find shadow IT, the tools employees use that never went through approval or procurement. For Chicagoland businesses that haven't centralized identity management yet, this audit is often what prompts them to do it.
Step Two: Analyze Usage and Identify Waste
With a complete inventory in hand, overlay usage data to see where money is being wasted. Unused licenses, oversized tiers, and duplicate tools are the three biggest sources of recoverable spend.
| Waste type | How to spot it | What to do | When |
|---|---|---|---|
| Unused licenses | No login in 60 to 90 days; accounts for people who have left | Deprovision the account, reclaim the seat, transfer any data | Now (monthly plans) or at the next true-up |
| Oversized tiers | Paid features nobody uses when you compare them with the lower plan | Downgrade, or flag for renegotiation | Mid-term if the vendor credits it, otherwise at renewal |
| Duplicate tools | Two or more paid tools doing the same job in different teams | Pick one per function and plan the move | Before the weaker tool's next renewal |
| Forgotten renewals | Annual charges with no named owner on your renewal calendar | Assign an owner and review usage 60 days ahead | Every quarter |
Unused licenses are the most common waste. Most SaaS platforms have admin dashboards showing each user's last login. Pull this for every application with more than five licenses and look for users who haven't logged in within 60 or 90 days. Departed employees whose accounts were never deprovisioned are a reliable source of waste and also a security risk, since a former employee's active credentials are a potential way in. Reclaiming unused licenses usually saves money immediately with no operational impact.
Tier mismatches happen when a business pays for a higher plan than its usage requires. A team using Salesforce Sales Cloud Enterprise for features the Professional tier covers is overspending on every seat. Compare the features your team uses in each platform with what lower tiers provide. Most vendors will downgrade mid-year with a credit applied, though some make you wait until renewal; flag those for renegotiation at the next contract date.
Duplicate tools serve the same main purpose. Common examples in Chicago small businesses: two project management platforms (Asana and Monday.com bought by different teams), two paid video conferencing tools (Zoom and Microsoft Teams), two e-signature services (DocuSign and Adobe Sign), or two password managers. Both are rarely necessary. Usually one was bought because employees didn't know the other existed, or because a team preferred a different tool. Consolidating to one tool per function cuts cost and reduces the context-switching burden on employees.
Step Three: Right-Size and Renegotiate
Next, act on what you found through cancellations, downgrades, and renegotiations. Timing matters. Most SaaS vendors won't prorate refunds mid-contract on annual subscriptions, so your best moment to negotiate is at renewal. Build a renewal calendar with every annual contract date and assign someone to review usage and pricing before each one.
Monthly subscriptions can be cancelled almost immediately with no penalty, so they're the easiest wins. Cancel any tool with no active users, any free-tier tool that converted to paid without anyone using it, and any duplicate the team has agreed to drop.
For annual contracts, prepare for renegotiation. SaaS vendors, especially mid-market players competing for Chicago SMB customers, have a lot of room on pricing, particularly at renewal. If you can credibly show that you're evaluating alternatives, that your usage doesn't justify the current tier, or that you'll commit to a longer term in exchange for a discount, vendors will often offer a discount rather than lose the account. The relationship with your account executive matters: start the conversation before the renewal date, not on the day the invoice arrives. Our IT vendor management guide covers how to prepare for those conversations.
For tools that are valuable but expensive, see whether a narrower license structure (fewer seats, a lower tier) can meet your needs at lower cost. Vendors often prefer a smaller account to a cancellation, which gives you room to negotiate.
Step Four: Establish a SaaS Governance Process
An audit solves today's problem. Governance keeps it from rebuilding over the next 12 months. For Chicagoland businesses that have let SaaS adoption happen ad hoc, the aim is visibility, not bureaucracy: a light process that makes new purchases visible and considered without slowing teams down.
A practical governance framework for small businesses has three parts. First, a software request process: any new SaaS tool above a set cost threshold (typically $50/month or $500/year, at the business's discretion) needs a simple request that records the tool name, cost, intended use, number of users, and whether an existing tool already covers the need. You don't need an approval committee; a shared form that goes to the business owner or operations lead is enough. Just having to write the request down cuts impulse purchases.
Second, a centralized software inventory, kept current in a spreadsheet or dedicated tool, that records every active subscription, its cost, contract dates, owner, and number of users. Update it when tools are added or removed, and review it quarterly to catch renewals before they auto-charge.
Third, an offboarding checklist that includes a SaaS account review for every departing employee. When someone leaves your Chicago business, their accounts in every SaaS tool should be deprovisioned within 24 hours, their licenses reclaimed, and any data they owned transferred to their manager or successor. This step prevents both the security risk of active ex-employee credentials and the waste of paying for accounts no one uses.
Shadow IT: What to Do When Employees Adopt Tools You Did Not Approve
Shadow IT, software employees use without IT or management knowing, is common in businesses without governance. (We cover it in more depth in Shadow IT in small businesses.) How you respond matters. Prohibition rarely works: if employees are using an unsanctioned tool, it usually solves a real problem the sanctioned alternatives don't handle as well. Banning it without addressing that need just pushes the behavior out of sight.
A better approach is discovery followed by evaluation. Tools such as Microsoft Defender for Cloud Apps can discover cloud apps in use on your network, but an audit of card charges and sign-ins catches most of it in a small business. When shadow IT turns up in an audit, ask the employee or team to explain what problem the tool solves and why the sanctioned alternative falls short. Often they simply didn't know a comparable tool was already available, and consolidation solves it. Sometimes the shadow tool really is better for their work, which argues for sanctioning and standardizing it instead of forcing them onto a worse alternative.
For tools handling sensitive data (customer records, financial information, employee data, anything subject to Illinois privacy laws or industry regulations), the evaluation must include a security review of the vendor's data handling practices and certifications. Data stored in a consumer-grade AI tool or a collaboration app with no SOC 2 report or similar independent audit creates real compliance exposure for Chicago businesses in healthcare, financial services, legal, and other regulated industries.
SaaS Management Platforms: When Do You Need One?
Dedicated SaaS management platforms such as Torii, Zylo, and Productiv automate discovery, monitoring, and renewal management by connecting to your financial systems, your identity provider, and SaaS vendor APIs directly. They give you real-time visibility into usage, automatic license reclamation workflows, and renewal alerts. For businesses with large, complex SaaS stacks, they can be worth the cost.
For most Chicagoland small businesses under 100 employees, though, the manual audit and governance approach above is enough, and cheaper than adding another subscription to manage subscriptions. The tipping point for dedicated tooling is usually more than 80 to 100 active SaaS applications, several cost centers or departments with separate software budgets, or a dedicated IT or finance person who can run the platform. Below that, a well-kept spreadsheet and a quarterly review beat a tool nobody has time to configure.
Building a SaaS Rationalization Roadmap
After the initial audit, most businesses have a mix of immediate wins (cancellations and license reclamations that can happen this week) and longer-term consolidation decisions that need more evaluation, stakeholder buy-in, and data migration planning. A rationalization roadmap puts this work in a realistic order.
Tier 1 actions (immediate, no-risk): Cancel tools with zero users. Remove licenses for departed employees. Downgrade monthly plans that are clearly over-tiered.
Tier 2 actions (30–90 days): Consolidate duplicate tools. Prepare renegotiation positions for upcoming renewals. Centralize billing onto a single company card for visibility. Implement the offboarding checklist.
Tier 3 actions (90–180 days): Evaluate platform consolidation opportunities (moving from best-of-breed stack to a platform suite where the quality tradeoff is acceptable). Implement the software request process. Build out the renewal calendar. Conduct a security review of any shadow IT tools handling sensitive data.
For many small businesses, Tier 1 and Tier 2 actions alone recover a noticeable share of the software budget, money that can go to technology that drives growth instead of subscriptions nobody uses. Put the savings, and the renewal calendar, into your annual IT budget so they stick.
Frequently Asked Questions
What is SaaS sprawl and why does it happen to small businesses?
SaaS sprawl is the uncontrolled build-up of software subscriptions across a business: duplicate applications, unused licenses, forgotten trials that converted to paid plans, and tools bought by individual teams without central visibility. It happens because SaaS tools are easy to buy without IT involvement, employee turnover leaves orphaned accounts, and auto-renewing annual contracts rarely get reviewed. Zylo's 2026 SaaS Management Index found organizations leave an average of 36 percent of their SaaS licenses unused, and the same causes apply at small businesses on a smaller scale.
How do I find all the SaaS tools my company is paying for?
A complete SaaS audit pulls from four sources: 18 months of credit card and bank statements filtered for recurring charges, accounts payable records for annual invoices, email inboxes searched for subscription receipts and renewal notices, and your identity provider or single sign-on admin console to see every app employees have signed into. Cross-referencing all four usually turns up tools that no single source shows. For Chicago businesses under 100 employees, a spreadsheet-based audit is usually enough; dedicated SaaS management platforms make sense once you pass 80 to 100 active applications.
What is shadow IT and how does it create risk for small businesses?
Shadow IT is software employees use for work without management or IT knowing, such as tools signed up for with a personal email address or company card outside any approval process. It creates security risk (company data in apps with unknown security), compliance risk (regulated data processed outside your vendor agreements), financial risk (duplicate spending), and operational risk (workflows and data lost when employees leave). The answer is governance rather than prohibition: a light approval process that makes new SaaS adoption visible and evaluated without bureaucracy.
How much do small businesses typically overspend on SaaS?
There is no reliable small-business-only figure, but Zylo's 2026 SaaS Management Index, which draws mostly on larger organizations, found companies leave an average of 36 percent of their SaaS licenses unused. The largest sources are unused licenses (especially from departed employees), tier mismatches (paying for enterprise features the team never uses), duplicate tools bought by different departments, and auto-renewed annual contracts for tools teams stopped using months earlier. A focused audit usually pays for itself in the first year.
When should I consolidate SaaS vendors versus keeping best-of-breed tools?
Consolidation makes sense when you're paying for meaningful feature overlap, when integration complexity is creating manual work, or when a platform you already pay for offers adequate versions of features you're buying separately. Best-of-breed tools are worth keeping when they give you a competitive advantage the consolidated alternative can't match, or when switching costs outweigh the savings. For most Chicagoland SMBs the answer is a mix: consolidate commodity functions around Microsoft 365 or Google Workspace, and keep best-of-breed tools only for functions that directly drive revenue or set you apart.