Hero background

signal-based selling

Signal-Based Selling

Signal-Based Selling explained: the best cold email fails at the wrong time
In this post:
No headings found on page

Signal-based selling is a way of running outbound in which buying signals and trigger events, such as a closed investment round, a newly hired VP of Sales or a second look at your pricing page, decide when a rep reaches out, to whom, and what they write about. The list of companies that fit your profile stays. What changes is that the order in which you work it comes from what those companies are doing this week.

Most teams that say they do it have bought the signals and skipped the selling. The alerts land in a Slack channel, a few reps act on the ones that catch their eye, nobody owns the rest, and a month later the channel is muted. That's a feed, not a sales motion.

The missing piece is operational: which signals deserve a person, which person, how fast, with what message, and how you'll know it beats the list you worked before. This entry is about those decisions. The signals themselves have their own entries.

TL;DR

  • List-based outbound picks accounts for what they are. Signal-based selling keeps the same fit criteria but lets behavior set the order, which matters because LinkedIn's B2B Institute estimates that 95% of potential buyers are out of the market at any given time.

  • Run it as a set of written plays. Each play names one signal, the filter it must pass, the owner, a response deadline, the message angle, the channels and what happens when nobody replies.

  • Ownership follows the account, not the alert. The account owner gets it first, an open deal goes to its AE, customers go to their account manager, and unowned accounts go to a pool with a daily cap per rep.

  • Set response times per signal type. A pricing-page revisit from a fitting account deserves a same-day touch, while a funding round can wait a working day or two for a better-researched message.

  • Write to the problem the signal points at and keep private behavior out of the copy. In the EU, people can object to direct marketing at any time, including the profiling behind it, so an objection has to stop every play at once.

  • Measure each play on the share of signals touched in time, meetings, pipeline in euros and a comparison with accounts worked from the ordinary list. Fix speed and coverage before you judge the message.

  • Nebor builds these plays as routing rules, alerts and sequences inside the CRM and Clay account a client already runs, starting with one or two signals and adding more once the first ones produce meetings.

Same accounts, a different reason to call them

Traditional outbound starts from a profile. You filter by industry, size, region and title, build a list, and work it top to bottom at whatever pace the team can manage. Every account on that list fits. Most of them aren't buying anything this quarter, and the list can't tell you which few are. The B2B Institute at LinkedIn puts the share of companies that could buy from you but aren't ready yet at 95%.

The same cold email sent at two moments, ignored by a company that just renewed a competitor and answered by one that just raised a round, illustrating signal-based selling

Signal-based selling keeps the profile as a gate and adds a second question: which of these accounts gave us a reason to write this week? A new head of sales, a burst of job ads, three people from one company on your integration pages. The account was always a fit. The signal says the timing may have changed, and very often it also says what to write about.

That shifts who decides what a rep does each morning. On a static list, the rep works down the spreadsheet. In a signal-based setup, the system sets most of the queue and the rep decides how to handle each account. Teams that never make that shift explicit end up with a list nobody finishes and alerts nobody trusts.

List-based outbound choosing accounts by what they are next to signal-based selling choosing accounts by what they are doing, illustrating how signal-based selling differs from traditional outbound

Signal-led teams usually contact fewer accounts per week, since only a slice of the market shows anything worth acting on. The effort goes where a message has a reason to exist.

A signal-based selling play, written down

The unit of signal-based selling is the play: one signal, handled the same way every time it fires. Writing plays down is what turns scattered alerts into something a team can run, review and improve. Every play we build answers seven questions.

  1. Which signal fires it? One specific event, such as a pricing-page revisit, a new revenue leader or a job ad naming a tool you replace. The families to choose from are laid out under buying signals, with intent signals and trigger events covered on their own.

  2. What must the account pass first? Fit with your profile, plus suppression of customers, open deals, competitors and anyone who has opted out. If you rank accounts with account scoring or predictive lead scoring, this is where the score sets a floor.

  3. Who owns it when it fires?

  4. How fast must the first touch happen?

  5. What is the message about, and who in the account gets it?

  6. Which channels, in what order, over how many days?

  7. What happens if nobody replies, and when can the same play fire again for that account?

Four kinds of signal worth building plays around, funding, leadership changes, hiring and direct intent, illustrating which signals feed signal-based selling

Here's one filled in, for a payroll software company in Utrecht that sells to foreign businesses setting up in the Netherlands.

Play: first Dutch job ads. It fires when a company with no Dutch entity posts its first vacancies based in the Netherlands. It qualifies if the company has 50 to 500 employees, is headquartered in Germany or the UK, and isn't a customer or an open deal. An existing account owner takes it. Unowned accounts go to the SDRs covering that country, by round robin. The first touch goes out within two working days of the ad appearing. The message is about what a first Dutch employee means for payroll and contracts, sent to the HR or finance lead rather than the hiring manager named in the ad. The sequence is an email and a LinkedIn request from the same rep on day one, a call on day three if a number is on file, and a last email on day eight. With no reply, the account drops back to the normal list, and the play can only fire again if a Dutch office announcement or a second wave of local job ads appears within 90 days.

Each line is a decision someone would otherwise make differently every time. A team usually needs three to six plays like this, not thirty.

Who picks up a signal-based selling alert?

Ownership causes more friction than anything else here. When a signal fires, three people may feel entitled to it and none responsible for it. The rule that holds up is that the signal follows the account, which already has an owner or gets one from a fixed rule.

  • If the account has an owner, the owner gets the signal, even if a different SDR spotted it first.

  • If there's an open opportunity, the AE on that deal gets it as context, and no new sequence starts.

  • If the company is already a customer, it goes to the account manager as an expansion or risk signal, never into a cold sequence.

  • If nobody owns the account, it goes to a pool of SDRs by round robin, and the person who takes it becomes the owner.

All of this depends on the signal landing on the right company record. A pricing visit from an unnamed company, or a job ad matched to the wrong subsidiary, gets routed to nobody. Lead-to-account matching and website visitor deanonymization do that groundwork, and your existing lead routing rules should carry the rest rather than a separate set invented for signals.

Capacity needs a rule too. If signals fire faster than reps can act, the backlog ages and the timing advantage is gone. Cap the new signal accounts each rep receives per day, and if the cap is hit every day, tighten the filters. When two signals fire on the same account in one week, they belong in one thread from one person, with the stronger signal deciding the angle.

Response times by signal, not one deadline for everything

Signals fade at different speeds, so one response deadline is too slow for the hot ones and needlessly rushed for the rest. Set it per play. Speed to lead explains why the first hours matter for anyone who has raised a hand, and the logic applies more loosely to everything else.

A buying window losing value over the days after a signal fires, next to four steps for starting with one signal and automating later, illustrating response speed in signal-based selling

In practice we sort plays into roughly three speeds. Signals aimed directly at you, such as a repeat pricing visit from a fitting account or a reply to an old thread, get a touch the same working day. Company changes like a new executive, a raise or a hiring spree get one to two working days, because a researched message beats a fast generic one. Slow research signals, such as rising third-party intent on a topic, don't get a rep at first. They raise the account's priority and wait for something aimed at you to confirm them.

Deadlines only hold if the signal reaches a person automatically, as a task or alert created the moment it passes its filters, in whatever the owner works in: HubSpot, Salesforce or a Slack channel per rep. Enrolling the contact in the right sequence can be automated too. On HubSpot's Enterprise tiers, a workflow can enroll contacts in a sequence with the contact owner as sender. Whether the first email goes out untouched or waits for a rep's edit is a choice per play: high-volume plays can run alone, while plays aimed at senior people in large accounts get a draft and a human. Most of what it takes to take the routine steps of prospecting off reps' plates sits in exactly this hand-off.

Writing to the reason, not the observation

A signal earns you a reason to write, not the right to say you've been watching. A funding round, a job ad or a new leader's announcement is fair to mention, since the company published it. A visit to your pricing page is not, because however accurate, it reads as surveillance.

Two openings compared, one referencing a public funding round with a useful insight and one citing private pricing-page visits, illustrating how to write signal-based selling messages

So private signals decide timing and public ones can shape the copy. Either way, write about the problem the signal points to: a burst of SDR job ads points at onboarding and territory problems a few months out, and that's the subject. How to read the detail inside an event, from vacancy text to a new leader's last job, is covered under trigger event. When the signal is first-party, the same motion goes by the name inbound-led outbound, while a website visitor tracking workflow is one way to turn a site visit into a first touch.

Plays work best as short multi-channel outreach sequences where the email, the LinkedIn message and the call refer to each other. They also need a hard stop. Under Article 21 of the GDPR, a person can object at any time to processing for direct marketing, including profiling related to it, and after an objection their data can no longer be used for that purpose. So one opt-out must suppress the person across every play and tool, not only the sequence they replied to.

Measuring signal-based selling play by play

Counting signals captured says nothing about selling. Each play needs four numbers: the share of qualifying signals that got a first touch within the deadline, meetings booked, pipeline created in euros, and the same figures for comparable accounts worked from the ordinary list. Per-signal measures, such as which signal types convert best and how many alerts turn out to be false alarms, are covered in the buying signals entry.

Take a made-up quarter for the Utrecht company. A pricing-revisit play saw 60 qualifying signals, reached 51 of them within the same-day deadline (85%), booked 9 meetings and created 4 opportunities averaging โ‚ฌ24,000, so โ‚ฌ96,000 of pipeline. A funding-round play saw 120 signals, reached only 70 in time (58%), booked 5 meetings and created one โ‚ฌ20,000 opportunity. The obvious reading is that funding signals don't work for this company. The better reading is that 50 funding signals never got a timely touch at all, so the play hasn't really been tested yet. Fix the coverage first, then judge the message.

The comparison with the ordinary list tells you whether the signal caused anything. Accounts that show signals are often better accounts to begin with, which flatters a play. To check, hold back a small share of qualifying accounts, say one in ten, and work them on the normal cadence. If that group books nearly as many meetings, the signal is picking good accounts but the play adds little on top.

Rolling out one play at a time

The quickest way to stall is to switch on every signal source at once. Start with the one or two signals your best recent deals had in common, write the plays and run them by hand if you have to. One rep checking a single source each morning and writing the same day is a legitimate first version, and it shows which signals produce conversations before you pay to automate them.

The signal stack that detects signals next to the selling motion that acts on them, with signal-led accounts at the front of the queue and steady list-based outbound behind them, illustrating how signal-based selling fits alongside traditional outbound

Once a play books meetings, automate its detection. Tools like Clay can watch for changes on the accounts and people you track; its Signals documentation lists new hires at target companies, job changes and promotions among the options. The set of sources you settle on becomes your sales signal stack, and the logic that combines them, scores them and decides which play fires is signal orchestration. For campaign ideas built on specific signals, see these signal-based outbound campaigns.

Keep the ordinary list running underneath, since signals only ever cover a slice of the market. Signal plays get worked first and list-based outbound fills the rest of the day. Review the plays every quarter, retire the ones that don't produce meetings, and watch for the four habits that sink most programs: acting days late, treating one weak signal as urgent, sending a generic sequence after a specific signal, and quoting private behavior back at the prospect.

The bottom line

Signal-based selling is less about the signals than about what a team commits to doing when one fires. The data has been easy to buy for years. The teams that get meetings from it have a short list of written plays, an owner for every signal, deadlines that match how fast each signal fades, and messages about the buyer's problem rather than their browsing.

It also has to beat the alternative. A play that can't outperform comparable accounts from the ordinary list adds tooling cost without adding pipeline, and should be fixed or switched off. The plays that survive that test become the most reliable part of how a company finds and wins new customers, because they put a rep in front of the right account at a moment when the account has a reason to listen. That's what reading buying intent is for in the end.

When Nebor sets this up, the plays become real routing rules, alerts and sequences in the client's CRM and Clay workspace, written down in plain language next to the rules themselves. The team that runs them can then add a play, retire one or move a deadline without waiting on us.

Frequently asked questions

Does signal-based selling replace list-based outbound?

No. At any moment only a small part of your market shows a signal strong enough to act on, so signals alone rarely fill a pipeline. Most teams run both. Accounts with a qualifying signal go to the front of the queue and get a message tied to it, while good-fit accounts that haven't signaled yet still receive steady outreach from the ordinary list, with lower expectations for reply rates.

How is signal-based selling different from a sales signal stack?

The signal stack is the set of sources and tools that detect signals, such as website visitor identification, job-post data, funding news and intent feeds. Signal-based selling is what the sales team does with that output: who acts on which signal, how quickly and with what message. A stack with no plays behind it produces alerts nobody acts on, and plays with no stack have nothing to fire on.

Where does lead scoring fit into signal-based selling?

Scoring decides which signals are worth a person's time. A fit score sets the floor an account must clear before any play fires, and an intent or engagement score ranks accounts when several signals arrive in the same week. The plays then decide what happens next. Scoring without plays gives you a ranked list nobody works, and plays without scoring send reps after busy accounts that were never a fit.

Can a small sales team run signal-based selling without new software?

Yes, for one or two signals. A founder or a single rep can check job boards, funding news or the company's own website analytics each morning and write to fitting accounts the same day. Doing it by hand for a few weeks shows which signals lead to conversations in your market. Automating detection and alerts only becomes worth paying for once a play is producing meetings and the manual checks start taking too long.

Is signal-based selling the same as inbound-led outbound?

Inbound-led outbound is one kind of signal-based selling. It uses first-party signals, mainly visits to your own website from companies that didn't fill in a form, to trigger outreach. Signal-based selling is the wider practice and also acts on outside events such as funding rounds, executive hires, hiring pushes and third-party research. Most teams run inbound-led plays alongside plays built on public company changes.

Who should own signal-based selling, sales or marketing?

Usually both, with a clear split. Marketing or RevOps tends to own the sources, the fit filters and the scoring, because those are shared data decisions. Sales owns the plays: the messages, the sequences and the follow-up. The handover point should be written down, along with who can change a play's filters, so that neither side changes what the other relies on without warning.

Should an AI SDR act on signals without a rep involved?

For some plays it can. High-volume, low-stakes plays, such as a short sequence after a relevant job ad at a small company, can run end to end once the messages have been tested by people. Plays aimed at senior buyers at large accounts are better handled as an AI-written draft that a rep checks and sends. Either way, a person should review a sample of outgoing messages every week.

Is signal-based selling the same as account-based marketing?

They overlap but aren't the same. Account-based marketing starts from a fixed list of named target accounts and coordinates marketing and sales around them over months. Signal-based selling decides when and why to approach an account based on what it is doing now, and it can run on any fitting account. Many teams use signals inside ABM to decide which named accounts get attention this week.

Why do signal-based selling programs stall after the first month?

The usual causes are organizational rather than technical. Alerts arrive without a clear owner, so they sit unanswered. Too many signal sources get switched on at once, the volume overwhelms reps, and they mute the channel. Messages fall back to a generic template, so prospects can't see why they were contacted now. And nobody compares results with the ordinary list, so nobody can show the program is working.

Share this post

Outbound

Intent

Revenue tips, Weekly

Workflows, automation strategies, and GTM insights delivered straight

Ready to build your
GTM engine

Let's talk about your sales challenges and how we can help you scale

Nebor brand chevron in purple, section accent
Nebor brand chevron in orange and purple, section accent
Revenue tips, Weekly

Workflows, automation strategies, and GTM insights delivered straight

Ready to build your
GTM engine

Let's talk about your sales challenges and how we can help you scale

Nebor brand chevron in purple, section accent
Nebor brand chevron in orange and purple, section accent

Ready to build your pipeline

Let's discuss how to implement lead generation into your GTM strategy

Let's discuss how to implement lead generation into your GTM strategy

Book a call with our team to discuss how this workflow fits your sales process and timeline.

Services

Case Studies

Resources

About

Services

Case Studies

Resources

About

Nebor logo, a go-to-market and RevOps agency based in Amsterdam

Services

Case Studies

Resources

About

Nebor logo, a go-to-market and RevOps agency based in Amsterdam