What Sales Prospecting Tools Actually Do

Sales prospecting tools are the software you use to get from "we should sell to businesses like that" to a message arriving in someone's inbox. The phrase covers at least four separate jobs, and the vendors selling under it own different combinations of those jobs. That is the whole reason buying one is confusing: two products described with identical words can do almost nothing in common.

The disclosure first, because it should change how you read the rest. We build Keaz Signals, which sells ecommerce leads with live buying signals attached. We compete for this budget and we have an interest in how you evaluate the category. So this is not a ranking and there is no shortlist at the end. It is a structural argument about what the four jobs are, which one is usually missing, and how to tell which one is missing in your case.

If you take one thing from it: most teams who feel their prospecting stack is broken go shopping for a better version of a layer they already have. The gap is usually somewhere else.

Four jobs hide inside the phrase. Finding the accounts, attaching a contact you can reach, sending and following up, and deciding who enters a sequence today rather than next month. Every prospecting stack does all four somehow — the question is only whether a tool does it or a person does it by hand.

1. Finding. Building the pool of businesses that could plausibly buy from you, and filtering it down to a segment. Industry, size, country, platform, installed software. This is the layer people usually mean when they say "lead database".
2. Verifying and enriching. Turning a company into a person you can actually email, and checking the address is real before you send to it. Sometimes the same vendor as layer one, often not.
3. Sending. Sequences, follow-ups, mailbox rotation, reply detection, and the infrastructure underneath — domains, warmup, reputation. A large and mature software category in its own right.
4. Deciding when. Choosing which of the thousands of accounts that match your filter get contacted this week, and on what grounds. This is the layer that most often has no tool in it at all.

Layers one to three have obvious buyers, obvious budgets and crowded markets. Layer four tends to be invisible, because it does not feel like software — it feels like judgement, or like the part of the job the senior person is good at. That is exactly why it survives unexamined in stacks that are otherwise well equipped.

The adjacent categories map onto these layers rather than replacing them. A sales intelligence platform is mostly layers one and two. A sales engagement platform is layer three with reporting on top. An AI SDR is usually layer three with drafting attached. None of those labels tells you anything about layer four, which is the one worth checking.

The established prospecting tools are good at three things we are not, and an honest evaluation should start there rather than with their limitations. Breadth of coverage, depth of person-level data, and the unglamorous plumbing that keeps a sending operation alive.

• Breadth. A general tool covers every industry at once. If your buyer this quarter is a logistics firm and next quarter a law practice, one subscription serves both. A vertical tool serves one of them, and only if you picked the right vertical.
• Person-level targeting. Job titles, seniority, department, direct dials in some cases. If your sale requires reaching a named Head of Operations rather than whoever reads the shop's inbox, that is a real capability and the reason this category exists.
• Sending infrastructure that has been beaten on for years. Warmup, mailbox rotation, bounce handling, reply classification, CRM logging. Boring, and most of the value once a team is above about five people sending.

There is a fourth strength that gets less credit: these tools make the work legible to a manager. Records land in the CRM, activity is attributed, and someone can answer the question of how many accounts were touched last week. A vertical tool that skips that is asking a team to give something up.

None of this is throat-clearing before the criticism. If layers one to three are where your gap is, the mature general tools are the right purchase and this post is not an argument against buying one.

Layer four is the timing decision, and in most stacks it is made by a person scrolling a filtered list. The filter describes states — this business runs Shopify, sells apparel, sits in Belgium, employs eleven people. Every one of those was true last month and will likely be true next month. That durability is what makes the data worth storing, and it is exactly why it cannot tell you when to write.

Two consequences follow, and both are structural rather than a complaint about any particular vendor.

The first is that a filter over a static pool is a filter anyone else can run. If four agencies sell the same service into the same segment and all four describe that segment the same way, all four are looking at the same list on the same Monday. Nothing about a state field is scarce, so the list cannot be the differentiator.

The second is that state data carries no expiry you can act on. A record saying a store uses a particular email tool does not say whether it was installed on Tuesday or four years ago. Those are opposite sales situations — one is a company mid-project with budget open and a problem unsolved, the other settled the question long before you heard of it — and the field looks identical in both.

An event is a different kind of fact. The store started running Meta ads nine days ago. It launched a product. It installed a retention tool. It rebuilt its storefront. It went from posting monthly to three times a week. An event carries a date, and the date is what makes a cold message read as relevant rather than random. It is also perishable, which is the property that makes it worth more than a durable field: a fact that is only useful for a fortnight is a fact your competitors are mostly not holding.

That is a difference in what the data is, not an accusation that anyone sells it dishonestly. A tool built to describe states describes them well. It is being asked, by whoever bought it, to answer a question about timing that its data model does not contain — and it answers by handing the question back to a human, who then does the best they can with a spreadsheet and a hunch.

We built layer four for one vertical, and the cost of that choice is breadth. The pool is 4.1 million Shopify and WooCommerce stores across Europe and North America, re-scraped weekly, as of August 2026. By the standards of a general prospecting tool that is a small pool, and deliberately so: two platforms, two regions, one kind of business.

The narrowness is not the point — the observability is. A store is a public thing. Its ads run somewhere you can look, its storefront changes visibly, its product pages appear and disappear, its social accounts carry dates. Watching a store every week produces events. Watching a private company's org chart mostly produces a slightly newer version of the same state. We picked the vertical where the events are visible from outside.

So the record is a store plus what changed about it recently, with contacts attached, including founder addresses that are not publicly listed. The events we currently detect are listed in the buying signal catalogue, and what sits underneath is described on the ecommerce leads database page. Read both before a trial, because they are also the honest place to discover that your offer does not match any signal we detect.

On layer three we did not rebuild what already works. Sending runs through your own Instantly workspace — campaigns are created there, the domains and mailboxes stay yours, and status and replies sync back. The sales agent drafts per-store copy from the signal plus a knowledge base you write once. Segments are built with country, platform, follower and other conditions, with a live audience estimate as you narrow them.

On data protection our position is narrow on purpose: we are GDPR-conscious by design, and responsibility for what you send stays with you. We will not claim more than that, and a vendor in this category who claims more is worth a second look. That is a structural statement about where the responsibility sits, not a claim about anyone else's compliance.

A post with this title is supposed to end in a numbered list of vendors with a pricing table. There is not going to be one, and the reason belongs in the text rather than in a footnote.

We have not measured anyone else's product. We have not sampled a competitor's records against a ground truth, counted how many of their contacts bounce, or audited how old their coverage of any segment is. Anyone publishing a table of those figures about their rivals either did that work and can show it, or is repeating a number they liked the look of. Ours would be the second kind, so it is not here.

We are also not going to put prices side by side. What each product in this category meters is not the same thing — one charges per credit, one per contact revealed, one per seat, one per mailbox — and a table that lines those up as if they were comparable would be dishonest arithmetic dressed as a service to the reader.

The same restraint applies to claims pointing our way. We will not tell you our addresses are more accurate than the alternatives, because we did not run that test. We will not quote you a reply rate or promise a deliverability outcome. A reply rate is a property of your offer, sent to your audience, from your sending setup — a vendor controls one of those three, and a figure produced under someone else's conditions is not evidence about yours.

What survives once the unmeasured claims are stripped out is the four-layer question, which you can answer yourself in a trial without trusting anyone's marketing. Our head-to-head write-ups against the named alternatives, including the ones where we recommend the other product, live on the comparison page rather than in blog posts, so that they can be kept current in one place.

Most of the demand behind the phrase "sales prospecting tools" is not demand for what we built. If any of the following describes you, buy the general tool and stop reading comparison posts.

• You sell to any industry other than ecommerce, or to several at once. Our pool is Shopify and WooCommerce stores and nothing else. A general tool covers the rest of the economy; we cover none of it.
• Your market is outside Europe and North America. We do not have it, and we are not going to present a thin pool as a pool.
• You work LinkedIn. We have no LinkedIn signals, no LinkedIn sending, and no plans to add either. If that is your channel, this is not a close call.
• You need the records outside the system. We do not export. Leads move into campaigns and stay there. If your CRM is the system of record for prospecting, that should rule us out, and you should find that out here rather than in week two of a trial.
• You need to reach a named senior person by title, at scale, with a direct dial. That is what the general tools are built for and it is not what we are built for.
• You want triggers we have not shipped. Registry and firmographic triggers and hiring signals are marked planned on our own site, which means they do not exist today. Other products in the category have them now.

There is also a limit that applies to every product here, ours included. More lists and faster drafting do not create capacity to answer replies. The clearest sign a tool like this fits is paid sales capacity that is not fully booked. If your calendar is filled by referrals, you probably do not need one yet — and if the constraint is people rather than pipeline, the question is a different one, closer to outsourcing versus automating the SDR function.

Work backwards from where the process actually stalls rather than forwards from a feature list. Five questions locate the gap, and none of them requires trusting a published figure.

1. Build your real segment, not a demo segment, and read the count. Forty accounts means no amount of data quality saves it. Two hundred thousand means the segment is not a segment. If the count is wrong, your gap is layer one.
2. Pull twenty records and check them by hand against the live websites. Twenty is enough to notice systematic staleness, and it is your own measurement rather than someone else's claim. High bounce or wrong-person rates put your gap in layer two.
3. Look at where your sends are landing and how the domains are holding up. If volume is fine and placement is not, the gap is layer three, and no new database will move it.
4. Ask what makes the tool send today rather than next Tuesday. If the only answer is that today is the next slot in a schedule, layer four is empty and a person is filling it. That is fine at fifty accounts a week and does not survive five hundred.
5. Check whether anything in the product carries a date — not the record's last-updated stamp, a date on the thing that happened. If nothing does, you are supplying the timing yourself whether you planned to or not.

If your answers put the gap in layer four and you sell to Shopify or WooCommerce stores in Europe or North America, we are worth twenty minutes. 1,000 leads are free on signup, which is enough to find out whether your segment exists in our pool and whether a signal fires in it often enough to matter. What that costs once you are past the free leads is on the pricing page. We would rather you test that against your own segment than take our account of the market on trust.

• Keaz Signals product pages — /ecommerce-leads-database, /signals, /sales-agent, /compare and /pricing — retrieved 3 September 2026. Source for the signal list, the segment builder, the Instantly sending model, the export limitation, the LinkedIn position and the planned-but-unshipped triggers.
• Own pool figures: 4.1 million Shopify and WooCommerce stores under watch across Europe and North America, re-scraped weekly, as of August 2026. These numbers move; treat the date as part of the number.
• 1,000 free leads on signup, as of August 2026.
• Related posts on this blog: what a sales intelligence platform knows, what a sales engagement platform does, what an AI SDR actually automates and SDR outsourcing versus a signal-led agent.
• No competitor database sizes, coverage percentages, accuracy rates, prices or reply rates are cited in this article. That is deliberate, and the reason is in the section on why there is no tool ranking here. We did not run those measurements, so we do not report them.