Right now, somewhere in your Slack, a bot is announcing that a target account just visited your pricing page. Nobody will do anything about it.
Not because your team is lazy, but because that signal is one of forty pings today, disconnected from the CRM, the owner, and any suggested next step. The modern GTM stack is great at detecting intent and terrible at doing anything with it. Intent tools, CRM, LinkedIn, product usage, community: every layer emits signals, and reps are left stitching them together by hand.
The math on that is unforgiving. Salesforce's State of Sales research finds reps spend under a third of their week actually selling; the rest disappears into admin, internal meetings, and research. A signal that requires twenty minutes of digging to figure out who it belongs to, whether it matters, and what to do next isn't a signal. It's another research task in a week that's already 70% research tasks.
More data won't fix that. Activation will. Here's what the gap looks like in practice, from the operators and buyers living it.
"Siloed and difficult to action": one growth team's story
One mid-market growth team, now a Common Room customer, had done everything right by the standard playbook. They had signals flowing in from multiple channels: intent tools and visitor-identification tools pinging Slack throughout the day. Real coverage, real intent data.
And then... nothing. In their own words, once the ping landed in Slack, "there's not much we can really do with that signal."
The wish list they described is the definition of activation:
- One layer on top. Consolidate every signal source into a single view instead of parallel Slack channels.
- Scoring by relative importance. A pricing-page visit from a target account is not the same as a stray blog view; the system should know the difference.
- Push, not pull. Route qualified signals directly into campaigns and outbound tooling automatically, instead of relying on a rep to notice and act.
- Always-on listening. Their target list was roughly 20,000 companies. As they put it, the AEs definitely don't have time to check each target account one by one for matching signals. The system has to listen so reps don't have to.
The summary that stuck, in the customer's own words: good signals and intent, but siloed and difficult to action.
That's the trap most teams are in: every new signal source adds visibility and subtracts actionability, until reps tune out the whole channel.
The 4Rs: what activation should look like (Tom Slocum, SD Lab)
Tom Slocum starts from the rep-side failure mode:
"Too many reps are still pitching whenever they're ready to sell. Not when the buyer is actually ready to buy."
-- Tom Slocum, CEO & Founder of SD Lab
His filter, whether he's running outsourced outbound or coaching internal teams, is the 4Rs: right person, right message, right time, right channel. And the way you get there is signal capture: hiring, funding, new roles, pricing-page visits, competitor mentions, increased product usage.
"All of that gives you a real reason to reach out, because there's something actually going on."
-- Tom Slocum, CEO & Founder of SD Lab
Saad Khan of Trumpet adds the stakes: signals have raised the standard. Now that relevance at the right moment is possible, buyers can tell the difference. Generic outreach doesn't read as neutral anymore; it reads as noise, and it burns the account for the rep who comes next.
The 4Rs sound obvious until you try to run them across thousands of accounts with signals scattered in six tools. That's not a discipline problem. It's an infrastructure problem.
What it looks like when activation works
Two Common Room customers describe the other side of the fix, and both frame it the same way: one place.
At one mid-market software company, the senior leader who runs SMB sales has a team of full-cycle reps who are mostly working inbound, which leaves them about two hours a day for prospecting. Her requirement, in her own words:
"You've got two hours... I would like it to be one place that they go, to understand who they should reach out to, what they should reach out with, and then to execute the task from there too."
The problem she was solving is the same one that growth team described: signals existed, but they were hidden and scattered, some in the CRM, some in marketing automation, some in one-off campaigns, with no single centralized place to answer the only question that matters at 9am: who is the best person to reach out to today?
The sales leader at another mid-market customer went even further when mapping her SDR motion. The goal wasn't just consolidation; it was removing thinking from the loop entirely:
"I want to build so many specific plays and then tag them with the right messaging so that they don't have to really think about it."
Her bar for the workflow: reps spending "90% of their time in Common Room" for prospecting, working pre-built plays with the messaging already attached, at the volume the number requires.
The takeaway: aggregate, resolve, act
Signal coverage is table stakes. The differentiator is the layer that unifies signals from every source, resolves them to real people at real accounts with Person360, and routes the next action to a rep with context through plays and workflows.
Keep the intent tools you already have; the fix isn't ripping anything out. It's aggregating what your stack already emits and acting on it in one motion, so a pricing-page visit becomes a prioritized, context-rich task for the right rep instead of ping number forty-one in a muted channel.
When a signal fires, your team shouldn't wait for the next meeting. And they definitely shouldn't have to go find it.
See what's possible with Common Room
- Signal aggregation: every source (web, product, community, social, intent) unified in one place, always listening across your full target list.
- Identity resolution: signals resolve to a real person at a real account, with full context attached.
- One-motion activation: pre-built plays route the signal to the right rep with messaging already tagged, at two-hours-a-day speed.
Stop stitching signals by hand. Request a demo of Common Room.