Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
This Claude prompt builds a one-screen cold call brief before you dial — verified direct number, the one signal worth leading with, and an opening line specific to this person and this moment. Lusha validates the contact, pulls the direct number, and scans for account signals. Takes under 2 minutes to run.
<context>
I'm about to make a cold call. I have a name, a company, and a LinkedIn profile. I want to validate the contact, get their direct number, and build a one-screen call brief: opening line, likely objection, and the one signal worth leading with.
My prospect:
- Name and title: [NAME, TITLE]
- Company: [COMPANY NAME]
- LinkedIn URL (optional): [URL OR "SEARCH BY NAME AND COMPANY"]
- What I sell: [PRODUCT / SOLUTION]
- Why I'm calling today specifically: [SIGNAL OR "FIND ONE FROM LUSHA"]
</context>
<task>
1. Use Lusha to validate the contact:
- Confirm their current title and that they're still at the company
- Pull their verified direct phone number. Mobile preferred over switchboard.
- Pull verified work email as a fallback if the call goes to voicemail
- Note their tenure in the current role
2. Use Lusha's signals layer to find the strongest reason to call this company today:
- Recent exec hire in the relevant function
- Headcount growth in the team we sell into
- Funding event in the last 90 days
- M&A activity
- If no signals found, flag it. Don't invent a reason.
3. Build a one-screen call brief:
CONTACT
- Verified name, title, direct number, email fallback
- Tenure in role (shapes how you open)
SIGNAL
- The one thing happening at this company right now that makes this call timely
- If no signal: flag as "no live signal: call based on ICP fit only"
OPENING LINE
- Under 20 words
- References the signal or their role directly
- Not "How are you?" not "Did I catch you at a bad time?" not "I'll be quick"
- Gets to the point in the first sentence
EXPECTED FIRST OBJECTION
- The most likely pushback from someone in this role at this company
- One sentence on how to handle it without going defensive
GOAL FOR THIS CALL
- Not a close. The one specific thing to walk away with (a meeting, a referral to the right person, a confirmed pain point).
4. If the contact can't be validated or the direct number isn't available:
- Return what Lusha has and flag the gap
- Suggest the next best action (try the main line and ask for them, reach out on LinkedIn first, find a warm intro path)
</task>
<constraints>
- The opening line must be under 20 words and must be specific to this person or this signal. A line that could be used on any call is not acceptable output.
- Don't invent signals. If Lusha returns nothing, say so. A call based on ICP fit is still worth making, just framed differently.
- The brief is one screen. I'm reading this before I dial, not during.
- If the direct number isn't available, say so clearly. Don't return a switchboard number without flagging it.
</constraints>The situation: An SDR is working through the Tier 1 list from Play 09. Next up: Sofia R., VP of Sales at Waverly Digital, 22 days into the role. He’s about to dial and has 3 minutes to prep.
Output: Verified direct mobile, one signal, an opening line he can actually use, and the one objection he’ll almost certainly hit.
CONTACT
SIGNAL
Waverly Digital has posted 8 new sales roles in the last 30 days — SDR, AE, and Sales Ops. That’s a 35% headcount expansion underway. A new VP of Sales inheriting a scaling team almost always means the data and tooling stack is being evaluated alongside the hiring plan.
OPENING LINE
“Sofia — saw you joined Waverly three weeks ago and you’re already scaling the team. Curious what the data setup looks like.”
18 words. Specific to her tenure and the hiring signal.
EXPECTED FIRST OBJECTION
“I’m still getting settled — not looking at new tools right now.”
How to handle: “Totally makes sense — I’m not pitching anything. Most new VPs I talk to find the data layer is the first thing that surfaces as a gap when you’re ramping reps. Happy to show you what the team is currently working with in 10 minutes.”
Reframe from “new tool” to “understanding what you inherited.” Takes the pressure off without backing down.
GOAL FOR THIS CALL
A 15-minute screen share in the next two weeks where she can see the current team’s data setup. Not a demo, not a proposal — just visibility. That’s the only ask.
Contact and signals validated via Lusha connector, May 21. Direct number and email masked for privacy.
Cold call prep usually means 10 minutes on LinkedIn hoping to find something to mention. Lusha in Claude does the same job in 90 seconds and adds what LinkedIn can’t give you: a verified direct mobile, a signal from the account you can actually lead with, and a specific opening line built from both. The objection handling isn’t generic sales advice — it’s written for this role at this company at this stage. That’s the prep that changes how a cold call starts.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
The prompt flags it clearly and suggests the next best action — main line and ask for them by name, LinkedIn message first, or find a warm intro path via a mutual connection. A switchboard number is never returned without a flag.
The brief returns “no live signal — call based on ICP fit only” and adjusts the opening line accordingly. A call without a signal is still worth making if the ICP fit is strong — it just needs a different frame: lead with what you’ve seen at companies their size and stage rather than something specific happening at theirs.
Yes — that’s what it’s built for. 90 seconds per contact before you dial. Run it from the prospect list built in Play 09 and you go into every Tier 1 call with a validated number, a signal, and a specific opening line.
The cold sequence play is for written outreach — email and LinkedIn. This play is for a live call. The output is different: a call brief with a spoken opening line and an objection handler, not a sequence of written messages. Use both together — sequence first, call brief when you dial.
Yes. Someone 3 weeks into a new role is in listening mode — they’re open to input they’d reject later. Someone 6 months in has already made early decisions and the frame shifts to “here’s what you might have missed.” The opening line in this play reflects which situation you’re in.
Put “search by name and company” in that field. Lusha searches by name and company domain — the LinkedIn URL is a helpful input but not required.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
