A client needed to automate one thing. A sales training funnel. Somebody buys a course, they get enrolled in a membership site, the CRM updates, the sequence starts. Straightforward. I started with GoHighLevel because that's what the client was already paying for and I figured we could keep it in one system.
GoHighLevel couldn't enroll buyers in the membership site the way we needed. So we added Make.com as a middleware layer. Make.com worked for about 2 days until we hit a dead end on the membership side, because WishList Member's REST API turned out to be broken in a way that wasn't documented, and the Digest authentication protocol it used was incompatible with every automation tool we'd tried. We burned maybe a week. 3 tools deep, each one added to solve the problem the previous one created.
The fix was backing all the way out and finding the one integration path that didn't require an additional layer. One direct connection, no middleware. The client's funnel works now. It runs on fewer tools than we started with, which is the part that still feels counterintuitive to most people when I describe it.
I keep having versions of this experience. At work, at clients, in my own business. Something isn't working, the instinct is to add a tool, the tool creates a new problem, you add another tool to solve that problem, and now you have 3 problems and 2 subscriptions you didn't have last month. The default motion in sales ops is addition, so deeply embedded that most teams don't even recognize it as a choice. Pipeline is down, so you buy a sequencer. Reps miss quota and somebody adds a conversation intelligence platform to listen to their calls. Every conference talk is a product launch. Every vendor's pitch is about what their tool does, never about what you should stop doing.
0114 tools for 5 people
I manage the tool stack for about 20 reps at my day job. Pipedrive talks to a call scoring platform I built, which connects to JustCall for telephony, AssemblyAI for transcription, Claude for analysis, Google Sheets for some reporting, and a custom payment matching system that listens for Stripe webhooks. Every one of those connections is a potential failure point that needs monitoring. When something breaks at midnight it's usually one of the connections. I maintain this stack because each piece earns its place and I've verified that. But I also know, from sitting inside it every day, that each additional tool costs a lot more than its subscription price. The stitching, the monitoring, the admin time, the context switching, and the data integrity risk every time information moves from one system to another.
A typical 5-person sales team that I've audited is running something like 14 tools. A CRM, 2 or 3 enrichment providers because somebody signed up for ZoomInfo and then somebody else signed up for Apollo and nobody canceled the first one, a standalone sequencer even though the CRM has sequences built in, a dialer, a scheduling tool, a conversation intelligence platform, an analytics dashboard layered on top of the CRM's own reporting, a proposal tool, project management, and usually some kind of intent data provider. The monthly cost runs about $4,200. The team uses maybe 35% of the features across all of them. 40% of those licenses haven't been actively used in 90 days, which is an industry number that matches what I see in practice almost exactly.
When something breaks at midnight it's usually one of the connections.
Consolidated, that same team needs maybe 5 or 6 tools. A CRM that handles sequences natively. One enrichment source. One source of buying signals. Communication tools. And maybe conversation intelligence if the deal complexity warrants it. Everything else goes, and the cost drops to about $1,400 a month. That's $33,600 a year back, which for a 5-person team is roughly a quarter of somebody's salary redirected from software licenses to actual pipeline work.
02Nobody noticed for 2 weeks
The math is obvious every single time. Nobody wants to be the person who turns something off.
You walk into a team and you show them that they're paying for 2 enrichment tools that pull from the same underlying data sources, and nobody says "great, let's cancel one." The reaction is some version of fear. What if the one we cancel was doing something we don't know about. What if there's a workflow running in the background that depends on it. What if we lose data. What if we need it next quarter for the campaign that marketing is planning. The tool has existed on the credit card for 14 months and nobody can describe what it does, and they're still scared to turn it off.
The tool has existed on the credit card for 14 months and nobody can describe what it does, and they're still scared to turn it off.
I'll tell you what actually happens when you turn it off. Nothing. Nothing happens. Nobody notices for 2 weeks. Then somebody in finance notices the line item is gone and asks when it was canceled and whether anyone approved it. That's the entire disruption.
The deeper fear is that removing a tool feels like going backward. The entire culture of B2B sales operations is oriented around building, adding, scaling, growing the stack. Having fewer tools feels like having less infrastructure, which reads as less serious, less ready. A 14-tool stack looks like a company that's invested in its sales process. A 5-tool stack looks like a startup that hasn't gotten around to buying the real stuff yet. The optics are backward and everyone knows the optics are backward and they keep buying tools anyway.
034 layers and everything else goes
I think about this in terms of what I'd ask about any individual tool if I were auditing it cold. Can you name the last deal it influenced? A specific deal that closed because this tool existed. Does anyone on the team use it at least once a week? Logging in because a notification fired doesn't count. Using it means doing something they couldn't do without it. Does it duplicate something your CRM already does? That last one catches people constantly. Most modern CRMs have sequences, scheduling, basic enrichment, and reporting built in. Teams pay for standalone versions of features their CRM already includes because they bought the standalone tool in 2022 when the CRM didn't have the feature yet, and nobody went back to check after the CRM added it.
I ran into a stat recently that 65% of SaaS apps in an average org are adopted without IT approval. Someone on the team signs up for a free trial, enters a company credit card, and starts using it. 6 months later they've moved on to a different role or a different company and the tool keeps charging. Nobody owns it or maintains it. It just exists on a credit card statement that somebody in accounting reconciles once a quarter without asking whether each line item still serves a purpose. When the person who bought the tool leaves, it becomes an orphan. The line item keeps getting paid because nobody remembers who's responsible for it.
When the person who bought the tool leaves, it becomes an orphan. The line item keeps getting paid because nobody remembers who's responsible for it.
The framework I've landed on for small teams, and I mean teams of 2 to maybe 10 people, is 4 layers. You need a CRM. That's your single source of truth. Every contact, company, deal, and activity lives there. If a tool doesn't write back to the CRM, it functionally doesn't exist because the data it generates will never inform a decision. You need one data source for enrichment and prospecting. Pick the one that covers your ideal customers best and go deep with it. You need one execution layer for sequencing, email, and task management. If your reps are running sequences in one tool and logging calls in another and managing tasks in a third, you've already lost hours of selling time to tab-switching before anyone picks up the phone. And you need one intelligence source, whatever signal matters most for your specific market. Hiring data, intent signals, what tech a prospect already runs, whatever. Pick one. Go deep.
Everything beyond those 4 layers needs to earn its place every quarter, not every year. Because the stack has a natural tendency to grow and no comp plan rewards shrinking it.
04Nobody's job description includes remove tools
That's the part that makes me the most tired. The incentive structure. No vendor, including the honest ones, will ever tell you to use fewer tools. Their business model is subscriptions, so their job is to make you believe you need their product, and their sales team is compensated on new accounts and expansion revenue. The entire apparatus of B2B software sales is designed to make your stack bigger. The blog posts, the case studies, the ROI calculators, the "see how Company X increased pipeline by 40%," all of it points in one direction: add this tool.
The only people who benefit from subtraction are the operators inside the company and the company itself. The ops person who maintains the stack, the finance person who pays for it, the reps who have to use it. And the outside consultants whose business model doesn't depend on you subscribing to something, which is a small group because most consultants are also resellers or implementation partners for the tools they recommend.
No vendor, including the honest ones, will ever tell you to use fewer tools.
I built a prospecting system for my own business that runs as a single markdown file. You drop it into an AI session and it runs. The file is the product. Competitors are packaging similar capabilities into full products with dashboards and integrations and subscription tiers. I keep looking at those products and thinking about how every additional component is another surface area for something to go wrong. The one-file version is ugly. It's also been running for months, since there are no connections in it to break.
94% of sales orgs say they plan to consolidate their stack. That number comes up in surveys every year, and the actual consolidation rate is nowhere close to it. The follow-through dies because the what-ifs are real, the vendor pressure never lets up, and nobody's job description includes "remove tools." Read any RevOps job posting. It's always "evaluate and implement." Never "evaluate and subtract." The language itself is biased toward addition.
The change has to come from the operator side, from the person inside the company who actually maintains the stack and knows what gets used and what doesn't. That person usually knows exactly which tools to cut. They've known for months. They just haven't had the cover to do it because removing a tool that a VP approved last year feels like a political move even when the math is obvious.
0511 months at $180 a month
I canceled a tool at work last year that had been on the books for about 11 months. It was an analytics overlay on top of Pipedrive that produced dashboards we could build natively in Pipedrive with about 20 minutes of configuration. I asked 3 reps if they used it. 2 didn't know it existed. The third knew it existed but used Pipedrive's built-in reports instead. The tool cost $180 a month. I canceled it, rebuilt the 2 dashboards it was theoretically providing in Pipedrive, and nobody mentioned it again. That was 11 months of paying $180 for a tool nobody used.
I suspect most teams have at least 2 of those. Tools still charging a credit card, duplicating something the CRM already does, used by nobody, owned by somebody who left. The first time you go looking for them it's a little shocking how many there are. The second time it's just maintenance.
The hard part is remembering to look.
If your stack is growing but your pipeline isn't: demo.outblox.com