Adam Robinson didn't hedge. On July 15, the RB2B and Retention.com CEO published a newsletter post titled "The Death of Signal Orchestration" and named five real companies — Koala, Warmly, Common Room, Pocus, and Unify — as his evidence that a whole category of intent data tools is finished. Cold-email desks and RevOps Slack channels have been fighting about it since, and most of the argument has missed the question actually worth answering.
The newsletter post that has outbound arguing about intent data tools
Robinson runs one of the more visible companies in the exact space he's now writing an obituary for, which is part of why the post traveled the way it did. When the CEO of a buyer-intent company tells you buyer-intent is dying, people read it differently than they'd read the same claim from an outside analyst. That's not a knock on him — it's just why “The Death of Signal Orchestration” landed in enough inboxes to become an argument instead of a blog post nobody noticed.
The piece argues, in broad strokes, that signal orchestration — the layer of software built to catch buying signals, stitch them together across sources, and hand a rep something worth acting on — is dying as a standalone category. Robinson names five companies as his examples of that category: Koala, Warmly, Common Room, Pocus, and Unify. We don't have his full reasoning verbatim, and we're not going to pretend we do. What we can say honestly is the shape of the claim: intent data tools built as their own separate layer, sitting apart from the rest of the GTM stack, are losing their reason to exist on their own.
“The Death of Signal Orchestration”
That's the actual title, published on RB2B's newsletter on July 15, 2026. It's a provocative headline attached to a real argument, and provocative headlines about buying signals travel fast in a market that's already nervous about whether any of this software pays for itself.
This category didn't come out of nowhere. The pitch that built it between 2023 and 2025 was straightforward: stop cold-calling a phone book and start reaching people who are already showing intent to buy. Warm outbound, the theory went, converts at multiples of blind outbound, and a good enough signal stack should tell a rep exactly who to call and when they're most likely to answer. That pitch was directionally true often enough to raise real venture money and stock a lot of vendor booths. It's also exactly why a headline naming five of those vendors by name was always going to travel further than one executive's personal opinion.
| ROBINSON'S READ | THE GTM-ENGINEERING COUNTER-READ | |
|---|---|---|
| What's happening to the category | Standalone signal-orchestration tools are dying | Standalone tools are consolidating into broader workflow layers, not vanishing |
| Where the value goes | The stand-alone tooling layer was the mistake | The layer moves — from a dashboard you check into a step embedded inside a workflow |
| What a team should actually do | Stop investing in the category | Audit whether existing signal tools are wired into action, not whether the category survives |
Neither side of that table is a strawman. Both are honest readings of a real disagreement, and both are trying to answer the same underlying question: does warm outbound built on buying signals still work in 2026, or was the whole premise always shakier than the vendor decks made it look? The disagreement isn't really about whether a job change or a pricing-page visit is a meaningful signal. Almost nobody on either side of this argument thinks the raw data got worse. The disagreement is about what a team is supposed to do with that data once it exists, and that's a workflow question dressed up as a category question.
The counter-case: consolidation, not death
The pushback hasn't come from a single named rival with a competing newsletter. It's come from the GTM-engineering community — the practitioners building outbound motions on top of Clay-style workflow tools — and it's a fair characterization of a school of thought, not a single quote from a single person. Their position, in short: signal-based selling isn't dying, it's getting absorbed. Point tools that used to live as their own subscription, their own login, their own Slack alert, are getting pulled inside broader orchestration workflows where the signal is one input among several rather than the whole product.
Clay itself is instructive here, since it's the workflow tool most often cited in this camp's thinking. It didn't start out as a signal-orchestration platform in the sense Robinson is using the term — it started as a way to blend disparate data sources into one enrichment table and let a workflow decide what happens next. Under that model, an intent signal becomes one column feeding a decision, not the whole product a team pays for. That's the structural shift the GTM-engineering camp keeps pointing at: the winning pattern isn't "buy a tool that watches for signals," it's "build a workflow that can ingest a signal from anywhere and route it automatically." Whether the signal originates from a purpose-built vendor or an internal script barely matters once it's inside that workflow.
That distinction matters more than it sounds like it does. A tool "dying" and a tool "getting swallowed by a bigger workflow" produce very different outcomes for the team that bought it. If the category is dying, you cancel and wait for whatever's next. If it's consolidating, the tool itself might survive fine — as a feature, an API, a data source feeding something else — while the standalone habit of logging into it and reading a dashboard is what actually goes away.
That's the actual mechanism behind the “consolidation, not death” argument. It's not that buying signals stopped mattering. It's that a signal sitting inside a dashboard nobody's watching was never really doing anything, and the market is finally pricing that in. The tools built purely to surface signals are losing ground to workflows built to act on them — which is a category shift, not a category death, even if it kills off a specific logo or two along the way.
Why intent data tools became an ROI question in the first place
This argument didn't start in a vacuum. We reported on the AI-outbound ROI problem two days before Robinson's post went up, and the underlying data explains why a headline like “the death of signal orchestration” found an audience ready to believe it. Belkins' 2026 study found that 77% of teams running AI in lead generation can't confirm it delivers a positive ROI, and close to half never built a measurement loop at all. Teams in that position are primed to believe any tool in their stack might be dead weight, because plenty of what they're running actually might be.
None of this is separate from the ROI confusion already baked into outbound generally. A team that can't confirm whether its AI sequencing tool paid for itself isn't a team with the appetite to defend a monthly signal subscription on faith alone. When close to half the market surveyed hadn't measured AI lead-gen ROI at all, the honest read isn't that every tool in the stack is broken — it's that almost nobody built the scoreboard needed to tell broken from working. Robinson's post landed inside that exact vacuum. A specific, named argument about five specific tools is easier to act on than a vague sense that something in the stack isn't paying off, even when the specific argument oversimplifies what's actually happening underneath it.
Jordan Crawford's framework from that same piece is worth restating here in one line: the fix isn't adding another autonomous layer on top of a process you've never audited, it's establishing ground truth from the deals you've already closed and lost. That framework applies directly to intent data tools. Before you decide Robinson is right or the GTM-engineering camp is right, you need to know whether your own signal tooling ever produced a booked meeting you can point to — not whether the category as a whole is trending up or down on somebody's LinkedIn feed.
We've made a version of this consolidation argument before, in our piece on shared versus dedicated cold-email infrastructure: the underlying capability rarely disappears, it just migrates to wherever the workflow around it is strongest. The same pattern shows up in how AI agents are starting to run entire marketing workstreams instead of sitting inside a single point tool — see our case study on AI agents running a marketing team for what that looks like when the workflow, not the individual tool, becomes the unit that matters.
The audit that tells you if your signals are already dead
Here's the verdict, and it's not both-sides mush. Robinson's “death” framing is provocative, and provocative is a legitimate way to get twenty thousand outbound leaders to actually read a newsletter. But it's too binary for what the data actually supports. The real pattern is consolidation: standalone signal and intent data tools are getting pulled into broader GTM-engineering workflows, not erased from existence. That raises the bar for teams still running them as disconnected point solutions, because a signal tool bolted onto nothing is now competing against signal tools that are wired into an actual workflow — and it's losing.
Wired-in looks unglamorous in practice. It's a lead that gets enriched and scored the moment a signal fires, dropped into a sequence without a human touching a spreadsheet, and surfaced to a rep only once it clears a threshold worth their time. Not-wired-in looks like a login you check on Mondays, a CSV export nobody downloads, or a Slack channel with a bot posting alerts that scroll past unread. Both setups can run on the exact same underlying signal. The difference is entirely in what happens in the fifteen minutes after the signal fires, and that's the fifteen minutes Robinson's framing skips past.
This is also where Something Inc.'s own cold email work starts every engagement: not with which tool a client is running, but with whether the tool's output ever reaches a human or a sequence that acts on it. We've seen the gap play out in client work like our FMS Investor Services engagement, where the constraint was never the existence of a signal — it was whether anything downstream was built to do something with it the moment it fired.
None of this means every tool on Robinson's list survives, or that the GTM-engineering camp is right by default just because it's the more crowded side of the debate. Some of what's currently sold as a standalone product probably does get folded into a broader workflow layer within the next year, exactly as the consolidation read predicts. That's a category maturing, not a category failing. The mistake would be reading Robinson's post as blanket permission to abandon signal-based selling altogether, when the actual lesson underneath the headline is narrower and more useful: audit the wiring before you audit the vendor.
So skip the debate about whether the category survives the next twelve months, because that's not actually your decision to make and arguing about it doesn't move your pipeline. Whether Koala, Warmly, Common Room, Pocus, and Unify are still standalone companies a year from now is a question for their investors, not for the team trying to book meetings this quarter. The decision that is yours: whether the buying signals you're already paying for are wired into something that acts, or whether you built yourself an expensive way to watch numbers change on a screen nobody's looking at.
Robinson gave the industry a headline, and headlines are useful precisely because they force a decision that was overdue anyway. The GTM-engineering camp gave the correction, and corrections are useful because they keep a real signal from getting thrown out with a dying label. Neither camp is going to audit your stack for you. Your own pipeline will tell you which read applies to your team, and it won't need a newsletter, a Slack thread, or another hot take to do it — it just needs someone willing to pull the last quarter of signals and actually look.
See where you are cited today
A free snapshot audit of your rankings and AI citations before we ever talk.
Tyler leads work at the intersection of SEO and generative engines at Something Inc., helping B2B brands get ranked and cited across every major AI engine.