Coverage, accuracy & freshness
How this is scored
How much of the target market the database actually covers — judged on DACH and EU coverage as much as North American — and what the vendor documents about verification and refresh, because accuracy claims cannot be checked from outside.
0 — No stated coverage, no refresh cadence, no verification method; accuracy asserted as a percentage with nothing behind it.
3 — Headline record counts for the whole database, thin or unstated European coverage, and no description of how often records are re-verified.
5 — Coverage stated per country or region including DACH, email verification described, a stated refresh cadence, and firmographics beyond name and domain.
8 — Coverage broken down by country, industry and data type (email, direct dial, mobile), verification method and refresh cadence documented, company data drawn from official registers where available, and a bounce or credit-back guarantee with stated terms.
10 — The vendor is accountable for its data: per-country coverage and accuracy methodology published, every field carrying a last-verified date visible to the user, register-sourced company data, and credit-back terms that make inaccuracy the vendor's cost rather than the buyer's.
The RevOps Manager
Headline counts are the usual "millions of verified emails, direct dials and company profiles", with coverage outside the US described only as global search — nothing broken out per country and nothing specific to Germany, Austria or Switzerland. Verification is documented better than most (SMTP, human checks, email-open validation, triple-verified claims) and re-verification is stated at least every 90 days, though the captured pages give different figures for the interval, and we found no public information on bounce guarantees or credit-back terms. That lands it above a bare record count but short of the per-market coverage a DACH rollout needs. 1 2 5