Against broad contact databases

A contact database and SkySearch solve different problems.

Need ten thousand contacts at firms a database already lists? Buy a coverage database. Reach for SkySearch when it comes back empty.

Where the two stop agreeing.

Seven questions. The answers are not the same shape. On the questions a database is built for — common contacts, at volume, at speed — a database wins, and this table is not about those.

A broad contact database and SkySearch compared across seven questions
The question Broad contact database SkySearch
What it is built for Maximum coverage and list volume Getting one important person right
When no record exists Returns nothing, or the nearest record Begins an active investigation
What confidence rests on A status flag from a single source Agreement across six independent signals
Evidence Not shown to you The full trail attached to every result
When the answer is uncertain A guessed pattern, sold as a find A scored fallback route, or nothing at all
Private companies and Asia Thin, built around firms it already lists The case it was designed for
When it comes back empty The credit is spent whatever comes back No charge below the confidence bar

The confidence key

A number you can act on, not a status flag.

The score says how strongly the independent signals agree, not how certain we feel. Three bands, and you always know which one you are in.

  • 85+ Verified Separate signals agree on the same route. It is ready to send.
  • 65–84 Reported, unverified High enough to report the address. Not high enough to call it verified. We label it, so you can confirm it before you write.
  • <65 Below 65, no charge We report no address, and we charge no address credit. What we did find stays, clearly labelled, with a fallback route.

Two purchases, not two vendors.

Most teams need both. The question is only which one you reach for today.

Buy a broad database when

  • You need ten thousand contacts, not ten.
  • The companies are listed and public.
  • Coverage and list volume are the point.
  • The person is already on file: a lookup is instant, and cheaper per contact than live research.

Reach for SkySearch when

  • The database returned nothing, or the nearest record.
  • The company is private, or the filing is in another language.
  • You must justify the contact months later.

What "the full trail" means

Every result shows its working.

A database hands you a row. SkySearch hands you the route, and the six steps behind it. They stay with the result, so you can justify a contact months later.

  • Which individual you mean, set apart from namesakes.
  • The operating entity behind the trading name.
  • The domains that entity actually uses.
  • The address pattern used there.
  • Whether the mail route accepts the address.
  • What in the public record agrees with it.

An example

6 of 6 signals agree

Owner · Rimfall Holdings

Contact route r.p•••••@rimfall-hldg.co.th Confidence 93 · ready to send
  1. IDIndividual matched and set apart from two namesakes
  2. ENTOperating entity confirmed against the registry filing
  3. DNSGroup domain found behind the local trading name
  4. PATAddress pattern read from four real examples
  5. MXMail route accepted, catch-all not detected
  6. XRAgreed by a public filing signature block

An example. Every name, company and address here is invented, and partly masked. Below 65 we report no address. We charge no address credit.

Bring us a name we should not be able to resolve.

Ten free credits, on us. No card. Nothing charged for what we cannot establish.

Or see what a credit costs before you sign up.

Start free