More Resources
Prompt

Alert the team when a target account shows a buying signal

Built by: Lusha
Time to build: 2 min
Difficulty: Easy
Tools: Claude ▪ Gmail ▪ Lusha ▪ Slack

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 and Gmail thread output, but were not pulled from a live session. Run the prompt with your own data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

A funding round at a target account is worth nothing if the rep finds out two weeks later. This Claude prompt scans target accounts weekly via Lusha, checks Gmail for any existing thread with the account, and posts a structured alert to Slack the same week the signal is detected — verified contact details included, one specific first move attached.

The prompt

Open in Claude Open in ChatGPT 
<context>
I want to alert the right person on Slack the moment a target account shows a buying signal — before anyone discovers it manually and before the window closes. The alert should include the signal, whether we already have a thread with this account, and one suggested first move.

My target accounts:
- Account list: [PASTE COMPANY NAMES — one per line]
- Slack channel: [CHANNEL NAME — e.g. #signal-alerts or #revenue-team]
- Account owners: [REP NAME PER ACCOUNT — or "find from context"]
- What I sell: [PRODUCT / SOLUTION]
</context>

<task>
1. For each account, use Lusha's signals layer to check for buying signals in the last 30 days:
   - New exec hire in the function I sell into
   - Funding event (Series A or later)
   - Headcount surge in the relevant function (15%+ growth)
   - M&A activity as the acquirer (growth signal, not risk)
   - New office or geographic expansion

2. For each account where a signal is detected:
   - Confirm the signal via Lusha — type, approximate date, specifics
   - Search Gmail to check whether anyone is already in an active thread with this account
   - Use Lusha to find the most relevant current contact for the signal

3. Draft a Slack alert for each signalled account:
   - Lead with the signal, not the account name
   - State what was detected and why it matters for timing
   - Include current contact details: verified name, title, email
   - State whether an existing Gmail thread exists — and if so, who owns it
   - One specific suggested first move
   - Tag the account owner
   - Under 100 words, *bold* key fields

4. Post each alert to the specified channel.

5. No signals detected: no post — only alert on confirmed signals.
</task>

<constraints>
- Only post when Lusha confirms a signal. No speculative alerts.
- The suggested first move must be specific: not "reach out" but exactly who to contact, how, and what angle.
- If an existing Gmail thread is found: the alert must reference it.
- One alert per account per signal event.
</constraints>

What you'll get back

The situation: A sales manager runs this weekly scan on 8 target accounts. This week Lusha detects signals at two accounts — a new VP of Sales hire at [collaborative AI workspace] and a Series B funding round at [revenue orchestration platform].

Slack alert 1 — posted to #signal-alerts

📈 New VP Sales hire at [collaborative AI workspace] — @james.ae

Signal: E.R. joined as Head of Sales Development 11 days ago — first dedicated SDR leadership hire at [collaborative AI workspace]. New SDR leaders evaluate data and tooling in the first 30 days.

Contact: E.R., Head of Sales Development — e.r@[n*****].com ✓ · mobile available

Existing thread: D.R. (Head of Sales Strategy) replied to outreach 38 days ago asking for enrichment details. Thread went cold — pick it back up and reference E.R.’s hire as the reason to reconnect now.

First move: Reply to the D.R. thread today — “Saw [collaborative AI workspace] just brought on a Head of Sales Dev. Given what you said about the ops review, this feels like the right moment to reconnect.”

Slack alert 2 — posted to #signal-alerts

💰 Series B funding — [revenue orchestration platform] — @sarah.ae

Signal: [Revenue orchestration platform] announced Series B funding 6 days ago. Post-funding is the highest-intent window for tooling conversations — new budget, new headcount targets, new urgency to build the right stack.

Contact: M.T., VP of Revenue Operations — m.t@[c****].com ✓ · mobile available

Existing thread: M.T. replied to outreach in March asking about pricing. No follow-up was sent. Thread is cold but the relationship exists.

First move: Email M.T. today referencing the funding and the open pricing question: “Congrats on the Series B — when we last spoke you asked about pricing. With the new round, the timing looks different. Worth revisiting?”

No signal detected this week: [Conversation intelligence SaaS] · [Customer support SaaS] · [CRM platform] · [Sales enablement SaaS] · [Sales content SaaS] · [AI revenue platform] — no alerts posted.

Signals confirmed via Lusha connector. Gmail threads checked in live session. May 26, 2026. Contact details masked for privacy.

Why use Lusha in Claude

The [revenue orchestration platform] alert is the one that demonstrates the full value of the Gmail layer. Without it, the alert says “funding detected, reach out to M.T.” With it, the alert says “you already have a thread with M.T. from March where pricing was discussed — use the funding as the reason to reopen it.” That’s the difference between a cold outreach and a warm re-entry with a specific angle. The signal creates the timing. The Gmail history provides the context. Lusha validates the contact details. Slack delivers it to the right person in the same channel where the team already works.

Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • How often should I run this?

    Weekly. Signals don’t change daily but the window to act on a signal closes fast — a funding announcement is highest-intent in the first two weeks. Running weekly ensures the alert arrives within the window, not after it.

  • What if multiple signals fire on the same account in the same week?

    The prompt posts one alert per account per run, combining all signals detected into one post. Running it again the following week will only alert on new signals not previously flagged.

  • What's the difference between this and the weekly signal digest?

    The weekly signal digest builds a full account intelligence digest for a saved territory — it’s a reading document. This prompt fires targeted Slack alerts at specific people for specific accounts with a suggested action attached. Different output format, different audience, different urgency level.

  • What if I don't have an existing Gmail thread with the account?

    The alert says “no prior thread — first contact” and the first move is a cold outreach angle based on the signal. The Gmail check adds context when history exists — its absence doesn’t block the alert.

Related Prompts

Ready to run this?

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

Start for free Read the Docs