“I saw your company is growing” could be about anything. “I saw you’re building out your London office” could only be about one thing, and it tells the reader you actually looked at their specific situation instead of running a template against a list. A location-based hiring surge is one of the easiest signals to turn into a genuinely specific opener, and one of the most commonly wasted, because most outreach mentions the growth without naming where it’s happening. Connect Lusha to Claude and this prompt checks target accounts for a location-specific hiring surge, then drafts outreach that names the actual place, not just the fact of growth.
Localize outreach to a company’s regional expansion
The prompt
Here are my target accounts: [paste company names or domains].
Using the Lusha connector, check each one for a hiring surge by
location in the last 30 days. For each match, return the company
name, the specific location surging, and the surge percentage.
Then draft a two-line outreach opener for each one that names the
specific location directly - not "your company is growing," but the
actual city or region. Keep each opener under 30 words and end with a
question, not a pitch.What you'll get back
The situation: a rep pastes 15 target accounts and asks for location-specific openers wherever a regional surge is found.
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 use Lusha in Claude
Most reps already know that referencing a real signal beats a generic opener. What gets lost in practice is specificity within the signal itself — “your company is growing” and “your London office grew 40% this month” are built from the same underlying data, but only one of them proves the rep actually looked. This prompt forces that specificity by name, and keeps the draft under 30 words so it reads as a real note, not a templated paragraph with a location swapped in. Contact and company data is verified across multiple sources and handled under GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance.
FAQ
Why does the opener need to end in a question?
A question invites a reply without asking for anything yet. Naming the signal proves you looked; asking a real question about it is what actually starts a conversation instead of just displaying research.
What if a company has surges in multiple locations?
Ask Claude to draft a separate opener for each location, or pick the largest surge if you only want one per account. Either works — the prompt handles both if you specify.
How is this different from the general hiring-surge-by-location play?
That play finds the accounts and the surging location. This one takes that same signal a step further into a drafted, ready-to-send opener, rather than stopping at the finding.
Can I use this for existing customers expanding into a new office, not just prospects?
Yes — a customer opening a new regional office is often an expansion signal. The same localized-opener approach works for an expansion conversation, not just a first touch.
Is this compliant to run?
The prompt reads business hiring activity by location, the same information visible on a company’s own job postings. Lusha’s data is professionally sourced and opt-outs are honored automatically; no personal contact details are revealed until you choose to enrich a specific person.
Ready to run this?
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
