November 6, 2026
Case Study: 100 Meetings From a Signal No Database Has
How counting pumps in production, a field no B2B database has, turned a manufacturing list into a ranked market and 100 meetings in three months.
By AthonBound Team
A manufacturing client needed to find the companies that would buy its cooling system. Every database could list manufacturers. None could say which ones actually had the problem. So we built the field that decided everything.
Quick answer: For a client selling a cooling system for control units, the buying signal wasn't industry or company size: it was how many pumps of a specific type each company ran in production. No database has that field, so we built it: we mapped companies with in-house production, identified which ran those pumps, counted how many, and set the threshold using the real list instead of the client's assumption. The client said ten pumps; we opened the range to five, looked at the market, and set the cut at eight. The system booked 100 meetings in about three months, on very high-value contracts.
The client and the problem
The client sells a cooling system for control units. What it delivers is simple to state: more production in the same time. Control units overheat, production slows or stops, and every company with an in-house line knows exactly what each stoppage costs.
The challenge wasn't explaining the value. It was finding the companies where that value was real, among thousands of manufacturers that all looked the same in a database.
Why the database couldn't answer
Filter any B2B database for manufacturing, by size and country, and you get a long list. Every company on it matches the filter. Most of them don't have the problem, and the ones that do are indistinguishable from the ones that don't.
The question that mattered was: how many pumps of that type does this company run in production? That's not a filter you can select. It's a field that has to be built.
| Approach | What it gives you |
|---|---|
| Database filter: manufacturing, size, country | Every manufacturer, with or without the problem |
| Custom signal: number of pumps of that type in production | Only the companies with the problem, ranked by how much of it they have |
What we built
1. Mapped the companies with in-house production. Not every manufacturer runs its own line. The first cut was the companies that do.
2. Identified which ones ran those exact pumps. The type the client's system was built for.
3. Counted how many each one had. This was the step that created the value. Not finding the companies: counting.
4. Wrote to the ones above the threshold. With a message that spoke to exactly that situation.
The threshold decision
The client's instinct was ten pumps: below that, they thought, the problem wasn't worth solving.
Instead of taking that number as given, we opened the range down to five, to see how much of the market sat below the client's line. Then, looking at the real list, we set the cut at eight.
If we'd taken the client's ten at face value, every company with between five and ten pumps would have been excluded without anyone knowing how many there were. On contracts of that value, each one of those would have been a lost meeting.
Is there a field in your market that no database has? We'll look at your buyer and show you which signal would change who you contact. Get a free GTM assessment →
What the system produced
| Signal | Number of pumps of a specific type in production |
| Threshold | 8, set from the real list (client's assumption was 10) |
| Result | 100 meetings in about three months |
| Deal size | Very high-value contracts |
The meetings are the visible result. The system underneath is what produced them: a market mapped from scratch, a signal nobody else could see, and a threshold set by data instead of instinct.
What this case shows
The signal can be a number, not a yes or no. "Has pumps" would have been a weak signal. "Has eight or more" turned the list into a ranking.
The client's threshold is a starting point, not a rule. Opening the range and reading the real market found accounts the client would have excluded.
The value is in counting, not finding. Anyone could list the manufacturers. Nobody else knew how many pumps each one ran.
Not every case has two markets. In other projects, companies without the signal are a second market with a different message. Here, below the threshold, the problem simply doesn't exist. It's worth saying, because it isn't always the case.
How it applies beyond manufacturing
The same method works anywhere the buying signal is a quantity: number of locations, machines, vehicles, open roles of a type, products in a catalog. Find what a company with the problem shows from the outside, count it, and let the number set the order.
The method step by step is in how to build a B2B lead list no database has. The system it runs inside is described in what is market intelligence infrastructure.
FAQ
What was the buying signal in this case?
The number of pumps of a specific type each company ran in production. It isn't available in any B2B database, so it was built from scratch.
How was the threshold chosen?
The client suggested ten. We opened the range to five to see the real market, then set the cut at eight based on the actual list.
What were the results?
100 meetings in about three months, on very high-value contracts.
Why not use a standard database filter?
Because the filter returns every manufacturer, with or without the problem. Only the custom signal separated the companies that would buy.
Can this approach work in other industries?
Yes, whenever the buying signal is a quantity you can count from public evidence: locations, equipment, vehicles, roles, products.
Want to find the column your competitors can't see? We'll map your market and show you which signal separates the buyers. Get a free GTM assessment →