When a target account announces a partnership, most outreach reads it as one signal about one company. It’s usually two. The account itself is worth the standard commercial-activity outreach. But the company they just partnered with is a second, separate opportunity — sometimes a better ICP fit than the original target, sometimes a channel worth building a relationship with directly. Connect Lusha to Claude and this prompt checks target accounts for new partnership announcements, then evaluates the partner named in each one as its own lead.
The prompt
Here are my target accounts: [paste company names or domains].
Using the Lusha connector, check each one for commercial activity news
in the last 60 days, specifically partnership and integration
announcements. For each one found, identify the partner company named
in the announcement, then check whether that partner company also
matches my ICP: [describe your ICP, e.g. B2B SaaS, 200 to 2,000
employees].
Return a table with the original target account, the partner named in
the announcement, and whether the partner matches my ICP.
Finish with the partner companies worth treating as their own lead,
and a one-line reason for each.
What you’ll get back
The situation: a rep pastes 15 target accounts and asks for partnership news, plus whether any named partner is worth pursuing directly.
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 account list to see live results.
Why it works
Commercial activity news names two companies, but most outreach only reads it as a signal about one. This prompt treats the partner as a lead in its own right, then checks it against your actual ICP instead of assuming every named partner is worth chasing — most won’t be. The result is a short, filtered list of real second-order opportunities, not a wide net of every company mentioned near a target account. Contact and company data is verified across multiple sources and handled under GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance.