You can now prospect, enrich, track signals, and clean up CRM data from inside a Claude conversation. No tab switching, no exporting CSVs, no learning a filter syntax. Ask for what you need in plain English, and Lusha’s verified data comes back in the chat.
This is the full walkthrough — what the plugin actually does under the hood, how to set it up, and five real workflows, each with real Lusha data instead of a mockup. By the end, you’ll know exactly what to type and what to expect back.
In this guide
→ What the plugin actually does
→ How to set it up
→ Workflow 1: Build a prospect list
→ Workflow 2: Clean up a CRM export
→ Workflow 3: Scan target accounts for buying signals
→ Workflow 4: Find lookalike accounts
→ Workflow 5: Research a single account before a call
→ What it costs, what it doesn’t replace, and the FAQ
What the plugin actually does
The plugin connects Claude to Lusha’s database of 300M+ verified contacts and 30M+ company profiles, plus the signals layer that tracks funding rounds, executive moves, hiring surges, and other named events across those companies.
Mechanically, here’s what happens when you ask Claude for something: Claude reads your request, maps it to Lusha’s structured search filters — job title, seniority, department, company size, industry, location — and calls Lusha’s API. The response comes back into the conversation as readable contacts or companies, not raw JSON. You never see a filter syntax. You also never see anything Claude invented; every name, title, and company in a response came directly from a live Lusha call.
Three categories of data are available through the plugin:
How to set it up
Workflow 1: Build a prospect list
Describe the audience the way you’d describe it out loud:
“Find me VPs of Revenue Operations at companies with 200 to 1,000 employees. I want their verified email and a sense of which companies they’re at.”
Claude maps that to job title, seniority, and company size filters and runs the search. Here’s a real sample, pulled live the same way:
Real contacts from the Lusha API, June 2026. Names abbreviated for privacy. Full details available on reveal inside Lusha.
707 contacts matched this exact search. You can keep narrowing in the same conversation — by industry, by country, by a specific list of target companies — without starting over.
Workflow 2: Clean up a CRM export
Paste a list of names and companies straight into the chat:
“Here’s a CRM export — 30 contacts. Check if each one still has a current, high-confidence email, and flag anyone who’s changed companies or gotten promoted in the last year.”
Claude matches each row against Lusha and confirms current title and standing. Running this against two of the contacts from Workflow 1, both come back unchanged — still VP of Revenue Operations at the same company, still the same email on file:
That’s the same job-change and promotion signal that powers Lusha’s audience datasets, now running against your own list instead of a fresh search. With 30% of B2B contact data decaying every year, running this quarterly against an active pipeline list is the difference between reps calling a working number and reps calling a dead one.
Workflow 3: Scan target accounts for buying signals
Take a target account list and ask for the signal scan directly:
“Scan Front, Sigma, and Fresha for buying signals since the start of the year — funding, executive moves, hiring surges. Tell me which one is in the strongest buying position right now.”
Run on the same three companies from Workflow 1, this is what actually comes back:
Real signal events from the Lusha API, June 2026.
This is the part a generic intent score can’t give you. Fresha just took $80M and is actively hiring — new money, confirmed urgency. Sigma just lost its CRO, which is a real account-risk signal if Sigma is a customer, or a re-entry opportunity if it isn’t and the new regime hasn’t settled on a vendor stack yet. Front’s hiring surge plus a channel-sales executive hire suggests a partnership-led GTM push. Three companies, three different stories, each backed by a dated, sourced event — not a single number trying to summarize all of it.
Workflow 4: Find lookalike accounts
If you already know which accounts convert well, ask Claude to find more like them:
“Here are 8 of our best customers by domain. Find me 20 more companies that look like them — similar size, similar industry, similar profile.”
This needs at least 5 reference companies to produce a useful match. The output is a ranked list of lookalike companies you haven’t already worked, which you can immediately follow with Workflow 1 to find the right contacts at each one.
Workflow 5: Research a single account before a call
Fifteen minutes before a discovery call, ask for the full picture on one account:
“Give me everything on Sigma — size, industry, any recent signals, and who else besides my contact might be part of the buying committee.”
Based on what’s actually in Lusha right now, this comes back with the firmographic profile, the CRO departure and APJ expansion signals shown above, and a list of other senior contacts at the company — so you walk into the call already knowing the org just lost its revenue leader, which is exactly the kind of thing worth asking about directly.
What it costs
The plugin doesn’t have its own pricing. It spends your existing Lusha credits, the same balance you’d use in the app or through the API. A short reference, since it changes how you’ll want to phrase requests:
If you only need to confirm someone exists and holds a certain title, ask Claude to search without revealing contact details — you’ll see the match and decide whether it’s worth spending the credit before you do.
What it doesn’t replace
The plugin is another way to reach the same data, not a separate product. For building and exporting a list of several hundred contacts to load into a sequencer, the Lusha app’s bulk export is still the faster path. For automated, always-on workflows — enrich every new lead the moment it hits your CRM, alert a rep the instant a champion changes jobs — that’s what the n8n integration and the API are for. The Claude plugin is built for the in-between moments: a quick prospecting pass, a sanity check on a list, a signal scan before a call, all without leaving the conversation you’re already having.
