B2B Lead Generation When the Buyer Runs a Store
The generic definition of B2B lead generation assumes the buyer is a company with a buying committee. When the buyer runs a Shopify or WooCommerce store, the unit of work is a storefront and the trigger is an observable change on it.
Agencies and software companies selling to ecommerce stores
- →B2B lead generation is the work of finding organisations that might buy and starting a conversation worth having. The definition is sound; what changes by market is what counts as the organisation.
- →When the buyer runs a store, the unit is a storefront rather than a company, and the person who decides is usually the founder rather than a role account.
- →The trigger is an observable change on the storefront — new Meta ads, a product launch, an email tool going live — not a stage in a funnel you cannot see.
- →Our pool is 4.1M Shopify and WooCommerce stores across Europe and North America, 41,200 of them carrying a signal from the last seven days, as of August 2026.
- →This is the wrong approach if your buyers are not stores, if you need CSV export, or if you sell on LinkedIn. We do none of those things.
What B2B lead generation actually means
B2B lead generation is the work of identifying organisations that plausibly need what you sell, finding a person there who can decide, and starting a conversation at a moment when it is worth having. That definition holds across every B2B market. What changes from one market to the next is what an organisation actually looks like.
Ours is a specific market, and the disclosure belongs up front. We build Keaz Signals, an ecommerce leads database with live buying signals. We are a vendor in the category this article describes. What follows is a structural argument about a market, not a neutral survey of tools, and you should read it that way.
The readers we have in mind are agencies and software companies selling to ecommerce stores — not store owners, but the people who sell to them. If you run a Shopify store yourself, this is not written for you.
The generic answer to the question assumes a company with a corporate website, a buying committee, job titles that map cleanly onto functions, and a procurement process with stages you can track. For a large share of the businesses agencies actually sell to, none of that is true. The definition survives; the playbook built on top of it does not.
Where the generic definition breaks
It breaks in three places: the organisation is smaller than the definition expects, the decision has no committee, and the buying stage is invisible from outside. A three-person Shopify brand has no procurement process to enter and no role accounts to sequence against. The enterprise playbook does not degrade gracefully here — it stops matching.
Take the standard motion as it is usually taught. You build an account list from firmographics: industry code, headcount, revenue band, technology installed. You map the committee. You sequence by role. You wait for a trigger like a funding round, a leadership change or a new office.
Now apply it to a store turning over real money with four employees. Headcount tells you nothing useful about spend, because a small team can run a large ad budget and often does. Industry codes flatten every direct-to-consumer brand into one undifferentiated bucket. There is no committee — there is a founder and perhaps one marketer. Funding rounds are rare, and leadership changes rarer still.
What you are left with is a list of storefronts that look identical on paper. Everyone buying from the same category of source receives the same rows, which is why the same founders get the same message in the same week from three of your competitors. That is a targeting failure, not a copywriting failure, and no amount of rewriting the first line fixes it.
What counts as a lead when the buyer is a store
The unit is a storefront, not a company record. A store is a live thing you can observe from outside: it is running ads or it is not, it launched a product this week or it did not, it installed a retention tool or it has not. Those observations are the qualification, and they need nobody to fill in a form.
This changes what a row means. A company record tells you what a business is. A storefront observation tells you what it is doing. The first is stable and mostly useless for timing. The second changes week to week and is almost entirely about timing.
Our own pool gives a sense of the proportions. As of August 2026 the database holds 4.1M Shopify and WooCommerce stores across Europe and North America, and 41,200 carried a fresh buying signal in the preceding seven days. Both numbers move, which is why they are dated here.
The gap between them is the argument. On those figures about one store in a hundred is doing something this week that gives you a reason to write. The 4.1M is a directory. The 41,200 is a work queue.
The trigger is a change you can see
A buying signal here is an observable change on the storefront itself, not an inferred intent score. New Meta ads going live. Active ad count rising. A product launch. An email marketing tool appearing. Newsletter activity starting or stopping. Social cadence jumping. A storefront rebuild.
What makes those usable is that each carries its own reason to make contact. New ads running means budget is moving and creative becomes the bottleneck before spend does. An email tool going live means retention is being built right now, setup unfinished. A product launch is when marketing support is needed most. On how this differs from scored intent, see what each intent data category can see.
Stores are re-scraped weekly and every signal carries a last-seen date, so what you act on is days old rather than weeks old. An ad campaign in its first week and in its sixth are not the same message, and only one reads as though you were paying attention.
Two signal types people ask for are not there. Registry and firmographic triggers, and hiring signals, are both marked Planned on our own catalogue and are not live. If your motion depends on either, it does not work yet.
Where the contact sits
Contacts arrive with the store rather than as a separate enrichment step, and they include founder addresses that are not published anywhere on the site. For a four-person brand that is usually the only address worth having, because the founder is the buying committee.
We build these ourselves — from store pages including legal notices, from the Meta ad library, from Instagram and TikTok, and through our own contact discovery and verification. Bought lists are a starting point, never the answer. On why the usual enrichment chain runs out, see where the enrichment waterfall runs dry.
We are not going to publish a hit rate. We have not measured, in a way we would defend in public, what share of stores in the pool carry a reachable founder address — and a number invented for a blog post is worth less than the admission that we do not have one. If that figure decides your purchase, ask for it on a call where we can be specific about your market instead of quoting an average.
What we are not going to claim
Three things this article will not tell you: that a signal-led list lifts your reply rate by some figure, that this approach is GDPR-compliant for your particular use, or how we compare per unit of data against anyone else. Each is either unmeasured, not ours to assert, or dishonest as a comparison.
On reply rates, we offer no guarantee. Any number quoted without your offer, your market and your sending history in it is marketing rather than evidence. Timing helps because the reason to write is real; how much it helps depends on things we do not control.
On data protection, our position is deliberately narrow: we are GDPR-conscious by design and we will not claim more than that. Responsibility for what you send stays with you. A blog post is not the place that gets widened, and anyone telling you their database makes your outreach lawful is selling you something other than software.
On price, what products in this category meter is not the same thing — stores, contacts, credits, exports, sends — and a table lining them up as though it were would mislead you. Our pricing is public. The comparisons worth reading are the ones that name the rows where we lose.
Where this is the wrong approach
If your buyers are not ecommerce stores, this is the wrong tool and the wrong article. Everything above depends on the buyer having a public storefront that changes in observable ways. A company selling to hospitals, manufacturers or law firms has no equivalent surface, and generic B2B data is the right choice there.
Four more limits, stated plainly because they are real and worth planning around:
- We cover Shopify and WooCommerce and nothing else. Other platforms are not in the pool.
- We cover Europe and North America. Other markets are not in the pool.
- We do not export. Leads move into campaigns and stay there. If your workflow needs a CSV, that is a dealbreaker — and it should be.
- We have no LinkedIn signals and no LinkedIn sending, and no plans to add them. If your channel is LinkedIn, buy something built for it.
Sending runs through Instantly, in your own workspace, with replies syncing back — a strength if you already work there, a constraint if not.
How the pieces fit together
In order: pick the stores you can serve, let a signal decide when to write, write from that signal, and send. Four steps, and the one most teams get wrong is the second — they build the list carefully and then send on a schedule rather than on an event.
Segmenting comes first: country, platform, follower count and other conditions narrow the pool to stores you can actually serve, with a live audience estimate as you build. That is what the ecommerce leads database is for. Timing then comes from the event, and the buying signal catalogue describes each type and why it is worth acting on. The writing is where the AI sales agent composes per store from the signal plus your own services, references and tone — not a template with a first name slotted in.
Signing up gives you 1,000 leads free inside segments you build yourself, which is a cheaper way to test this premise than reading more about it.
Questions we get
What is B2B lead generation?
Finding organisations that plausibly need what you sell, identifying someone there who can decide, and starting the conversation at a moment when it is worth having. The definition is stable across markets. What changes is what counts as an organisation, and what tells you the moment has arrived.
How is it different when the customer is an ecommerce store?
The unit is a storefront rather than a company record, the decision usually sits with a founder rather than a committee, and the timing comes from an observable change on the store — new ads, a product launch, an email tool going live — rather than from a funnel stage you cannot see.
Does a bigger database mean more leads?
Not by itself. As of August 2026 our pool held 4.1M Shopify and WooCommerce stores, and 41,200 of them carried a fresh signal in the previous seven days. The full pool is a directory; the smaller number is the work queue. Size sets the ceiling, the signal sets the order of work.
Can I export the leads?
No. Leads move into campaigns and stay there. Sending runs through Instantly in your own workspace, with status and replies syncing back. If your workflow needs a CSV, this is the wrong tool, and we would rather say so before you buy.
Is signal-led outreach GDPR compliant?
We are GDPR-conscious by design and we will not claim more than that. Responsibility for what you send stays with you. Anyone telling you their database makes your outreach lawful is selling you something other than software.
Builds the signal pipeline behind Keaz Signals. Writes about what the store data actually supports, and what it does not.
Keep reading
Skip the pool building. Start at chapter four.
Signals hands you the stores that are already moving. You write the email. Get in line and we will tell you whether your market is still open.
Launch my agent