A company signal tells you an account is worth watching. A contact signal tells you who to actually call. Most prompts stop at the first layer — company scaling, sure, but scaling companies are run by dozens of people, and only a few of them are worth reaching out to first. Connect Lusha to Claude and this prompt checks your target list for companies showing funding and a hiring surge, then runs a second, separate check inside each match for anyone recently promoted or hired into a VP-level role — the person with a fresh mandate and nothing decided yet.
The prompt
Here are my target accounts: [paste company names or domains, up to 25].
Step 1: using the Lusha connector, check each company for a funding
event and a hiring surge in the last 90 days. Return a table of which
companies show both.
Step 2: for each company that matches, search for contacts at that
company in a VP-level or above role who were promoted or changed
companies in the last 90 days. Return their name, title, and what
changed.
Finish with a ranked list: company, the specific VP found, and a
one-line reason to reach out to that person specifically.
What you’ll get back
The situation: an AE pastes 20 accounts from a growth-stage territory and wants both the company signal and the actual person to contact.
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
Company signals and contact signals live at different levels in Lusha’s data, and that’s a feature here, not friction. The company check confirms the account is actually scaling — funding plus a hiring surge, not just one loosely-related event. The contact check runs separately, scoped to just the companies that passed step one, and looks for the specific person whose role changed in the same window. That two-step structure is what makes the output a name and a reason instead of just an account on a list. Contact and company data is verified across multiple sources and handled under GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance.
FAQ
Why run this as two steps instead of one combined filter?
Company signals and contact signals are different data layers — a company doesn’t “have” a VP promotion, a person does. Checking them separately and joining the results is both more accurate and the only way to actually get a named contact out the other end, not just a qualified account.
What if a company matches step one but nobody matches step two?
That’s expected, and the output says so — the account is still worth watching, it just doesn’t have a specific new-authority contact to lead with yet. Reach out to whoever owns that account through your normal contact, or hold it for the next run.
How many accounts can I check at once?
Up to 25 per run through the connector. The two-step structure means larger lists take longer to process — for bigger territories, run it in batches of 25.
Can I use this for a different seniority level, not just VP?
Yes — swap “VP-level or above” for any seniority tier the connector supports. Director-level works the same way for a broader, less senior-focused version of the same check.
Is this the same as the funding-plus-surge-plus-executive-hire prompt?
Related but different. That prompt checks all three as company-level signals and doesn’t confirm a specific named contact. This one is built to end in a person, not just a flagged account — use this one when the next step is picking up the phone.
