Enrich and segment a target account list for personalized campaigns
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha connector output, but were not pulled from a live session. Run the prompt with your own account list and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.
Enriching and segmenting a target account list for personalized B2B campaigns means adding verified firmographics, buying signals, and the right contact per account to every company name — then grouping accounts by shared profile so each segment gets a message that reflects what those companies actually have in common. This Claude prompt takes a flat list of company names, runs every account through Lusha for firmographic depth and signal data, surfaces the right contact per account, and returns a segmented list with a specific message angle per group — ready for email, paid, or direct outreach in the same pass.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I have an account list for an upcoming campaign but it needs enrichment before we can use it properly. Right now it's just company names — no firmographic depth, no contacts, no signals. I need to enrich every account with verified data, segment the list by firmographic profile, and identify the right contact per segment so the campaign message can be tailored to each group.
My account list:
- Paste your account list: [PASTE COMPANY NAMES OR DOMAINS — one per line]
- Campaign goal: [e.g. "Q3 outbound campaign targeting RevOps" / "product launch to mid-market SaaS"]
- Target persona: [e.g. "VP of Revenue Operations, Director of Sales Ops"]
- Seniority floor: [e.g. "Director and above"]
- Segmentation criteria: [e.g. "by company size" / "by funding stage" / "by tech stack" / "by industry" — or "suggest segments"]
- Campaign channel: [e.g. "email" / "paid social" / "direct outreach" / "all"]
</context>
<task>
1. For each account on the list, use Lusha to enrich with verified firmographic data:
- Current headcount and headcount growth trend
- Industry and sub-industry
- Funding stage and most recent funding event
- HQ location and regional offices
- Tech stack (if available)
- Revenue range (if available)
2. Check Lusha's signals layer per account for the last 30 days:
- Funding event, exec hire in target function, headcount surge, M&A, tech stack change
3. Find the right contact per account matching the target persona:
- Most senior verified contact in the target function
- Verified work email and direct mobile
- Flag any account with no verified contact at the required seniority level
4. Segment the enriched list based on the stated segmentation criteria:
- If "suggest segments": analyse the enriched data and recommend 3–4 natural segments
with a distinct message angle for each
- For each segment: list the accounts, the shared firmographic profile,
and a one-line message angle recommendation
5. Return:
- Full enriched account table: company, headcount, industry, funding stage,
tech stack, signal, verified contact
- Segment breakdown: segment name, accounts in segment, shared profile, message angle
- Any accounts with no verified contact — flag for manual research
- Summary: X accounts enriched, X segments, X accounts needing contact research
</task>
<constraints>
- Only return Lusha-verified contact data. Don't fill gaps with guesses.
- If segmentation criteria is "suggest": base segments on the actual data returned, not assumptions.
- Message angle per segment must be specific — not "personalize the email" but what specific
angle works for that firmographic profile.
- Flag missing contacts clearly — don't skip them silently.
</constraints>What you'll get back
The situation: A demand gen manager has a list of 8 company names for a Q3 RevOps campaign. No firmographic data, no contacts. Running enrichment and segmentation before briefing the copywriter.
Enriched account table
| Company | Headcount | Industry | Funding | Tech stack | Signal | Contact |
|---|---|---|---|---|---|---|
| Dunmore Analytics | 580 | B2B SaaS | Series B · 18d | Salesforce · Gong | 💰 Funding | T.K., VP Sales ✓ |
| Crestline Software | 340 | B2B SaaS | Series A | HubSpot · Outreach | 📈 Hiring +22% | R.V., VP RevOps ✓ |
| Ashford Platforms | 420 | B2B SaaS | Series A | HubSpot · Salesloft | None | M.L., Head Sales Ops ✓ |
| Greenway Cloud | 510 | B2B SaaS | Series B | Salesforce · Outreach | None | J.A., SVP Sales ✓ |
| Briarway SaaS | 290 | B2B SaaS | Seed | HubSpot · Apollo | None | P.O., VP Sales ✓ |
| Falcrest Tech | 380 | B2B SaaS | Series A · 9d | Salesforce · Gong | 💰 Funding | P.N., VP RevOps ✓ |
| Elmont Systems | 610 | B2B SaaS | Series C | Salesforce · Marketo | None | C.N., Director RevOps ⚠ below VP floor |
| Halcyon Data | 470 | B2B SaaS | Series B | HubSpot · Gong | None | S.P., VP RevOps ✓ |
Suggested segments (segmentation criteria: “suggest segments”)
Segment A — Post-funding growth companies (2 accounts) Dunmore Analytics · Falcrest Tech Profile: Series A or B closed in last 30 days · 300–600 employees · active hiring Message angle: “You just closed a round — your RevOps stack needs to scale with the headcount. Here’s how teams at your stage handle the data quality problem before it breaks.”
Segment B — Scaling SaaS on HubSpot (3 accounts) Crestline Software · Ashford Platforms · Briarway SaaS Profile: 290–420 employees · HubSpot as CRM · Series A or Seed Message angle: “RevOps teams on HubSpot at your size hit the same wall — enrichment gaps slow SDR ramp. Here’s how to fix it natively.”
Segment C — Mid-market Salesforce shops (2 accounts) Greenway Cloud · Halcyon Data Profile: 470–580 employees · Salesforce as CRM · Series B Message angle: “At your scale, Salesforce data decays faster than the team can clean it. Here’s what mid-market RevOps teams do about it.”
Missing contacts — flag for research
Elmont Systems — only Director-level contact found in RevOps. Run the find the decision-maker prompt to find VP or above before activating.
Summary: 8 accounts enriched · 3 segments · 1 account needing contact research
Illustrative example — fictional company names used. Run with your own account list to see live results.
Why use Lusha in Claude
Lusha in Claude converts a flat list of company names into a campaign-ready segmented file in one pass — without a data team, without a spreadsheet cleanup session, and without waiting for a CRM export. The tech stack field is what makes the segmentation genuinely useful: knowing that Crestline, Ashford, and Briarway are all on HubSpot means the three accounts share a specific context that shapes the message. A campaign email that references HubSpot natively — “here’s how it works with your CRM” — converts better than a generic enrichment pitch. Lusha verifies both the firmographic data and the contact, so the message reaches the right person at the right company with the right angle. The missing contact flag on Elmont is equally important — an un-flagged gap means the campaign either skips the account silently or sends to the wrong person.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What if I don't know how to segment the list?
Set segmentation criteria to “suggest segments” — the prompt analyses the enriched firmographic data and recommends 3–4 natural groupings based on what the accounts actually have in common. Segments are based on the data returned, not on assumptions about the industry.
How specific should the message angle be?
Specific enough that a copywriter can write the subject line from it without asking a follow-up question. “Personalize the email” is not a message angle. “RevOps teams on HubSpot at your size hit the same wall — enrichment gaps slow SDR ramp” is a message angle.
What if a segment only has one or two accounts?
A segment with one account is just one account. Don’t force it into a group with a different profile just to balance the numbers. A single Tier 1 account with a strong signal and a verified contact deserves a one-to-one personal message, not a sequence.
How is this different from the ABM target list play?
The ABM target list play starts from a campaign brief and builds the account list from scratch. This play starts from an existing account list and enriches it. Use the ABM play when the list doesn’t exist yet. Use this play when the list exists but lacks firmographic depth, contacts, and segmentation.
Can I run this on a CRM export?
Yes — paste the company names or domains from the CRM export into the account list field. Lusha enriches each account against the live data, which means any company that’s stale in the CRM gets updated firmographics and a current contact. The output is also a useful data quality check on the CRM itself.
Ready to build this?
Get started with Lusha and set up this play in minutes.