Learn

Signal-based prospecting

Reach accounts when something just changed that makes your offer relevant.

Roadmap: Data, enrichment & signals

Why it matters

Static lists of companies that fit the ICP get the same emails as everyone else. Signals add timing: a company hiring its first RevOps lead, a new VP who just joined, a funding round, a competitor's tool appearing on their site, a visit to your pricing page. Outreach tied to a real, recent event typically gets noticeably higher reply rates than cold lists, and it gives the copy something specific and true to say. Building reliable signal detection, scoring and routing is core GTM engineering work.

What it's made of

  • Brainstorming signals from the customer's buying journey
  • Sorting signals by strength, freshness and how easy they are to detect
  • Sources: job posts, funding, leadership changes, tech installs, web visits, product usage
  • First-party signals: website, product, community, events
  • Scoring fit and intent separately, then combining them
  • De-duplicating and time-boxing signals so each one triggers once
  • Routing signals to the right owner and play
  • Measuring which signals actually predict meetings

Where good signals come from

Look at the last 20 deals you won and ask what happened at each account in the 90 days before the first conversation. Common answers: they hired for a role your product supports, a new leader arrived, they adopted or dropped a related tool, they expanded to a new region, they raised money, or they visited your site repeatedly. Those events are your candidate signals, and they're specific to your product. Copying another company's signal list rarely works.

Rate each signal on three things

  • Strength: how strongly does it suggest a need? A job post for the exact role your product helps is strong. A generic press release is weak.
  • Freshness: how fast does it decay? A new leader is most receptive in their first 90 days. A funding round in roughly the first few months.
  • Detectability: can you find it reliably and cheaply at scale, or only by hand?

Score fit and intent separately

Keep a fit score (does this account match the ICP?) and an intent score (are there recent signals?). A high-fit, high-intent account gets a fast, personal play. High fit with no intent goes into a monitored list. Low fit with high intent, such as a tiny company hammering your pricing page, might get a self-serve nudge rather than a sales rep. Collapsing both into one number hides that distinction.

Give intent points a time decay (for example, halve them every 30 days) so old activity doesn't keep an account at the top forever.

From signal to action

Every signal needs a defined play, or it's just noise in a dashboard:

  • Trigger: what exact event, from which source, with which filters.
  • Owner: the account owner if one exists, otherwise a routing rule.
  • Play: the sequence, task or alert it creates, and how the message uses the signal.
  • Suppression: don't fire again for the same account within N days, or if a deal is open.
  • Feedback: log the signal on the record so you can measure meetings per signal later.

Mid-level looks like

Sets up a few standard signals (new hires, funding, job posts) and routes matching accounts into a sequence.

Senior looks like

Derives signals from won-deal timelines, weights them by measured conversion, combines first- and third-party data, and retires signals that don't predict pipeline.

Common pitfalls

  • Treating every signal as equal, so a minor blog mention triggers the same play as a new decision-maker.
  • Mentioning the signal awkwardly ("Congrats on your funding!") instead of connecting it to a likely problem.
  • Acting on signals weeks after they happened, when the moment has passed.
  • Building twenty signals and never checking which ones produce meetings.

Practice drills

  1. Drill 1

    For a product that helps companies onboard new sales reps faster, list ten possible signals, rate each on strength, freshness and detectability, and pick the top three to build first.

    A strong answer: Signals tied to the product's actual value, honest detectability ratings, and a ranking that favours strong, cheap-to-detect signals.

  2. Drill 2

    Design a scoring model that combines fit and intent for 10,000 accounts, including time decay. Show how three example accounts would score and what play each gets.

    A strong answer: Separate fit and intent dimensions, explicit weights with reasons, decay, and different actions per quadrant.

  3. Drill 3

    After two months, you have meeting data for 8 signals. Describe how you'd decide which to keep, re-weight or drop.

    A strong answer: Meetings per 100 accounts triggered by each signal, sample-size caution, comparison against a no-signal baseline, and a plan to retest borderline signals.

Best resources for this skill

Repos, courses, articles and podcasts, ranked by how much they teach.

Podcast

The Clay Playbook for Hyper-Targeted Outbound | How to Turn Multiple Signals Into One Story | Why Your List Matters More Than Your Message | The "Magic Wand" Framework for Finding Your Best Customers…

Most founders think GTM engineering is just cold outbound done better. Clay's Head of GTM Engineering Osman Sheikhnureldin reveals why that mindset will cost you months of wasted effort. In this episode, Osman walks us through exactly how to identify your ideal customers at the perfect moment, then demonstrates his framework live with two early-stage founders - showing you can't just wing GTM eng…

focal podcastDec 202575 min
Podcast

Your Skills Should Outlive Your Stack ft. Fahad Ali Khan

In today's episode, I chat with Fahad, a GTM engineer with a background in B2B sales, about running signal-based outreach at scale for an enterprise client. Fahad breaks down how he built a Clay table pulling multi-location account data through Serpo.dev's HTTP API, running parallel Clay agents to qualify accounts against the client's criteria and segment them into tier one, tier two, and tier th…

The GTM Engineer PodcastJul 202612 min
Podcast

GTM Engineer: Everett @ Clay

Everett Berry's definition of GTM engineering is deceptively simple: remove the technical constraints that stop companies from growing as fast as possible. But in this episode, he unpacks what that actually requires in practice, and most senior GTM leaders will recognize immediately that the bottleneck almost never comes from a lack of ideas. From how Canva monitors customer social feeds at scale…

Stacked GTMMay 202656 min
Podcast

Turn Your Best Sales Rep Into A Machine ft. Yuval Canfi

In today's episode, I chat with Yuval Canfi, GTM Engineer at Celery, about building custom outbound machines for internal sales teams. Yuval walks through the platform he built at his previous company, Eko: type in a company name and Clay finds the website, pulls threshold signals like headcount, location, and vertical, and ranks accounts by likelihood to close. Only the top-ranked companies get…

The GTM Engineer PodcastSep 202617 min
Podcast

The #1 GTM Engineer In The World | Jordan Crawford, Founder @ Blueprint GTM

In this episode, Jordan Crawford outlines how revenue leaders can build an autonomous pipeline generation engine and transition away from static playbooks. The discussion covers practical methods for extracting competitor usage data, identifying segments of users who are far more likely to buy, and generally how top GTM teams are using GTM Engineering to dramatically improve their results. The ho…

ToplineApr 202656 min
Podcast

Great GTM Strategy Starts With A Story ft. Aamir Massoud

In today's episode, I chat with Aamir Massoud, GTM Lead at Numero, about running precise, signal-driven outbound with a lean team inside one of the more complex enterprise sales environments — the office of the CFO. Numero is a vertical AI platform that deploys agents into finance and accounting workflows without ripping out ERPs or CRMs. Aamir breaks down why he starts every GTM build not with a…

The GTM Engineer PodcastAug 202619 min

Read next

Next skillOutbound infrastructure & deliverability