Find expansion contacts at an existing customer in ChatGPT

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: ChatGPT ▪ Lusha
Type: Template

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. Run the prompt with your own customer account and expansion context to see live results.

Expansion rarely starts with a blank account.

You already have a customer, a relationship, and some proof of value. But the next opportunity may sit in another team, another region, another department, or with an executive who has not been part of the conversation yet.

The problem is that most expansion motions rely too heavily on the current champion. If that person does not know who else should care, the account stays smaller than it should.

This prompt uses Lusha in ChatGPT to verify the current customer contact, map adjacent stakeholders, check for recent account signals, and recommend the best expansion path. Instead of asking “who else should we talk to?” in the abstract, you get a verified list of people who may own the next use case, region, team, or buying decision.

How to start

1

Open Lusha in ChatGPT

Go to Lusha in ChatGPT and click “Start chat.” Every conversation started this way is automatically Lusha-enabled.

2

Or invoke Lusha in any existing conversation

Type @Lusha in the prompt bar and select Lusha from the dropdown. Unlike Claude, Lusha does not activate automatically in every ChatGPT conversation. You must invoke it every time.

3

Add the customer account and expansion goal

Copy the prompt below, add the customer account, current contact, use case, and expansion goal, and send. Lusha maps relevant stakeholders and recommends who to engage next.

The prompt

Start from Lusha in ChatGPT or type @Lusha before sending.

@Lusha Find expansion contacts at this existing customer
and recommend the best path to grow the account.

CUSTOMER ACCOUNT:
Company: [company name or domain]

CURRENT RELATIONSHIP:
Current customer contact: [name and title]
Current team or department using us: [team or department]
Current use case: [what they use us for]
Known value or outcome: [one sentence, if known]

EXPANSION GOAL:
I want to expand into:
[new team / new region / executive sponsor / more users /
new product / renewal support / adjacent use case]

MY PRODUCT:
[One sentence describing what you sell and the problem
it solves]

Using Lusha, do the following:

1. VERIFY THE CUSTOMER ACCOUNT
   Confirm the company profile:
   - Company name
   - Domain
   - Industry
   - Employee count
   - HQ location
   - Revenue range if available
   - Company LinkedIn if available

2. VERIFY THE CURRENT CONTACT
   Confirm the current customer contact’s:
   - Current title
   - Department
   - Seniority
   - Location
   - LinkedIn profile if available
   - Whether they appear to still be at the company

   If the current contact appears to have changed roles or
   left the company, flag it immediately.

3. MAP EXPANSION PATHS
   Based on the current use case and expansion goal,
   identify possible expansion paths:

   - Expand within the current team
   - Expand to an adjacent department
   - Expand to another region
   - Add an executive sponsor
   - Add an operations or RevOps owner
   - Add a technical or systems owner
   - Add renewal or procurement influence
   - Hold until there is a stronger signal

4. FIND EXPANSION CONTACTS
   Find relevant contacts at the customer account who may
   own or influence the expansion path.

   Prioritize:
   - Leaders above the current contact
   - Adjacent team leaders
   - Regional owners
   - Operations, RevOps, IT, Data, Sales, Marketing, or
     Customer Success owners, depending on the use case
   - Executive sponsors when relevant

   For each contact, return:
   - Name
   - Current title
   - Department
   - Seniority
   - Location
   - LinkedIn profile if available
   - Verified business email availability
   - Direct or mobile phone availability
   - DNC status if available

5. CHECK ACCOUNT SIGNALS
   Check for recent company signals from the last 6 months
   that may support the expansion motion.

   Prioritize:
   - Hiring surges
   - Hiring surges by relevant department
   - Hiring surges by location
   - Headcount increases or decreases
   - IT spend changes
   - Website traffic changes
   - Commercial activity news
   - Corporate strategy news
   - Financial events news
   - People news
   - Product activity news
   - Risk news
   - Promotion or company-change signals for relevant contacts

6. RECOMMEND THE BEST EXPANSION PATH
   Choose one primary expansion path.

   Explain:
   - Why this path makes sense
   - Which contact should be engaged first
   - Whether to ask the current champion for an intro
   - Which signal supports the timing, if available

7. WRITE THE INTRO ASK
   Write one short message to the current customer contact
   asking for a warm intro to the recommended expansion
   contact.

   Message:
   Under 90 words.
   Reference the current use case or value.
   Explain why the new stakeholder may be relevant.
   Make the ask collaborative, not political.
   Do not make it sound like you are going around the
   current contact.

8. OUTPUT FORMAT
   Return:
   - Customer account verification
   - Current contact verification
   - Expansion path options
   - Recommended expansion contacts
   - Recent account signals, if any
   - Best expansion path
   - Intro ask message
   - Reasoning

Do not invent contacts, emails, phone numbers, companies,
signals, results, or internal account history. If Lusha
cannot verify a contact or signal, mark it clearly.

What you’ll get back

 

A verified expansion map that shows which stakeholders to engage, which path to take, and how to ask for the intro. Here’s what the output looks like:

Customer expansion map — Lusha

FieldValue
Customer account[Company A] · verified customer account · 1,000–5,000 employees
Current contactR.M. · Director of Sales Operations · confirmed at company
Best expansion pathExpand to RevOps · adjacent owner likely supports rollout and data governance
Recommended contactA.B. · VP Revenue Operations · verified email available · mobile available
Supporting signalHiring surge in Operations · supports broader workflow need
Intro askShort champion message included · collaborative, under 90 words

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. Run the prompt with your own customer account and expansion context to see live results.

 

Why use Lusha in ChatGPT to find expansion contacts

 

Expansion is easier when the account already trusts you, but trust does not automatically create a path to the next team, region, or stakeholder. The current champion may not know who else should be involved, or they may not have the authority to expand the relationship alone.

Lusha helps map the next path inside the account. The prompt verifies the current contact, identifies adjacent stakeholders, checks recent account signals, and recommends who to engage next. That gives account teams a clearer way to grow the relationship without relying only on the current point of contact.

The signal layer helps with timing. If the customer is hiring in a relevant department, increasing IT spend, growing headcount, or showing product or commercial activity, the expansion conversation may be more timely. If the account shows risk signals, the motion may need to shift toward retention, efficiency, or executive alignment.

The result is an expansion motion built around verified people, account context, and a clear next step.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use. Lusha is GDPR compliant and covers contacts across North America, EMEA, and APAC.

FAQ

  • When should I use this prompt?

    Use it when you want to expand an existing customer account into another team, region, use case, product, or executive relationship. It is especially useful before QBRs, renewals, expansion planning, and account reviews.

  • Should I contact the expansion stakeholder directly?

    Not always. In many customer accounts, it is better to ask the current champion for a warm intro. The prompt includes a collaborative intro ask so the expansion motion does not feel like you are going around them.

  • What if my current champion left the company?

    The prompt asks Lusha to verify whether the current contact is still at the company. If they appear to have left or changed roles, the output should flag that and recommend a new contact path inside the account.

  • Can this help with renewals?

    Yes. For renewals, the prompt can help identify executive sponsors, procurement or finance influence, operational owners, and additional stakeholders who may affect renewal confidence or expansion potential.

  • What if there are no useful expansion signals?

    The account can still be worth expanding if the current use case and stakeholder map support it. Signals help with timing, but the prompt can also recommend a path based on role relevance, department adjacency, and account structure.

Related Plays

Ready to run this?

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

Get free access Read the Docs