TLDR: In SaaS, timing is the variable that separates pipeline from noise. These five Claude prompts — all built on Lusha’s signals layer — tell you which accounts are in an active buying window right now, when a champion move is worth acting on, which closed-lost accounts have a real re-entry trigger, and which customers are 90 days from a churn conversation. All five run in Claude with the Lusha connector.
SaaS sales runs on timing. A Series B company in month two of a new CRO’s tenure is a completely different conversation than the same company six months later, after the stack has been decided. A closed-lost account where the original champion just landed at a new ICP-fit company is the warmest call in the pipeline. A customer whose champion just departed is a renewal at risk — not a renewal in progress.
The buying signal is the information that tells you which moment you’re in. Without it, every account looks the same. With it, the P1 accounts separate themselves from the noise every Monday morning.
These five prompts are built for SaaS AEs, CSMs, and RevOps teams running signal-driven territory management. They cover the full signal lifecycle: stacked buying signals on active accounts, weekly prioritization against live inputs, champion movement on both sides of the deal, closed-lost re-entry, and early-warning churn detection. All five run in Claude with the Lusha connector.
Connect Lusha to Claude in two minutes →
Timing and prioritization (Prompts 1–2)
In SaaS, the window between a buying signal firing and a competitor acting is measured in days. A funding round at a target account, a new CRO hire, a sales headcount surge — each one opens a conversation that closes on its own schedule. These two prompts tell you which accounts are in that window right now, and exactly what to do about each one this week.
Prompt 1 — Find accounts with stacked buying signals
One signal is interesting. Three signals on the same account in the same 90-day window is a buying intent pattern. In SaaS, where funding rounds unlock tool budgets, new CROs rebuild GTM stacks, and hiring surges signal a team coming online that needs your product — the accounts firing multiple signal types simultaneously are the ones most likely in an active evaluation right now. This prompt scans an account list, counts distinct signal types per account, and returns a TIER 1–4 ranked list with the rep’s specific call priority for the week.
<context>
I want to find the accounts in my list with the highest concentration of buying signals — multiple signal types firing in the same window. These are the accounts most likely in an active buying cycle right now.
</context>
<task>
1. Take this account list (one per line, domain or name):
[PASTE ACCOUNT LIST]
2. For each account, use Lusha's signals layer to retrieve activity in the last [WINDOW, e.g. 90 days]:
- Financial events (funding rounds, IPO, M&A, strategic investments)
- Leadership events (executive hires, promotions, departures)
- Hiring surges by department
- Product launches and partnerships
- Headcount growth (1m, 3m, 6m, 12m)
- Web traffic shifts
3. Count distinct signal types per account. A stacked-signal account has 3+ different signal types firing in the window.
4. Output a ranked table sorted by signal density (high to low):
Account | Signal types fired | Detailed signals | Stack score | Recommended priority
5. Assign a stack score:
- TIER 1 — 4+ distinct signal types in the window (drop-everything outreach)
- TIER 2 — 3 distinct signal types in the window (call this week)
- TIER 3 — 2 distinct signal types in the window (monitor and reach out next week)
- SINGLE — 1 signal type only (worth tracking, not stacking)
- QUIET — no signals in the window
</task>
<constraints>
- Stack density is the metric, not absolute signal count. An account with 20 product launches is one signal type. An account with one hiring surge plus one leadership change plus one acquisition is three signal types — a higher stack score.
- Surface the actual signals per row so the rep can read the pattern, not just trust the rank.
- Multiple instances of the same signal type (e.g., three hiring surges over three weeks) count as one signal type. Persistence within a type strengthens that one signal, but stack score measures cross-type breadth.
- Do not invent signal types or events. Surface only what Lusha returns.
</constraints>Prompt 2 — Prioritize your accounts for the week
Most SaaS reps start Monday working accounts in whatever order comes to mind. This prompt scores every account against three live inputs — Lusha buying signals, open Gmail threads, and upcoming Google Calendar meetings — and returns a P1–P4 ranked list with one specific action per account. The P1 classification requires both a live signal and an open thread or upcoming meeting: signal creates the urgency, context creates the angle. Run it Monday morning. Work through the list in order.
<context>
It's the start of the week and I want to know which accounts to prioritize — not by gut feel or alphabetical order, but based on what's happening at each account right now, what's sitting open in my email threads, and what's coming up in my calendar.
My accounts:
- Account list: [PASTE COMPANY NAMES AND PRIMARY CONTACTS — one per line]
- What I sell: [PRODUCT / SOLUTION]
- Current pipeline stage for each: [PASTE DEAL STAGE OR "VARIES"]
</context>
<task>
1. For each account, use Lusha to check for buying signals in the last 14 days:
- New exec hire in the relevant function?
- Funding event?
- Headcount surge?
- Any structural change that creates urgency?
2. Search Gmail for thread status per account:
- Is there an unanswered outbound email sitting open?
- Did the contact reply recently but I haven't responded?
- Is there an open commitment I made that hasn't been followed through?
3. Check Google Calendar for upcoming meetings with each account:
- Is there a call in the next 7 days?
- Is there a meeting that needs prep?
4. Score and rank each account for this week:
- P1 — ACT TODAY: live signal + unanswered thread or meeting this week
- P2 — REACH OUT THIS WEEK: live signal, no open thread
- P3 — FOLLOW UP: open thread with no reply, no signal
- P4 — MONITOR: no signal, no open thread, no meeting — nothing urgent this week
5. Return a weekly account priority list:
- Accounts ranked P1 → P4
- For each account: signal (if any), thread status, next meeting (if any), recommended action
- One specific action per account — not "follow up" but what exactly to do
- Total: X accounts need action this week, X can wait
</task>
<constraints>
- P1 requires both a signal AND an open thread or upcoming meeting. Don't over-assign P1.
- One specific action per account — not generic advice.
- P4 accounts get one line maximum — don't pad the output.
- If an account has a meeting this week but no signal and no open thread: P3, not P2.
</constraints>Champion movement and re-entry (Prompts 3–4)
Champion movement is the highest-frequency signal event in SaaS. The industry has shorter average tenure than any other B2B vertical. A past champion moving to a new company is the warmest possible opening — verified relationship equity at an account you’ve never sold. A closed-lost account where the decision-maker has been replaced is a deal the rep can re-open with a completely different framing. These two prompts handle both directions.
Prompt 3 — Write the outreach when a contact changes jobs
A job change notification opens a window of roughly 30 days — after that, the person is settled and the “congrats on the new role” frame starts to feel dated. This prompt fires inside that window: Lusha validates where the contact actually landed, checks whether the new company fits your ICP, and writes the outreach for the specific relationship type — past customer, warm prospect, or cold. A generic congratulations note is not acceptable output; the message references something real about the prior relationship or the new company’s signal profile.
<context>
Someone I know from a past deal, customer relationship, or outbound sequence just changed jobs. I want to reach out while the move is fresh — but I need to check where they landed first, whether the new company is a fit, and write an outreach message that references the relationship without making it awkward.
The person:
- Name: [NAME]
- Old company and title: [OLD COMPANY, OLD TITLE]
- New company (if known): [NEW COMPANY — or "find it from Lusha"]
- My relationship with them: [PAST CUSTOMER / WARM PROSPECT / NEVER CLOSED / FORMER CHAMPION / MET AT EVENT]
- What I sell: [PRODUCT / SOLUTION]
- Last interaction (if any): [DATE AND CONTEXT — or "none"]
</context>
<task>
1. Use Lusha to find and validate where they landed:
- Confirm their new company and current title
- Pull verified work email and direct phone at the new company
- Note how long they've been in the new role
2. Use Lusha to check whether the new company is a fit:
- Company size, industry, geography
- Headcount in the function relevant to what I sell
- Any signals at the new company: funding, exec hiring, headcount growth
- Quick ICP read: is this worth pursuing, or is the new company outside our target?
3. Check whether the new company is already a customer or an active prospect:
- If joining an existing customer: relationship expansion, not new business
- If joining an active prospect: may accelerate or change the deal dynamic
- If neither: new outbound opportunity with a warm contact
4. Based on the situation, write one outreach message:
PAST CUSTOMER or FORMER CHAMPION joining a new company:
- Reference the past relationship directly — don't pretend it didn't happen
- One specific thing from the previous relationship relevant at the new company
- Under 80 words
- Ask if it makes sense to reconnect, not pitch immediately
WARM PROSPECT who never closed:
- Acknowledge the move
- One sentence on why the new company makes the conversation more relevant (or less)
- Under 80 words
- If the new company is outside ICP: say so and close the loop gracefully
COLD — met once or no meaningful relationship:
- Don't overclaim the relationship
- Lead with the new company signal, not the prior connection
- Under 60 words
5. Return:
- Validated new contact details
- ICP fit read on the new company
- Situation type (existing customer / active prospect / new opportunity)
- The outreach message, ready to send
- One flag: anything about the move worth knowing before you reach out
</task>
<constraints>
- Validate the new role via Lusha before writing anything. Don't assume the LinkedIn notification is current.
- The message must reference something real — the prior relationship, a specific signal, or the new company context. A generic "congrats on the new role" is not acceptable output.
- If the new company is outside ICP, say so — don't write outreach for a company that isn't a fit.
- Under 80 words for warm contacts, under 60 for cold. Count them.
</constraints>Prompt 4 — Surface buying signals on closed-lost accounts
The closed-lost list is the most under-mined pipeline asset in SaaS. The rep already had a buying conversation. The objection is documented. The buying group is known. The only missing piece is the trigger that changes the buying context enough to make the second conversation worth having. A new CRO is the strongest reset signal — they arrive with no allegiance to predecessor vendor decisions. A fresh funding round closes a budget objection specifically. A product launch resets a stack-fit objection. This prompt scans the closed-lost list for those triggers, ranks the ones worth acting on, and parks the ones where nothing has changed for the next monthly scan.
<context>
I have a list of closed-lost accounts from the last [WINDOW, e.g. 12-18 months].
I want to find the subset where a real re-engagement trigger has fired since the deal closed — events that change the buying context enough to warrant a fresh conversation.
For each closed-lost account, I'll provide:
- Account name or domain
- Close-lost date
- Primary objection or loss reason
</context>
<task>
1. Take this closed-lost list (one row per account, with close date and loss reason):
[PASTE LIST]
2. For each account, use Lusha's signals layer to scan for re-engagement triggers fired AFTER the close-lost date:
- New leadership in the buying group function (CRO, CTO, CMO, COO, CSO — anyone above the prior contact's manager)
- Funding events (round, IPO, M&A — anything that resets budget conversations)
- Strategic investments (signals direction of spend)
- Major product launches (new category entry, platform repositioning)
- Hiring surges in the function the rep originally sold into
3. For each triggered account, output:
- Account name and close-lost date
- Original loss reason
- Trigger event(s) and date
- Re-engagement angle — a one-sentence reframe tying the trigger back to the original objection
- Recommended outreach contact (new leader if leadership changed; original contact if no leadership change)
4. Park accounts where no trigger has fired since the close-lost date. List them at the bottom for the next monthly scan.
5. Rank the triggered accounts: leadership changes first (highest signal), then funding events, then product launches, then hiring surges.
</task>
<constraints>
- A trigger must have fired AFTER the close-lost date. Events from before the deal was lost don't count — the buyer already knew about them.
- New leadership in the buying group is the strongest single trigger. A new CRO at an account lost on sales-team objections is a near-mandatory re-engagement.
- Do not invent loss reasons or fabricate signal events.
- Park accounts with no trigger fired. They go to next month's scan. Do not force outreach.
</constraints>Protecting existing revenue (Prompt 5)
In SaaS, NRR is the number that determines whether the business compounds. The signals that predict churn are visible 60–90 days before the renewal call — but they hide in places CSMs don’t monitor without a structured scan. This prompt runs that scan monthly, surfaces the accounts at risk before the renewal window closes, and flags the specific play required for each one.
Prompt 5 — Flag renewal risk on existing customers
A customer whose original champion just departed is a renewal-at-risk by structural definition — the new buyer inherits the budget line but not the conviction behind it. A customer being acquired is under a 12-month vendor review clock. A customer in active layoffs is in cost-discipline mode on every line item. This prompt scans the customer book for those deterioration signals, ranks accounts by risk severity, and flags the most important finding: accounts where both expansion signals and risk signals are firing simultaneously — the moment the executive sponsor decides.
<context>
I'm a CSM, CS leader, or AM. I want to scan my customer book for the events that precede churn — leadership departures, layoffs, M&A as the acquired party, lawsuits, security incidents — so I have 60-90 days of warning instead of 30.
For each customer, I'll provide:
- Account name or domain
- Renewal date (or quarter)
- Original buyer / champion (name and role)
</context>
<task>
1. Take this customer book (one row per customer, with renewal date and original champion):
[PASTE LIST]
2. For each customer, use Lusha's signals layer to scan the last 90 days for renewal-risk triggers:
- Executive departures (especially the original champion or their manager)
- Headcount decreases (layoffs, restructuring)
- M&A as the acquired party (acquirers consolidate stacks)
- Lawsuits filed against the company (financial / governance risk)
- Security incidents (operational distraction, vendor scrutiny increases)
- Sustained hiring freeze in the function we serve (budget contracting)
- C-suite turnover beyond a single role (broader instability)
3. For each customer, return:
- Customer name and renewal date
- Original champion status (still in role, departed, manager changed)
- Risk triggers fired
- Trigger dates
- Risk angle — one sentence on what this means for the renewal
- Recommended save play (executive sponsor escalation, value reinforcement, contract restructure)
4. Rank customers by risk severity:
- HIGH — original champion departed OR 2+ risk triggers fired in the window
- MEDIUM — 1 risk trigger fired that doesn't involve the original champion
- LOW — minor risk signal (single security issue, isolated departure outside buying group)
- STABLE — no risk signals in window
5. Surface any customer where BOTH expansion AND risk triggers have fired. These are the highest-priority CSM conversations — opportunity and risk firing simultaneously is the moment the executive sponsor decides.
</task>
<constraints>
- The original champion departing is the single strongest risk trigger. A new buyer in their seat means re-selling the value of the product from week one.
- M&A as the acquired party is the second strongest. Acquirers typically review every vendor contract in the first 12 months post-close.
- Do not invent risk events. Surface only what Lusha returns.
- A customer with no triggers is STABLE — that's data, not absence of data.
- When expansion signals (from the customer expansion prompt) and risk signals fire on the same account, surface both. Mixed-state accounts are the highest-priority CSM conversations.
</constraints>The pattern across all prompts
Every prompt on this list is built around the same principle: the signal tells you when, not just who. SaaS territories are large enough that touching every account every week is impossible — and doing it anyway produces noise, not pipeline. The prompts here replace the guesswork with a structured answer: which accounts are in an active buying window, which job moves are worth acting on, which closed-lost deals have a real re-entry trigger, and which customers are heading toward a churn conversation before you know it. Lusha surfaces the signals. Claude ranks them and writes the action. The output is always a specific next step, not a data dump.
Where these prompts live
All five run in Claude with the Lusha connector.
