Your GTM Stack Isn't Consolidating. It's Specializing.

I sat through a demo last month where the rep spent the first ten minutes not on the product, but on a slide titled "Stop the Tool Sprawl." Twelve logos on the left, crossed out in red. One logo on the right, glowing. The pitch: buy us, delete the other eleven, sleep better. I've now seen a version of that slide from four different vendors this year, and every single time the room nods along like it's obviously true.

It is not obviously true. It might not be true at all.

The pitch every CRM vendor is selling you

You know the pitch even if you've never sat through that exact slide. Consolidate your gtm tech stack. Fewer logins, fewer vendors, fewer invoices to reconcile at the end of the quarter. One platform for marketing, sales, and service, so your data lives in one place and your team stops context-switching between six tabs. HubSpot has built a category around this promise. Salesforce has built an empire on it. The pitch is seductive precisely because tool sprawl is a real, felt pain — anyone who has managed a RevOps stack knows the Tuesday-afternoon dread of realizing three systems have three different numbers for the same pipeline.

The trouble is the pitch quietly swaps one problem for another and asks you not to notice. It treats tool count as the disease and a single vendor as the cure, when the actual complaint underneath most tool-sprawl horror stories was never "we have too many logins." It was "our data doesn't talk to itself." Those are different problems with different fixes, and a suite only solves the first one — sometimes by making the second one worse, because now your entire sales tool stack is hostage to whatever one vendor decided to build this quarter.

I don't think the vendors pushing this are lying, exactly. A single platform genuinely is simpler to administer than fifteen scattered subscriptions. But simpler to administer and better at the actual job are not the same claim, and the report that landed on my desk two weeks ago makes the gap between them pretty hard to ignore.

What 62 revenue leaders actually run

Michel Lieben and the team at ColdIQ published the 2026 GTM Tool Report on July 15, and it's the most useful thing I've read this year on what a real gtm tech stack looks like once you strip away the vendor slide. The methodology is refreshingly blunt: 62 founders, heads of growth, and revenue leaders at organizations doing north of $1M in revenue answered one open-ended question about the tools they run daily. No multiple choice, no pre-loaded vendor list to pick from. They just said what they actually use.

Here's what came back at the top of the list.

Sit with that ordering for a second. Clay — a data-enrichment and orchestration tool, not a CRM, not a suite, not anything you'd put on a "Stop the Tool Sprawl" slide as the hero — leads adoption at 71%. n8n, a no-code automation and workflow tool, sits at 48%, ahead of HubSpot's 39%. Attio, itself a newer, more modular CRM built for exactly this kind of stack, comes in at 32%. If consolidation into a single all-in-one platform were actually winning, HubSpot's number should be the biggest one on the page, not the third.

The report also surfaced something the adoption percentages alone don't capture: how many tools these leaders are actually running. Stack sizes in the group ranged from 15 tools to 54. Nikola Sokolov at influencers.club runs the widest stack in the sample at 54 tools. On the lean end, Pierre Herubel at Content Path and Roq Xever at PredictLeads each run 15. Benjamin Douablin at FullEnrich runs 19; Jaspar Carmichael-Jack at Artisan runs 25. None of those numbers looks like consolidation. They look like teams building a sales tool stack sized to the job, not shrinking toward some vendor-approved minimum.

“Consolidation now happens at the data layer.”

That line is Lieben's, and it's the sharpest sentence in the whole report. It's not that revenue leaders stopped caring about complexity. It's that the layer where they're actually solving it isn't "which vendor do I log into," it's "where does my data live and how does it move." That's a meaningfully different problem than the one the consolidation pitch is selling you a fix for.

Your gtm tech stack isn't shrinking. It's specializing.

Lieben's report groups what it found into four recurring themes, and each one is a small rebuttal to the all-in-one story on its own.

Put those four together and you get a picture that looks a lot like GTM engineering as a discipline, not a buzzword: specialized tools, each good at one narrow job, connected by an orchestration layer that a practitioner builds and owns rather than buys pre-assembled. This is the same pattern we walked through in our piece on the intent-data-tools consolidation debate — the tools aren't disappearing into a single suite, they're getting wired into workflows where the signal, or the enrichment, or the send, is one input among several rather than the whole product a team is paying for.

It also tracks with what we've seen doing actual outbound work for clients. A devtools company doesn't need the same sending cadence as a services firm, and it definitely doesn't need its enrichment logic, its sequencing logic, and its CRM all governed by the release calendar of a single vendor. Our cold email work almost never starts by asking a client which suite they're on. It starts by asking whether the individual pieces they already have are actually connected to each other, which is a different — and much more answerable — question.

RevOps tooling and the complexity myth

Here's the part of the consolidation pitch that doesn't survive contact with this data: it mistakes tool count for complexity. Those are not the same number, and treating them as interchangeable is how a vendor gets you to sign a contract that solves the wrong problem.

None of this is an argument that every team should run 54 tools, or that buying a CRM is a mistake. HubSpot showing up at 39% and Attio at 32% in this same survey means plenty of serious operators are running one as a real piece of their stack, not as a rebellion against it. The argument is narrower than that, and it's the one the vendor slide never makes: the number of tools you run is not the metric that predicts whether your GTM motion is fast, clean, and trustworthy. Whether those tools share data automatically is that metric, and a sales tool stack can pass or fail it at almost any size.

We've watched this play out directly in client engagements too. Our work with Matroid leaned on exactly this kind of assembled stack — ads and outbound feeding the same pipeline rather than living in separate systems someone had to reconcile by hand — and the lift came from the connections, not from anyone reducing their vendor count first. Teams chasing ROI on AI-driven outbound run into the identical wall, which we covered in our look at why so many AI outbound tools can't prove their return: the tool wasn't the problem, the missing feedback loop between tools was.

So the next time someone hands you the crossed-out-logos slide, ask the question it's designed to make you skip: crossed out for what? If the eleven tools on the left were never talking to each other and never fed a workflow anybody built on purpose, sure, consolidating them into fewer logins is a real improvement, if a modest one. But if the actual complaint is that nobody wired the data layer, buying a single suite doesn't fix that. It just gives you one very expensive login where you used to have eleven cheap ones, with the same disconnected mess underneath, now harder to leave.

The consolidation pitch is comfortable because it hands you a single villain — too many tools — and a single hero — one platform. GTM engineering is less comfortable, because it hands you homework: figure out what your enrichment layer actually needs, what your automation layer actually needs, what each channel actually needs, and go connect them on purpose. It's more work up front. It's also what the 62 leaders who answered ColdIQ's survey are actually doing, whether or not it matches the slide you sat through last month. You don't need permission to build a stack that looks like theirs instead of the one being sold to you. You just need to stop mistaking a shorter tool list for a smarter one.

See where you are cited today

A free snapshot audit of your rankings and AI citations before we ever talk.