Audit contact coverage gaps across your named accounts

<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>

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:

[Conversation intelligence SaaS] — RED (1 critical gap)

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

[Customer support SaaS]  — AMBER (stale contacts, no critical gaps)

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

[Sales enablement SaaS] — GREEN (full coverage)

Full coverage, all contacts verified.

[Sales content SaaS] — AMBER (1 important gap)

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

Coverage summary: 4 accounts · 1 RED ( Conversation intelligence SaaS) · 2 AMBER ( Customer support SaaS,  Sales content SaaS) · 1 GREEN ( Sales enablement SaaS) Critical gaps: 1 (Conversation intelligence SaaS — no technical evaluator) Stale contacts: 2 ( Customer support SaaS — both VP→SVP promotions)

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