Signal-led outbound: eight signals worth acting on

Your SDR team sent 12,000 emails last quarter. The reply rate was under 1%, two sending domains ended up on blocklists, and the meetings that did get booked were mostly with people who were never going to buy.

Meanwhile, one of your best-fit target accounts hired a new CRO, posted six SDR roles and visited your pricing page three times in a week. Nobody noticed. The account was sitting in a list, waiting for step four of a generic sequence.

That is the gap signal-led outbound closes. Volume is rarely the problem in modern outbound. Timing is.

What a signal actually is

A signal is a change at an account that makes your offer more relevant right now. It is not a firmographic fact ("they have 400 employees") and it is not a guess ("they are probably growing"). It is an event, with a date, that you can point to in the first line of a message.

The best signals share three traits: they are observable (you can see them in public data or your own systems), recent (days or weeks old, not months), and connected to your value (they create or sharpen a problem you solve).

The eight signals

1. Hiring in the roles you serve. A first RevOps hire, a wave of SDR roles or a new data team. Hiring is budget being spent on the problem you solve.
2. Funding. New money comes with new targets and a board asking how the plan will be hit. Strongest in the first 90 days after the announcement.
3. Leadership changes. A new CRO, CMO or VP Sales usually reviews the stack and the process in their first quarter. They are looking for quick wins with their name on them.
4. Technology changes. A CRM migration, a new tool in your category or the removal of a competitor's tag from their website.
5. Website intent. Repeat visits to pricing, comparison or integration pages from the same company, especially by more than one person.
6. Champion job moves. A past user or buyer who knows your value has joined a new company. These convert better than almost any other signal.
7. Expansion. New offices, new markets, new product lines or a big new customer announcement.
8. Product usage. For existing customers or free users: teams approaching plan limits, new departments signing up, or a key feature being adopted fast.

Not every signal is equal, and not every account deserves a response. That is where most teams go wrong.

Score signals by strength and fit

A single blog visit from a poor-fit company is noise. A new CRO at a perfect-fit account is a priority. Two things decide which is which:

• Signal strength: how directly the event connects to a buying decision, and how recent it is. A champion move this week is strong. A funding round from last year is not a signal any more.
• Account fit: how closely the account matches the customers you win and keep. Industry, size, tech stack and business model all count.

Put the two together and you get a simple map of what to do with each account.

A simple scoring model is enough to start. Give each signal type a base score from your own win data (champion moves and leadership changes usually top the list), multiply by account fit, and decay the score over time. A useful rule of thumb is to halve a signal's weight every 30 days and drop it after 90.

Route strong signals to a named owner

The second common failure is detection without action. Signals land in a shared list or a dashboard, and by the time anyone looks, the moment has passed. Routing fixes that: every signal above a threshold goes to a named person, with a response time.

The thresholds are a starting point, not a rule. Set them so the account executive bucket holds only as many signals as your team can genuinely act on within the response time. If it fills up every week, raise the bar; if it is empty, lower it or add another signal source.

Make the response time visible. A weekly view of "signals routed, signals actioned within SLA" tells you more about outbound health than any activity count.

Write the first line from the signal

When a message starts from a real event, the reason for reaching out is obvious, and the rest of the email can be short. The structure that works best is three parts: the signal, the problem it usually creates, and a low-effort question.

Notice what is missing: no company history, no feature list, no "I hope this finds you well". The signal does the work that personalisation tokens pretend to do.

Each signal type suggests its own angle. A few patterns that work:

• New leader: their first 90 days are about quick wins. Offer one specific, low-effort improvement others in their role have made.
• Funding: the board now expects a plan for growth. Talk about the bottleneck that usually appears when teams scale after a raise.
• Champion move: lead with the shared history. They already know what you do; ask whether the same problem exists in the new role.
• Pricing page visits: do not mention the tracking. Answer the question they were probably asking, such as how pricing works for a team their size.
• Technology change: a migration creates work and risk. Offer help with the part that usually goes wrong.

Keep a short library of these angles, written by your best reps, and let agents draft from it rather than inventing a new pitch for every account.

Measure meetings per signal, not emails sent

Signal-led outbound sends far fewer messages, so activity metrics will look worse before results look better. Measure the funnel by signal type instead, and you will quickly see which signals deserve more attention.

Take a team that moves from 12,000 generic emails a quarter to around 80 signal-led contacts a month. The worked numbers below show why the trade is worth it. Swap in your own.

Common mistakes

• Watching too many signals at once. Start with the three that best match how your best customers bought. Add more only when the first ones are working.
• Treating every signal the same. A champion move and a single blog visit are not the same event. Score them.
• No expiry. Signals decay. A rule that drops anything older than 90 days keeps the list honest.
• Ignoring existing customers. Hiring, funding and leadership changes at current accounts are expansion signals too. Route them to the account manager, not only to new business.
• Mentioning the tracking. "I saw you visited our pricing page" feels like surveillance. Use the signal to choose the topic, not as the opening line, when the signal is private.
• Automating the send. Let agents detect, score, research and draft. Let a person decide what goes to a buyer, at least until edit rates prove the drafts are consistently good.

Where AI agents help

Signal work is a strong fit for AI agents because it is constant, repetitive and spread across many sources. An agent can watch job boards, news, funding databases, your website analytics and your CRM every day, match each event to the right account, score it, research the context and draft the first message with the signal quoted. A person reviews and sends. Every action is logged to the CRM, so you can see later which signals turned into pipeline.

That log is what makes the system improve. After a quarter you can see which signal types produced meetings and which produced nothing, and reweight the scores from your own results rather than a vendor's defaults.

Where to start this week

1. Pull your last 20 closed-won deals and note what changed at each account in the 90 days before the first meeting. Those are your first signals, taken from how your own customers actually bought.
2. Pick the top three and set up a simple way to see them weekly, even by hand.
3. Route each one to a named owner with a response time, and track meetings per signal for a month.

That is the work our Core program, with a revenue intelligence focus, covers: signal detection across your sources, account scoring with the reason recorded, and rep-ready briefs and drafts, built into your CRM.