Build a data quality SLA report for the sales org

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

This Claude prompt gives RevOps and sales leadership a data quality SLA report for the full pipeline. Lusha verifies every deal contact and returns ACV exposure by verification status — VERIFIED, DEGRADED, FAILED, CRITICAL FAIL. The executive summary includes a dollar figure, a compliance rate, and one specific recommendation. Built for the RevOps or VP Sales who needs to make the case for a data refresh — or prove they don’t need one.

 

The prompt

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

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

What you'll get back

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:

StatusDealsTotal ACV% of pipeline
VERIFIED4$217K38%
DEGRADED3$242K43%
FAILED1$50K9%
CRITICAL FAIL1$58K10%

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


CRITICAL FAIL — immediate action required

Highspot enterprise expansion — $58K — Negotiation Contact B.N., Sr Director RevOps: confirmed departed from Highspot. No verified contact at this account at Negotiation stage. Replacement found: J.S., VP of Revenue Operations — [email protected] ✓ 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

DealCompanyContactIssueACVStage
Zendesk renewalZendeskA.L.Promoted VP→SVP — title stale$180KProposal
Seismic expansionSeismicM.C.VP→SVP promotion — email only, no phone$95KProposal
Gong new bizGongA.O.Title confirmed, email only — no mobile$72KDiscovery

FAILED

DealCompanyContactIssueACVStage
Salesloft reactivationSalesloftContact unverified — no Lusha record$50KDiscovery

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 Highspot deal can advance. The risk of not fixing this: the Highspot deal stalls at Negotiation, the Zendesk renewal proposal lands with wrong titles, and the Salesloft deal stays in Discovery indefinitely with no one to call.

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

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

Why it works

“We have a data quality problem” doesn’t get budget or attention. “$350K of active pipeline doesn’t meet our defined verification standard, including one Negotiation-stage deal with no verified contact” does. The SLA framing turns a hygiene argument into a revenue argument. The executive summary paragraph is designed to be shared directly — in a board prep, a leadership meeting, or a RevOps roadmap conversation. The by-stage breakdown is where the actionable insight sits: Proposal-stage data quality issues are more urgent than Discovery ones, and CRITICAL FAIL at Negotiation is a revenue risk that needs to be resolved this week.

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

FAQ

  • What should the data quality standard be?

    A reasonable baseline: every deal contact verified and reachable (email + phone) within the last 90 days. For enterprise deals at Proposal stage or beyond: verified within 30 days. The tighter the standard, the lower the compliance rate will be — but the more useful the report. Start with 90 days and tighten once the org is consistently hitting it.

  • How often should I run this?

    Monthly for active pipeline, quarterly for a full org-level report. Monthly gives you a trend line — if compliance is improving, you’re building the right habits. If it’s declining, you know before it affects close rates.

  • Can I share this report directly with leadership?

    Yes — the executive summary paragraph is written to be shared as-is or lightly adapted. Copy it into a Slack message, a board slide, or a RevOps roadmap doc. The specific dollar figures and compliance rate are what make it legible to a non-RevOps audience.

  • What do I do with DEGRADED deals?

    Update the CRM titles and run a Lusha phone number check where only email was returned. DEGRADED is a fixable state — it doesn’t require a relationship reset, just a data update. Set a standard that DEGRADED deals get upgraded to VERIFIED before they move to the next stage.

  • How is this different from the rep account scorecard?

    The rep account scorecard is a per-rep coaching tool for use in a 1:1 or QBR. This report is an org-level SLA document for RevOps and leadership — covers the full pipeline across all reps, uses compliance rate and ACV exposure as the primary metrics, and produces an executive summary.

Ready to build this?

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