When's the last time a lead showed up in your outbound with the actual reason attached to it, not just a name and a title?

If you're running a normal outbound stack, the honest answer is probably never.

Everyone has the data. Almost nobody has the system.

Estimated reading time: 4 min 35 sec

Background

Hey, I'm Miguel!

I run The SaaS Consultants, a remote full-service sales and marketing agency that helps SaaS companies launch their first sales-led motion, spanning cold outbound, paid ads, and sales hiring. Running it remotely means I get to live as a digital nomad. I'm currently in South America, working toward C1 fluency in Spanish.

My favorite part of running the agency is the GTM engineering side: building the automation and systems behind growth (Clay, Make, n8n, cold email and calling stacks, paid media funnel buildouts, CRMs) instead of just running campaigns by hand. It lets me use my engineering background instead of leaving it behind.

Before the agency, I was a software engineer, including a stint at a big tech company, a B2C AI startup I exited just three months after launch, and a B2B SaaS product I built to recurring revenue. I split my time between the agency, travel, and learning new languages.

Want to know exactly which GTM system to fix first?

Take the 60-second GTM Readiness Assessment

I'll tell you your biggest constraint and the exact next step to fix it.

1. The one signal everyone already uses, and why it's dying

Job changes are the most saturated signal in B2B right now.

You know the message. "Noticed you recently joined {COMPANY}. That's exciting. Congrats!! Sooo... want to buy?"

Someone called this out this week and got it exactly right: job change signals are probably the most overused and saturated signal for sales teams. Every SDR tool ships this trigger out of the box. Every prospect has seen it a dozen times.

That doesn't mean signal-based outbound is dead. It means most people only ever built one signal, and they built the easiest one to spam.

2. Signals are a category, not a single trigger

There are four real categories of buying signal, and most teams only touch one.

I break this down with clients constantly, so here's the actual taxonomy:

  • Intent signals. Research and content engagement. Visiting competitor pricing pages, downloading a comparison guide, showing up in a G2 category search.

  • Growth signals. Funding rounds, aggressive hiring, new office openings, traffic spikes. Companies that are expanding usually need new tools and infrastructure to support it.

  • Change signals. Leadership transitions, tech migrations, org restructuring. These open doors because someone new is making decisions differently than the last person did.

  • Distress signals. Public complaints, negative reviews, compliance issues. These create urgency and openness to switching that a cold list never will.

Job changes are one flavor of change signal. That's it. One flavor of one of four categories, and it's the one every competitor is already firing off the same script against.

The other three categories are wide open, mostly because they're harder to monitor than "did this person's title change on LinkedIn."

3. Why almost nobody actually runs this as a system

Having the data isn't the bottleneck. Turning it into a live process is.

Most B2B teams aren't short on data. They've got intent signals sitting in their analytics, engagement data in their CRM, and technographic data a few clicks away. What they don't have is a pipeline that watches for a signal, fires an enrichment, and routes a qualified lead into outreach without a human manually pulling a list first.

That's the actual gap the "zero of 50" stat is pointing at. Most companies still run outbound as a batch process: pull a list, enrich it, upload it, send it, repeat next month. A signal-based system runs as a loop instead. Something happens, the system reacts, and by the time your rep sees the lead, the context is already attached to it.

Batch versus loop is the real difference between list-based and signal-based outbound. It has nothing to do with whether you own a Clay seat.

4. The pipeline that actually makes this work

The build is simpler than it sounds. It's five steps, and you already have the pieces.

Here's the version I run for clients, generalized so it works regardless of which signal category you're monitoring:

  1. Pick one signal source. A LinkedIn event, a review site category, a job board, a tech stack monitor. Start with one, not five.

  2. Filter before you enrich. Qualify on role first. Decision-maker titles only, and strip out agencies, freelancers, and job seekers before anything touches your enrichment budget.

  3. Enrich the qualified set. Company domain, verified work email, company size, whatever your ICP actually needs to score the lead. Not everything Clay's 150+ providers can pull, just what you'll use.

  4. Score it against your ICP, not just your TAM. Total addressable market tells you who could buy. Your ICP tells you who's most likely to buy right now. A signal without an ICP filter just gives you a bigger, faster version of a bad list.

  5. Route it with the signal attached. The rep or the sequence needs to know why this lead showed up today. "Sarah attended your competitor's webinar last Tuesday" is a personalization hook. A cold name with no context isn't.

Step 5 is the one everyone skips. They build the enrichment, then dump the output into the same generic sequence they were already running. The whole point of a signal is that it explains the timing. If your outreach doesn't reference it, you've built an expensive way to generate a regular list.

5. The failure mode worth naming

Signals without judgment become the exact thing they were supposed to replace.

I saw pushback on this too, and it's fair: someone called signal-based outbound "the new version of AI slop in GTM." They're not wrong about the failure mode, they're wrong about the cause.

The slop version looks like this: a signal fires, a template fills in the trigger event, and a message goes out within the hour with zero human judgment anywhere in the loop. That's not signal-based outbound. That's list-based outbound with a faster trigger.

The fix isn't to abandon signals. It's to keep a qualification step in the loop, the same way step 2 and step 4 above do. A signal tells you when to reach out. It doesn't replace the work of confirming who and figuring out what to actually say. Skip that, and you've built spam with better timing.

Conclusion

The lists everyone's still running on are the same lists everyone else has access to. The signal everyone's already automated is the one that's most saturated.

The whitespace isn't in finding a smarter list. It's in the three signal categories almost nobody has bothered to wire up, and in actually building the loop instead of running the same monthly batch with a new coat of paint.

Ask yourself that question again. When's the last time a lead showed up in your outbound with the reason already attached? If the answer is never, that's not a scary answer. That's the whitespace nobody's built into yet.

Want to know exactly which GTM system to fix first?

Take the 60-second GTM Readiness Assessment

I'll tell you your biggest constraint and the exact next step to fix it.

Already know you want to work together? Skip the assessment and grab 30 minutes with me directly.

Reply

Avatar

or to participate