Spot account risk signals in ChatGPT

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

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 target accounts or open opportunities to see live results.

Not every signal means “go sell.”

A company may be reducing headcount, losing website traffic, lowering IT spend, dealing with risk news, or showing signs of internal pressure. That does not always mean the account is a bad fit. But it does mean the message, timing, and next step should change.

The problem is that most reps treat every account the same until someone replies or the deal stalls.

This prompt uses Lusha in ChatGPT to check target accounts for risk signals, explain what changed, and recommend whether to contact now, hold, reframe the outreach, or multi-thread the deal. Instead of pushing forward blindly, you get a clearer view of whether the account is ready, risky, or needs a different approach.

How to start

Open in Claude Open in ChatGPT
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

Paste your accounts and send

Copy the prompt below, paste your target accounts or open opportunities, add your product context, and send. Lusha checks for risk signals and helps you decide whether to contact, hold, reframe, or multi-thread.

The prompt

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

@Lusha Check these accounts for risk signals before I
reach out or move the deal forward.

ACCOUNTS:
Paste company names or domains:
1. [company name or domain]
2. [company name or domain]
3. [company name or domain]

CONTEXT:
Use case: [new outbound / open opportunity / renewal /
expansion / re-engagement]
Target persona: [persona or title]
Current stage, if relevant: [prospecting / discovery /
demo / proposal / renewal / expansion]
My product: [one sentence describing what you sell and
the problem it solves]

Using Lusha, do the following:

1. MATCH AND VERIFY THE ACCOUNTS
   Match each company to the correct Lusha company profile.
   Return:
   - Company name
   - Domain
   - Industry
   - Employee count
   - HQ location
   - Revenue range if available
   - Match status

   If a company cannot be matched, flag it clearly.

2. CHECK ACCOUNT RISK SIGNALS
   For each matched account, check for risk or negative
   movement signals from the last 6 months.

   Prioritize:
   - Risk news
   - Headcount decrease over 1, 3, 6, or 12 months
   - Website traffic decrease
   - IT spend decrease
   - Negative market intelligence news
   - Financial events news that may indicate pressure
   - Corporate strategy news that may affect priorities

3. CHECK BALANCING SIGNALS
   Also check for positive or mixed signals that may change
   the interpretation.

   Look for:
   - Hiring surges
   - Hiring surges by relevant department
   - Headcount increases
   - IT spend increases
   - Website traffic increases
   - Commercial activity news
   - Product activity news
   - People news
   - Promotion or company-change signals for relevant contacts

4. INTERPRET THE SIGNALS
   For each account, explain what the risk signal may mean
   for my use case.

   Keep the interpretation grounded.
   Do not assume the company is in crisis unless Lusha
   returns signals that support it.
   Do not turn every negative signal into a reason to pitch.

5. ASSIGN AN ACCOUNT STATUS
   Choose one:

   Contact now:
   Risk signal creates a relevant, timely reason to reach out.

   Reframe outreach:
   Account may still be relevant, but the message should
   change because of the signal.

   Multi-thread:
   Current contact or deal may be exposed to risk, so find
   additional stakeholders.

   Hold:
   Signal suggests poor timing or unclear urgency.

   Exclude:
   Account is poor fit, unmatched, or too risky for this motion.

6. FIND RELEVANT CONTACTS
   For accounts marked Contact now, Reframe outreach, or
   Multi-thread, find 1-2 relevant contacts matching the
   target persona or likely ownership of the problem.

   Return:
   - Name
   - Current title
   - Department
   - Seniority
   - Location
   - LinkedIn profile if available
   - Verified business email availability
   - Direct or mobile phone availability
   - DNC status if available

7. WRITE THE NEXT MOVE
   Based on the account status, write one of the following:

   If Contact now:
   Write a short outreach email under 100 words.

   If Reframe outreach:
   Write a revised opening angle under 50 words.

   If Multi-thread:
   Write a short message asking to involve another stakeholder.

   If Hold or Exclude:
   Explain why not to reach out now.

   Do not:
   Sound alarmist.
   Mention sensitive risk signals in a way that feels intrusive.
   Say "I saw your headcount dropped."
   Overstate what the signal proves.
   Invent company problems, layoffs, projects, or internal
   priorities that Lusha did not return.

8. OUTPUT FORMAT
   Return:
   - Account risk table
   - Risk signals found
   - Balancing signals found
   - Account status
   - Recommended contacts, if relevant
   - Recommended next move
   - Reasoning

Do not invent companies, contacts, emails, phone numbers,
or signals. If Lusha cannot verify a risk signal, mark it
clearly.

What you’ll get back

 

A risk-aware account check that shows what changed, how it may affect outreach or pipeline, and what to do next. Here’s what the output looks like:

Account risk signal check — Lusha

FieldValue
Account checked[Company A] · matched by domain
Risk signalHeadcount decrease · -5% over the last month
Balancing signalHiring surge in IT · suggests selective investment, not full stop
Account statusReframe outreach · avoid growth-heavy message
Recommended contactR.M. · VP Operations · verified email available
Next moveLead with efficiency and prioritization, not expansion

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 target accounts or open opportunities to see live results.

 

Why use Lusha in ChatGPT to spot account risk signals

 

Risk signals do not always mean an account is a bad target. Sometimes they mean the timing is sensitive. Sometimes they mean the message needs to change. Sometimes they mean the rep should multi-thread before the deal loses momentum.

Lusha helps make that call with verified account signals. The prompt checks for signals such as risk news, headcount decreases, website traffic decreases, IT spend decreases, and financial or corporate strategy news. It also checks for balancing signals, because accounts are rarely simple. A company may be reducing headcount overall while still hiring in IT, investing in systems, or launching a new product.

That context helps reps avoid the wrong message. A growth-heavy email may land badly at an account under pressure. A more useful message may focus on efficiency, consolidation, risk reduction, or helping the team do more with less.

The result is a more thoughtful account motion: reach out when it makes sense, reframe when needed, hold when timing is poor, and multi-thread when the deal is exposed.

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

  • What counts as an account risk signal?

    Risk signals can include risk news, headcount decreases, website traffic decreases, IT spend decreases, financial events, or corporate strategy news that may affect timing, budget, or priorities at the account.

  • Does a risk signal mean I should stop prospecting the account?

    Not always. A risk signal may mean you should change the message, contact a different stakeholder, or wait for stronger timing. The prompt helps separate accounts to contact now from accounts to reframe, multi-thread, hold, or exclude.

  • Should I mention the risk signal directly in outreach?

    Usually no. The prompt asks ChatGPT to avoid intrusive language like “I saw your headcount dropped.” Instead, it turns the signal into a more thoughtful business angle, such as efficiency, prioritization, consolidation, or doing more with fewer resources.

  • Can this help with open opportunities?

    Yes. For open deals, risk signals can help reps understand why a deal may be slowing down, whether the buying group needs to expand, or whether the message should shift before the next touchpoint.

  • What if Lusha finds both positive and negative signals?

    That is common. The prompt checks for balancing signals so the account is not judged from one data point alone. For example, a company may show overall headcount reduction while still hiring in a relevant department or increasing IT investment.

Related Prompts

Ready to run this?

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

Get free access Read the Docs