What signal-based prospecting actually looks like in a CRM

A sales team that buys intent data and pipes it into a dashboard has bought a report. A sales team that routes the same data into the CRM, scores it against ICP fit, and puts it in front of the right rep at the right hour has bought a motion. The difference is entirely plumbing.

Over the last year we have built this in HubSpot and Salesforce for about a dozen B2B teams. The architecture is consistent enough that it is worth writing down.

1. Decide what counts as a signal

Most teams start too broad. A signal is only useful if a rep can act on it within a week and if the action is obviously different from what they would have done anyway. In practice that narrows the list quickly:

• A target account hires into a role that owns your budget line.
• Two or more people from one domain visit pricing within 14 days.
• A closed-lost champion appears at a new company in the ICP.
• A competitor renewal window opens, inferred from job posts or tech-stack change.

Everything else — funding rounds, generic content downloads, LinkedIn follows — goes into the enrichment layer as context, not into the queue as a trigger.

2. Land signals on the record, not in a report

Signals belong on the company object. We create a small set of properties — signal type, signal date, signal source, signal strength — and write to them from Clay or the vendor webhook.

The winning setups were never the ones with the best data. They were the ones where acting on the data was the path of least resistance.

3. Score fit and intent separately

Collapsing ICP fit and buying intent into one number destroys information. A perfect-fit account with no activity needs nurture; a poor-fit account browsing pricing needs a qualification call, not a sequence.

4. Give the queue an expiry date

Signal-driven tasks should disappear. We set a 10-day time-to-live on every triggered task: if it has not been worked, it closes and the account drops back to the standard cadence.

5. Measure the delta, not the volume

The metric that matters is not how many signals fired. It is the reply rate and meeting rate of signal-triggered outreach against your baseline cadence over the same window.