Key points
- Confirm the business represented by each website before contact search.
- Separate account research from supported contact discovery.
- Measure accepted accounts, contacts and unresolved matches separately.
A domain-first prospecting workflow starts with known company websites, reviews which businesses they represent and then finds relevant contacts. Keep account identification separate from contact search and field validation.
“Reverse company enrichment” is a broad workflow label. It does not establish that every provider offers a domain-to-company profile endpoint or returns all the fields your CRM needs.
Review what each website represents
Keep the original source URL and the proposed company website value. Distinguish a corporate site, product brand, subsidiary, directory listing and partner page before treating the domain as an account.
- Confirm the business identity and relevant operating unit.
- Review redirects, regional sites and important subdomain context.
- Retain the source and observation date.
- Hold ambiguous account relationships for research.
A shared parent domain does not automatically make two operating businesses the same target. Likewise, different domains can belong to related entities without making every contact interchangeable.
Choose the operation for the actual task
| Task | Input | Result to review |
|---|---|---|
| Identify an account | A website and supporting business evidence | The company or operating entity represented |
| Research account conditions | Appropriate company sources | Evidence of the product, market or technical condition needed |
| Discover relevant people | Supported company-website and role criteria | Available contacts and actual responsibility |
| Review contact fields | Specific returned values and intended use | Availability, independent checks and unresolved questions |
Dievio supports documented company-website contact search. Do not present that as a universal company-enrichment endpoint, automatic current-stack detection or a newly verified contact source.
Define account fit before expanding contacts
Write why the company belongs in the campaign and what would exclude it. A sponsor list, competitor customer story or hiring page can supply a research lead without proving current buying intent.
Keep role selection tied to the problem your offer addresses. A CTO, operations manager and business owner may have different responsibilities even at the same account.
Use the ICP framework for fit and the role-variant guide for discovery.
Step-by-Step: The Reverse Enrichment Workflow
- Collect website references from an appropriate source and retain provenance.
- Review company identity and unresolved entity relationships.
- Apply account-fit criteria and relevant exclusions.
- Use supported company and role search criteria for a bounded cohort.
- Review returned identities, current responsibility and required fields.
- Hand off accepted records with evidence and a next-action owner.
A free count preview shows matching contact scope, not unique-company totals or full sample contact details. New retrieval uses the applicable credits.
Turn a list of websites into an audience
Keep the original spreadsheet column so you can trace each entry back to its source. Paste the websites or mixed text into Domain Extractor, choose registered domains when subdomains belong to the same company, then copy the unique domain list. Review cases where a subdomain represents a distinct business.
For a small list, open free count Preview. On a phone, first select Show Filters. Open Company Website, paste the domains one per line and select Add websites. Put full URLs on separate lines. Confirm that each intended domain appears in the filter and fix any entries left in the text box.
Add the job titles you need and run Preview Count. For example, try stripe.com and webfx.com with Head of Sales, VP of Sales, Sales Director and Director of Sales. The count covers the combined audience. To see each company separately, reopen Company Website and choose Check coverage by company. For a single company, you can start from the company domain finder.
Import a company website column from CSV
Open free count Preview, then open Company Website and expand Import websites from CSV. Load a CSV or TSV with named columns and select the column containing domains or full website URLs. Each import can add up to 100 new domains. Use files up to 2 MB with at most 10,000 data rows.
For a small test, use a file with columns named Company and Company Website. Put stripe.com on one row and https://www.webfx.com/ on another. Review the proposed domains, choose Add imported websites and download the import report before leaving the filter. It links each source row to its normalized domain and explains skips such as blank values, invalid websites and duplicates.
Keep the original CSV for company IDs and other fields. Dievio uses only the chosen websites in the search filter. The import report describes the input rows. Preview Count shows the combined total after applying your role and company filters. For a count by company, select Check coverage by company in Company Website. Download the coverage report to get a row for every domain in the batch, up to 100. An exact zero means no profiles matched your current filters for that domain. Estimates have their own label, and unavailable counts are left blank in the CSV.
After Preview Count, select Get contacts with these filters and sign in. Set a total lead limit for the search. Use Maximum per company to retrieve up to 20 contacts per company, within a total limit of 500. The search starts with one contact per matching company in the order you added the domains, then takes another pass if the total allows. Download the company search report to see the actual number returned for every domain. A zero in this report means the search returned no contacts for that domain. The earlier coverage report shows how many profiles matched your filters. After a search that uses company websites, choose Export, Overview and CSV. Join the company_domain column to the normalized domain in the import report to recover the CRM IDs and other columns from your original file. You can also use Save Leads and later export the saved list as an Overview CSV. The domain stays with the saved contact. Older rows without a stored domain have an empty cell when exported alongside newer rows.
Check company coverage after a domain change
A company can change its website before the domain stored on existing profiles changes. Compare both websites in the free coverage report when a known company returns an exact zero on its current domain.
- Confirm the domain change on the company’s own site. For a worked example, Wise’s announcement confirms the change from TransferWise to Wise. Compare
transferwise.comandwise.com. - Open free Preview, add both domains under Company Website and choose Check coverage by company. Start with All profiles and no role or location filters. Add the filters needed for your search and check again. Use the status beside each number to distinguish exact counts from estimates and unavailable counts.
- Keep both website values and the same CRM account ID in your source file when you have confirmed they represent the same business. Use the exported
company_domainto join each row back to its source domain. Review current employer and role before using an older record. If you search both websites, apply your account limit across the joined results because the search allocates results by submitted domain.
A redirect can also follow an acquisition or a split. Check the company’s announcement before grouping records under one account. For example, the Kellogg separation notice identifies two independent companies.
Run a bounded search request from a script
Copy the clean domains into the company_websites array. Send this example to POST /api/public/search with your API key and the JSON content type. Keep the key outside your spreadsheet. The request retrieves up to 10 contacts across both domains on the first page. See the Search API contract.
{
"company_websites": ["stripe.com", "webfx.com"],
"job_titles": ["Head of Sales", "VP of Sales", "Sales Director", "Director of Sales"],
"include_emails": true,
"include_phones": false,
"max_results": 10,
"_page": 1,
"_per_page": 10
}Read the returned records from preview_data. Each returned lead uses one API credit. An empty page uses zero. Keep the requested domain list next to the response. If a row lacks enough company information to match it to your sheet, flag it for manual review.
A domain absent from the first page can have matching contacts beyond the result limit. For a per-domain review, run a separately capped request for the domains you still need to check. Record empty results separately from timeouts or credit errors before retrying. See the batch-processing guide.
Preserve review limits at handoff
A populated email or profile match does not establish current employment, mailbox reachability or permission for outreach. Keep validation outcomes and preferences connected to the destination record.
Do not overwrite a trusted company association just because another domain was returned. The field-mapping workflow covers identity conflicts and protected values.
Measure accepted accounts and contacts separately
Report reviewed company identities, relevant contacts, unresolved matches and delivery outcomes under distinct definitions. A large contact count at a few domains is not broad account coverage.
Start with a small known account set in filtered contact search. Expand after the team can explain why each account and contact qualified for the intended task.



