What a Sales Intelligence Platform Knows, and What It Cannot
A sales intelligence platform is good at telling you which companies match your criteria. It is usually silent on which of them changed this week, and that is the part that decides whether outreach lands.
Agencies and software companies evaluating a sales intelligence platform for outreach to ecommerce stores
- →A sales intelligence platform sells you records about companies. A record describes a state, and a state cannot tell you when to make contact.
- →The category's strengths are real: coverage across every industry, contact data at scale, and integrations into the CRM you already run.
- →We will not compare database sizes or accuracy rates with anyone, because we did not measure theirs and neither did most of the people quoting figures at you.
- →Keaz Signals watches 4.1 million Shopify and WooCommerce stores in Europe and North America, re-scraped weekly, as of August 2026. One vertical, deliberately.
- →If you sell outside ecommerce, need CSV export, or work LinkedIn, a general platform is the better purchase. We have none of those.
What a sales intelligence platform is
A sales intelligence platform is a database of companies and the people who work at them, sold with filters on top. You describe the kind of business you want to sell to — industry, size, country, revenue band, installed software — and it returns a list of matching records with contact details attached. Most also push those records into a CRM and track whether anyone acted on them.
The disclosure first, because it changes how you should read the rest. We build Keaz Signals, which sells ecommerce leads with live buying signals attached. We are in this category, competing for the same budget, and we have an interest in how you evaluate it. What follows is a structural argument rather than a product comparison: what the shape of a company record lets you know, and what it does not, whoever sells it to you.
The short version is that these platforms answer the question of who very well, and the question of when almost not at all. If your outreach is failing, the second question is usually the one that broke.
Three things the category genuinely does well
It is worth being specific about the strengths, because we do not have them and a fair evaluation should start there.
- Breadth. A general platform covers every industry at once. If your buyer this quarter is a manufacturing firm and next quarter a dental practice, one subscription serves both. A vertical tool serves exactly one of them, and only if you picked the right vertical.
- Named-person data at scale. Job titles, seniority, department, direct dials in some cases. If your sale requires reaching a VP of Operations by name rather than whoever answers the shop's inbox, that is a real capability and it is the reason the category exists.
- Integration into the system your team already lives in. Records flow into the CRM, duplicates get resolved, activity is logged against the account, and the sales manager gets a report. Boring, and it is most of the value in a team above about five reps.
None of that is marketing puffery. Those three things are why a general sales intelligence platform is the default purchase, and for a lot of teams the default is correct.
What a record cannot tell you
Every field on a company record describes a state. This business runs Shopify. It sells apparel. It sits in the Netherlands. It employs fourteen people. Each of those was true last month and will probably still be true next month. That durability is what makes the data worth storing, and it is also exactly why it cannot tell you when to write.
Two consequences follow, and they are structural rather than a complaint about any particular vendor.
The first is that a filter over a static pool is a filter everyone else can also run. If four agencies sell the same service to the same segment, and all four describe the segment the same way, all four are looking at the same list on the same Monday. The list is not the differentiator. Nothing about a state field is scarce.
The second is that state data has no expiry you can act on. A record that says 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 a budget open and a problem it has not solved yet. The other is a company that settled this question long before you heard of it. The field looks identical in both cases.
An event is a different kind of fact. The store started running Meta ads eight days ago. It launched a product. It installed a retention tool. It rebuilt its storefront. It began posting to TikTok three times a week when it used to post monthly. An event carries a date, and the date is the entire reason a cold message reads 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 two weeks is a fact your competitors mostly are not holding.
That is a difference in what the data is, not an accusation that anyone is selling it dishonestly. A platform built to describe states describes them well. It is simply being asked, by whoever bought it, to answer a question about timing that its data model does not contain.
Why we will not compare database sizes or accuracy rates
This category markets on two numbers above all others: how many records are in the database, and how accurate they are. A comparison post is supposed to tabulate those numbers for you. We are not going to, and the reason belongs in the text rather than in a footnote.
We have not measured anyone else's database. We have not sampled a competitor's records against a ground truth, we have not counted how many of their contacts bounce, and we have not audited how old their coverage of any segment is. Anybody 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 will not appear here.
The same restraint applies to our own claims in the other direction. We will not tell you our email addresses are more accurate than the alternatives, because we did not run that test either. We will not quote you a reply rate. 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 is left when you strip out the unmeasured claims is the structural question from the previous section, which you can answer yourself in a trial without trusting anyone's marketing: does this product know that something changed, and when.
What changes when the unit is a store rather than a company
We built the narrow version of this, and it is worth describing plainly so you can see the trade rather than take our word for the result.
The pool is 4.1 million Shopify and WooCommerce stores across Europe and North America, re-scraped weekly, as of August 2026. That is a small pool by the standards of a general platform, and deliberately so: one platform pair, two regions, one kind of business. The point of the narrowness is not the count. It is that a store is a public thing. Its ads run in a place you can look at, its storefront changes visibly, its product pages appear and disappear, its social accounts have dates on them. Watching a store weekly produces events. Watching a private company's org chart mostly produces a slightly newer version of the same state.
So the record we sell is a store plus what changed about it recently, with contacts attached. The events we currently detect are listed in the buying signal catalogue, and what the underlying database contains is described on the ecommerce leads database page. Both are worth reading before a trial, because they are also the honest place to find out that your offer does not match any signal we detect.
Sending runs through your own Instantly workspace, so the domains and mailboxes stay yours, and the sales agent drafts per-store copy from the signal plus a knowledge base you write once. 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 you should be suspicious of a vendor in this category who does.
Where a general sales intelligence platform is the better choice
Most of the demand for the phrase "sales intelligence platform" 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 more than one industry, or to any industry other than ecommerce. Our pool is Shopify and WooCommerce stores and nothing else. A general platform covers the rest of the economy; we do not cover any of it.
- Your market is outside Europe and North America. We do not have it, and we are not going to pretend a thin pool is 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. For teams whose CRM is the centre of the world, that is a dealbreaker, and it should be.
- You need to reach a named senior person by title, at scale, with a direct dial. That is what the general platforms 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. Several competitors have them now.
There is also a limit that applies to every product in this category, 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.
How to evaluate one in a week
Trials in this category tend to be spent admiring filter menus. Four questions get you further, and none of them require trusting a published figure.
- Does anything in this product carry a date? Not the record's last-updated stamp — a date on the thing that happened. If nothing does, the product describes states, and you are supplying the timing yourself whether you planned to or not.
- Build your real segment, not a demo segment, and read the count. If it returns forty companies, no amount of data quality saves it. If it returns two hundred thousand, the segment is not a segment.
- Pull twenty records and check them by hand against the live website. Twenty is enough to notice systematic staleness, and it is your own measurement rather than someone else's claim.
- Ask what makes it send today rather than next Tuesday. If the only answer is that today is the next slot in a schedule, you have bought a sequencing tool with a database attached, which is a legitimate purchase and a different one from the one the pricing page describes.
If you want to run questions two and three against our pool, 1,000 leads are free on signup, which is enough to find out whether your segment exists here and whether a signal fires in it often enough to matter. We would rather you test that than read our account of somebody else's market. Our side-by-side write-ups against the named alternatives are collected on the comparison page, including the ones where we recommend the other product.
Sources
- Keaz Signals product pages — /ecommerce-leads-database, /signals, /sales-agent and /pricing — retrieved 31 August 2026. Source for the signal list, the sending model, the export limitation 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.
- No competitor database sizes, coverage percentages, accuracy rates or reply rates are cited in this article. That is deliberate, and the reason is in the section on why we will not compare them. We did not run those measurements, so we do not report them.
Questions we get
What is the difference between a sales intelligence platform and a lead database?
In practice the terms are used interchangeably, and the distinction that matters is not in the label. A lead database sells you records. A platform adds filtering, enrichment, CRM sync and reporting on top of the same records. Both are describing states of companies. Neither term tells you whether the product knows that something changed recently, which is the question worth asking.
Do I still need a sales intelligence platform if I have a signal tool?
Often yes, and they solve different problems. A signal tool tells you which accounts are worth contacting this week inside the segment it watches. A general platform covers segments the signal tool does not watch at all, and reaches named senior contacts by title. If you sell to ecommerce stores and nothing else, one may be enough. If ecommerce is one of four markets you sell into, it will not be.
How current is the data in a sales intelligence platform?
It varies by vendor and by field, and you should measure it yourself rather than accept a published figure. Pull twenty records in your own segment during a trial and check them against the live websites. Twenty is enough to see systematic staleness. For our own pool: stores are re-scraped weekly, so signals surface days old rather than weeks old, as of August 2026.
Can I export the leads to my CRM?
With most general platforms, yes — CRM integration is one of the category's genuine strengths. With Keaz Signals, no. We do not export; leads move into campaigns and stay there. If your CRM is the system of record for prospecting, that limitation should rule us out, and we would rather you learn it here than in week two of a trial.
Does it cover LinkedIn?
Many platforms in the category do, through LinkedIn-derived contact data or sending integrations. We do not. Keaz Signals has no LinkedIn signals and no LinkedIn sending, and no plans to add them. Our signals come from what ecommerce stores do in public: ads, storefront changes, product launches, installed tools, social and newsletter activity.
Builds the signal pipeline behind Keaz Signals. Writes about what the store data actually supports, and what it does not.
Keep reading
Reading about signals is fine. Seeing yours is better.
Access opens per market, in order of signup. When your seat is ready you see which stores in your niche are moving and what we would send them.
Launch my agent