TLDR: Four Claude prompts built for the signal types that matter most in Financial Services selling — M&A activity that reshuffles budget owners overnight, leadership changes at banks and asset managers that open or close windows without warning, regulatory events that create urgent spending pressure, and the compressed deal timing that makes acting on a signal within 48 hours the difference between first call and missed quarter. All four run on the Lusha connector for Claude.
Why buying signals in Financial Services require a different read
Financial Services buying signals don’t announce themselves the way SaaS signals do. A bank doesn’t post a press release when the new CRO decides to rebuild the compliance stack. A PE-backed portfolio company doesn’t send a calendar invite when the integration team is about to consolidate vendors. A regional insurer doesn’t tweet that a regulatory exam just surfaced a gap that needs a solution by Q3.
The signals are there — M&A filings, executive moves, hiring surges in risk and compliance functions, LinkedIn announcements from a new CFO three weeks into the role — but reading them requires connecting dots across sources that don’t sit in a single feed. And in Financial Services, the timing window is narrow. A new CRO who just arrived from a competitor has 90 days to make her mark before the budget cycle locks. A bank acquisition creates a 60-day window where the acquirer is actively evaluating which vendor relationships carry forward. Miss it and the window closes.
The four prompts in this article use Lusha’s signals layer and verified contact data to surface these events, assess the timing window, and return a specific first move — not a generic “reach out” recommendation, but who to contact, what signal to reference, and what angle is most likely to land given where they are in the event cycle. All four connect through the Lusha connector for Claude.
Connect Lusha to Claude in two minutes →
Section 1: Getting the pre-call brief right before you dial
Prompt 1: Build a single-account signal brief before a call or meeting
In Financial Services, walking into a call without knowing what’s happened at the account in the last 90 days is a liability. If a bank just completed an acquisition and you spend ten minutes asking about their current vendor stack, you’ve signaled that you’re not paying attention. If a new CFO joined three weeks ago and you open with a renewal conversation framed around the previous CFO’s priorities, you’ve already lost the room.
This prompt builds a structured pre-call brief for any account — pulling leadership changes, M&A activity, strategic investments, product announcements, and hiring surges from Lusha’s signals layer, then organizing everything into a 3-line headline summary and 3–5 specific talk tracks. The brief is designed to be read in under two minutes before a call, not studied for an hour.
<context>
I have a discovery call or strategic review on [ACCOUNT NAME / DOMAIN] in the next [TIMEFRAME, e.g. 24 hours].
I want a complete pre-call brief — every recent signal in the last 6 months, organized so I can scan it in 60 seconds.
</context>
<task>
1. For the target account, use Lusha's signals layer to pull every signal type from the last 6 months. Organize the output into five categories:
- Leadership: executive hires, executive promotions, executive departures
- Strategic moves: M&A, IPO, funding rounds, strategic investments
- Product activity: launches, integrations, new features
- Hiring intensity: surges by department and by location, headcount growth (1m / 3m / 6m / 12m)
- Market signals: web traffic shifts, partnerships, new customers, recognition events
2. For each signal, return:
- Event type
- Event date or signal date
- Headline / one-line summary
- Source article URL where available
3. At the top of the brief, surface a 3-line "headline" summary:
- Most important leadership move
- Biggest strategic shift
- Strongest active hiring signal
4. After the categorized brief, suggest 3-5 talk tracks for the call, each tied to a specific surfaced signal.
</task>
<constraints>
- Pull every available signal type, not just funding and hiring. Pre-call briefs need leadership, product, and market context too.
- Surface the source article URL on every signal that has one — useful for outreach and discovery prep.
- Do not invent any event, date, or name. Surface only what Lusha returns.
- If no signals fired in the window, surface that honestly. A quiet account is intelligence too.
</constraints>Section 2: Timing outreach to the signal window
In Financial Services, the signal is only half the work. A leadership change at a bank is a buying signal for about 90 days — after that, the new executive has either committed to an incumbent vendor or moved on from the problem. An M&A announcement creates urgency in the first 60 days of integration planning; by month four, the decisions have usually been made. Knowing a signal exists isn’t enough. Knowing whether you’re inside or outside the window determines whether you reach out now or hold for next quarter.
Prompt 2: Decide the right moment to reach out based on signals
This prompt combines Lusha’s signals layer with Gmail engagement history to return a single timing recommendation — NOW / SOON / HOLD / COLD APPROACH — with the reasoning behind it. In Financial Services contexts, the signals it weighs most heavily are leadership transitions, M&A activity, and regulatory filing dates, all of which have well-defined urgency windows. A new CRO who joined 10 days ago is a NOW. The same CRO at day 95, four weeks before year-end close, is a HOLD.
<context>
I want to know the best moment to reach out to a specific prospect — not based on a calendar reminder, but based on what's actually happening at the account right now. I want to check for signals, cross-reference with any prior email history, and get a specific recommended outreach timing and angle.
My prospect:
- Company: [COMPANY NAME OR DOMAIN]
- Contact: [NAME AND TITLE — or "find the right person"]
- What I sell: [PRODUCT / SOLUTION]
- Last time I reached out: [DATE OR "NEVER"]
</context>
<task>
1. Use Lusha's signals layer to check what's happening at this account right now:
- New exec hire in the function I sell into?
- Funding event in the last 60 days?
- Headcount growth in the relevant function (15%+)?
- M&A activity?
- Any structural change that creates urgency or budget?
2. Search Gmail for any prior outreach history with this company:
- Has anyone from the team emailed this account before?
- What was the last topic? Did the contact reply?
- How long ago was the last touch?
3. Combine signal + history to produce a timing recommendation:
- NOW: strong signal detected + no recent outreach — reach out this week
- SOON: signal detected but recent outreach exists — wait 2–3 weeks
- HOLD: no signal + recent unanswered outreach — wait for a trigger
- COLD APPROACH: no signal, no prior history — reaching out on ICP fit only
4. If NOW or SOON: draft the specific outreach angle:
- Which signal to lead with
- Which contact to reach (verified via Lusha)
- Whether to reference prior email history or treat as fresh outreach
- Draft subject line and opening sentence only — not a full email
5. Return:
- Signal summary: what was detected, when, and why it matters
- Prior contact summary: last touch, topic, outcome
- Timing recommendation: NOW / SOON / HOLD / COLD APPROACH
- If NOW or SOON: contact details and opening angle
</task>
<constraints>
- Timing recommendation must be based on actual signal data — not a default "reach out now."
- HOLD is a valid recommendation. Don't manufacture urgency where none exists.
- The opening angle must reference the specific signal — not a generic product pitch.
- If no contact is specified: find the most relevant verified contact via Lusha.
</constraints>Prompt 3: Scan your CRM contacts for role changes that open new doors
Leadership changes in Financial Services create buying windows, but they also create a separate problem: contacts you thought you had go cold without warning. A champion at a regional bank gets promoted to a group-level role and is no longer running the vendor evaluation. A CFO you’ve been nurturing for six months takes a position at a different institution. A compliance director who knew your product inside out moves to a competitor.
This prompt scans a contact list against Lusha’s signals layer and contact records to return a PROMOTED / MOVED / NO CHANGE / NO MATCH classification for every contact in the list — and for anyone who’s moved or been promoted, flags whether the change creates a new opportunity (access to a larger budget, a more senior relationship, an intro to the new account) or a coverage gap that needs filling immediately.
<context>
I have an existing CRM contact list. I want to know which of these contacts had a role change — promotion or company move — in the last 12 months. Both events open a re-engagement window.
</context>
<task>
1. Take this CRM contact list (one row per line, with name and current company):
[PASTE CONTACT LIST]
2. For each contact, run two parallel lookups:
- Signals layer: query Lusha's contact signals (promotion, companyChange) for time-series events in the window
- Contact lookup: query Lusha's contact record for the contact's current jobStartDate and previousJob fields
3. Combine the results. A role change is detected if EITHER:
- The signals layer returned a promotion or companyChange event in the window
- The contact's jobStartDate is more recent than the CRM record's lastUpdated date and the title or company has changed
4. Output a role-change table:
Name | CRM record | Current Lusha record | Change type | Detected by | Signal date | Action
5. Assign a change type per row:
- PROMOTED — same company, new title or expanded scope (re-engage with first-90-days framing)
- MOVED — new company since the CRM record was created (update the row, re-engage at the new employer)
- NO CHANGE — Lusha confirms the CRM record is still current (no action needed)
- NO MATCH — Lusha cannot resolve the contact (re-research or archive)
6. Summarize at the top: total contacts scanned, total promoted, total moved, total no change, total no match.
</task>
<constraints>
- Use two detection paths. The signals layer is a time-series of discrete events; the contact record is the current state. Role changes show up faster in the contact record's jobStartDate than in the signals stream, so check both.
- A PROMOTED row carries the strongest re-engagement signal. Surface the job start date so the rep can time the message inside the first-90-days window.
- A MOVED row is two rows of work — update the CRM (old record is dead) and re-engage at the new employer.
- Do not invent fields. If both detection paths return nothing and the contact's current record matches the CRM, the row is NO CHANGE.
</constraints>Section 3: Monitoring for signals across the full book
Prompt 4: Run a weekly signal scan and post the alerts to Slack
Individual signal checks before a call are valuable. A weekly scan across the full book is how you make sure nothing falls through. In Financial Services, where the window on a leadership change or M&A event can close in 60 days, a signal that goes unnoticed for three weeks because it wasn’t on anyone’s radar that week is a missed opportunity that doesn’t come back.
This prompt runs a weekly scan across a list of target accounts using Lusha’s signals layer, identifies any account where a signal has been confirmed in the past 7 days, and posts a Slack alert with the verified contact details for the right person to reach out to and one specific first move. The alert format is designed to be acted on immediately — not read, filed, and forgotten.
<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>The pattern across all four prompts
Financial Services signals require two things that most signal workflows skip: verification and timing. A leadership change rumored on LinkedIn isn’t the same as a verified job start date in Lusha’s contact record. An M&A announcement from eight months ago isn’t the same as a deal that closed last week. Every prompt in this article uses Lusha to confirm the signal before acting on it, and flags the timing window so you know whether you’re inside it.
The other pattern is specificity. Financial Services buyers — CROs at banks, CFOs at asset managers, compliance leads at insurers — are approached by vendors constantly. Generic outreach referencing a “recent change at your company” reads as mass mail. What lands is a message that demonstrates you know exactly what changed, when it happened, and why it’s relevant to what you’re offering. The prompts in this article are built to return that specificity: not “there’s been leadership activity” but “a new Chief Risk Officer joined 34 days ago, she’s previously implemented [category] solutions at two prior firms, and the hiring data suggests she’s rebuilding the risk function before H2.”
The Lusha connector provides the verified contact and firmographic layer that makes all four prompts work — 300M+ verified contacts, compliant under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe. No guessed fields, no format assumptions. If Lusha can’t verify it, the prompt flags it rather than inventing it.
Where these prompts live
All four prompts are in the buying signals section of Lusha Plays.
