Lead intelligence · discovery, reconciled
Every prospecting tool eventually fills your CRM with rows nobody can use.
Companies you already sell to, arriving as new accounts. People with no email, no phone and no profile, arriving as leads. A queue that grows faster than anybody works it, until the whole thing gets ignored.
The interesting engineering here is not the discovery. It is everything that refuses.
- No lead without a way to reach somebody
- Checked against what you already hold
- Nothing lands until a person says so
- Vestra Freightbecomes a lead2 emails · 1 direct line
- Okonkwo Industriesbecomes a lead1 profile link only
- Brennan & Halestays for reviewnothing — no email, no phone, no profile
Three answers a competitor does not have
The three ways prospecting data normally ruins a CRM.
Each of these is answerable here, and each is a page you can read before you ever speak to us.
Scoring
Nine factors you weight, and the arithmetic on hover.
A senior person visible. Hiring for a role that matters to you. Recent funding. A decision-maker present. A leadership change. Any hiring signal at all. How many contacts were found. Industry fit. A recruiting tool detected on the site.
You set the weights and the bands. A blank weight means "use the default" and is dropped rather than sent as a zero, so the merge stays reversible. A typed value out of range is brought into range rather than rejected. And the badge on each row unpacks into the factors that produced it.
- The bands are yours, and the colours follow them —
The screen reads your thresholds rather than a default somebody chose — so the colour on the row means what your team agreed it means.
- Your targeting is configured once, not per run —
A run can override three things — industries, regions, how many companies — and shows the other nine as a read-only preview with a link to change them properly.
- Credits are visible before they are spent —
Used against quota, with the cycle, and an unmistakable state when the quota is gone.
Landing
Nothing is written into your CRM until somebody says so.
This was a deliberate reversal. An earlier version wrote discovered companies straight into accounts, contacts and leads — and the migration that removed it is titled after the decision.
The split it encodes: discovery decides what is worth returning at all; your team decides what is worth pursuing. Which is why what arrives is a queue with three actions rather than a pile of records.
Nine reasons for saying no
Structured rather than free text, so the pattern in your rejections is readable later.
A snooze that comes back
Re-appliable while it is still in the queue, refused once it has been decided — and a snoozed row can never be promoted automatically behind your back.
Promotion links the contacts properly
Not just a company and some people, but the relationship between them, so every screen that reads it sees the promotion.
The whole module
Every capability, with a page that names the screen.
Written after reading how each one actually behaves — which is why each page tells you what it refuses to do as plainly as what it does.
Questions that decide it
Including one correction worth making early.
›Does this identify visitors to our website?
No. That is a different category of product and this is not one — nothing here watches your website, resolves an address to a company, or tells you who browsed. If you see that capability described anywhere in our own material, it is wrong and we are fixing it.
›Does rejecting a company teach it anything?
Not today. Your reasons are recorded and read by you; they do not travel back to change future scoring. Worth knowing, because it is a reasonable thing to assume.
›Can discovery run on a schedule?
No. A run is launched deliberately, because a run spends credits.
›Can a rep work the queue without being an administrator?
Today the shipped sales roles do not include these permissions, so granting them means a custom set. Raise it during setup rather than discovering it on day one.
›Can we export the queue?
Not today — it is worked in place.
›How does this relate to finding individual contacts?
Differently. This finds companies. Finding a named person's email or number is a separate capability in the CRM, with its own providers and its own credits.
Book a demo
Bring a list of accounts you already sell to.
The first one is the test that matters.
- Run discovery and count how many of them come back as new
- Find one it scored well with nobody contactable, and see where it went
- Dismiss three and read back the reasons a month later
- Promote one and check the contacts are linked, not just created