PROMPT

Enrich a list of company domains

A Claude prompt that takes a list of company domains and returns full firmographics per company — headcount, revenue range, founding year, funding history, location footprint, LinkedIn presence, and industry classification. Built for RevOps building ABM lists, CS planning expansion, and marketing scoring named accounts.

Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the domains and run.

Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.

The prompt

<context>
I have a list of company domains. I want to enrich each one with firmographics, funding history, and location footprint before scoring or planning outreach.
</context>

<task>
1. Take this domain list (one per line):
   [PASTE DOMAINS]

2. For each domain, use Lusha to return:
   - Company name and alternative names
   - Headcount band and LinkedIn follower count
   - Revenue range (annual USD)
   - Founded year and company type (public, private)
   - Full funding history (rounds, amounts, IPO status)
   - HQ city and country, plus a count of regional offices
   - Main industry and sub-industry
   - Key specialties or product areas

3. Output an enrichment table:
   Company | HQ | Headcount | Revenue range | Total raised | Last round | Offices worldwide | Industry

4. Flag any domain Lusha cannot resolve.

5. Summarize at the top: total enriched, total no-match, total combined headcount, total combined capital raised.
</task>

<constraints>
- Do not invent fields. If Lusha returns no record for a domain, surface it as no-match.
- Funding history should include the last round date and amount where available.
- Office count helps RevOps understand regional reach without listing every address.
- Use Lusha's canonical company name, not the literal domain string.
</constraints>

What you'll get back

Input: 5-domain ABM list (snowflake.com, datadoghq.com, notion.com, together.ai, verkada.com).

Output: 5 of 5 enriched, total combined headcount ranging from 8,500 to 21,500 across the five companies, total combined capital raised exceeding $4.5 billion. Below is the real result from running the prompt against the live Lusha connector.

CompanyHQHeadcountRevenue rangeTotal raisedLast roundOffices
SnowflakeSan Mateo, CA5,001–10,000$1B–10B$2.03B (Public)Post-IPO Equity, Apr 202230+ globally
DatadogNew York, NY1,001–5,000$1B–10B$1.02B (Public)Post-IPO Debt, Dec 2024 ($870M)20+ globally
NotionSan Francisco, CA501–1,000$50M–100M$343M (Private)Series C, Oct 2021 ($275M)6 globally
Together AISan Francisco, CA201–500$50M–100M$533M (Private)Series B, Feb 2025 ($305M)4 globally
VerkadaSan Mateo, CA1,001–5,000$250M–500M$644M (Private)Series E, Feb 2025 ($200M)16 globally

The enrichment captures both public (Snowflake, Datadog) and private (Notion, Together AI, Verkada) companies. Verkada’s Series E in Feb 2025 and Together AI’s Series B in the same month are the most recent funding events. Notion’s last priced round was Series C in 2021 — three years quiet at the top of the cap table.

Five credits consumed for five successful enrichments.

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude

Why use Lusha

A domain list is not an account list. Five domains in a row look the same until the enrichment runs — then one is a $10B public company and one is a Series B startup. Three patterns matter for any team scoring accounts before outreach.

Funding history tells you where the account is in its lifecycle. A company three years past its last priced round behaves differently from a company that closed Series B this quarter. Notion’s quiet stretch at the top of the cap table is a different sales motion than Together AI’s fresh $305M Series B. The prompt surfaces both the last round and the full history so the rep reads the trajectory, not just the headline.

Headcount band plus office count maps the territory question. A 1,000-employee company with 6 global offices behaves differently from a 1,000-employee company with 16. Multi-region presence signals where the AE needs partner coverage and where the customer team needs to plan rollout support.

Public vs private changes everything about how the conversation lands. Public companies have SEC filings, quarterly earnings, and a CFO who reports to Wall Street. Private companies have board updates, fundraising windows, and a CFO who reports to a small group of VCs. The prompt surfaces companyType inline so the rep tunes the message.

Data drawn from 300M+ verified contacts and millions of company records under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • How many domains can I paste at once?

    Up to 100 per run. The Lusha tool processes the batch in one call. For larger lists (500+ domains), batch by region or tier so each session stays scannable.

  • What if a domain doesn't resolve?

    The prompt flags it as no-match. Three common causes — the domain is a redirect to a parent company, the company is too small to be in the verified company base, or the domain has been recently registered and not yet indexed. The user can re-search by company name in those cases.

  • What about subsidiaries or domain variants?

    Lusha returns the parent company record when a subsidiary domain is provided. The alternativeDomains field surfaces other domains the company is known by. For multi-entity research, run the parent and the entity separately.

  • Does this enrich contacts too, or only companies?

    This prompt enriches companies only. To enrich contacts inside those companies, run the named-account contact prompt as a follow-up. Most ABM workflows do both — company enrichment first to score and prioritize, contact enrichment second on the accounts that score in.

  • Can I include intent or technographic signals?

    This prompt focuses on stable firmographics — headcount, revenue, funding, location. For technographic (which platforms each company runs) and intent (which categories they’re actively researching), pair this with the tech-stack prospect list prompt or the funded-companies prompt.

  • Will the prompt show the company description and specialties?

    Lusha returns those fields. The prompt’s table format keeps them off the summary view for scannability, but they’re available in the underlying response and Claude will surface them on request.

Ready to build this?

Get started with Lusha and set up this play in minutes.