Generic cold outreach is dead, but outbound is very much alive. The difference is signal. A signal is a dated, verifiable event that tells you a prospect has a reason to listen right now. Outbound that leads with signal is not cold, it is contextual.
This post walks through how BRG builds signal-based lists from scratch, what data sources we actually use, and the common traps teams fall into when they try to move from firmographic lists to signal lists.
Three Categories of Signal
Structural signals are changes inside the target company. Funding announcements, hiring bursts, leadership hires, acquisitions, new office openings, product launches, and layoffs. These shift budget availability and strategic priority.
Technology signals are changes to the prospect stack. New platform adoption, legacy system sunsetting, integration additions, and app store listings. These signal either urgency (migration window open) or adjacency (new tool in, complementary tools next).
Intent signals are public behavior that indicates active evaluation. Webinar attendance, review site activity, conference attendance lists, podcast appearances on relevant shows, public commentary on specific problems, and content consumption patterns.
The Signal Sources We Use
Every source below has failure modes. Use them in combination, not alone.
Apollo
Core firmographic and persona data, plus basic signals like recent funding and employee growth. Apollo is the backbone for most SDR teams because the data is deep and the API is reliable. Weakness: the signals are lagging indicators and often shared with thousands of other teams already.
Clay
Clay is less a data source and more an orchestration layer. It pulls from dozens of enrichment providers, runs conditional logic, and lets you build signal workflows with AI in the middle. Where Clay wins is combining three or four weak signals into one strong one. A company that raised a Series A, hired a VP of Sales in the last 60 days, and just posted 4 SDR openings is a different prospect than any of those alone.
TheirStack
Technographic signals from job postings. If a company posts a role requiring HubSpot experience, they almost certainly run HubSpot. If they post a role mentioning "migrating off Marketo," they are an active in-market buyer for marketing automation. TheirStack reads this from public job descriptions at scale.
Netrows
Reverse IP lookup on website visitors. Not a traditional outbound signal but useful for "who is checking us out right now." Overlaps with 6sense and RB2B in the intent data category.
LinkedIn Sales Navigator
Underused for signals. Sales Navigator tracks leadership changes, job changes, and recent posts, all of which are usable triggers. Pair this with a scraper like PhantomBuster or the Clay LinkedIn integration to pull signal data into your list building workflow.
Manual scraping for niche signals
Industry-specific signals rarely show up in commercial databases. Licensing board filings for insurance MGAs, FMCSA records for freight brokerages, PE portfolio announcements, union contract expirations. For specialized verticals these signals convert better than anything you can buy, because nobody else is sending outreach referencing them.
The Signal Decay Problem
Every signal has a half-life. Funding news is hot for about 90 days. Leadership changes are hot for 60. Job posting surges are hot for 30. Technology migrations are hot for whatever the migration window is (usually 90 to 180 days). After decay, the signal is noise.
Build your workflow to filter signals by age, not just presence. A Series B funding announcement from 18 months ago is not a signal, it is history. A Series B from last Tuesday is active budget.
The Combination Rule
One signal is a reason to consider. Two signals is a reason to sequence. Three signals is a reason to prioritize. The higher the stakes of your offer, the more signals you should require before adding a prospect to a primary tier.
For a $500/month SaaS tool, one signal is fine. For a $50,000 agency retainer or a six-figure enterprise license, three signals is the minimum bar.
The BRG ICP Engine
BRG built an internal tool called the ICP Engine to combine signals from Apollo, Clay, TheirStack, and custom scrapers into a single ranked prospect list, filtered through client ICP rules. Part of every DFY and IOY engagement.
Common Mistakes
Buying a 10,000-row list from one provider and calling it signal-based. Apollo alone is not signal-based. You need multi-source enrichment and filter logic.
Not tracking signal-to-meeting conversion by source. If you do not know which signal types are converting best for your business, you cannot optimize list spend.
Letting stale signals pollute your list. Set an automatic decay window. Signals older than 90 days get demoted or dropped.
Writing signal-based messaging with a generic template. If your cold message does not explicitly reference the signal that qualified the prospect, you wasted the signal.
What to Build First
If you are starting from zero: pick one primary signal type that maps cleanly to your buying trigger (funding, hiring, tech migration, or leadership change). Build a workflow that pulls that signal daily. Filter through your ICP. Write messaging that explicitly references the signal. Run this for 60 days before adding complexity. One clean signal beats five messy ones.