Home Guides Leading Company Databases vs Full-Web Mapping
Guide · Factual comparison

Leading Company Databases vs Full-Web Mapping

Not a versus piece, despite the title: two structurally different tools, each right for different jobs. How accumulation and derivation differ, what each cannot do, and a decision framework — including the rows where the database wins.

100M+
classified domains as the census base
24.7M
business & finance sites
≥20%
of confirmed fits miss obvious keywords

Two tools, one confused conversation

Most sourcing disappointments come from asking one tool to do the other's job. Two structurally different objects exist — each with real strengths — and the trade-offs are architectural, not vendor-specific.

Company database

A curated index: profiles assembled over years from filings, registrations, news, funding events, and web crawls — wrapped in workflow (search, filters, alerts, contact data, CRM sync).

Full-web census

The entire domain population of a category, read and classified against a specific buyer's thesis at the moment of screening — existence-driven, not source-driven.

Our position: we build the census tool. This comparison will say so where relevant — but the honest version includes the many situations where a database is the right purchase. No competitor names appear; the trade-offs are architectural.
Coverage

The share of the real, operating population a tool can show you.

Depth

How much verified information the tool holds per company. The two are in tension in every data product ever built.

How each object gets built

Neither architecture is superior in the abstract — each buys something the other structurally cannot reach.

Accumulation (database)

  • Sources feed continuously: registries, filings, funding events, news, job postings, web crawls, research teams
  • Each profile is a merged, deduplicated dossier that improves as sources accrete
  • Optimizes for: depth and retrievability — rich profiles, standardized fields, fast search
  • Inclusion logic: source-driven — a company enters when some feed notices it
  • Blind spot: companies that merely operate profitably for decades get noticed late, thinly, or never

Derivation (census)

  • Starts from domains: 100M+ classified domains, 24.7M business sites across 700+ categories
  • Asks per market: which of these domains belong to operating companies in this category?
  • Triage + deep extraction: reads each site against the buyer's thesis, capturing 15 signals with verbatim quotes
  • Inclusion logic: existence-driven — a company enters because its website exists
  • Blind spot: no longitudinal depth — no deal histories, executive moves, or funding timelines

What leading company databases do well

Credit where due. If your targets are $20M-revenue-plus companies with institutional footprints, a good database probably already covers most of them with data no website read can reconstruct.

Mid-market profile depth

For companies that generate filings, transactions, and news, profile quality is genuinely strong: firmographics, ownership histories, comparable transactions, executive contacts.

Daily-use workflow

Saved searches, trigger-event alerts, contact enrichment, CRM integrations, team collaboration. A census is an episodic artifact — not a login your associates live in.

Multi-use-case breadth

The same subscription serves sourcing, comps, market landscaping, and contact finding. A census is thesis-specific by design — no pretense of general-purpose reference.

Contact data

Databases invest heavily in verified emails and direct dials; web mapping yields whatever contact paths companies publish. For list-to-dialer workflows, that difference matters.

Where the index boundary binds

Four limitations are architectural — properties of accumulation itself, not of any vendor's execution.

The long tail is structurally thin

Small private operators generate no filings or coverage — source-driven inclusion misses them. In fragmented verticals this population is most of the market: our specimen census found 17,300 live US companies in a 25,000-domain sample.

Classification error compounds quietly

Index taxonomies assign codes by heuristic. A misfiled company is invisible to every filtered search. A fifth or more of confirmed fits in our runs lacked the category's obvious homepage keywords.

Thesis specificity exceeds filter algebra

A real thesis is textual — "independent, field-service-led, ISO 17025 accredited, no group ownership." Most clauses are reading tasks over site language, not database fields.

Staleness follows the source cycle

Ownership changes at small companies surface as quiet footer edits no feed carries. One in ten keyword-perfect candidates proved group-owned at read time. Census evidence quotes live pages — freshness is the run date.

The evidence standard: auditability as a feature

Committees care about this more each year: what does the tool let you prove? For an IC memo or data room, "the database says so" ages poorly when a spot-check fails.

Database: assertion

  • Row asserts industry: X, employees: Y, ownership: private
  • Provenance ranges from strong (a filing) to opaque (a model estimate)
  • Misclassification lives in the profile until a source contradicts it

Census: evidence

  • Every signal carries a verbatim quote and source URL
  • "Independent" is a documented absence of group disclosures, not a flag
  • Misclassification — the quote shows why; the fix is one row; the rubric improves
16/16

evidence snippets verified in one machining specimen

5 per specimen

documented exclusions — a list that can't show what it rejected can't prove what its inclusions mean

Local error correction

when a census errs, the quote shows why and the fix is one row — not a silent model update

Cost structures, compared honestly

The products price differently because they are different economic objects. Neither number is small; the comparison that matters is cost per covered target and cost per supported decision.

Database subscription

  • Recurring platform cost — commonly five figures annually per seat tier
  • Justified across many users, many use cases, continuous access
  • Best amortization: fund working many theses across standard mid-market populations

Census project pricing

  • Proof project from €4,900 per thesis
  • Full universe + deep shortlist from €9,900
  • Annual monitoring from €18,000/thesis — custom ICP re-runs included

PE platform

Prosecuting one vertical for years — owning the census plus monitoring typically costs less than a multi-seat license and covers companies the license cannot show.

Independent sponsor

One thesis on personal economics — the difference is sharpest here. See our separate guide on sequencing that spend.

The hidden cost

An export that misses a third of a fragmented market doesn't invoice you for the miss. Estimate it anyway — uncontested conversations close on different terms than auctions.

A decision framework, and the case for both

The choice reduces to a handful of questions about your situation rather than the products:

Your situationBetter-fitting toolWhy
Targets are established mid-market+, with filings and news presenceLeading company databaseProfiles are deep where sources are rich; census adds little there
Thesis lives in a fragmented, long-tail verticalFull-web censusIndex coverage is structurally thin exactly where your targets live
Criteria are textual: service model, contract language, credentials, independenceFull-web censusReading tasks, not filter algebra; evidence quoted per company
You need contacts, alerts, and daily self-serve searchLeading company databaseWorkflow is the accumulated product's core strength
You must show an IC or client the complete denominatorFull-web censusEnumerated population with documented exclusions; auditable
Many ad-hoc questions across many marketsLeading company databaseGeneral-purpose reference beats per-thesis projects
One vertical, prosecuted for yearsCensus + monitoringOwn the map; refresh on deltas; re-run ICPs as the thesis sharpens
Note: half the rows point to a database. Sophisticated teams increasingly run both — the subscription as daily workflow, the census to know (rather than hope) what the workflow can see. The empirical bridge is a coverage test on your own thesis — including the direction where your existing coverage turns out excellent.

Limits of the census, stated plainly

These limits are the boundaries that make the rest of the claims trustworthy. The tool that admits what it cannot do is generally the tool whose other claims survive checking.

No financials

No revenue, EBITDA, or valuation estimates — only proxy-based size bands. No deal histories, verified contact hierarchies, or longitudinal executive movements.

Web-visible only

Reads the web-visible market — in B2B nearly all of it, but purely offline sole operators and closed-network suppliers should be quantified, not waved away.

Thin-site residue

A few percent of every screen returns insufficient evidence — sites too thin to classify honestly. These land in a flagged category rather than a guessed one.

Thesis-shaped

Superb depth against your criteria — no pretense of general-purpose reference. Re-running a new ICP over an already-mapped universe is fast and included.

How to test the comparison on your own market

Settle it empirically before committing budget. The test costs one vertical and a few hours of comparison work — ideally a market where you believe your current coverage is strong.

1

Obtain the census

Get the full census of a vertical you know well — a proof project, or a manual census if the market is small.

2

Three-way overlay

Lay the census against your database export for equivalent filters and your CRM's accumulated records for the space.

3

Read both directions

Census-only companies are your uncontacted margin. Export-only companies deserve equal scrutiny — misclassified, acquired, or a genuine census miss.

Result: a measured coverage rate on a market you can sanity-check from experience — replacing a tooling opinion with your own data. Verticals of similar fragmentation behave similarly, so the measurement generalizes. This is a productized engagement for us — structured around exactly this comparison.

Frequently asked questions

No — the difference is the inclusion logic and the unit of work. A database includes companies its sources noticed and stores standing profiles; a census includes companies because their domains exist, and produces thesis-specific readings rather than general profiles. Practically: the census contains long-tail and vocabulary-mismatch companies no feed ever surfaced, and its per-company content is your criteria evidenced with quotes, not standardized fields. The two converge only in the well-covered mid-market, which is exactly where a database is the right tool.

In fragmented verticals, the census — not marginally but structurally, because index inclusion depends on signals small companies do not emit. Our specimen industrial category triaged ~17,300 live US operating companies from a 25,000-domain sample; eligible-independent universes per subvertical (93 to 702 companies) were heavy with businesses whose only trace is their own site. In concentrated, well-covered markets the gap narrows toward zero. The honest answer is per-vertical and measurable — which is why we recommend testing coverage on a market you already know before believing anyone's generality, including ours.

Mostly the false-positive families: directories and associations wearing industry keywords, dead companies with live profiles, misclassified businesses, and — the costly one — subsidiaries of groups still profiled as independent. One in ten keyword-perfect candidates in our runs carried a group-ownership disclosure on inspection. A census reads each site at screening time and documents exclusions with the disqualifying quote, which is why its universe is usually smaller than a raw export of the “same” market and more usable per row.

No, and we do not recommend it in most cases. The complementary pattern works: subscription for daily search, contacts, alerts, and general reference; census per prosecuted thesis, for coverage, evidence, and the denominator. The census also improves the subscription's ROI — gap analysis identifies which CRM records are dead or acquired, and the evidence fields make existing outreach sequences concrete. Teams sometimes do downsize seat counts after owning their core verticals' censuses; that is an outcome to measure toward, not a precondition.

Through monitoring deltas against the mapped universe: scheduled re-checks that report new entrants, newly dormant sites, and newly disclosed ownership changes, monthly or quarterly, with annual full re-reads — from €18,000 per thesis per year. Deltas are economical because triage state is already known; only changes need deep reading. The census-plus-deltas model keeps the map current for the thesis you are prosecuting, which is a different (and for sourcing, usually better) freshness contract than a subscription's source-cycle refresh across everything.

Keep reading

CRM / database gap analysisTAM mapping guideHow PE firms source add-onsScreening out false positivesOur methodPricing
What we refuse to sell: no “ready to sell” flags, no revenue or EBITDA guesses, no owner-age profiling, no distress detection — and no engagements in consumer-captive verticals. Read our standards; serious buyers tell us this page is why they trusted the rest.

See what the full universe looks like for your thesis

One email. We send the specimen report the same day — every company scored and ranked with full signal transcripts, plus the exclusions we documented and why.

Request the specimen report