An account scaling engineering by 30% this quarter isn’t evaluating the same thing an account scaling sales by 30% is. One needs infrastructure, the other needs a sales stack. Sending both the same nurture email is the marketing equivalent of pitching the company instead of the department. Connect Lusha to Claude and this prompt checks a target list for department-level hiring surges, then matches each one to the content asset built for that specific audience.
Serve department-specific content to accounts surging in that function
The prompt
Here are my target accounts: [paste company names or domains].
Using the Lusha connector, check each one for a department-level hiring
surge in the last 30 days. Return a table with company name, surging
department, and surge percentage.
Here is my content library, mapped by department: [list your assets,
e.g. "Engineering — infrastructure scaling guide", "Sales — enablement
checklist", "Product — roadmap planning template"].
Match each surging account to the right asset based on its surging
department. If no asset matches, flag it as a content gap instead of
forcing a mismatch.
Finish with a send-ready list: account, department, matched asset, and
a one-line reason the match fits.
What you'll get back
The situation: a marketer pastes 20 target accounts and a content library of five department-mapped assets, and asks for matches.
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.
What to do next
Lusha’s department-level hiring surge signal already tells you which function is scaling, not just that the company is. This prompt adds the second half: matching that specific department to the content built for it, and being honest when nothing matches instead of quietly sending the closest thing. A content gap surfaced is more useful than a mismatch sent — it tells marketing exactly which department-specific asset to build next, based on real demand, not a guess. Contact and company data is verified across multiple sources and handled under GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance.
FAQ
List whatever categories you actually have, even if they’re by use case or persona rather than department. The prompt matches on whatever structure you give it — the department-mapped example is just the most common version.
They’re flagged, not forced into a weak match. That gap list is itself useful — it tells you which department-specific asset is worth building next, based on real accounts asking for it right now, not a guess.
Yes — a department surging at an existing customer is often an expansion signal, not just a content-fit question. The same match logic works for a customer marketing or expansion motion.
That play finds the accounts and the surging department. This one takes that list a step further, matching each surging department to a specific content asset instead of stopping at “here’s who’s hiring.”
The prompt reads business hiring activity, 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.
