More Resources
Prompt

Time enterprise outreach around earnings reports

Tools: Claude ▪ Lusha

A newly funded startup and a public enterprise account don’t run on the same budget clock. The startup’s window opens with a funding round. The enterprise account’s window opens and closes with its own quarterly earnings cycle — a strong quarter often means new investment gets approved, a weak one often means a freeze until the next report. Reaching out with no awareness of which phase a target account is in means pitching into a freeze half the time. Connect Lusha to Claude and this prompt checks large target accounts for recent earnings activity and times outreach to the window it opens.

 

The prompt

Open in Claude Open in ChatGPT 
Here are my large or public target accounts: [paste company names or
domains].

Using the Lusha connector, check each one for financial events news in
the last 60 days, specifically earnings reports. Return a table with
company name, report date, and whether the report read positive,
neutral, or negative based on the coverage.

Then flag two groups:
(1) positive or neutral report - budget conversations are more likely
    open, reach out now
(2) negative report or no report found yet - hold outreach, budget is
    more likely frozen until the next cycle

Finish with the accounts in group one, ranked by how recent the report
was.

What you'll get back

The situation: an enterprise AE pastes 12 large public target accounts and asks for earnings-based timing.

The output:

Example output

Checked 12 accounts: 5 reported earnings in the last 60 days

Positive or neutral (3): [Company W] reported 9 days ago, revenue ahead of guidance — budget conversations likely open. Two more with the same read.

Negative or no report (2): [Company X] reported a miss 3 weeks ago — hold outreach until the next cycle.

Ranked group to reach out to now: [Company W] first, most recent positive report, two more behind it.

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

Public enterprise accounts are governed by a fiscal reporting cycle that private, funded companies simply don’t have. Every other funding-triggered play in this library reads a single event (a round closing) as the whole signal. This one reads the sentiment of the report too, not just its existence, since an earnings report on its own doesn’t say which direction the budget is about to move. Contact and company data is verified across multiple sources and handled under GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance.

 

FAQ

  • Those are built for privately funded companies where a round closing is the trigger. This is built for public or large enterprise accounts, where the equivalent trigger is a quarterly earnings report, not a funding event.

     

     

  • A weak quarter often means near-term budget caution, not a permanent close. Holding for one cycle and checking again after the next report is usually more effective than either pushing through a freeze or writing the account off entirely.

  • From the coverage and framing of the earnings report itself — beat or miss guidance, revenue direction, and how the report was covered. It’s a directional read, not a financial analysis.

     

     

  • Quarterly, timed to when your target accounts typically report. Running it more often won’t surface new information between report dates.

  • The prompt reads public financial reporting, the same information covered in any financial news outlet. 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.

Related Prompts

Ready to run this?

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

Start for free Read the Docs