A Series B founder pulled up his sales tools list for me last quarter. Fourteen logos. A CRM, a sales engagement platform, a separate dialer, two data vendors that did roughly the same thing, a conversation intelligence tool nobody had logged into since onboarding, a "revenue intelligence" platform the board asked him to buy, a scheduling app, a proposal tool, and a few I had to ask him to explain. He paid for all of it. His reps used maybe four of them.
That is the sales tech stack problem in one screenshot. Not too few tools. Too many, half-used, paying twice for the same job, and held together with brittle integrations that break the moment a field name changes. I see it on almost every audit I run. The team thinks they have a tooling gap. What they actually have is a tooling tax.
This piece is about how to read that tax, cut it, and end up with a stack your reps will actually open. I will use real benchmark numbers from a 2025 study of 938 B2B companies, because the gut-feel version of this conversation goes nowhere with a CFO in the room.
What a sales tech stack actually is
A sales tech stack is the set of software your revenue team uses to find, contact, manage, and close deals. At the center sits the CRM. Around it: prospecting and data tools, a sales engagement or sequencing layer, calling, scheduling, proposals and e-signature, and some kind of reporting or forecasting.
That is the textbook version. In practice a stack is rarely designed. It accrues. A rep asks for a tool, a manager expenses it, a new VP brings their favorite from the last company, marketing buys something that overlaps with what sales already has. Nobody removes anything, because removing a tool means a conversation and keeping it means a renewal that auto-clicks through. So the stack grows in one direction only.
Wasted per rep per year on overlapping sales tools, according to a 2025 benchmark of 938 B2B companies. On a 50-rep team that is $117,000 a year buying the same job twice.
The numbers most teams have never seen
Here is what the average looks like, so you can place yourself against it. The 2025 benchmark put the typical B2B sales stack at 8.3 tools costing $187 per rep per month, which is $2,244 a year per rep before you count integration and admin time. SaaS companies run hotter, around $412 per rep per month.
The waste is not subtle. About 73% of teams run overlapping tools, with 40 to 60% functional redundancy between them. The most common overlap is an email automation tool sitting next to a sales engagement platform that already does email. The second is a conversation intelligence tool next to a separate call recorder. Roughly half of all software licenses across a company go unused.
And adoption is worse than the spend implies. In the benchmark, the high-adoption tools (a CRM, a sequencer, a prospecting tool) saw 45 to 61% daily usage. The low-adoption ones sat at 9 to 18%. CPQ utilization came in at 9%. So the picture is not "we use a lot of tools." It is "we pay for a lot of tools and use a few of them every day."
I want to be careful with these averages. Your number is the one that matters, and you can pull it in an afternoon: open the billing portal, list every line item, and write down how many seats are active versus paid. Most teams have never done this once.
Why more tools makes reps sell less, not more
The standard pitch for any sales tool is that it gives reps time back. Buy enough of them and reps should be selling all day. The data says the opposite is happening.
Reps spend about 28 to 30% of their week actually selling. The rest goes to CRM data entry (around 17%), internal meetings, email, scheduling, and research. The teams with the biggest stacks are often the ones where reps sell the least, because every new tool adds a place to log in, a field to update, and a tab to keep open. Top performers spend 34% of their time selling, bottom performers 23%, and the gap is mostly admin drag.
There is a second cost that does not show up on any invoice. When two tools surface different "next best actions" to the same rep, the rep stops trusting both. I have watched this kill an expensive AI rollout. The forecasting tool said one thing, the CRM said another, the engagement platform nudged a third, and reps quietly ignored all of it and went back to their gut. Fragmented tooling does not just waste money. It teaches your team to distrust the system you are asking them to live in.
A tool nobody opens is not a small loss. It is a signal the rest of the stack is also optional.
Adoption is contagious in both directions. One ignored tool teaches reps that ignoring tools is fine, and that habit spreads to the CRM you actually need them to use.
The two stacks: what bloat looks like next to what works
The difference between a bloated stack and a working one is rarely the tool count by itself. It is whether each tool owns a job no other tool is doing, and whether the data flows between them without a human copying fields. Here is the contrast I draw for clients.
One RevOps leader in the research cut a 120-person org from 14 tools to 6. Revenue per rep went up 22%, satisfaction scores improved, and they saved $210,000 a year in licensing. The interesting part is that revenue went up after removing software. Fewer places to look meant reps spent more time in front of buyers and trusted the one system that was left.
How to audit your stack in an afternoon
You do not need a consulting engagement to find the bloat. You need the billing portal, a usage report from each tool, and a willingness to cancel things. Here is the sequence I run.
The job-mapping step is where the savings hide. Email automation plus a sales engagement platform is the most common duplicate, and it costs about $1,890 per rep in wasted spend. Conversation intelligence plus a standalone recorder is the next, at roughly $2,150. You almost never need both halves of either pair. Pick the one your reps already open and kill the other.
When you score usage, do not let "we might need it" win. A tool you might need is a tool you can buy again in a day. A tool sitting at 9% adoption is a tool you are paying for so one person can feel covered. The renewal will happen automatically if you do nothing, which is exactly why doing nothing is the expensive option.
The lean stack for Series A and B
If you are building from a smaller base, do not copy the enterprise diagram. Most Series A and B teams need fewer than ten tools, and the order you add them matters more than the brand. Here is the spine I would build today.
Start with the CRM. HubSpot or Salesforce if you want a platform, Attio if you want something faster to set up and reshape. This is the one tool that cannot be optional, and it should be the place every other tool writes back to. If your CRM is not the source of truth, nothing downstream will be either.
Add a prospecting and data layer next. Clay for enrichment and signal tracking, paired with one primary data vendor rather than three. The waterfall approach matters here because no single provider has good coverage on everyone, and I have written a full breakdown of how to run that without burning credits in the Clay enrichment playbook.
Then a sales engagement layer for sequencing and calls, and that is mostly it for the front end. Reporting can live inside the CRM until you genuinely outgrow it. A separate revenue intelligence platform is a real category, but it is a later purchase, not a Series A one. Same with standalone conversation intelligence: worth it once you have enough calls to coach against, premature before that.
The glue layer is the piece teams skip and then regret. Native integrations get you most of the way, but the edge cases (custom routing, enrichment on a trigger, syncing a field two tools disagree on) need an automation tool. I run most of this on n8n, and I compared it against the alternatives in n8n vs Zapier vs Make. The point is to have one glue layer, not five point-to-point connections that each break independently.
Where AI changes the math
The AI tools shifted the benchmark in a way worth knowing before your next purchase. AI-native CRM features posted a 287% ROI with a 7-day time to value in the study, while traditional CRM came in at 124% over a 90-day ramp. Tools scoring high on AI-native design hit 241% average ROI with a 4% failure rate. Tools scoring low sat at 34% ROI and a 64% failure rate.
I read that as a buying rule, not a hype signal. The tools paying off are the ones where AI does a job inside a system reps already use, not the ones bolted on as a separate destination. An AI feature in your CRM that drafts the follow-up gets used. A separate AI tool that asks reps to leave the CRM to get a recommendation does not. The same logic applies to AI SDRs, which I dug into in the AI SDR reality check: the wins come from augmenting the workflow, not adding a new island to it.
So when a vendor pitches you an AI layer, ask one question. Does this live inside the tool my reps already open, or is it a new tab? If it is a new tab, you are buying adoption risk along with the license.
Not sure which tools to cut?
Book a free 30-minute stack audit and we will map your tools to jobs, flag the overlaps, and show you the three cuts that save the most without slowing reps down.
Book a stack audit →What good looks like six months out
The teams that get this right do not end up with a perfect diagram. They end up with a stack small enough that one person can explain every tool in it, where each tool earns its keep in daily usage, and where data moves without a human retyping it. Adoption stops being a fight because there is less to adopt and the few things left are the things reps would miss if you took them away.
The CFO conversation gets easier too. "We cut four tools, saved $200,000, and revenue per rep went up" is a sentence that buys you trust for the next purchase. "We added another platform and hope it helps" is not.
Tooling will not fix a broken process, and no amount of consolidation will save a team selling the wrong thing to the wrong accounts. But a bloated stack actively makes a decent team worse, taxing the hours they should spend selling and teaching them to distrust the system. Cutting it back is one of the few RevOps moves that saves money and improves output at the same time. That combination is rare enough to do first.
If you want a hand running the audit or rebuilding the spine, that is most of what we do at Ziel Lab across CRM and RevOps, AI automation, and go-to-market work.
FAQ
How many tools should a B2B sales stack have?
The average is 8.3 tools, but average is not the goal. Most Series A and B teams run well on six or fewer: a CRM, a prospecting and data layer, a sales engagement tool, a glue or automation layer, and reporting inside the CRM. Add more only when a tool owns a job nothing else is doing and clears 30% daily usage.
What is the most common waste in a sales tech stack?
Overlapping tools that do the same job. The top offender is an email automation tool sitting next to a sales engagement platform that already sends email, which costs around $1,890 per rep a year. A standalone call recorder next to a conversation intelligence tool is the second. Roughly 73% of teams run at least one of these overlaps.
How do I know if a sales tool is worth keeping?
Look at daily active usage, not feature lists. In the 2025 benchmark, tools worth keeping sat at 40 to 61% daily usage, while the ones being wasted sat at 9 to 18%. If a tool is under 30% daily usage and no rep can defend it in one sentence, it is a renewal you should cancel.
Does consolidating tools hurt sales performance?
The data points the other way. One 120-person org cut from 14 tools to 6 and saw revenue per rep rise 22% alongside $210,000 in annual savings. Fewer tools meant less admin, less tab-switching, and more trust in the one system that was left. The risk is cutting a tool reps actually use, which is why you score usage before you cancel.
Should I buy AI sales tools in 2026?
Buy the ones that live inside a tool your reps already open, not the ones that ask reps to leave the CRM. AI-native CRM features posted a 287% ROI in the benchmark, while bolt-on tools with low AI-native scores managed 34% and failed 64% of the time. The test is simple: does it add a feature to an existing workflow, or a new tab to ignore?
Cut the bloat before you add anything
If your stack has grown past the point where one person can explain every tool, you are paying the tooling tax. Start with the inventory, map tools to jobs, score usage, and cut the duplicates. Then rebuild the spine around a CRM that is the genuine source of truth.
We run this audit for B2B teams every week, from the spreadsheet of line items to the rebuilt stack reps actually use. If you want to find your three biggest cuts and the savings behind them, get in touch and we will take a look together.