You open the CRM on Monday morning. Two hundred accounts. Which ones are worth calling? Most reps solve this with gut feel or alphabetical order. Neither works.
Signal-based selling replaces the guess with data: behavioral and event signals decide which accounts a B2B SaaS sales team works and when, and the rep gets the reason in plain language.
At a Series A identity security company, I built the system that answers that question with data. It monitored 400+ named accounts in Clay, scored each one hot, warm, or cold every week, and put a one-pager in Salesforce telling the rep why this account and why now. This post is what I built, what it costs to run, who runs it, and what I would change.
The system at a glance
Five pieces, in the order they run:
- A named account list, built from the ICP and kept at 400+ accounts. Small enough to know, large enough to produce pipeline.
- Clay workflows monitoring signals across the list: new CISO or security-leadership hires, security headcount growth, compliance events and breaches, funding rounds, and tech-stack changes that indicated fit.
- A weekly scoring pass that rolled the signals into hot, warm, or cold per account. Accounts with multiple concurrent signals went to the top of the outbound list.
- A one-pager in Salesforce for every hot account: the signals, the likely angle, and the people to reach. Reps never left the CRM to use the system.
- Battlecards for accounts in motion, personalized from the signals, so outreach referenced what was actually happening at the account instead of opening with a pitch.
The outcome metric was close-rate parity: rep-sourced deals closing at the same rate as founder-sourced ones. That is the honest test of a prospecting system, because founder deals close on context and timing, and parity means the system is supplying both. The Signal Engine case study covers how the same engagement played out.
What it costs, and who runs it
Two things get scoped before anything gets built.
The first is the run cost. The system runs on paid compute: Clay credits, enrichment waterfall lookups across the provider chain, and LLM tokens for the generated one-pagers. I model the per-account monthly cost across the full list and put it in the scope as a line item, so the CFO sees the operating cost before the system exists instead of finding it on the first invoice.
The second is ownership. The scope names owners before launch. Who owns the Clay tables and workflows when they break. Who triages signal quality when a source goes noisy. Who runs the quarterly re-weighting. Who owns the Salesforce integration. Those rules live in documentation, the company brain approach I use everywhere now, so the system survives handoff instead of living in the head of whoever built it.
What signals actually tell you
Signals come in three categories, in ascending order of how hard they are to get and descending order of how well they explain themselves.
Contextual signals are events that precede buying: a new executive in the buying role, a breach or compliance failure in a security market, a funding round, job postings for the roles your product serves. These were the workhorse of the system. They are public, they are timely, and a rep can open with them naturally, because “you just hired a CISO” is a reason for a conversation and “you scored 87” is not.
First-party signals come from your own properties: pricing page visits, case study downloads, multiple people from one account showing up in the same week. Most reliable, least available at Series A, because your traffic is thin. They got heavier weights and lighter volume.
Third-party intent comes from providers who track research behavior across the web. Useful, with one warning from the field: the black-box platforms that score accounts for you and cannot show the rep why are the ones reps quietly stop trusting. If the rep cannot see the reason, the score changes nothing about the call. Transparency beat sophistication every time I watched this play out.
How to build the scoring model
Work backward from closed-won. Which signals appeared before those deals entered pipeline, and how far in advance? Weight accordingly. Ours looked roughly like this, adapted to the security market:
- New security-leadership hire: heavy
- Breach or compliance event: heavy
- Security team headcount growth: medium
- Funding round: medium
- Pricing or product page visit: medium, heavier if multiple visitors
- Content engagement: light
Accounts crossing the hot threshold triggered rep action that week. Warm accounts went into nurture. Cold accounts were left alone, which matters as much as the rest: the system’s job is also to stop reps from burning goodwill on accounts with no current reason to talk.
Two mechanics kept it honest. Decay: signals age, and a pricing visit from three months ago is trivia, so scores fell automatically when new signals stopped. Quarterly re-weighting: the first model is always wrong, and the discipline is checking which signals actually preceded pipeline and adjusting, so the model gets less wrong each quarter.
Why Clay, and what the tool actually bought us
The enrichment layer matters because signals get matched to accounts, and bad firmographic data sends the right signal to the wrong record. Clay’s waterfall approach, querying multiple providers and taking the first good answer, gave us coverage a single-provider contract could not, at a fraction of the cost, and its research agents handled the lookups that used to be an SDR’s afternoon.
But the tool is the least interesting part of the story. I have watched companies buy the same stack and get nothing, because the scoring discipline, the CRM one-pager, and the weekly cadence were missing. The tool monitors accounts. On its own it produces no pipeline.
What made reps actually use it
Every prospecting system dies the same death: reps ignore it. Three choices prevented that.
The answer lived where reps work. The one-pager was in Salesforce, on the account. No new tab, no separate dashboard, no login to forget.
Every score came with a why. The signals were listed in plain language with dates. A rep could defend the outreach in their own words, which meant they trusted it enough to send.
Volume stayed capped. A handful of hot accounts a week per rep, not fifty alerts a day. Alert fatigue is how good systems get muted. Better to miss an opportunity than to train reps to ignore the channel that finds them.
What I would do differently
Positioning first, signals second. A signal tells you when to reach out. It cannot fix what you say when you get there. Where messaging was still generic, well-timed outreach just failed faster. If your positioning has not been validated against real buyer language, run that diagnostic before wiring signals.
Hold the outcome metric from the start. Activity metrics recover instantly and mean nothing. Close-rate parity took two quarters to show, and it was the number that made the board conversation simple.
Signal-based selling is one lane of a larger loop: positioning feeds content, content feeds signals, signals feed prospecting, prospecting feeds pipeline, pipeline feeds measurement. Wire it into that operating model and it produces pipeline you can forecast. On its own it is the next dashboard nobody opens.
If you are building this
Everything above is enough to build it yourself. The tooling is the easy part. What decides whether it produces pipeline is the discipline: keeping the weekly pass honest, and actually re-weighting each quarter instead of letting the first model calcify.
Two situations are worth outside help. If your company changed its story recently, a rebrand, a new category, a move upmarket, and pipeline has not caught up, signals wired to the old ICP point reps at the wrong accounts. You get well-timed outreach that fails faster. The Gap Map is the two-week diagnostic I run to find which of your four systems still tells the old story, targeting and signals included. If you want the outside view first, the AI Visibility Baseline is the free preview: enter your brand and category and it shows where AI assistants surface you, or your competitors, on the questions that start a deal.