Audit multi-thread coverage on an open deal
A Claude prompt that takes an open deal and audits the multi-thread coverage against the verified buying group. Lusha returns the full set of decision-makers, technical evaluators, end users, and influencers at the prospect. The prompt compares that map against the contacts the AE has touched so far, flags the gaps that matter at the current deal stage, and prescribes the next two or three touches in priority order.
Single-threaded deals are the single biggest forecast risk in B2B. Built for AEs running deal reviews and Sales Managers checking pipeline health.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just describe the deal and the contacts you’ve touched, then run.
Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.
The prompt
<context>
I have an open deal. I want to audit my multi-thread coverage against the full verified buying group at the prospect — surface the gaps that matter at my current deal stage, and identify the next two or three touches I should make.
My open deal:
- Prospect company / domain: [COMPANY]
- Deal stage: [Discovery / Proposal / Negotiation / Closing]
- What I'm selling: [PRODUCT / SOLUTION]
- Contacts I've already touched (name and role): [LIST]
- Days since last touch with each: [LIST]
</context>
<task>
1. Use Lusha to pull the verified buying group at the prospect company, organized by role family:
- Economic buyer (CFO, VP Finance, or C-suite owner of the function)
- Technical evaluator (CTO, VP Engineering, Solutions Engineering leadership for product-led evaluations)
- End user (the function leader who will own the day-to-day use — VP Sales, VP Marketing, etc.)
- Influencer (RevOps, procurement, sometimes IT — the operators who shape the decision around the named buyers)
- Executive sponsor (the C-suite owner of the broader business unit)
2. Compare the buying group against the contacts already touched.
3. Apply the deal-stage gap framework:
- Discovery stage — must have: technical evaluator touched. Should have: end user + at least one influencer. Optional: economic buyer.
- Proposal stage — must have: economic buyer + technical evaluator + end user. Should have: influencer (especially procurement and RevOps).
- Negotiation stage — must have: economic buyer + procurement (or finance gate). Should have: executive sponsor.
- Closing stage — must have: economic buyer signed off + executive sponsor briefed. Should have: end user confirmed for rollout.
4. Output a coverage audit:
- Touched contacts and their role in the buying group
- Critical gaps (musts missing for current stage)
- Important gaps (shoulds missing for current stage)
- Acceptable gaps (optional for current stage — for context)
5. Prescribe the next 2-3 touches in priority order, with verified contact details and a one-line angle per touch.
6. Flag any contact in the buying group who has been touched but has gone quiet for more than 14 days at the current deal stage. Stale threads in active deals are forecast risk.
</task>
<constraints>
- Coverage requirements are deal-stage dependent. A discovery-stage deal without the economic buyer touched is normal. A proposal-stage deal without the economic buyer touched is a critical gap.
- Each prescribed next touch must include a specific angle, not generic "reach out to the CFO."
- Do not invent contacts or roles. Surface only what Lusha returns. If a role family is empty at the prospect, flag it as a structural gap that may require manual research.
- The audit is a tool for the AE's judgment, not a replacement for it. Surface the gaps; let the AE decide which to close first.
</constraints>What you'll get back
Input: Open deal at Snowflake. Stage — Proposal. Product — sales productivity platform. Contacts touched so far: Keegan R. (SVP Sales Americas, end user), Patrick H. (VP RevOps, influencer), Dwarak R. (VP AI Engineering, technical evaluator).
Output: 3 contacts touched out of a verified 8-person buying group. 2 critical gaps identified for Proposal stage. 1 stale thread flagged. Below is the real result from running the prompt against the live Lusha connector.
Buying group coverage audit
| Role family | Verified contact at Snowflake | Status |
|---|---|---|
| Economic buyer | Brian R., Chief Financial Officer | NOT TOUCHED — critical gap |
| Technical evaluator | Dwarak R., VP and Head of AI Engineering | Touched 12 days ago |
| End user | Keegan R., SVP of Sales, Americas Acquisition | Touched 8 days ago |
| Influencer | Patrick H., Vice President of Revenue Operations | Touched 23 days ago — stale thread |
| Executive sponsor | Jonathan B., Chief Revenue Officer (incoming, March 31, 2026) | NOT TOUCHED — critical gap (new role, fresh mandate) |
| Security / procurement gate | Mayank U., Chief Security & Trust Officer (new role, April 1, 2026) | NOT TOUCHED — important gap for procurement review |
Critical gaps for Proposal stage
1. Economic buyer (Brian R., CFO) not touched. At Proposal stage, the deal pricing needs to land with the budget owner before negotiation. The CFO will see the contract; better that he sees it pre-briefed than as a surprise. The deal’s been at Proposal for several weeks with no CFO touch — this is the highest-priority gap to close this week.
2. Executive sponsor (Jonathan B., new CRO) not touched. The new CRO arrived March 31 and is inside his first-90-days mandate window. Active GTM deals are exactly the kind of evaluation he’ll want context on. Reaching him pre-emptively means the deal lands in front of him as “in motion with the right people” rather than “discovered during vendor review.”
Important gaps
3. Security / procurement gate (Mayank U., new CSTO) not touched. At Proposal stage moving toward Negotiation, the security review is the typical gate. The new CSTO role is brand new at Snowflake and unfilled at the time of the original deal kickoff. Early coordination with his team prevents the security review from becoming a 6-week procurement delay later.
Stale threads
4. Patrick H. (VP RevOps) — last touched 23 days ago. RevOps influence on a sales productivity deal is significant. A 23-day silence at Proposal stage signals he’s either deprioritized the conversation or moved on to other priorities. Worth a re-engagement touch before the deal moves to Negotiation.
Next 2-3 prescribed touches
- Brian R. (CFO) — economic buyer, critical gap. Angle: pricing brief framed as “wanted to give visibility before the contract reaches your team.” Send this week.
- Jonathan B. (incoming CRO) — executive sponsor, critical gap. Angle: “deal context for incoming CRO mandate” — position the active engagement so he sees it as foundational, not new spend. Send within the next 14 days.
- Patrick H. (VP RevOps) — stale thread. Angle: revival hook using the new CRO arrival as the natural pretext to re-engage RevOps on what the new mandate means for the deal’s roadmap. Send this week alongside the CFO touch.
The verified buying group data reused from earlier gallery runs — zero new credits consumed.
Why use Lusha in Claude
Multi-thread coverage is the single biggest forecast accuracy factor in B2B deals over $50K ACV. Three patterns repeat across every deal review.
Single-threading is invisible until it breaks. An AE who only knows the end user thinks the deal is healthy because the end user is engaged. The deal isn’t healthy — it’s structurally fragile because every other role in the buying group is undefined. When the end user goes on PTO or transitions internally, the AE has no fallback. The prompt makes the structural fragility visible before it breaks the deal. Coverage audits run monthly across the pipeline are how Sales Managers spot the risky deals before they slip.
Deal stage changes the gap framework. A discovery-stage deal without the economic buyer touched is normal — the rep is still scoping fit. A proposal-stage deal without the economic buyer touched is a critical gap — the contract is going to surprise the budget owner. The prompt applies the right gap framework for the current stage, surfaces the must-haves vs the should-haves vs the optional, and prioritizes the gaps that matter for moving the deal forward.
Stale threads at active stages are forecast risk. A buying group contact who was engaged at Discovery but has been silent for 23 days at Proposal is a fading thread. The deal looks active because other contacts are still talking, but the silent thread is leaking forecast confidence. The prompt flags stale threads specifically because they look healthier than they are — the AE last spoke to the contact, the conversation didn’t end on a no, the relationship technically exists. But silence at this stage is a slow loss in progress.
The prescribed next touches are deal-mechanics, not generic outreach. “Reach out to the CFO” is not an action plan. “Brian R., CFO, send a pricing brief framed as ‘wanted to give visibility before the contract reaches your team,’ this week” is an action plan. The prompt’s value is forcing specificity into the next-touch sequence — name, role, angle, timing.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How is this different from the buying group prompt in the prospecting gallery?
The buying group prompt is built for a target account in active sales mode — the rep is mapping who to engage to start the deal. This prompt fires after the deal is open and audits whether the current coverage is enough to close. Different starting point, different output. The buying group prompt is the map. This prompt is the gap analysis on the map vs the AE’s actual touches.
Why are coverage requirements deal-stage dependent?
The buying group’s relevance shifts as the deal advances. The technical evaluator is critical at Discovery (they validate fit). The economic buyer becomes critical at Proposal (they own the budget). Procurement becomes critical at Negotiation (they own the contract terms). An audit that ignores stage produces too many false-positive gaps at early stages and missed gaps at late stages. The stage-aware framework makes the audit usable across the pipeline.
What if the verified buying group at the prospect doesn't have everyone in the standard role families?
The prompt surfaces empty role families honestly. Some companies don’t have a traditional CTO (technical work reports into engineering VPs). Some don’t have procurement as a distinct gate (legal handles contracts). The prompt notes when a role family is structurally absent at the prospect, so the AE doesn’t waste cycles looking for a contact that doesn’t exist.
How often should I run this against my open deals?
For AEs: every Monday during deal review. For Sales Managers: as the audit layer in monthly pipeline reviews — surface the deals with critical gaps for one-on-one focus. The output is most useful when paired with the rest of the pipeline acceleration gallery — stuck-deal revival fires on the deals that lost momentum; this prompt fires on the deals that are still moving but missing structural coverage.
What counts as a "stale thread"?
A buying group contact who was meaningfully engaged earlier in the deal but has gone silent for more than 14 days at the current active stage. The 14-day threshold is the default; for fast-cycle deals (under 90-day average sales cycle), 7 days may be the right threshold. The prompt accepts a custom threshold in the constraint block.
Can I run this against a list of deals in one pass?
Yes. Sales Managers running multi-deal pipeline reviews paste 8-15 deals with stage and current touches, and the prompt returns a coverage audit per deal. The output for batch use surfaces the deals with critical gaps at the top of the response so the highest-risk deals get attention first.
Ready to build this?
Get started with Lusha and set up this play in minutes.
