Prospecting lists grow. They almost never shrink on their own. An account added six months ago because it showed growth or funding can still be sitting on a rep’s list today, long after that signal reversed — because nobody checks a list for the absence of momentum, only its presence. Connect Lusha to Claude and this prompt checks every account on a list for any decline signal, and returns a shorter, cleaner list of who’s actually still worth working.
Clean up prospecting lists using decline signals
The prompt
Here is my current prospecting list: [paste company names or domains].
Using the Lusha connector, check each account for any decline signal
in the last 90 days: headcount decrease, IT spend decrease, or website
traffic decrease. Return a table with company name, which decline
signal fired, and the date.
Then sort into two groups:
(1) no decline signal found - keep working
(2) one or more decline signals found - deprioritize or remove
Finish with the cleaned-up list of accounts still worth a rep's time,
and a separate short list of removed accounts with the reason each
was cut.What you'll get back
The situation: a rep pastes a 40-account prospecting list built up over the last two quarters and asks for a decline check before the next sprint.
The output:
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 data and connectors to see live results.
Why use Lusha in Claude
A prospecting list is usually built once, off a positive signal, and never re-checked. This prompt runs the check that normally never happens: not “who’s showing growth,” but “who’s stopped.” Three decline signal types run in a single pass, so an account doesn’t need to show every kind of pullback to get flagged, one is enough. The output is deliberately two lists, not one filtered list, so nothing gets silently dropped without a reason attached. Contact and company data is verified across multiple sources and handled under GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance.
FAQ
Not necessarily — that’s a judgment call, not a rule. Some teams remove on any single signal, others wait for two. The prompt sorts accounts into “flagged” and “clean,” the decision to deprioritize versus fully remove is yours to apply.
This runs all three decline types at once, so an account pulling back on IT spend but not headcount still gets caught. A single-signal check misses that.
Monthly is a reasonable cadence for a working list. Run it more often on a smaller, higher-priority list where stale accounts cost more in wasted rep time.
That’s fine — the prompt flags, it doesn’t decide for you. An account with strategic value or an existing relationship might stay on the list despite a decline signal; the flag just makes that a deliberate choice instead of an oversight.
The prompt reads business-level signals — headcount, spend, and traffic trend — the same category of public business information covered elsewhere in Lusha’s signal set. Lusha’s data is professionally sourced and opt-outs are honored automatically.
Ready to run this?
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
