The 12 best Claude prompts for sales — verified prospecting, pipeline acceleration, and deal closing. Copy, paste, run. Connect Lusha for verified data.
The 12 prompts below are the ones a working B2B sales rep actually runs in 2026 — not the 12 most clickable, the 12 most useful. Each one is built to run inside Claude with the Lusha connector enabled, which means the contacts, signals, and account data come back verified — A+ email confidence grades, mobile direct dials, time-stamped funding and leadership events, named buying groups — rather than generated by the model.
Organized by deal stage so you can find what you need fast. Copy the green/black block, paste it into Claude, replace the bracketed values with your specifics, and run.
Connect Lusha to Claude in two minutes →
Prospecting (Prompts 1–4)
The opening motion. Building lists, finding triggered accounts, mapping buying groups, catching role changes.
Prompt 1 — Build a verified prospect list from a natural-language ICP
The foundational use case. Describe who you want to reach. Get back a callable list with verified email and direct dial.
<context>
I'm prospecting for new business and want a verified contact list that matches my ICP.
</context>
<task>
Use Lusha to find 25 verified contacts that match:
- Job titles: [TITLES — e.g., VP of Revenue Operations, Head of RevOps]
- Industry: [INDUSTRY — e.g., B2B SaaS / Software Development]
- Headcount: [RANGE — e.g., 500-2,500]
- Geography: [COUNTRY / REGION — e.g., United States]
- Technologies (optional): [TECH STACK — e.g., Salesforce, HubSpot]
Return a table:
Name | Title | Company | Validated email | Mobile direct dial | DNC status
</task>
<constraints>
- Only include contacts with hasWorkEmail: true
- Surface email confidence grade (A+ through D) per row
- Flag any phone number with DNC = true
</constraints>See the full workflow with a live demo →
Prompt 2 — Find recently funded companies to prospect
Companies that just closed a round have unlocked budget and are scoping spend. The best single time-bound prospecting signal in B2B.
<context>
I want to prospect into companies that recently raised funding — that's when budget unlocks for new vendor spend.
</context>
<task>
Use Lusha's signals layer to find companies that raised funding in the last [WINDOW — e.g., 90 days] matching:
- Industry: [INDUSTRY]
- Headcount: [RANGE]
- Geography: [REGION]
- Funding round type (optional): [Seed / Series A / Series B / Series C+ / Strategic Investment]
For each company, return:
- Company name, headcount, industry
- Funding round details: amount, date, lead investor, source article URL
- The verified [TARGET TITLES — e.g., CRO, VP Sales] at the company with validated email and direct dial
Rank by round recency (newest first).
</task>
<constraints>
- Only return contacts with validated work email
- Surface the round date and amount inline so I can reference them in outreach
</constraints>See the full workflow with a live demo →
Prompt 3 — Build a verified buying group for a target account
For named-account prospecting. Get the full buying group at one company organized by role family — economic buyer, technical evaluator, end user, influencer, executive sponsor.
<context>
I'm starting a sales motion at [TARGET ACCOUNT]. I need the full verified buying group, not just one contact.
</context>
<task>
Use Lusha to find the verified buying group at [TARGET ACCOUNT] for a [PRODUCT / SOLUTION] sale. Organize the output by role family:
- ECONOMIC BUYER (CFO, VP Finance, or C-suite owner of the function — 1-2 contacts)
- TECHNICAL EVALUATOR (CTO, VP Engineering, Solutions Engineering leadership — 1-2 contacts)
- END USER (the function leader who'll own day-to-day use — VP Sales, VP Marketing, etc. — 1-2 contacts)
- INFLUENCER (RevOps, procurement, IT — 1-2 contacts)
- EXECUTIVE SPONSOR (the C-suite owner of the broader business unit — 1 contact)
For each contact:
Name | Title | Role family | Validated email | Direct dial | Job start date
Flag anyone in their first 90 days in role — that's a fresh mandate window worth referencing in outreach.
</task>
<constraints>
- Only include contacts with validated email
- Group by role family, not seniority
- If a role family has no clean match at the account, surface it as a structural gap
</constraints>See the full workflow with a live demo →
Prompt 4 — Find people who just changed roles in your target persona
A contact who just changed jobs has 90 days of new-mandate authority. The strongest single trigger for outbound conversion.
<context>
I want to find people who just took new roles matching my ICP — first-90-days mandate windows are the strongest outbound conversion trigger.
</context>
<task>
Use Lusha's signals layer to find contacts whose job start date is within the last [WINDOW — e.g., 90 days] AND who match:
- Target titles: [TITLES — e.g., CRO, VP Sales, Head of RevOps]
- Industry: [INDUSTRY]
- Headcount: [RANGE]
- Geography: [REGION]
For each contact, return:
- Name and new title
- Company and current headcount
- Job start date (so I can calculate mandate-window days remaining)
- Previous job (so I understand the trajectory)
- Validated email and direct dial
Rank by job start date — most recent first.
</task>
<constraints>
- The contact's previous role and current role should be a real transition (promotion, lateral move, or company change), not the same role at the same company
- Surface the previous employer when available — useful context for the outreach opener
</constraints>See the full workflow with a live demo →
Pipeline Acceleration (Prompts 5–8)
For deals already in motion. Reviving stuck deals, auditing coverage, briefing for calls, advancing stages with discipline.
Prompt 5 — Revive a stuck deal with a fresh signal trigger
The deal went quiet two months ago. Don’t write “just checking in.” Find a real reason the conversation should re-open.
<context>
I have a stuck deal — went quiet after the last meaningful touch. I need a fresh signal-based hook to re-open, not a "checking in" email.
My stuck deal:
- Prospect company: [COMPANY]
- Primary contact: [NAME, TITLE]
- Last meaningful touch date: [DATE]
- Stage where it stalled: [STAGE]
- What I was selling: [PRODUCT]
- Next step that didn't happen: [WHAT WAS SUPPOSED TO HAPPEN]
</context>
<task>
Use Lusha's signals layer to scan the prospect company for events fired AFTER my last meaningful touch date:
- Leadership events (new hires, departures, promotions)
- Strategic moves (M&A, funding rounds, strategic investments)
- Product activity (launches, integrations)
- Hiring surges in the function I sell into
For each signal, map a re-engagement angle:
- What changed
- Why it matters to my deal
- One-line email opener tied to the signal
Rank by re-engagement strength: STRONG (leadership change, fresh funding, M&A) / MEDIUM (product launch, hiring surge) / WEAK (minor news).
Recommend the primary hook plus one backup.
</task>
<constraints>
- The signal must have fired AFTER my last touch date
- The hook references the signal, never the silence
- If no signal has fired, surface that honestly — manufactured urgency is the wrong move
</constraints>See the full workflow with a live demo →
Prompt 6 — Audit multi-thread coverage on an open deal
Single-threaded deals slip. This prompt audits whether your buying-group coverage matches the deal stage and prescribes the next touches.
<context>
I have an open deal and want to audit my multi-thread coverage against the verified buying group, then identify the next 2-3 touches I should make.
My deal:
- Prospect company: [COMPANY]
- Stage: [Discovery / Proposal / Negotiation / Closing]
- Product I'm selling: [PRODUCT]
- Contacts I've already touched (name, role, days since last touch): [LIST]
</context>
<task>
Use Lusha to pull the full verified buying group at the prospect. Apply the deal-stage coverage requirements:
- Discovery → Proposal: must have technical evaluator + end user touched
- Proposal → Negotiation: must have economic buyer + technical evaluator + end user
- Negotiation → Closing: must have economic buyer + procurement gate
- Closing → Won: must have economic buyer signed off + executive sponsor briefed
Output:
- Touched contacts (role + last-touch recency)
- Critical gaps (musts missing for current stage)
- Stale threads (touched but silent 14+ days at active stage)
- Prescribed next touches with verified contact details and a one-line angle
</task>
<constraints>
- Each prescribed touch needs a specific angle, not generic outreach
- Flag any contact in the buying group who has been touched but gone quiet 14+ days
</constraints>See the full workflow with a live demo →
Prompt 7 — Get a single-account signal brief before the call
Pre-call prep in 60 seconds. Every signal event in the last six months at one account, organized into five categories, with talk tracks.
<context>
I have a discovery call or strategic review on [ACCOUNT NAME] in [TIMEFRAME — e.g., 24 hours]. I need a complete pre-call brief.
</context>
<task>
Use Lusha's signals layer to pull every signal at the account from the last 6 months, organized into five categories:
1. LEADERSHIP — executive hires, promotions, departures
2. STRATEGIC MOVES — M&A, IPO, funding, strategic investments
3. PRODUCT ACTIVITY — launches, integrations, new features
4. HIRING INTENSITY — surges by department, headcount growth, geographic spikes
5. MARKET SIGNALS — web traffic shifts, partnerships, new customers
For each signal:
- Event type and date
- One-line summary
- Source article URL where available
At the top, surface a 3-line headline summary:
- Most important leadership move
- Biggest strategic shift
- Strongest active hiring signal
After the categorized brief, suggest 3-5 talk tracks for the call, each tied to a specific surfaced signal.
</task>
<constraints>
- Pull every signal type, not just funding and hiring
- Surface source URLs on every news event that has one
- If the account is quiet (no signals in the window), surface that honestly
</constraints>See the full workflow with a live demo →
Prompt 8 — Stage-gate readiness check before advancing a deal
The moment before you update the CRM stage. Does the buying-group coverage actually justify the advance, or are you stage-inflating?
<context>
I'm about to advance a deal to the next stage. I want a readiness check before I do.
My deal:
- Prospect company: [COMPANY]
- Current stage: [CURRENT]
- Target stage: [TARGET]
- Product I'm selling: [PRODUCT]
- Contacts touched so far: [LIST]
- Reason I want to advance: [ONE-LINE WHY]
</context>
<task>
Use Lusha to pull the verified buying group. Apply the stage-gate framework for the target stage:
- Discovery → Proposal: must have technical evaluator + end user
- Proposal → Negotiation: must have economic buyer
- Negotiation → Closing: must have economic buyer + procurement gate
- Closing → Won: must have economic buyer signed + executive sponsor briefed
Return one of:
- ADVANCE — coverage meets requirements, proceed with stage update
- HOLD, close one gap — close the listed specific gap first
- HOLD, significant gap — coverage is structurally insufficient, deal may be stage-inflated
For HOLD decisions, prescribe the next 1-2 touches: contact, role they fill, one-line angle, timeline.
If my "reason for advancing" doesn't match the actual coverage (e.g., end user enthusiasm but economic buyer not touched), flag the disconnect honestly.
</task>
<constraints>
- The framework is not negotiable — Proposal-stage deal without economic buyer is not ready for Negotiation
- A HOLD decision protects forecast accuracy. Be clear which decision applies.
</constraints>See the full workflow with a live demo →
Closing and post-close (Prompts 9–12)
For deals at the wire and the customer relationships that follow.
Prompt 9 — Decision-maker validation pre-close
The final pre-signature check. Has the signer departed? Did a new C-suite role get created? Run this before you hit send on the contract.
<context>
I'm about to send a contract for signature. Validate decision makers and structural state at the prospect before I hit send.
My deal at contract stage:
- Prospect company: [COMPANY]
- Planned signer: [NAME, TITLE]
- Contract value (annual): [DOLLAR AMOUNT]
- Contract term: [LENGTH]
- Buying group I've worked with: [LIST]
- Last meaningful touch with the signer: [DATE]
</context>
<task>
Validate three things:
1. SIGNER VALIDATION
- Is the planned signer still at the prospect?
- Does the current title match what's on the contract?
- Job start date — recent enough that authority for this contract size may not yet apply?
- Seniority appropriate for the contract value?
2. BUYING GROUP VALIDATION
- Each contact's current title still matches my notes?
- Anyone in the group departed or changed roles since my last touch?
3. STRUCTURAL CHANGES AT THE PROSPECT (last 30-90 days)
- Executive departures in the contract approval chain
- Leadership hires creating new approval routing
- M&A (especially as acquired party — triggers contract freezes)
- Security incidents (may trigger new procurement scrutiny)
Return one of:
- SEND — validated, no structural changes, contract goes out today
- HOLD, verify one thing first — minor issue, specific verification needed
- HOLD, structural change — significant change affects contract path, surface what changed and the next move
</task>
<constraints>
- Validation is binary on each check — don't soften with "probably still there"
- If the signer has departed, surface the replacement candidate
</constraints>See the full workflow with a live demo →
Prompt 10 — Surface urgency signals for time-to-close compression
Find real buyer-side reasons the decision should happen on a faster clock. Replaces manufactured “end of quarter” urgency with structural buyer urgency.
<context>
I want to legitimately compress time to close. Find real buyer-side reasons the decision should happen faster — not manufactured seller-side urgency.
My open deal:
- Prospect company: [COMPANY]
- Current stage: [STAGE]
- Current target close date: [DATE]
- Faster target: [DATE — typically 30-60 days earlier]
- Product I'm selling: [PRODUCT]
- Primary contact: [NAME, TITLE]
</context>
<task>
Use Lusha's signals layer to scan the prospect for time-bound events — fired or upcoming — that create natural urgency:
- New leadership mandate windows (CRO, CFO, CMO, CTO inside first 60-90 days)
- Procurement gates forming around new C-suite roles (e.g., new CSTO)
- Fiscal year crossings (when does the prospect's fiscal year start?)
- Post-funding allocation windows (60-90 days after a round closes)
- M&A windows as the acquirer (vendor rationalization typically 12 months post-close)
- IPO post-listing windows (6-12 months of investor-mandated growth spend)
For each event:
- Status: OPEN NOW / CLOSING in 30-60 days / OPEN SOON / CLOSED
- Compression angle: how this event creates a buyer-side reason to decide now
- Honest framing: the sentence I can use in the next conversation
- Right contact for the conversation
Rank by compression strength: STRONG / MEDIUM / WEAK.
Recommend the strongest angle plus the right contact to deliver it to.
</task>
<constraints>
- The urgency must be buyer-side, not seller-side
- The framing must be honest — reference the buyer-side event as a reason, not as pressure
- If no time-bound events exist, surface that honestly — manufacturing urgency is the wrong move
</constraints>See the full workflow with a live demo →
Prompt 11 — Find the new champion when yours moves on
The relationship resilience prompt. Your champion left. Find the verified replacement before the renewal cycle reaches them first.
<context>
My champion at an existing customer just left. I need to find the verified replacement and re-engage before the renewal cycle reaches them first.
My departed champion:
- Name: [NAME]
- Former title at the customer: [TITLE]
- Customer account: [CUSTOMER]
- Function they owned: [FUNCTION]
</context>
<task>
1. Use Lusha to find current contacts at the customer matching the departed champion's function and seniority (4-6 candidates, including one level up).
2. CROSS-VALIDATE each candidate against their individual record:
- Confirm current employer is still the customer
- Confirm current title and job start date
- Flag anyone who ALSO moved to a different company (company-side data may still list them)
3. For each verified candidate, return:
- Name and current title
- Validated email and direct dial
- Tenure in role
- Previous job (trajectory)
- Inheritance likelihood: HIGH / MEDIUM / LOW based on scope, seniority, tenure
4. If no clean candidate emerges in the function, surface the C-suite owner one level up as the re-engagement starting point.
</task>
<constraints>
- Cross-validation is the critical step. Company search may return contacts whose individual records show they moved on.
- Inheritance likelihood is a judgment based on scope, tenure, seniority — surface the reasoning
</constraints>See the full workflow with a live demo →
Prompt 12 — Build a multi-thread map for an existing customer
Single-threaded customer relationships are renewal risk in slow motion. Build the 6-8 verified relationships you should have at every active customer.
<context>
I have an existing customer where I'm under-threaded — I know one main contact but should know 6-8 across the buying group.
My known contact:
- Name: [NAME]
- Title: [TITLE]
- Customer: [CUSTOMER NAME]
- Function we sold into: [FUNCTION]
</context>
<task>
Use Lusha to find 6-8 additional verified contacts at the customer, organized into five relationship roles:
- PEER OF CHAMPION — same function, same level (1-2 contacts)
- MANAGER / SKIP-LEVEL — the boss above and the boss above that (1-2 contacts)
- ADJACENT FUNCTION — leaders in adjacent functions the engagement should touch (2-3 contacts)
- EXECUTIVE SPONSOR — C-suite owner of the broader business unit (1 contact)
- SUCCESSOR CANDIDATE — Director/VP-level who could step into my champion's role if they move (1 contact)
For each:
Name | Title | Validated email | Direct dial | Relationship role | Why this person matters (one sentence)
Group output by relationship role, not seniority. Flag any role where Lusha returns zero — that's a structural gap.
</task>
<constraints>
- Only include contacts with validated email
- Cap at 2 contacts per relationship role for readability
- For ADJACENT FUNCTION, pick functions that genuinely connect to the engagement
</constraints>See the full workflow with a live demo →
The pattern across all 12 prompts
The 12 prompts above cover three different sales motions but share one structural pattern: the verified data layer is what makes the prompt usable. Generic Claude prompts ask the model to generate a list of likely contacts at a company. These prompts retrieve the verified contacts from Lusha — with email confidence grades, direct dial DNC status, job start dates, and named buying signals tied to source articles.
The difference shows up in the bounce rate, the conversation legitimacy, the deal slip prevention, and the renewal-risk catch rate. Verified data isn’t a nicety. It’s the unlock.
Connect Lusha to Claude in two minutes →
