AI prompt

Ask for a contact and get the whole account in Claude

Tools: Claude ▪ Lusha

Contact enrichment with buying signals is what happens when a lookup stops being a lookup. Give Claude with the Lusha connector one name, and it returns the verified person, the account behind them, every dated event at that company in the last 90 days, the other people who decide, and a reason to reach out this week. Not just a name, an email or a phone number. The company, the signals, the people who decide, and why this contact is worth your time.

Example outputs in this play are illustrative. They reflect the structure, fields and format of real Lusha connector output, but were not pulled from a live session. Names are masked to initials, emails show the domain only and phone numbers are masked. Run the prompt with your own data and connectors to see live results.

The prompt

Open in Claude Open in ChatGPT

Use the Lusha connector. I am going to give you one contact. Return the full story, not just the contact card.

Contact: [FIRST LAST], [COMPANY]  (or paste a work email or LinkedIn URL instead)

Step 0. Run account_usage first (0 credits). Tell me the balance and what this run will cost before you spend anything.

1. The person. Search and enrich the contact. Confirm they are still at the company. Return verified title, work email, direct dial if available, location, and the date each field was last verified. Check contact signals for the last 90 days and flag a job change or promotion.

2. The account. Enrich the company: headcount, industry, HQ, revenue range, technologies, estimated IT spend and monthly web traffic where available.

3. What changed. Pull company signals for the last 90 days. Keep only dated events: hiring surges by department and location, headcount change, IT spend change, funding, and news (corporate strategy, people, commercial activity, risk). Drop anything older than 90 days and anything that repeats an earlier item. One line per event, date first.

4. Who else decides. Run the buying group for the company. List decision makers, potential champions and end users with title, up to 8 people, and mark whether my contact is one of them. Show which have an email or phone available. Do not reveal them yet.

5. The next move. Three lines: why this account is worth time this week (cite the dated events), who to contact first and why, and one opening line that names a specific dated event.

Format: five short sections with those headings. Show credits spent at the end. If a step returns nothing, say so in one line and move on.

What you'll get back

The situation. A rep gets a name from a webinar list: J.K., a RevOps lead at a mid-size software company. No context, no history. Rather than search, enrich, open the company, check signals and search again, she pastes the name into Claude and asks for the full story.

The output, five sections, in order:

Cost check · Balance 1,240 credits. This run: about 6 to 12 credits (contact enrich 1, company enrich 1, signals 1 per matched type, buying group 1 per role revealed, if you choose to reveal).

1. The person

J.K. · Head of Revenue Operations · still at [company], verified Oct 2026
Work email j.k@[company].com · confidence A1 · verified 2026-10-03
Direct dial +1 ••• ••• 0148 · verified 2026-09-21
Contact signals, last 90 days: promoted from Director to Head of RevOps, 2026-08-14

2. The account

[Company] · 480 employees · B2B software · HQ Austin, TX · revenue range $50M to $100M
Technologies include Salesforce, Outreach, Snowflake · est. annual IT spend $4.1M · monthly web traffic 92K

3. What changed (90 days)

2026-10-05 · Surge in hiring by department: Sales +41% vs 90-day average
2026-09-29 · IT spend increase, +12% on the prior reading
2026-09-12 · Commercial activity: new partnership announced with a payments platform
2026-08-14 · People news: new Head of RevOps (your contact)

4. Who else decides

Decision maker · M.T. · VP Sales · email available, phone available
Decision maker · R.S. · CFO · email available
Potential champion · J.K. · Head of RevOps · your contact
End user · A.P. · Sales Operations Manager · email available
End user · D.L. · SDR Team Lead · email and phone available

5. The next move

Worth time this week: a sales hiring surge and an IT spend increase inside the same month, two weeks after a new RevOps lead arrived. Budget and headcount are moving together.
Contact first: J.K. She is the potential champion, she is new in the seat, and the hiring surge lands on her desk.
Opening line: “Saw [company] posted 41% more sales roles than usual this month, right after your move into the Head of RevOps seat. When a team grows that fast, the data behind the dialer usually doesn’t keep up. Worth 15 minutes?”

Credits spent: 7

Contact and company details above are illustrative. In a live run every field carries the date Lusha last verified it, and every signal carries the date of the event.

Why it works

Lusha in Claude does five jobs in one conversation because the connector exposes each one as a tool: contact search and enrich, company enrich, company and contact signals, buying group, and a zero-credit balance check. Claude sequences them, keeps only dated events from the last 90 days, and reasons across the results to say who to call first. The buying group returns the three roles Lusha documents, decision maker, potential champion and end user, so the map is grounded in the product rather than guessed. Every reveal is a choice: the prompt shows what is available before spending a credit on it. Lusha’s data is GDPR certified and CCPA validated, and the connector works on every plan, including Free. See the Trust Center and the MCP documentation.

FAQ

What does this prompt cost to run?

It depends on what Lusha finds. The prompt runs account_usage first, which costs nothing, and tells you the balance and the likely cost before anything is spent. A typical run is single-digit credits: 1 for the contact enrich, 1 for the company enrich, 1 per matched signal type, and 1 per buying group role you choose to reveal. Nothing is revealed in step 4 until you say so.

Can I start from an email or a LinkedIn URL instead of a name?

Yes. Replace the contact line with a work email or a LinkedIn profile URL. Lusha resolves either to the same contact record.

Why only the last 90 days of signals?

A reason to reach out has a shelf life. Older events still exist in Lusha, and you can widen the window in the prompt, but a 90-day cut keeps the “what changed” section to things you can mention on a call without sounding late.

Does this work in ChatGPT too?

Yes. The Lusha connector runs in ChatGPT and any MCP client. Paste the same prompt. See AI connectors for setup.

Is Buying Group available on my plan?

Buying Group is in beta and available through the connector, the API and the Workspace. Reveals are 1 credit per role. Check pricing for current plan details.

Related prompts

Browse all Lusha Plays

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Start for free Read the Docs