The signal-based selling playbook: Clay + Common Room + orchestrator

TL;DR

Cadence-based outbound is dead. Signal-based selling is the architecture that replaces it. This is the build, vendor by vendor, with the workflow you can copy.

• The 2026 reference stack: Common Room (signals), Clay (orchestration), autonomous platform (activation), measurement layer (Dreamdata, HockeyStack or warehouse).
• Signal-triggered outreach delivers 3-5x reply rates of cadence-triggered outreach in our portfolio.
• Three signal classes outperform: hiring, product usage, competitor switch.
• The work that matters is the signal definition, not the message; the message is downstream of the signal.

Introduction

For the last decade, B2B outbound was a cadence problem. Pick 1,500 prospects, write a 6-touch sequence, hit send on Tuesday morning, measure reply rate on Friday. That motion is dead. It dies for three reasons: 73% of buyers actively avoid suppliers who send irrelevant outreach (Gartner 2025), inboxes are saturated, and AI on the receiving end is filtering generic outreach faster than the sending side can scale it.

The motion that replaces cadence-based outbound is signal-based selling. You no longer schedule outreach. You trigger it. The trigger is an observed buying behaviour: a new VP of Engineering hired at a target account, a usage spike in the free tier, a public switch from a competitor, a job posting referencing your category. The message is the response to the signal, not a calendar event.

This article is the operator playbook. Not a vendor pitch, not a theory piece. The architecture, the vendor map, the workflow examples, the unit economics. Written for the RevOps lead, GTM engineer or operator-CMO who needs to build this in the next 90 days.

The 2026 reference stack, layer by layer

The seven layers map directly to the GTM engineering system anatomy. The difference for signal-based selling is that the signal layer is no longer optional; it is the first-class citizen of the architecture.

Common Room: what it is and is not for

Common Room is the signal layer of record for teams whose buyer engages in community, product or dark-social behaviour. It surfaces 100+ signal types out of the box: GitHub stars, Slack community activity, Discord conversations, free-tier product events, webinar attendance, podcast guest mentions, LinkedIn comment activity.

It is the right tool when your buyer:

• Engages in public or semi-public communities (engineering, marketing, design, RevOps communities).
• Uses a free or freemium tier of your product before buying.
• Mentions you, your category or your competitors in dark social.

It is not the right tool when:

• Your buyer is a non-technical mid-market executive with no community footprint.
• Your motion is purely outbound to cold accounts with no engagement surface.
• Your category has no community formation.

In those cases, 6sense or Bombora intent data is the better signal source.

The pricing is meaningful (€18K to €60K annual depending on signal volume) and the deployment is heavy in the first 60 days because the value depends on connecting your specific community presence and product surfaces. Plan for the ramp.

Clay: what it is and is not for

Clay is the orchestration workbench. Functionally it is a programmable spreadsheet that calls 150+ enrichment APIs in a defined order (waterfall enrichment), applies logic, and outputs a workable record. The same workbench doubles as a workflow runner for many teams.

It is the right tool when:

• You need to combine signals from 3+ sources (hiring data, funding data, tech-stack data, product usage) into a single scored record.
• You want to customise enrichment per ICP segment without writing code.
• You want to run a list-build workflow on a recurring basis without engineering involvement.

It is not the right tool when:

• You need a true production workflow runner with state, retries, monitoring and SLAs (n8n or a dedicated orchestrator does this better at scale).
• Your team has no SQL or formula fluency (Clay assumes operator-level data fluency).

Most mature signal-based selling deployments run Clay as the enrichment and scoring layer, with a separate orchestrator (n8n, autonomous platform) handling the production workflow execution. The two are complementary, not redundant.

How the layers compose: the canonical workflow

Here is the end-to-end workflow that 11 portfolio companies are running in production today, abstracted into one reference implementation.

Step 1 (Signal capture, Common Room). A new account triggers a signal: a free-tier user logged in 3+ times this week from an organisation matching the ICP firmographics, and a separate user from the same organisation engaged with a key feature.

Step 2 (Identity enrichment, Clay). Common Room webhook fires into a Clay table. Clay calls Apollo, RB2B and the organisation’s website to resolve the firmographic footprint, identify the likely buying committee (VP-level personas in the relevant function), and verify contact emails.

Step 3 (Signal scoring, Clay). A scoring formula combines the signal weight, fit (ICP match), and engagement depth into a 0-100 score. Above 70 the workflow continues. Below 70 the record is parked for nurture.

Step 4 (Reasoning, autonomous platform). The autonomous platform retrieves the product-usage details, the buying committee, and the matching case study from the knowledge base. It drafts an opener that references the specific product behaviour, not the firmographic match.

Step 5 (Activation). The platform sends from the named owner’s inbox (warmed, EU-compliant, AI Act Article 50 disclosure where applicable). Reply detection routes positive replies into the CRM with a calendar booking link, neutral replies into a follow-up sequence, and negative replies into a suppression list.

Step 6 (Measurement). Every step writes to a measurement layer. Cost per qualified meeting, cycle time from signal to first reply, exception rate. The metrics are visible to the CFO in 60 seconds.

Total operator time per signal-triggered conversation: 11 minutes (review, approve send, manage exceptions). Total elapsed time from signal to first reply: 4 to 18 hours depending on inbox warm-up and reply patterns.

The signals that actually predict revenue

In our portfolio of 18 GTM rebuilds, three signal classes outperform every other.

Hiring signals. A new VP-level hire in the buyer function is the strongest single signal we have measured. New VP of Engineering = security tooling and developer-experience tooling triggered. New CMO = MarTech rebuild triggered. New CFO = financial tooling triggered. The conversion-to-meeting rate on hiring-triggered outreach is 12 to 18% in our data, versus 1 to 3% for cadence-triggered.

Product-usage signals. Engagement spike in the free tier, feature adoption, integration setup. The shortest signal-to-revenue path in PLG motions. Conversion 8 to 14%.

Competitor switch signals. Public announcement of a vendor switch, RFP issued, integration deprecation. Hardest to detect, highest intent when detected. Conversion 18 to 25%.

Three signal classes underperform expectations.

Pure intent data from 6sense or Bombora. Useful as a baseline filter but does not move conversion meaningfully when used as a single trigger. 2 to 4% conversion. Combine with another signal class for compounding effect.

Website visit signals (RB2B and equivalent). High volume, low specificity. Useful for account-prioritisation, weak as a stand-alone trigger.

Job-posting keywords. Easy to scrape, low signal-to-noise ratio. Better as enrichment than as trigger.

What changes about the message

A signal-triggered message is structurally different from a cadence message. Three rules.

The message names the signal. “Saw you brought on a new VP of Engineering last week” is the signal. “Hope your week is going well” is not. The message that does not reference the signal is wasting the signal.

The message is shorter. Median high-performing signal-triggered email in our portfolio is 67 words. Cadence emails average 154 words. The signal carries the relevance; the message just has to clear the path to a yes.

The message offers a specific path. Not “would you be open to a 15-minute chat?” but “open to swapping notes on what’s working for your engineering team’s tooling stack in the first 30 days?”. Specific to the signal.

Eric Nowoslawski of Growth Engine X has been making this argument for two years:

“The best email you send is the one where you do 10 minutes of research.”

The signal compresses the 10 minutes into 90 seconds. The message becomes the response to research the agent did, not a generic pitch.

The unit economics

This is the part that closes the deal with your CFO.

The tooling cost goes up (more sophisticated stack); the operator cost drops more than it (less manual list-building, fewer wasted touches). Net cost per qualified meeting drops by 50 to 60% in the deployments we have measured.

Jordan Crawford of Blueprint GTM frames the broader argument:

“The list is the message.”

Signal-based selling is the operational implementation of that idea. The work moves from drafting messages to defining signals.

Where Falora fits

Falora is the orchestration plus governance layer in this architecture. We do not replace Common Room or 6sense; we make them act on schedule. We do not replace Clay’s enrichment; we consume its scored records and route them through the workflow. We add three things that the best-of-breed stack does not include natively:

Exception routing with confidence thresholds. Agents act autonomously above defined confidence levels and escalate to a named human below them. The exception rate is observable and tunable.

EU AI Act Article 50 disclosure as a runtime feature. Every materially AI-generated message ships with the disclosure metadata, configured centrally, audited automatically.

Audit trail for every step. Every signal received, every enrichment call, every send, every reply classification, every escalation is captured in one log. The CFO can audit the full trail in one query.

The other vendors in the stack are best-of-breed at their layer. The orchestration plus governance layer is the one that wins or loses at production scale.

A 30-day signal-based selling deployment

For a team starting from a cadence-based outbound baseline, here is the 30-day deployment we run.

Days 1 to 5: signal definition. Workshop with sales, marketing and RevOps. Define 5 to 7 signal types that the team agrees predict revenue for your ICP. Document the signal in writing with a named owner per type.

Days 6 to 12: stack setup. Deploy Common Room (or your chosen signal source), configure Clay tables for enrichment, connect the orchestrator. End-state: a signal can flow end-to-end with a manual approval gate at the send step.

Days 13 to 20: pilot run. Run the workflow on one ICP segment with manual approval on every send. Measure reply rate, conversion, and exception types. Calibrate confidence thresholds.

Days 21 to 30: scale. Move the highest-confidence signal types to autonomous send with exception-only review. Keep the lower-confidence types on manual approval. Measure cost per qualified meeting weekly.

By day 30 you have a working signal-based motion at small scale and a clear roadmap to broaden coverage in the next quarter.

Frequently asked questions

Can I run signal-based selling without Clay? Yes, with more engineering effort. n8n + custom scripts + the enrichment APIs directly is functional. Clay is a productivity multiplier, not a hard dependency.

Can I run signal-based selling without Common Room? Yes if your buyer is not in communities or free-tier products. 6sense, Bombora and custom scrapers can substitute. Common Room is the dominant choice for community-led and PLG motions.

What is the minimum team size to run this? One operator with 40 to 60% of their week, plus on-demand help from a developer or GTM engineer for stack setup. Below this, the manual list-build motion is more cost-effective.

Does this replace my SDR team? Partially. The list-building, research and initial outreach work compresses. The senior-conversation and multi-threading work does not. Most teams in our portfolio go from 4 to 6 SDRs to 1 to 2 SDRs plus the signal stack within 12 months.

How does this interact with AI SDR products like 11x or Artisan? Those products fit at the activation layer (Layer 5). They are not orchestrators in the sense this article uses the term. The signal-based architecture above can use them as one of several activation endpoints.

Conclusion

Cadence-based outbound is the highest-cost, lowest-yield motion in B2B in 2026. Signal-based selling is the architectural replacement. The reference stack (Common Room + Clay + autonomous orchestrator + measurement) is mature enough to deploy in 30 days and produces 3 to 5x the reply rate of cadence at half the operator cost.

The work that matters is not the tool selection. It is the signal definition. Picking the right signals for your ICP is where the leverage lives.

If you want help defining your signal set and standing up the stack, book a signal-based selling diagnostic with Falora.

Sources

• Common Room, Signals platform documentation
• Clay, Custom Signals
• Letterdrop, Signal-Based Selling Guide 2026
• RevPartners, Scaling Signal-Based Selling with HubSpot, Clay and Octave
• Octave, Clay Lead Scoring: Building Fit and Intent Models
• nRev, B2B Buying Signals: 2026 Guide
• Gartner, Future of Sales 2026
• Twelfth, Best Signal-Based Marketing Platforms 2026

Related reading on Falora

• The anatomy of a GTM engineering system
• GTM engineering vs growth marketing
• AI SDRs vs human SDRs: 7 conditions where AI loses
• The outbound agency cost autopsy
• MCP for GTM

About the author

Jeroen De Broyer is co-founder of Falora. He has personally deployed signal-based selling architectures in 11 European B2B SaaS scale-ups and has spent the last decade observing what does and does not work in mid-market outbound. He writes on LinkedIn.