A database and a primary-source research process answer different questions. Searchable categories can produce a candidate population quickly. Company pages, filings and suitable registers can then establish narrower facts, with their own limits. The efficient sequence often uses structured discovery before focused verification rather than demanding that either layer do every job.
Here, primary research means investigating original company statements and official records, not an assurance that every statement has been independently audited. A retained page shows what the source said. The question is whether that statement supports the specific acquisition criterion.
What the options do
Commercial databases
A provider collects and standardises company records for search. This reduces the work needed to find candidates and explore category boundaries. Field definitions and provenance vary, so estimated revenue, inferred ownership and industry tags should keep their original attribution. A record can be useful for discovery even when it is insufficient to accept a decisive screening answer.
Primary-source desk research
An analyst checks identity and investigates the company against explicit questions using suitable original materials. Retained passages make the answer reviewable. Research is slower when a company has little public information or a complex structure, and some questions remain unanswered. The benefit is a clearer basis for screening, not a guarantee that public statements disclose the whole business.
Compare the operating work
| Dimension | Commercial databases | Primary-source desk research |
|---|---|---|
| Route to a conversation | Records and possible contact fields; no introduction implied. | Company understanding; no access to an owner implied. |
| Population covered | Broad search within the provider’s taxonomy and coverage. | Chosen sources and questions shape the researched population. |
| Evidence standard | Provenance and estimates must be evaluated field by field. | Original passages support only the claims they actually make. |
| Cost drivers | Subscriptions, rights and record reconciliation drive effort. | Reading, interpretation, retention and review drive effort. |
| Timing constraint | Candidate retrieval can precede detailed verification. | Preparation time depends on ambiguity and source availability. |
| Exclusivity and competition | Other subscribers can obtain similar company records. | Other buyers can investigate the same public sources. |
| Control and responsibility | Provider controls schema and much of the update process. | Buyer defines questions and acceptance standards. |
When to choose each
Commercial databases
Choose a database first when its coverage overlaps the mandate and the team needs an initial population or a repeatable search. Inspect field definitions and usage terms before designing exports. Test a sample against known criteria, and preserve the query and retrieval date so apparent gaps can be investigated rather than accepted as proof that no companies exist.
Primary-source desk research
Choose deeper research when exclusion rules, service mix or entity boundaries determine whether a company belongs in the mandate. It is also appropriate before a high-context introduction. Define what counts as sufficient evidence and which private questions must remain open; otherwise the team can spend indefinitely seeking public answers that cannot reasonably be found.
Common mistakes
- Calling a vendor field a verified fact because it is neatly formatted. Structure makes data easier to use, not necessarily more reliable.
- Researching every available detail before checking a fatal exclusion. Identity and disqualifying criteria should precede expensive collection.
- Equating missing database coverage with absence from the market. Check adjacent categories and independent sources before drawing that conclusion.
What the decision depends on
It depends on whether discovery or decision-grade support is the current bottleneck. Use databases for candidate generation where coverage is suitable, then research the fields that change the screening decision. Docket can start from a supplied list or build one, resolve identities and retain support for typed answers. It does not confer rights to restricted vendor material or validate estimates by importing them.
How to test the choice
Write down the current constraint before choosing a workflow: candidate coverage, evidence quality, access or the capacity to handle conversations. Compare alternatives against the same mandate and record the work needed to reach the same stage. A larger file, a delivered message and a held owner discussion are different outputs. Treat missing evidence and excluded records as part of the assessment rather than hiding them behind activity totals.
Start with a bounded review and examine the actual records. Ask which claims changed the decision, which questions stayed open and who must act next. Expand only when the handoff is workable. These comparisons are Docket’s qualitative assessments of operating methods, not performance benchmarks, promises of transactions or recommendations to acquire a business.
Discuss the research work your team needs or inspect the live demo before choosing a delivery approach.