Audit contact coverage gaps across your named accounts

Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.

Three contacts at an account with no economic buyer is a coverage gap, not coverage. This Claude prompt maps every required buying group role across named accounts using Lusha — flags CRITICAL GAPs, IMPORTANT GAPs, and STALE CONTACTs, and returns a verified replacement for every gap found. Built for enterprise AEs and ABM teams running named account programs.

The prompt

This prompt may contain placeholders — look for [BRACKETS] and fill them in.

<context>
I manage a set of named accounts and I want to audit whether we have the right contacts mapped for each one — not just whether we have any contact, but whether we're covering the right roles in the buying group. Gaps in contact coverage mean gaps in deal control.

My named accounts:
- Account list: [PASTE COMPANY NAMES — one per line]
- What I sell: [PRODUCT / SOLUTION]
- Buying group roles I need covered: [e.g. Economic buyer / Technical evaluator / Champion / Procurement]
- Contacts I currently have: [PASTE NAME, TITLE, COMPANY — one per line]
</context>

<task>
1. For each account, use Lusha to map the current verified contacts in the relevant buying group roles:
   - Who currently holds each role I need covered?
   - Are my existing contacts still in the right roles?
   - Are there roles I need covered but have no contact for?

2. For each account, return a coverage map:
   - Role: COVERED (existing verified contact) / GAP (no contact for this role) / STALE (contact no longer in this role)

3. Prioritize the gaps:
   - CRITICAL GAP: a must-have role with no verified contact — blocks deal progression
   - IMPORTANT GAP: a should-have role missing — increases risk at current deal stage
   - STALE CONTACT: someone I think I have but who's no longer in that role

4. For each GAP and STALE CONTACT: use Lusha to find the current verified contact for that role, with email and direct phone.

5. Return a contact coverage report:
   - Per-account coverage map with GREEN / AMBER / RED status
   - Critical gaps ranked by deal stage and ACV
   - Replacement contacts found via Lusha for every gap
   - Total accounts with at least one critical gap
</task>

<constraints>
- Coverage is role-specific, not headcount-specific. Having 3 contacts at an account but missing the economic buyer is a CRITICAL GAP.
- A STALE CONTACT is more dangerous than a GAP — it creates false confidence. Flag it prominently.
- If Lusha can't find a contact for a required role, flag it as a research task — don't leave it unmarked.
</constraints>

What you'll get back

The situation: An enterprise AE selling revenue intelligence software audits contact coverage across 4 named accounts. Required roles: Economic buyer (CRO/CFO), Technical evaluator (VP Eng/CTO), Champion (VP Sales/RevOps), Procurement (VP Finance/Legal).

Output from live Lusha run, May 25, 2026:


Gong — RED (1 critical gap)

RoleStatusCurrent contact
Economic buyer (CRO)COVEREDA.O., AVP Commercial Sales — verified ✓
Technical evaluator (VP Eng/CTO)CRITICAL GAPNo verified contact — Lusha returns no matching role
Champion (VP Sales/RevOps)COVEREDM.G., VP Finance & Treasury ✓
ProcurementIMPORTANT GAPNo finance/legal contact mapped

Replacement found: Lusha returns no CTO at Gong in current data. Flag for manual research — LinkedIn search for Head of Engineering at Gong before next exec meeting.


Zendesk — AMBER (stale contacts, no critical gaps)

RoleStatusCurrent contact
Economic buyerSTALE ⚠CRM shows A.L. as VP Global Sales — now SVP. Title stale, still at company
Technical evaluatorCOVEREDJ.P., VP Worldwide Sales Ops ✓
ChampionSTALE ⚠CRM shows E.L. as VP Sales — now SVP. Update CRM
ProcurementCOVEREDG.L., VP of Sales ✓

No critical gaps — but 2 STALE contacts will send wrong title signals if used in outreach without updating.


Highspot — GREEN (full coverage)

RoleStatusCurrent contact
Economic buyerCOVEREDJ.S., VP RevOps ✓
Technical evaluatorCOVEREDB.N., Sr Director RevOps ✓
ChampionCOVEREDP.K., Director RevOps ✓
ProcurementCOVEREDG.F., Sr Director RevOps ✓

Full coverage, all contacts verified.


Seismic — AMBER (1 important gap)

RoleStatusCurrent contact
Economic buyerCOVEREDM.C., VP RevOps ✓
Technical evaluatorIMPORTANT GAPNo technical contact mapped
ChampionCOVEREDM.C. (dual role)
ProcurementIMPORTANT GAPNo procurement contact mapped

Replacements found via Lusha: technical evaluator and procurement contacts available — details returned on live run.


Coverage summary: 4 accounts · 1 RED (Gong) · 2 AMBER (Zendesk, Seismic) · 1 GREEN (Highspot) Critical gaps: 1 (Gong — no technical evaluator) Stale contacts: 2 (Zendesk — both VP→SVP promotions)

Contacts verified live via Lusha connector, May 25, 2026. Names masked to initials.

Built by: Lusha
Time to build: 4 min
Difficulty: Medium
Tools: Claude, Lusha
Type: Prompt

Why use Lusha in Claude

Having contacts at an account is not the same as having the right contacts. An AE who has three relationships at Gong but none of them are the technical evaluator will discover that gap in a technical evaluation call, not before. The STALE CONTACT flag is the sharper finding — Zendesk looks covered until you check, and then you find out the two people you think you have are both SVPs now, not VPs. That gap creates false confidence that’s harder to fix than a known gap. Lusha in Claude maps the current verified state of every role in the buying group, so the coverage picture is based on what’s actually there.

Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • How often should I run this for a named account list?

    Monthly for active deals, quarterly for full named account programs. Active deals move fast — a contact can change roles between touches. Monthly checks catch gaps before they affect a live deal.

  • What if Lusha can't find a contact for a required role?

    The prompt flags it as a research task — a known gap is better than an assumed gap. Run a LinkedIn search for the role title at the company and use the find the decision-maker prompt to complete the record once you have a name.

  • What's the difference between a CRITICAL GAP and an IMPORTANT GAP?

    CRITICAL GAP: a must-have role with no contact — this blocks deal progression at the current stage. An economic buyer gap at Proposal stage, for example. IMPORTANT GAP: a should-have role missing — increases risk but doesn’t immediately block. A procurement contact gap at Discovery is an important gap; the same gap at Negotiation becomes critical.

Ready to build this?

Get started with Lusha and set up this play in minutes.