From a company name to context you can review.
One fictional company, four research decisions. Follow identity, comparable fields, professional relationships, and explicit unknowns into a useful handoff.
Vencavo has 299M+ contact records and 25M+ company records. This walkthrough uses fictional examples; it does not query the datasets or a live API/MCP service.
What happens around the record.
Identify
Resolve the company you mean before adding more context.
Local sample lookupStart with
forma.example
The research decision
Use the domain to locate the matching fictional company. In real research, check whether that identifier refers to a parent company, subsidiary, or product.
- Company
- Forma Labs
- Domain
- forma.example
- Source
- fictional-preview
- Production verification
- Not supplied
Keep the evidence in view
The local lookup resolves a fixture. It does not verify a real legal entity or establish ownership of a production domain.
Before moving onDoes the identifier belong to the business I intend to research?
Structure
Put comparable fields around the company.
Fictional field exampleStart with
Forma Labs · forma.example
The research decision
Keep the same field meanings across the research set. Preserve employee ranges as ranges and keep a missing value distinct from an observed zero.
- Industry
- SaaS
- Location
- San Francisco, US
- Employee range
- 51–200
- Revenue
- Not supplied
Keep the evidence in view
These sample fields can frame a shortlist. They do not establish product fit, growth, revenue, or buying intent.
Before moving onAm I using the field as defined, or asking it to prove something else?
Review relationships
Separate professional context from claims that still need evidence.
Illustrative relationshipStart with
Maya Chen · Forma Labs
The research decision
Read the role and department alongside the company. Establish reporting lines, current employment, and decision authority separately before relying on them.
- Professional
- Maya Chen
- Role
- VP Sales
- Department
- Sales
- Company
- Forma Labs
- Reporting line
- Not supplied
- Buying authority
- Not established
Keep the evidence in view
The role is fictional. A department is not a verified reporting line, and a senior title does not establish buying authority. Review each relationship against evidence for that specific claim.
Before moving onWhich relationships are supplied, and which still need an independent source?
Handoff
Carry the record and its limits into the next workflow.
Sample CSV · illustrative API/MCP contractStart with
A reviewed company record and the questions still open
The research decision
Choose a useful output shape and retain the source label. Keep unknown verification dates explicit so the next person or tool can inspect the limits.
{
"name": "Forma Labs",
"domain": "forma.example",
"industry": "SaaS",
"location": "San Francisco, US",
"employees": "51–200",
"source": "fictional-preview",
"production_verified_at": null
}Keep the evidence in view
The JSON above is formatted from the canonical sample. CSV downloads work. API/MCP requests, permissions, and automated delivery are not connected to this walkthrough.
Before moving onCan the next person distinguish the observed fields, the unknowns, and the next verification step?
Keep the evidence with the decision.
Use the company-research worksheet to keep observations, sources, interpretations, and open questions separate. The record supplies context; the research brief explains what you plan to do next.
Find the companies.
Understand the context.
Explore the data foundation for your team, your tools, and your next idea.