Last year, a 200-person company I worked with discovered they were paying for three different project management tools. Not intentionally. Marketing used Asana. Engineering used Jira. Sales used Monday.com. Nobody talked to each other.
Cost? $47,000 annually. For tools doing essentially the same job.
They're not unusual. Gartner research shows organizations waste between 25-35% of their software spending. That's real money. For a company spending $500K on software, that's $125K-175K disappearing every year.
But here's the trap: most "cost-cutting" audits break things. They rip out tools people depend on. They ignore why duplicates exist in the first place. Three months later, the shadow IT creeps back.
This guide takes a different approach. We'll find the waste without torching the productivity. Because the goal isn't spending less—it's spending smarter.
Step 1: Map Everything (Yes, Everything)
You can't fix what you can't see.
The single biggest reason tech stack audits fail? Incomplete inventories. Finance knows what's on the corporate card. IT knows what they've approved. But nobody knows about the tools being expensed through department budgets, the free trials that auto-converted, or the contracts signed by managers with purchasing authority.
Start with your expense reports. Pull 12 months of credit card statements, vendor payments, and reimbursements. Search for recurring charges. Flag anything that looks like software.
Then survey your team. Not a long form—just three questions: What tools do you use daily? Weekly? What tools do you pay for that aren't on your company card? You'll be surprised what surfaces.
Finally, check Single Sign-On logs and browser extensions. If you use Okta, Google Workspace, or Microsoft 365, you have usage data sitting in admin consoles. Export it.
Most companies discover 30-40% more tools than they expected at this stage. That's normal. It's also why this step matters.
Step 2: Categorize by Function, Not Vendor
Here's where most audits go wrong. They list tools alphabetically or by cost. Useless.
Instead, group by what each tool does. Communication tools. Project management. CRM. File storage. Analytics. Design. Development. Finance.
Now look for overlap.
Three communication tools? (Slack, Microsoft Teams, and that Discord server engineering set up.) That's overlap. Two CRMs? Overlap. Both Dropbox and Google Drive? Overlap.
But—and this is crucial—overlap isn't automatically waste.
Sometimes departments have legitimate reasons for different tools. Sales needs different CRM functionality than support. Marketing needs design tools engineers don't. Before you consolidate anything, understand why the duplication exists.
Ask users directly: "If we replaced Tool A with Tool B, what would you lose?" The answers will surprise you. Sometimes the "redundant" tool has one killer feature the primary option lacks.
Step 3: Measure Actual Usage (Not Licenses)
You're paying for 50 Salesforce licenses. Are 50 people actually using it?
This question makes finance teams nervous. The answer is almost always no.
Here's what real usage analysis looks like. Log into admin consoles. Export user activity reports. Look for last login dates, actions taken, features used.
Specifically, look for: Users who haven't logged in for 90+ days. Users who log in but don't do anything meaningful. Enterprise licenses for people who only use basic features.
I recently helped a company cut their CRM spending by 34%. They had 80 paid seats. Actual active users? 52. Another 15 logged in occasionally but only looked at dashboards—they didn't need full licenses.
The savings weren't just licenses. Fewer users meant less complexity. Less training. Less support overhead.
One warning: before you cut someone's access, ask them first. Sometimes "inactive" users access critical workflows quarterly. You don't want to discover that during end-of-quarter reporting.
Step 4: Identify Integration Dependencies
This is where cost-cutting audits become dangerous.
You find a tool that looks redundant. You remove it. Two weeks later, three other systems break because they depended on that tool's API. Nobody documented the integration. Now you're in crisis mode.
Before removing any tool, map its connections. Does it push data to other systems? Does it receive data? Do other tools authenticate through it?
Check Zapier, Make (Integromat), and native integration settings. Talk to whoever set up the workflows. Audit API keys.
I've seen companies spend more fixing broken integrations than they saved from removing the original tool. Document first. Cut second.
Sometimes the "wasteful" tool is actually infrastructure glue. It looks unnecessary on its own but keeps everything else connected. Those tools earn their cost even if nobody uses them directly.
Step 5: Negotiate Before You Eliminate
Here's a secret vendors don't advertise: almost every enterprise SaaS contract is negotiable.
Before you cancel anything, call your account manager. Tell them you're evaluating alternatives. Ask what they can offer.
Tactics that work: Request the price per user you found on their website (enterprise contracts often charge more). Ask about annual vs. monthly billing discounts—usually 15-20% difference. Negotiate multi-year deals if you're confident in the tool. Bundle products from the same vendor.
I've seen companies save 25-40% on existing contracts just by asking. Vendors want to keep customers. Retention is cheaper than acquisition. Use that leverage.
One company I advised reduced their HubSpot bill by $18,000 annually. Same features. Same users. They just asked for the same deal their smaller competitors were getting.
The worst they can say is no. Usually they don't.
Step 6: Plan the Consolidation Carefully
You've identified the waste. You've negotiated what you're keeping. Now comes the hard part: actually removing tools without destroying productivity.
Never rip and replace on a Friday.
Give affected users 30 days notice minimum. Explain why the change is happening—cost savings they can appreciate, not "management decided." Provide migration support. Document new workflows.
Run parallel systems during transition. Yes, it means paying for both tools temporarily. That's cheaper than the chaos of a hard cutover.
Measure before and after. If productivity drops, you need to know immediately. Have a rollback plan.
The best consolidations feel invisible to end users. The worst ones generate IT tickets for months. The difference is preparation.
Make This a Quarterly Habit
One-time audits don't work. Tech stacks grow back. New tools sneak in. Usage patterns change.
Build a quarterly review into your calendar. It doesn't need to be this comprehensive—just a quick check on usage reports, new subscriptions, and upcoming renewals.
Create a simple approval process for new tools. Not bureaucracy—just visibility. "Before you buy software, check if we already have something that does this." A 5-minute form saves thousands annually.
The companies that manage software costs well treat it like any other budget. Regular reviews. Clear ownership. Accountability.
Your tech stack should work for you, not the other way around. Audit it. Fix it. Then keep it fixed.
The 29% you're probably wasting? That's not just cost savings. It's budget for the tools you actually need but couldn't afford. Go find it.