Build a data quality SLA report for the sales org

<context>
I want a data quality SLA report for our sales org — a clear picture of how accurate our CRM contact data is right now, what the exposure is in terms of pipeline and revenue, and what it would take to get to a defined standard.

My pipeline:
- Active deals: [PASTE DEAL NAME, COMPANY, PRIMARY CONTACT NAME AND TITLE, STAGE, ACV — one per line]
- Total pipeline value: [DOLLAR AMOUNT OR "CALCULATE FROM ABOVE"]
- Our data quality standard: [e.g. "Every deal contact verified and reachable within the last 90 days"]
- Last time a data audit was run: [DATE OR "NEVER"]
</context>

<task>
1. For each deal's primary contact, use Lusha to verify:
   - Still at the company in the same role?
   - Verified email available?
   - Direct phone available?

2. Score each deal contact:
   - VERIFIED: confirmed at company, email and phone available — meets SLA
   - DEGRADED: still there but title changed, or only email (no phone) — partial SLA
   - FAILED: departed, unverified, or unreachable — below SLA threshold
   - CRITICAL FAIL: departed contact on a deal at Proposal stage or beyond — immediate action required

3. Calculate pipeline exposure:
   - Total ACV with VERIFIED contacts
   - Total ACV with DEGRADED contacts
   - Total ACV with FAILED contacts
   - Total ACV with CRITICAL FAIL contacts

4. Return the data quality SLA report:
   - Overall SLA compliance rate: % of deals meeting the defined standard
   - Pipeline exposure table: ACV by verification status
   - CRITICAL FAIL deals sorted by ACV — immediate action list
   - By-stage breakdown: where is data quality worst?
   - Estimated time and credit cost to bring all FAILED contacts to VERIFIED

5. Executive summary paragraph: current data quality state, ACV at risk, what it takes to fix it, and what the risk is of not fixing it.
</task>

<constraints>
- ACV at risk is the number that gets executive attention — lead the report with it.
- CRITICAL FAIL on a late-stage deal is not a data problem, it's a revenue risk — frame it that way.
- The executive summary must include a dollar figure, a % compliance rate, and one specific recommendation.
</constraints>

The situation: A VP of RevOps runs a full pipeline SLA audit before a board meeting. 9 active deals, $567K total pipeline. SLA standard: every deal contact verified and reachable within 90 days. Last audit: never.

Output from live Lusha run, May 25, 2026:

SLA compliance rate: 44% — 4 of 9 deals meet the defined standard.

Pipeline exposure table:

Total ACV not meeting SLA: $350K (62% of pipeline)

CRITICAL FAIL — immediate action required

[Sales enablement SaaS] expansion — $58K — Negotiation Contact B.N., Sr Director RevOps: confirmed departed from [sales enablement SaaS]. No verified contact at this account at Negotiation stage. Replacement found: J.S., VP of Revenue Operations — j.s@h***s***.com ✓ Action: Assign replacement contact in CRM today. Do not advance deal to Closing without re-establishing the relationship with J.S. A Negotiation-stage deal with no verified contact is not a deal — it’s a wishlist item.

DEGRADED — title changed, partial SLA

FAILED

By-stage breakdown:

• Discovery: 2 of 3 deals with data quality issues — earliest stage, lowest urgency
• Proposal: 2 of 2 deals DEGRADED — $275K at Proposal with stale or incomplete contacts
• Negotiation: 1 CRITICAL FAIL — $58K with no verified contact

Executive summary: 62% of our active pipeline — $350K out of $567K — does not meet the defined data quality standard. One deal in Negotiation has no verified contact at all, representing $58K of at-risk revenue that cannot progress to close without re-establishing the relationship. Two Proposal-stage deals totalling $275K have stale contact titles that will create friction in the sign-off process. To bring the full pipeline to SLA compliance: 6 contacts need Lusha verification runs (estimated 20 minutes and minimal credits), 3 CRM records need title updates, and 1 replacement contact needs to be assigned and introduced before the deal can advance. The risk of not fixing this: the sales enablement SaaS deal stalls at Negotiation, the customer support SaaS renewal proposal lands with wrong titles, and the sales engagement SaaS deal stays in Discovery indefinitely with no one to call.

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