A purchased list can save discovery work if its coverage, permitted use and field definitions suit the mandate. A built list can make inclusion rules explicit and combine sources that a single supplier does not cover. Neither approach establishes business fit or seller interest merely by producing rows. The relevant output is a population the team can explain and then qualify.
Treat origin, identity and acceptance as separate properties. A purchased record can become a well-supported candidate after verification. A custom-built record can still be wrong if it points to a namesake website or relies on an unsupported ownership assumption. Quality follows the workflow applied to the record.
What the options do
Buy a candidate list
A supplier provides company records assembled under its own methodology. This may offer a useful starting point and reduce repetitive searching. The buyer needs to know the collection date, entity definition, source rights and what the fields actually mean. A list sold for one purpose may not support the acquisition screen or contact programme the team intends.
Build a mandate-specific list
The team defines the activities, geographies and entity boundaries it wants to investigate, then combines appropriate discovery sources. It can document why each company entered the population and retain exclusions. The work requires maintenance and quality checks. Custom construction gives control over the search logic, but does not prove the resulting universe is complete.
Compare the operating work
| Dimension | Buy a candidate list | Build a mandate-specific list |
|---|---|---|
| Route to a conversation | Candidate records do not establish owner access. | A researched population does not establish owner access. |
| Population covered | Follows supplier sources, categories and update practices. | Follows the buyer’s stated scope and discovery sources. |
| Evidence standard | Imported fields need source and methodology checks. | Inclusion decisions need retained support and review. |
| Cost drivers | Acquisition rights plus reconciliation and verification. | Discovery, entity resolution, research and maintenance. |
| Timing constraint | A starting file may be available quickly. | Population assembly precedes a useful qualified list. |
| Exclusivity and competition | Similar lists may be supplied to other buyers. | Custom search logic creates no rights over companies. |
| Control and responsibility | Supplier determines initial fields and coverage. | Buyer sets inclusion rules and source combinations. |
When to choose each
Buy a candidate list
Choose a purchased starting list when its coverage is suitable, terms allow the intended work and the team can verify the decisive criteria. Review a sample before expanding. Budget for duplicate resolution and missing fields, and preserve the supplier attribution rather than presenting all imported values as the team’s independently established findings.
Build a mandate-specific list
Choose list building when category labels poorly capture the thesis, geographic detail matters or important segments are missing from available products. Define adjacent activities deliberately and reconcile companies, locations and parent entities. Keep a visible backlog of unresolved records so the finished shortlist does not conceal the parts of the population that were difficult to investigate.
Common mistakes
- Using a contact file as a market definition. Availability of an address says little about whether the business belongs in the thesis.
- Calling a custom list complete without an independent view of coverage. Record source gaps and consider which company types are likely to be missing.
- Discarding rejected or duplicate records without preserving why they were removed from the active population. Their history can prevent the same research work from being commissioned again.
What the decision depends on
It depends on the fit of available data and the specificity of the mandate. A purchased list can seed a built universe if provenance and rights remain clear. Docket accepts a client list or builds one, then uses Triage to resolve identity before detailed research. The key decision is how to qualify and maintain the population, rather than whether the first row originated inside or outside the team.
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.