Prompt

Find accounts increasing IT spend and work them first

Tools: ClaudeLusha

Outputs on this page come from a live run on September 9, 2026. Company names are masked to initials. No contacts were previewed or revealed.


An IT spend increase signal is one of 24 company signals available through the Lusha connector for Claude, and the one that answers the question every outbound team asks before a sequence goes out: does this account have money to spend right now. The prompt below runs the check as a batch, keeps the accounts with no signal in view, and ranks by consistency rather than size.

The prompt

Check my target account list for IT spend increases and rank who to work first.

Before anything else, run account_usage and tell me my remaining credits. Do not run any signal call if fewer than 50 credits remain; stop and tell me.

Here is my list (domain, one per line):
[PASTE UP TO 25 DOMAINS]

Customer domains (or write "none"):
[PASTE]

Steps:
1. Run signals_companies_search on the list with signalTypes ["itSpendIncrease"], startDate 90 days ago, maxResultsPerSignal 3. Batch in groups of 25 if the list is longer.
2. For every account that returned an IT spend increase, pull the size of the increase and the reading date. Keep accounts with no signal in the output as "no signal" so I see the full list, not only the hits.
3. Rank the hits: accounts with an increase on two consecutive monthly readings first, then single readings by size. Flag any single reading above 100% as VERIFY rather than ranking it at the top; a jump that size in one month is usually a data refresh, not a budget decision. Tag customers as EXPANSION and everyone else as NEW LOGO.
4. For the top 5 NEW LOGO accounts, write one opening line for outreach that references growing technology investment without quoting a number I cannot verify externally.

Output: one table with columns Account | IT spend signal | Reading dates | Segment | Opening line. Then two lines: what the ranking is based on, and credits used. Do not preview or reveal any contacts in this run.

What you'll get back

The situation. A target list of 25 B2B software companies, 400 to 20,000 employees. All ICP on paper. No idea which one is in a buying window.

The run. account_usage first, at zero credits: 454,038 credits on the account, signal reads priced at 1 credit per event. Then one batch call on all 25 domains for itSpendIncrease with a 90 day window. 14 of 25 accounts fired, 17 signal events, 17 credits.

What came back.

AccountIT spend signalReading datesSegmentOpening line
D.D. (observability, ~6,000 emp)+12% then +34%Jul 8, Aug 8NEW LOGOTwo months of rising tech spend in a row. That is a plan, not a blip. Worth ten minutes on what the new budget is for.
K.L. (marketing platform, ~2,000 emp)+20% then +7%Jul 8, Aug 8NEW LOGOYour technology line has grown two readings running. When budgets grow, data quality is usually the first thing that breaks.
H.S. (CRM, ~8,000 emp)+82%Aug 8NEW LOGOBig move in tech investment this quarter. Happy to share what teams at that stage fix first.
G.O. (revenue intelligence, ~1,500 emp)+70%Aug 8NEW LOGOYou are investing in the stack. Verified contact data is the cheapest line that makes the rest of it work.
A.M. (product analytics, ~800 emp)+66%Aug 8NEW LOGOBudget is moving. The question is what is still manual on the GTM side.
Z.D. (support software)+40%Aug 8NEW LOGO
S.N. (enterprise workflow)+11%Aug 8NEW LOGO
S.F. (data cloud)+7%Aug 8NEW LOGO
T.W., O.K., A.S., S.P., D.S.+227% to +264%Aug 8VERIFYHeld out of ranking. Five readings above 200% in one month on budgets of $170M to $1.25B read as a data refresh until confirmed.
11 accountsno signal

 

Ranking based on consistency across monthly readings first, then size. Credits used: 17. Confirmed live via Lusha connector, September 9, 2026. Company names masked to initials.

What happens next. This play ends at a ranked list of accounts. To find the budget owner at each one and check whether a verified email and direct dial exist before spending a reveal credit, hand the top five to the decision maker play below. Keeping the two steps separate is deliberate: it keeps this run at signal cost only, and it lets you decide who is worth a reveal after you have seen the ranking.

Why use Lusha in Claude

Most signal tools tell you a company is researching a topic. An IT spend increase is a different kind of evidence: a measured change in a budget line, with a date. Inside Claude, the Lusha connector runs the check as a batch, keeps the “no signal” rows so you see the whole list rather than only the winners, and separates customers from prospects so the same signal routes to a CSM or an AE. The run costs signal credits only; no contact is previewed or revealed until you decide the account is worth it. Every signal is sourced under Lusha’s data methodology and compliance framework.

FAQ

What counts as an IT spend increase?

A rise in the company’s estimated technology budget allocation compared with the prior reading. The signal carries a size, a date, and the budget range it was measured against. It does not break down which categories grew.

How far back does the signal go?

The prompt asks for 90 days, which returns up to three monthly readings. You can set startDate to any date in the last six months. Older than that returns nothing.

Why rank by consistency instead of size?

Because in the live run the five largest increases were the five least believable. Two consecutive readings in the same direction is harder to fake with a data refresh than one large jump. Size still breaks ties among single readings.

Why keep the accounts with no signal in the table?

Because “no signal” is information. If 11 of 25 target accounts show nothing, the list itself is the question, not the reps working it.

Does this spend credits?

Signal reads cost 1 credit per event returned. In the live run, 25 domains cost 17 credits. The prompt runs account_usage first at zero credits and stops under 50, so you never start a batch you cannot finish. No contact preview or reveal runs in this play.

Can I run this without a list?

Yes. Replace step 1 with prospecting_company_search using your ICP filters plus the itSpendIncrease signal. Validate filter values with prospecting_company_filters first; unrecognized values return empty results without an error.

Ready to run this?

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