AI prompt

Build a LinkedIn ad audience from companies with a buying signal this month

Tools: Claude ▪ Lusha

Company names in the live example are masked to initials and domains are hidden. This play works at company level only and returns no personal data.

A LinkedIn ad audience built from a static list keeps paying to reach companies that stopped growing months ago. This prompt builds the audience from companies that showed a dated buying signal this month, such as funding news, a new executive or a hiring surge, using the Lusha connector for Claude.

You get a clean upload CSV for LinkedIn Campaign Manager, a working table with the signal behind every company, and a date to rebuild it. Lusha does not push audiences to LinkedIn, so the last step is a manual upload, and the page says so up front.

The prompt

<context>
I'm building a LinkedIn company audience for: [campaign name and goal].
My ICP: [industry, company size, country].
Signals that mean "worth an ad now" for us: [for example funding news, a new executive, a hiring surge], in the last [30] days.
Exclude: [current customers, open opportunities and competitors, as domains or a CSV].
</context>

<task>
1. Credits. Run account_usage, which is free, and estimate the cost per page of results before searching.
2. Search. Find companies in Lusha that match my ICP and have at least one of those signals in the window. Pull [number] companies.
3. Clean. Drop companies whose industry doesn't match my ICP, anything on my exclude list, and duplicates. List every company you dropped and why.
4. Rank. Put companies with two or more signal types first, then companies with one.
5. Build two outputs:
   - An upload CSV for LinkedIn Campaign Manager with the columns companyname, companywebsite and linkedincompanypageurl, nothing else.
   - A working table with the same companies plus the signals each one showed and the signal window, for reporting.
</task>

<output>
- A summary: companies found, companies dropped by reason, companies in the final audience
- The upload CSV
- The working table
- The date to rebuild the audience, 30 days from today
- The credits the run used
</output>

<constraints>
- Company level only. Do not search for or reveal any contacts.
- Do not upload anything. I'll upload the CSV myself.
</constraints>

What you'll get back

The situation

We ran the prompt on October 25, 2026 for an example seller of sales software. ICP: US software companies with 201 to 1,000 employees. Signals: financial news, executive news or a hiring surge between September 25 and October 25, 2026.

Summary: 25 pulled, 7 dropped, 18 in the audience

StepCompanies
Matched the ICP and had a signal in the window2,033 in Lusha
Pulled for this run25
Dropped: industry outside the ICP (healthcare, finance, education, business services)6
Dropped: a direct competitor of the example seller1
In the final audience18

The industry filter let through six companies outside software, so the clean step is not optional. One company on the list was a direct competitor of the example seller, which is why the exclude list belongs in the prompt and not in a later review.

Signal mix: why the order counts

Signals per companyCompanies in the 25Rank in the audience
Three signal types: hiring surge, executive news and financial news6First
Two signal types14Second
One signal type: a hiring surge only5Third

Every company in the pull had a hiring surge. The ones with executive or financial news on top of it go to the front of the audience, so a limited budget reaches them first.

The upload CSV (first five rows)

companynamecompanywebsitelinkedincompanypageurl
J.[company].comlinkedin.com/company/[company]
M.[company].comlinkedin.com/company/[company]
C.[company].ailinkedin.com/company/[company]
I.[company].comlinkedin.com/company/[company]
F.[company].comlinkedin.com/company/[company]

The working table carries the same companies with the signals each one showed and the window, for reporting after the campaign runs. Download LinkedIn’s current company list template in Campaign Manager before the first upload and match the column headers to it.

Credits the run used

52 credits for 25 companies, about 2 per company, including the signal filter. The credit check at the start is free. At that rate, a 300-company audience costs roughly 600 credits.

Companies confirmed live via Lusha connector, October 25, 2026. The seller in this example is illustrative. The companies, signals, counts and credits are from the live run.

Why it works

Ad audiences go stale the same way contact lists do, only more quietly: nobody bounces, the budget just reaches companies that are no longer moving. Building the audience from dated signals keeps it tied to something that happened this month, and the 30-day rebuild date keeps it that way. Lusha returns each company’s LinkedIn page URL alongside its name and website, which gives Campaign Manager a direct match key. The prompt stays at company level, so no personal data goes into the ad platform. More on what a signal can and can’t tell you: five checks before you trust a buying signal. Data practices: data sources and the Trust Center.

FAQ

Does Lusha upload the audience to LinkedIn for me?

No. Lusha builds the CSV and you upload it as a company list in Campaign Manager. There is no direct sync between Lusha and LinkedIn Ads today.

How big should the audience be?

LinkedIn sets a minimum matched audience size before a campaign can run, and Campaign Manager shows the match count after upload. Our search matched 2,033 companies before cleanup, so pull enough pages to clear that minimum after the drops.

How often should I rebuild it?

Every 30 days. A signal from last quarter is a reason to call last quarter. The prompt gives you the rebuild date with every run.

Can I build a contact audience instead?

This play builds company lists only, so no personal data reaches the ad platform. To reach specific people at these companies, use an outbound play instead.

What does it cost?

About 2 credits per company in our run, including the signal filter. The credit check is free. Current plans: lusha.com/pricing.

Related prompts

Browse every play in the Campus library →

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.