Apollo gives you 275 million leads. That’s your problem.

Most B2B sales tools compete on database size. The teams actually hitting quota compete on signal quality. These two things are not the same, and confusing them is costing you pipeline.

Cameron Evans · Founder & CEO, Haku

19 June 2026 · 7 min read

Before I built Haku, I was a sales rep. A decent one — consistently in the top tier of a Series A SaaS company, managing my own pipeline, working a quota every quarter. And like every rep at every company trying to scale outbound in the last five years, I had access to Apollo.

Apollo is genuinely impressive. More than 275 million contacts. Dozens of filters. Sequences built in. A free tier that lets you start immediately. For a founder who has just raised their first round and needs to start building pipeline fast, it looks like everything you need.

The problem is not Apollo. The problem is what happens when you give a sales team 275 million people to contact and no clear framework for which ten thousand actually matter right now.

Volume without signal is just noise with extra steps

When I was running outbound, the tools I used gave me access to enormous databases. The workflow was the same every time: set some filters — company size, industry, job title — export a list, load it into a sequence, and start sending. It is a workflow that most B2B sales teams still run today, and it is why average cold email reply rates in 2026 sit at under 3.4%.

The instinct when reply rates drop is to increase volume. Send more emails. Call more contacts. Extend the sequence. But this is treating a relevance problem as a reach problem, and it makes things worse. Every irrelevant email you send trains the market to ignore you. Every cold call to someone who has no reason to speak with you today damages the reputation of your brand with that contact permanently.

“The problem is not finding enough people. It is finding the right people at the moment they are actually ready to buy.”

Signal-based selling solves this. Rather than building a static list and working through it, you identify the observable triggers that indicate an account is entering a buying window — a funding round, a key hire, a new product launch, a technology change, an uptick in relevant job postings — and you reach out at that moment, with a message that reflects what is actually happening in that business right now. Across Haku clients, timing outreach to buying signals drives a 32% increase in outbound engagement versus untriggered cold sequences. That improvement is not driven by sending more — it is driven entirely by sending at the right moment.

Why big databases make the signal problem worse

Here is the counterintuitive truth about large contact databases: the bigger the database, the harder it is to run a signal-based motion.

When a rep opens Apollo and sees 275 million contacts, the rational behaviour is to cast a wide net. The filters are good — you can narrow by title, company size, industry, funding stage, tech stack — but the output is still a list. A list has no inherent prioritisation. It does not tell you which accounts have just raised a Series B and are actively building a sales team. It does not tell you which companies have just switched CRM and are re-evaluating their entire stack. It does not know your ICP well enough to surface the fifty accounts you should be calling today versus the fifty thousand you theoretically could.

The gap between a list of leads and a ranked, signal-triggered account view is the gap between a team hitting 43% of quota — the current average across B2B sales — and a team that is consistently above it.

What buying signals actually predict a purchase

Not all signals carry the same weight. In practice, the triggers that most reliably indicate an account is entering a buying window are the ones that reflect genuine organisational change — not passive browsing behaviour that could mean almost anything.

The signals worth building around

Headcount growth in the sales or revenue function is one of the strongest. A company actively hiring SDRs or Account Executives is, by definition, investing in outbound — and they will need the tools to support it. A new VP of Sales or RevOps hire is equally significant: new leaders almost always audit and replace the existing stack within their first ninety days. A recent funding round signals budget availability and growth intent. A CRM migration signals a team actively re-evaluating their infrastructure.

Job postings alone — the default signal for most outbound teams using generic data tools — are weak in isolation. A job posting tells you a company is hiring. It does not tell you whether they have budget, whether they are in a buying cycle, or whether the role is relevant to what you sell. Stacking signals — combining a funding event with a new hire with a relevant job posting — is where the precision comes from.

Why timing matters more than the signal itself

A signal is only useful if you act on it quickly. The same trigger that represents a genuine opportunity today becomes background noise in a week, once the new hire has settled in, the budget has been allocated, and the vendor shortlist has been formed without you on it. The teams that win on signal-based outbound are not the ones with the most signals. They are the ones whose systems surface the right signal fast enough to act on it before it expires.

The real cost of bad data at the point of signal

There is a failure mode that kills signal-based outbound before it starts, and it is not strategy. It is data quality.

B2B contact data goes stale faster than most teams realise. People change jobs, companies restructure, email domains get retired. The moment a rep pulls a contact off a signal and finds a bounced email or a disconnected number, the opportunity is gone. By the time they have tracked down the right contact through manual research, the window has closed and a competitor has already booked the meeting.

The answer is not a larger database. It is a continuously validated one. At Haku, every contact is enriched through FullEnrich — a validation layer that aggregates more than seventeen independent data providers — ensuring the contact information attached to a signal is accurate at the moment of outreach, not at the moment the database was last refreshed. Our clients see 17% better data accuracy than teams relying on single-source static providers. In a signal-based motion, that gap is the difference between a sequence that lands and one that bounces before it starts.

What a signal-first outbound motion looks like in practice

The question I get asked most often when I describe this approach is: how do you actually build it? The answer depends on your ICP, but the structure is consistent.

Start with your business, not the database

A signal-first motion begins by understanding what an ideal customer looks like at the moment they are most ready to buy. That requires ingesting your own data — your CRM, your closed-won analysis, your case studies, the products you sell — and building a model of what good looks like before you ever open a prospecting tool. Most teams skip this step. They go straight to the database, set some filters, and start prospecting. The filters they set are based on static attributes — industry, headcount, geography — rather than dynamic buying behaviour.

Define the signals specific to your category

The signals that predict purchase intent vary by category. For a sales intelligence platform like Haku, the strongest signals are headcount growth in the sales or revenue function, a recent CRM migration, a new VP of Sales or RevOps hire, and evidence of investment in outbound tooling. For a fintech platform, the relevant signals might be a regulatory approval, a new market expansion, or a funding event. Generic intent data tools cannot make these distinctions. Custom signal models built around your specific ICP can.

Reach fewer accounts, more precisely

The operational output of a well-built signal model is a smaller, higher-quality list. Not 500,000 contacts you might eventually get to. A ranked view of the 500 accounts worth contacting this week, ordered by signal strength and recency, with validated contact data attached. Reps who work from this kind of list save a minimum of eight hours per week on research and validation alone — and they reach accounts at the right moment with a message that reflects what is actually happening in that business.

The question worth asking about your current stack

If your outbound motion is built primarily around a large contact database with static filters, it is worth asking what percentage of the accounts your team contacted last quarter were in an active buying window at the time of outreach. In most cases, the honest answer is: we do not know.

Not knowing is the problem. The tools that solve it are not the ones competing on database size. They are the ones competing on signal quality — on how accurately and how quickly they can surface the accounts that are ready to buy right now, with the validated data needed to reach them before the window closes.

That is the only outbound metric that compounds.