SaaS Tool Consolidation: How to Cut Your Tech Stack Without Breaking Workflows
Step-by-step guide to consolidating your SaaS stack. Covers audit frameworks, migration playbooks, vendor negotiation, and how to cut costs without losing productivity.
Whether you're looking for an angel investor, a growth advisor, or just want to connect — I'm always open to great ideas.
Get in TouchAI, startups & growth insights. No spam.
TL;DR: The average enterprise runs 200+ SaaS applications and spends $1,800 per employee per year on software. Budget pressure, security overhead, and AI platform bundling are forcing a reckoning. This guide walks you through how to audit your stack, score tools for elimination, manage migration risk without destroying productivity, and negotiate vendors into better deals — whether you are a buyer trying to cut costs or a founder trying to survive the consolidation wave.
I have done stack audits for companies ranging from 15-person seed-stage startups to mid-market firms with 400 employees. The pattern is identical every time: nobody knows what they are actually paying for.
The typical 50-person startup has between 60 and 120 active SaaS subscriptions. Maybe 20 of them are sanctioned by IT or finance. The rest crept in through individual credit cards, department budgets, or free trials that auto-converted. By the time someone runs the audit, they find four project management tools, three video conferencing platforms, two CRMs (because one team "prefers" the old one), and a $600/month subscription to a tool whose champion left eight months ago.
The numbers are not small. Zylo's annual SaaS Management Index pegs median SaaS spend at $1,800 per employee per year, with enterprise organizations averaging over $200 per employee per month. BetterCloud's State of SaaS report found that the average organization manages 130 SaaS applications, with enterprises often exceeding 300. Gartner forecasts worldwide SaaS spending will reach $247 billion in 2025, up from $197 billion in 2023.
Three dynamics created this sprawl:
The free trial problem. SaaS vendors perfected the frictionless free tier. Signing up requires only an email address. Upgrading to paid requires only a credit card. No procurement process, no IT review, no security clearance. An individual contributor can spin up a new tool in three minutes and expense it without approval. Multiply that across 100 employees over three years and you have a catastrophe.
The shadow IT explosion. During remote-first acceleration in 2020-2021, IT departments essentially gave up trying to control software adoption. Employees needed tools to work, procurement cycles were too slow, and the answer was "figure it out." That permissiveness created layers of technical debt that are still being unwound.
The best-of-breed delusion. For a decade, the conventional wisdom was to buy the best point solution in each category. Best email marketing tool. Best SEO platform. Best project management app. Best customer support software. In theory this sounds reasonable. In practice it creates a 200-tool stack where nothing integrates properly, data lives in 40 different silos, and your team spends 20% of their time manually moving information between systems.
The sprawl problem is not just a cost issue. It is a security issue, a productivity issue, and increasingly a competitive issue.
Every additional tool is an attack surface. Every SaaS vendor you connect to your Google Workspace or Okta is a potential breach vector. The average SaaS application requests access to files, calendar, email, and contacts. Multiply that across 150 applications and you have an unmanageable risk profile.
The productivity cost is harder to quantify but real. Context switching between tools is cognitively expensive. Every time an employee has to leave Slack, open their project management tool, pull data from the analytics platform, and paste it into a report, they are losing time and mental bandwidth that could go toward actual work.
The reckoning was inevitable. What changed is the pace.
Three forces converged between 2023 and 2026 to make consolidation urgent rather than aspirational.
Budget pressure from the efficiency era. The 2022 SaaS correction and subsequent capital tightening forced companies to treat software spend as a real cost center for the first time. When venture capital was cheap and growth was the only metric, nobody cared that the company was spending $2,000 per employee per year on SaaS. When the CFO starts requiring a positive contribution margin and a path to profitability, that $2,000 line item suddenly matters. I have seen CFOs institute software approval freezes, mandate quarterly stack reviews, and in several cases, centralize all SaaS purchasing under a single procurement function. The era of expensing random tools is ending.
Security and compliance pressure. The SEC cyber disclosure rules, GDPR enforcement actions, and SOC 2 requirements have made shadow IT genuinely dangerous rather than just annoying. When a security audit reveals 150 SaaS applications with OAuth access to company data, and only 40 of them are in the approved vendor list, that is a material risk. CISOs are now actively pushing for stack consolidation as a security measure, not just a cost measure. Every eliminated vendor is one fewer potential data breach.
AI bundling is collapsing point solution value propositions. This is the most disruptive force. Microsoft Copilot bakes AI writing, summarization, and analysis directly into Word, Excel, PowerPoint, Teams, and Outlook. Google Workspace Duet AI does the same. Notion AI is inside your wiki. Linear AI is inside your project tracker. When the platform you already pay for starts doing 70% of what your $200/month standalone tool does, the standalone tool loses its justification. The AI layer is effectively being bundled into the suite, and point solutions built on single-function value propositions are being commoditized faster than anyone anticipated.
The result is a buyer's market for consolidation. Companies are actively looking to cut 30-40% of their SaaS spend. Vendors who understand this dynamic are bundling aggressively, offering multi-product discounts, and acquiring point solutions to expand their suite. Vendors who do not understand this dynamic are churning customers to their larger platform competitors.
For context on how this fits into broader SaaS spending patterns, see SaaS Metrics Benchmarks 2026 — particularly the section on gross margin benchmarks by product type, which shows how compression is hitting different SaaS categories.
Most consolidation efforts fail not because companies make the wrong decisions, but because they try to skip phases. They see the cost savings, move too fast, break workflows, and cause a backlash that sets the program back by six months.
The framework I use has four phases, each with a distinct output:
| Phase | Name | Output | Duration |
|---|---|---|---|
| 1 | Audit | Complete stack inventory with spend, usage, and owner data | 2-4 weeks |
| 2 | Score | Ranked elimination list with justification | 1-2 weeks |
| 3 | Migrate | Execution plan with dependencies, timelines, and fallbacks | Ongoing |
| 4 | Govern | Process to prevent re-sprawl | Permanent |
Phase 4 is the one most companies skip and then wonder why their stack is bloated again 18 months later.
The audit phase is where most programs fail to get started because it feels overwhelming. The actual methodology is straightforward. You need four data sources:
1. Financial data. Pull every SaaS subscription from your accounting system. Search for recurring charges in your credit card statements, bank accounts, and expense reports. Look for subscription keywords: monthly, annual, per seat, per user, per month, per year. If you use a SaaS management platform like Zylo, Torii, or Productiv, they will auto-discover most subscriptions through expense integration. If not, you will need to do this manually or write a simple script to parse transactions.
2. Identity provider data. Export your SSO/IdP data (Okta, Google Workspace, Azure AD) to see which applications have active OAuth connections. This catches tools that bypass finance by using individual credit cards but still connect to company identity.
3. Usage data. For tools under SSO, most IdPs provide login frequency data. For tools not under SSO, you will need to survey teams or use browser extension-based discovery tools. Productiv is particularly good at this — it can measure actual feature engagement, not just login frequency, which matters because a tool can have 100% login rates and still be used for only 10% of its functionality.
4. Owner data. Every tool should have a named owner: the person responsible for the subscription, renewal, and team adoption. Ownerless tools are strong elimination candidates. If nobody can name who is responsible for a tool when you ask, that is your answer.
Build your inventory in a spreadsheet with these columns at minimum:
| Column | Notes |
|---|---|
| Tool name | Full product name, not abbreviation |
| Category | CRM, project mgmt, analytics, etc. |
| Annual cost | Fully loaded including overages |
| Seat count | Purchased vs active |
| Owner | Named individual, not department |
| Monthly active users | From IdP or usage tool |
| Integration count | Number of other tools connected to it |
| Contract end date | Renewal date for negotiation timing |
| Elimination score | Fill in during Phase 2 |
When you do this for the first time, expect to find at least 20% more tools than anyone thought you had. Expect to find tools with zero active users still billing. Expect to find duplicate functions across multiple tools. The audit is almost always shocking.
Seat waste. Purchase 100 seats, use 40. This is endemic. SaaS vendors make per-seat contracts difficult to downsize mid-term specifically because of this. Flag every tool where active users are below 60% of purchased seats.
Category overlap. When you categorize tools, you will often find three or four tools doing the same basic job. Three tools labeled "team communication," two labeled "document management," four labeled "analytics." This is where consolidation opportunity concentrates.
Zombie subscriptions. Tools where the last login was more than 60 days ago across all users. These are safe eliminations — nobody will complain.
Free-to-paid escalation traps. Tools that started free and auto-upgraded to paid as seat counts grew. These are often tools where nobody made an active buying decision and therefore nobody has a strong attachment to keeping.
Not all tools are equally easy or equally valuable to eliminate. The 80/20 principle applies here: roughly 20% of your tools will require 80% of the effort to evaluate and migrate. Correctly identifying which tools fall into which category is what makes a consolidation program succeed or fail.
I score tools on five dimensions, each rated 1-5:
Strategic necessity (1 = not at all necessary, 5 = core to how we operate). Is this tool in the critical path for revenue-generating work? A CRM is a 5. A tool one person uses to generate a report once a month is a 1.
Replaceability (1 = easily replaced, 5 = extremely difficult to replace). Can an existing tool in your stack absorb this function? Does a platform you already use have this feature? Replaceability scores drive consolidation decisions more than any other dimension.
Integration depth (1 = standalone, 5 = deeply embedded). How many other tools depend on data flowing through this tool? A tool at the center of a 10-tool integration web is expensive to remove. A standalone tool used by one person is cheap.
User adoption (1 = low adoption/low sentiment, 5 = high adoption/high sentiment). Usage data tells you current behavior. User sentiment tells you what will happen when you try to remove it. High-usage, high-sentiment tools will generate backlash if eliminated without a credible replacement. Low-usage, low-sentiment tools can be eliminated with a simple email.
Cost efficiency (1 = very expensive for value delivered, 5 = excellent value). Cost per active user relative to what you are getting. A $50/month tool used by 10 people daily is more defensible than a $2,000/month tool used by 2 people weekly.
The elimination score is a weighted average: (Strategic Necessity × 0.3) + (Replaceability × 0.25) + (Integration Depth × 0.2) + (User Adoption × 0.15) + (Cost Efficiency × 0.1). Invert it — tools with low scores are elimination candidates.
This scoring surface three categories:
Immediate eliminations (score < 2.0): Low usage, low integration, easily replaced, not strategic. Cut these first. Expect no pushback. These represent roughly 20-30% of most stacks.
Consolidation targets (score 2.0-3.5): Function can be absorbed by a platform bet, but requires active migration. These need a plan. They represent 40-50% of stacks and contain most of the cost savings.
Keepers (score > 3.5): High strategic value, deeply integrated, or irreplaceable in category. Negotiate harder at renewal, but do not eliminate without a very strong case. These represent 20-30% of tools.
The central strategic decision in any consolidation program is which platforms to consolidate around and which point solutions are worth keeping.
The premise is simple: every suite you adopt reduces the number of integrations you have to maintain, the number of vendors you have to manage, and the number of data silos you have to reconcile. The cost is that suites rarely beat the best point solution in any individual category. You are accepting "good enough" across 10 functions in exchange for integration, simplicity, and lower total cost.
The right answer depends on your maturity and category.
For most companies under 200 employees, I recommend anchoring around four platforms and filling gaps only where the platform's native capability is genuinely inadequate:
Communication and collaboration: Slack or Microsoft Teams. If you are Microsoft-heavy (Office 365, Azure), Teams makes sense as the hub. If you are Google Workspace-native, Slack often integrates better and has stronger third-party app support. Do not run both.
CRM and revenue operations: HubSpot or Salesforce. HubSpot's suite (Marketing Hub, Sales Hub, Service Hub, CMS Hub, Operations Hub) has become genuinely competitive at mid-market. For companies under $50M ARR, HubSpot's total cost of ownership is typically lower than Salesforce plus five point solutions for individual functions. The calculus flips at enterprise scale and complexity.
Project management and documentation: This is the messiest category and the site of the most aggressive platform wars. Notion, Linear, Asana, Monday, Jira, Confluence, and Coda are all competing for the same budget. My current recommendation is to separate execution (task tracking, sprints, roadmaps) from documentation (wikis, SOPs, meeting notes) only if your engineering team has strong opinions about their PM tooling. For non-engineering teams, Notion consolidates both functions adequately. For engineering, Linear for execution plus Notion for docs is a clean split.
Data and analytics: Looker, Mode, Metabase, or equivalent BI platform as your single source of truth. Resist the temptation to let teams build their own dashboards in five different tools. One analytics platform, governed carefully, eliminates more duplicated work than almost any other consolidation decision.
Point solutions retain their value when:
The gap is material and measurable. If the platform's native email marketing capability delivers 30% lower open rates than your specialized tool, that is real revenue impact you can quantify. That justifies keeping the point solution.
The switching cost exceeds the savings. Migrating three years of email campaign history, custom templates, and audience segments is not free. If the consolidation savings over 24 months are less than the migration cost and the productivity hit during transition, the math does not support consolidation.
The platform vendor has a weak roadmap in that category. Platforms bundle features to prevent churn, not because they are passionate about building best-in-class functionality in every category. If the platform version of a critical tool has been stagnant for two years, that is a signal.
Regulatory requirements demand specialized solutions. Certain industries have compliance requirements that generic platforms cannot meet. A healthcare company may need a specialized HIPAA-compliant communication tool regardless of what their collaboration suite offers.
Migration is where consolidation programs die. The failure mode is almost always the same: the decision to eliminate a tool is made at the leadership level, communicated poorly, executed without adequate training, and results in a productivity dip that generates enough organizational backlash to stall or reverse the entire program.
Managing migration risk requires treating it like a software deployment, not an administrative task.
Data portability audit. Before you commit to eliminating any tool, confirm that your data can be exported in a usable format. This sounds obvious. It is routinely skipped. SaaS vendors have strong incentives to make data export difficult. Some tools export to CSV formats that require manual cleanup. Some export to proprietary formats that cannot be imported elsewhere. Some have export limitations baked into pricing tiers. Audit this before you announce anything.
Workflow dependency mapping. For each tool you plan to eliminate, document every workflow that depends on it. Not just direct use — also Zapier/Make automations, API integrations, and Slack notifications triggered by that tool. I have seen consolidation efforts stall because eliminating a "minor" tool broke a critical automation nobody had documented.
Training and change management plan. Every migration needs a named migration lead, a communication plan, a training timeline, and a feedback channel. Employees who feel like consolidation is being done to them will resist. Employees who feel like they were consulted and trained will adapt. The difference is entirely in how you run the communication.
Parallel running period. For high-impact tool migrations, run the old tool and the new tool in parallel for 30-60 days before fully cutting off the old tool. Yes, this temporarily increases cost. It dramatically reduces the risk of a critical workflow breaking and nobody catching it until it causes real damage.
Rollback plan. Define in advance under what conditions you would pause or reverse a migration. "We will revert if adoption of the new tool is below 40% after 30 days" is a specific trigger. "We will revert if it is not working" is not.
Sequence migrations from lowest risk to highest risk, not from highest savings to lowest savings. The temptation is to cut the most expensive tool first. The correct approach is to build organizational confidence in the consolidation program by winning easy migrations first.
Zombie tools and duplicate function tools first. Low-touch migrated second. Deeply integrated, high-impact tools last.
Consolidation creates negotiating leverage that most buyers fail to use. Here is how to use it.
Time your negotiations with renewals. The best time to negotiate any SaaS contract is 90 days before renewal, not at renewal. At renewal, you are negotiating under time pressure. At 90 days, you have options. Start the conversation early.
Use consolidation as leverage in both directions. When negotiating with a vendor you plan to keep and potentially expand, tell them explicitly: "We are consolidating our stack and you are on the shortlist for expanded use. We are currently using your product for X. If pricing works, we would move Y and Z from competitors to you as well." Multi-product commitments are the fastest path to significant discounts — 20-40% is common.
When negotiating with a vendor you are considering cutting, tell them: "We are consolidating our stack. Your product is on the elimination list. We need you to justify continued spend by either improving the value you deliver or adjusting the pricing to reflect our actual usage." The threat of churn is real, and SaaS companies will often restructure contracts significantly to avoid it, especially in renewal cycles.
Negotiate on multiples, not percentages. Asking for a 10% discount is a small conversation. Asking for a three-year commitment at a fixed price in exchange for adding 100 seats from a competing product is a different conversation entirely. The vendor's finance team approves the first in an email. The second requires a sales call, but the outcome is orders of magnitude better.
Use competitor pricing data. Know what the competing product costs. Not the list price — the actual price companies are paying, which is often 20-40% below list due to standard discounting. Vendors.com, G2 reviews with pricing data, and communities like Pavilion or SaaS Insider are good sources. When you tell a vendor that their competitor is offering comparable functionality at 35% lower cost, the conversation changes immediately.
Lock in pricing escalation caps. Most SaaS contracts allow vendors to raise prices 5-10% per year without renegotiation. When signing multi-year agreements, negotiate a cap of 3% or less. This seems small in year one. Over three years on a $100,000 contract, the difference between a 3% cap and a 7% cap is $24,000.
Demand usage-based pricing where possible. If you are paying for 200 seats but using 130, that is a 35% waste. Many vendors will not proactively offer to resize you, but most will agree to right-size in exchange for a longer term commitment. Always ask.
Once you have completed your first audit manually, the question is how to automate ongoing visibility. Three platforms have emerged as the category leaders:
Zylo is the enterprise standard for SaaS management. It discovers subscriptions through financial system integration, tracks usage through SSO and direct integrations with major SaaS vendors, and provides benchmarking data comparing your per-seat costs against what comparable companies are paying. Zylo's benchmark database is particularly valuable for negotiation prep. Pricing is enterprise ($50K+ per year), which means it is most appropriate for companies with $5M+ in annual SaaS spend.
Productiv differentiates on usage analytics. While other platforms track whether someone logged in, Productiv tracks which features they actually used. This matters because a tool can have 90% login rates but 20% feature adoption — meaning people are logging in, not using it, and getting value from something else. Productiv's engagement data makes elimination decisions much more defensible. Pricing is mid-enterprise ($20-50K per year).
Torii is the most accessible option for mid-market companies. It has strong auto-discovery through expense integration and IdP integration, solid workflow automation for license reclamation (automatically notifying users when their subscription is about to be cancelled and giving them the option to justify continued access), and a cleaner self-service interface than the enterprise platforms. Pricing is $15-30K per year, making it accessible for companies with 100+ employees.
For companies under 100 employees, a combination of manual quarterly audits, Google Workspace admin console data, and a spreadsheet is often sufficient. The platforms pay for themselves once SaaS spend exceeds $1M per year.
If you are building a SaaS product rather than buying one, the consolidation wave is the single most important trend you need to understand.
The companies getting hurt are the ones that built point solutions in categories that platforms are now absorbing. If you built a standalone meeting notes tool, Microsoft Copilot and Notion AI now do what you do. If you built a standalone proposal management tool, HubSpot and Salesforce now have native proposal functionality. If you built a standalone customer success platform, your CRM vendor's expansion product line is coming for you.
The consolidation math is brutal for standalone tools. A buyer running a stack audit sees your $400/month product and asks: can the platform I already pay $2,000/month for do this? If the platform does it at 70% of your quality, the economics favor the platform. You are not being evaluated against a standalone competitor. You are being evaluated against "good enough, already paid for."
This does not mean point solutions cannot survive. They can. But it requires a different strategy than building the best single-function product.
If you are building a SaaS product in 2026, the question is not whether platforms will try to absorb your function. They will. The question is whether your product has structural characteristics that make it difficult to absorb.
Four characteristics create consolidation resistance:
Integration depth. The more deeply embedded your product is in a customer's workflow — the more other tools talk to it, the more data flows through it, the more automations depend on it — the more expensive it is to remove. Build integrations aggressively, not just with major platforms but with all the tools your target customer uses. Every integration is a switching cost.
Data moat. Products that accumulate unique, irreplaceable customer data are extremely hard to displace. Historical records, trained models on customer-specific data, benchmark datasets, audit trails — these are data assets that cannot be migrated away without real loss. Build your product to create these assets from day one.
Workflow ownership. There is a difference between being a tool in a workflow and owning the workflow. Owning the workflow means your product is the system of record for a critical process, the thing your customer thinks of first when that process comes up. Systems of record are extremely sticky. Features in other products are not. Define clearly which workflow you own and go deep on owning it completely, rather than broad across multiple workflows.
Category verticalization. Generic platforms beat generic point solutions. But vertical-specific platforms that understand the nuances of a particular industry or use case are much harder to displace with a generic suite. If you build the best-in-class tool for a specific workflow in a specific industry — say, compliance tracking for community banks, or content workflow management for media companies — the generic platform cannot replicate your vertical-specific functionality or your industry relationships.
The founders who will survive the consolidation wave are the ones who got deep in a specific workflow, in a specific vertical, with a specific customer type — and built enough integration depth and data moat to make displacement genuinely painful.
For a broader view of growth strategy in a capital-efficient environment, the bootstrapped startup growth strategy guide has useful frameworks that apply here as well.
The platform layer is itself in the middle of a competitive war that is worth understanding, because where the bundle wars land will determine which point solutions survive and which get absorbed.
HubSpot vs Salesforce. This is the defining mid-market CRM battle. HubSpot's strategy has been to expand from marketing automation into sales, service, CMS, and operations — building a full customer platform. Salesforce's response has been acquisition (Slack, Tableau, Mulesoft) and AI bundling (Einstein AI). For companies under $50M ARR and 500 employees, HubSpot's total cost of ownership advantage is significant — often $200-400K per year when you account for the point solutions Salesforce customers typically add. Above $100M ARR, Salesforce's enterprise customization and deep integrations justify the premium for most companies.
Notion vs the document/wiki world. Notion has displaced Confluence at hundreds of companies by offering a more flexible, developer-friendly workspace. But Notion is now facing consolidation pressure from both above (Microsoft Copilot and Teams baking in documentation) and below (Linear adding documentation features to capture the engineering workflow). Notion's response — deep AI integration and the Notion AI product — is the right instinct but has not yet produced a decisive advantage.
Microsoft 365 vs Google Workspace. The foundational layer of most companies' stacks is either Microsoft or Google. Microsoft has played the consolidation angle more aggressively with Copilot, baking AI into every product in the suite and giving enterprises a reason to pay premium pricing for functionality they previously bought from point solutions. Google Workspace Duet AI has followed. For most companies, the question is not which platform to use but how deeply to standardize on the suite's native features before buying additional tools.
The verticalization play. A less visible but important bundle war is happening in vertical SaaS — industry-specific platforms that absorb horizontal point solutions by offering a vertically integrated experience. Veeva in life sciences, Procore in construction, Mindbody in wellness. These vertical platforms are often immune to the horizontal bundle wars because they offer industry-specific workflows that generic platforms cannot match.
Understanding where your stack sits relative to these bundle wars tells you which of your vendor relationships are stable and which are likely to see significant price disruption or product change in the next 18 months.
Consolidation decisions need financial justification, especially when they involve migration costs and productivity risk. Here is the framework I use:
| Line Item | Current State | Future State | Annual Savings |
|---|---|---|---|
| Eliminated tool subscriptions | List annual spend | $0 | Full amount |
| Right-sized seat counts | Current seat cost | Reduced seat cost | Difference |
| Multi-product discounts on kept tools | Current pricing | Negotiated pricing | Discount amount |
| IT/ops overhead reduction | Hours × fully loaded rate | Estimated reduction | Time value |
| Total direct savings | Sum |
| Cost Item | Estimate | Notes |
|---|---|---|
| IT migration labor | Hours × rate | Data export, import, integration rebuild |
| Training and change management | Hours × rate | Training sessions, documentation |
| Parallel running period | Additional tool cost × weeks | Running old and new tool simultaneously |
| Productivity dip | FTEs × % productivity loss × duration | Estimate at 10-15% loss for 4-6 weeks |
| Total migration cost | Sum |
Payback period (months) = Total migration cost ÷ (Monthly direct savings)
A payback period under 12 months is an easy approval. Under 18 months is generally approvable. Over 24 months requires compelling qualitative justification.
Even if the direct ROI is marginal, document the indirect benefits that do not appear in the financial model:
These are real but difficult to quantify. Include them as qualitative context, not as hard numbers in your financial model. Leadership will discount inflated indirect benefit estimates. Credible qualitative notes support a decision, they do not manufacture one.
These are composite cases based on real patterns I have seen repeatedly, anonymized where necessary.
Situation: A B2B SaaS company at Series B had grown rapidly through acquisition and organic growth, accumulating software contracts across three legacy systems. A pre-IPO audit revealed 140 active SaaS subscriptions at $2.4M per year, or $13,300 per employee.
Approach: The new CFO commissioned a 30-day audit using Torii for automated discovery and a four-person task force (IT, Finance, HR, GTM lead) for owner mapping and scoring. The scoring exercise identified 42 immediate elimination candidates with a total annual spend of $380,000. A further 30 tools were identified as consolidation targets where function could be absorbed by platforms already in the stack.
Execution: The team ran the program in three waves over 9 months. Wave 1 (immediate eliminations) took 6 weeks and required almost no migration work — most tools were zombie or duplicate. Wave 2 (consolidation targets) took 4 months and included the full migration playbook: data portability audit, workflow dependency mapping, 30-day parallel running period for the three highest-risk migrations. Wave 3 (vendor negotiation) ran in parallel with Wave 2 and resulted in multi-year agreements with their top 5 vendors at 22% average discount.
Results: Stack reduced from 140 to 68 tools. Annual spend reduced from $2.4M to $1.35M — a 44% reduction. Payback period on total program investment (IT labor, training, Torii license) was 8 months. Security team retired 72 OAuth connections.
Situation: An early-stage startup was spending $850,000 per year on SaaS with 55 active subscriptions across 40 employees — $21,250 per employee, well above the benchmark range for their stage.
Approach: No SaaS management platform was needed at this size. The founder and COO spent three days pulling all credit card charges tagged as software, building an inventory in Notion, and categorizing by function. They found 8 categories with multiple tools, 12 tools with no identifiable owner, and 6 subscriptions that had been on auto-renew for tools nobody used.
Key decisions: Moved from Intercom + Zendesk hybrid to Intercom alone. Moved from Notion + Confluence + Google Docs triple overlap to Notion as single documentation layer. Eliminated standalone email marketing tool in favor of HubSpot Marketing Hub, which they were already paying for. Eliminated standalone video hosting in favor of Loom's hosting feature and YouTube unlisted.
Results: Stack from 55 to 28 tools. Annual spend from $850K to $490K — 42% reduction. Total program time investment: roughly 40 hours of internal work. No SaaS management platform needed. No external consultants.
Situation: A 600-person professional services firm was running Salesforce Sales Cloud for CRM, Marketo for marketing automation, Conga for contract management, Salesloft for sales engagement, and Gong for conversation intelligence — five separate vendors for the revenue function alone.
Approach: Rather than migrate away from Salesforce, they ran a competitive evaluation that included asking HubSpot for a full platform bid. They did not intend to move to HubSpot — but the competitive pressure forced Salesforce into a renegotiation. With the HubSpot bid in hand, they negotiated Salesforce into a bundle that included Sales Cloud, Marketing Cloud Account Engagement (Pardot/Marketo replacement), and Revenue Intelligence — eliminating three separate vendors.
Results: Eliminated Marketo, reduced Conga to a minimal contract, and negotiated a 28% reduction in total Salesforce spend in exchange for a 3-year commitment. Total savings: $340,000 per year. The HubSpot bid never needed to be executed — it served purely as leverage.
How long does a full stack consolidation program take?
For a company with 50-100 employees, a complete program from initial audit to stable post-consolidation governance takes 6-12 months. Larger organizations (500+ employees) should plan for 12-24 months. The audit and scoring phase moves quickly (4-6 weeks). The migration phase takes most of the time and should not be rushed. Trying to compress a migration that should take 4 months into 6 weeks is the most common cause of consolidation program failures.
What percentage of SaaS spend can realistically be cut?
Most companies doing their first serious consolidation can cut 25-40% of their SaaS spend. Companies coming off rapid growth through acquisition or remote-first expansion often cut 40-50%. These numbers are real but require disciplined execution. The easiest 15-20% comes from immediate eliminations (zombie tools, duplicates). The next 15-20% requires active migration. The final 5-10% comes from vendor negotiation and right-sizing.
Should we hire a consultant or do this internally?
For companies under 200 employees, I recommend doing this internally with a SaaS management platform. The methodology is not complex — it is disciplined and time-consuming, but not technically difficult. The risk of consultants is that they recommend tools and platforms from which they receive referral fees, and they often leave before the change management work is complete. If you use a consultant, make sure they are in scope for the full program including migration support, not just the audit and recommendations.
How do we prevent tool sprawl from returning?
Three governance practices prevent re-sprawl:
First, require a named owner and a business justification for every new SaaS purchase above a de minimis threshold ($500/month is a reasonable floor). No owner means no purchase.
Second, run a quarterly stack review. It does not need to be a full re-audit — just a 30-minute review of the current tool inventory looking for new zombie tools, renewed duplicates, and shadow purchases.
Third, make IT a service function, not a blocking function. Shadow IT proliferates when the approved procurement process is too slow. If the process to get a new tool approved takes six weeks, employees will bypass it. Build a fast-track approval process (48-hour turnaround for tools under $1,000/month with a clear owner) and shadow purchases drop dramatically.
What is the single highest-leverage consolidation decision for most companies?
In my experience, consolidating the revenue tech stack is the highest-leverage decision for most B2B companies. CRM, marketing automation, sales engagement, and customer success often have four to seven separate vendors at the cost of $500K-$1.5M per year, with complex integrations and significant data fragmentation across them. Consolidating to two platforms (one CRM/revenue platform and one sales engagement tool) with clean integrations between them saves money, improves data quality, and reduces the operational overhead of maintaining the revenue operation.
How does technical debt from old SaaS integrations complicate consolidation?
Technical debt from SaaS integrations is a real consolidation risk. Many companies have Zapier/Make automations, custom API integrations, or data pipelines built on the assumption that a specific tool exists in the stack. Removing that tool breaks the automation. The fix is the workflow dependency mapping step in the migration checklist — identifying every downstream dependency before committing to an elimination. For companies with significant automation infrastructure, a technical audit of all automations before starting the consolidation scoring is worth the investment. See managing technical debt in AI startups for related frameworks on technical debt prioritization.
What is the best tool for tracking SaaS spend for a 30-person company?
At 30 people, a manual approach with a spreadsheet is usually sufficient and much cheaper than any SaaS management platform. Pull all recurring charges from your corporate card and expense management tool, classify them, assign owners, and review quarterly. If you want automation, Torii is the most accessible platform at this size. Many companies also use their expense management tools (Expensify, Brex, Ramp) which have built-in spend categorization that makes manual audits significantly faster. Ramp in particular has strong software spend analytics built into the platform.
If you found this useful, the SaaS Metrics Benchmarks 2026 post has data on how SaaS spending benchmarks vary by stage and whether your current per-employee spend is in line with peers. For broader thinking on cost-efficient growth, bootstrapped startup growth strategy covers related frameworks.
How to manage AI inference costs in SaaS products. Covers token economics, caching strategies, model routing, usage caps, and building sustainable AI-powered features.
Deep dive into vertical SaaS opportunities in 2026. Why niche markets outperform horizontal plays on NRR, churn, and CAC — with specific verticals worth building in.
Complete playbook for migrating SaaS pricing to usage-based models. Covers metering infrastructure, hybrid pricing, revenue forecasting, and real migration timelines.