Post a deal risk alert to Slack when a prospect gets acquired
Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
This Claude prompt checks your pipeline for M&A signals via Lusha and posts a deal risk alert to Slack when a prospect is acquired — the deal owner and manager tagged, the impact assessed, one specific action included. Acquisition as the acquired party is the signal that kills deals silently. This play surfaces it the same week it happens.
Tools: Claude, Lusha, Slack
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I want to post a deal risk alert to our sales Slack channel when a prospect or customer gets acquired — before the rep discovers it on a call. The signal should go to the deal owner and their manager the same day it's detected.
My accounts to monitor:
- Account list: [PASTE COMPANY NAMES — or "check my active pipeline"]
- Slack channel: [CHANNEL NAME — e.g. #deal-alerts or #revenue-team]
- Deal owners: [REP NAME PER ACCOUNT — or "find from context"]
</context>
<task>
1. For each account, use Lusha's signals layer to check for M&A activity:
- Has the company been acquired as the target entity?
- Has the company announced a merger?
- Has there been a significant ownership or parent company change?
- Note: acquisition as the acquirer is a positive signal — only flag acquired-as-target
2. For each account where M&A is detected:
- Confirm the signal via Lusha: who acquired them, approximate timing
- Assess the deal impact:
- FREEZE RISK: vendor contracts often frozen during integration
- RE-ROUTE RISK: procurement and approval paths change after acquisition
- OPPORTUNITY: if the acquirer is also a prospect or customer, flag the relationship angle
- Find any new contacts introduced by the acquisition
3. Draft a Slack alert for each flagged account:
- Start with the impact, not the news
- State what was detected and when
- State the most likely deal impact
- Name one specific action the rep should take before their next touch
- Tag the deal owner and manager
- Under 80 words, formatted for Slack with *bold* key fields
4. Post the alert to the specified Slack channel.
5. If no M&A signals detected: no post needed.
</task>
<constraints>
- Only post when Lusha confirms M&A activity.
- Acquired-as-acquirer is not a risk signal — only acquired-as-target gets an alert.
- The recommended action must be specific: not "follow up" but a concrete next step.
- One alert per account per signal event.
</constraints>What you'll get back
The situation: A RevOps lead runs this weekly across 12 active deals. This week Lusha detects one M&A signal: Cartway Technologies was acquired 9 weeks ago.
Output: One Slack alert posted to #deal-alerts. Deal owner and manager tagged. Impact assessed as FREEZE RISK. One specific action included.
Slack alert — posted to #deal-alerts
⚠ Deal risk — Cartway Technologies | @james.r @manager.name
FREEZE RISK: Cartway was acquired 9 weeks ago as the target entity. Vendor contracts at acquired companies typically go under review during integration — new sign-offs required, timelines extend.
Action: Before sending the proposal, ask directly: “Has the acquisition changed how you handle new vendor approvals?” Don’t assume the original path still holds.
(68 words)
No other M&A signals detected this week — no alert posted for other accounts.
M&A signal confirmed via Lusha connector, May 19. Slack alert posted to #deal-alerts.
Why use Lusha in Claude
An acquisition that happened 9 weeks ago should have changed how the rep handles the Cartway deal weeks ago. Without a signal check, it surfaces on the call when the rep pushes for proposal sign-off and learns that procurement is now handled by the acquiring company’s legal team. That’s a 30–45 day stall that was avoidable. Lusha in Claude finds the signal and posts it to Slack — where the rep and manager already are — with the impact assessed and the next action specific. The alert goes to the right people the same week the signal is detected, not the week they discover it themselves.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What's the difference between FREEZE RISK, RE-ROUTE RISK, and OPPORTUNITY?
FREEZE RISK means vendor contracts are likely paused during integration — typical when the company is a smaller target absorbed into a larger acquirer. RE-ROUTE RISK means the deal can still move but approval paths have changed — new procurement contacts, different sign-off authority. OPPORTUNITY means the acquirer is already a customer or prospect — the acquisition may open a new relationship angle rather than stalling the existing one.
What if the acquisition happened months ago and I didn't catch it?
The prompt flags it regardless of how long ago it happened — if Lusha shows an acquisition that isn’t reflected in CRM notes, it surfaces. For a full historical audit of M&A signals across the pipeline, the ICP drift audit covers this as part of a broader firmographic check.
Should I always pause the deal when I get a FREEZE RISK alert?
Not automatically — pause the push for signature, but keep the relationship warm. The right action is the one in the alert: ask directly whether the acquisition changes the approval path before assuming the original deal structure still holds. The answer determines whether you pause or accelerate.
What if my company acquired a prospect — does that get flagged?
No — acquired-as-acquirer signals are explicitly excluded. The flag is only for when your prospect is the target of an acquisition, which is the risk scenario.
Ready to build this?
Get started with Lusha and set up this play in minutes.
