Score a rep’s pipeline data quality before a 1:1

Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha connector output, but were not pulled from a live session. Run the prompt with your own rep’s pipeline data to see live results. Personal details in any live examples are masked or abbreviated for privacy.

Scoring a rep’s pipeline data quality before a 1:1 means validating every contact on every active deal via Lusha, flagging departures and missing roles before a forecast call surfaces the problem, and identifying the pattern across the full pipeline that points to a specific coaching conversation. This Claude prompt runs the full validation in one pass — Lusha checks every contact, scores each deal GREEN / AMBER / RED, and returns a one-observation coaching note grounded in what the data shows rather than what the manager assumes.

The prompt

<context>
I'm preparing for a 1:1 with one of my reps. Before the meeting, I want to know the data quality state of their active pipeline — which contacts have departed, which accounts are missing key contacts, which records have stale or missing fields. I want to walk in knowing where the data gaps are so we can address them rather than discovering them on a forecast call.

My 1:1 prep:
- Rep name: [REP NAME]
- Rep's active deals: [PASTE DEAL NAME, COMPANY, PRIMARY CONTACT, STAGE, ACV — one per line]
- What we sell: [PRODUCT / SOLUTION]
- CRM: [SALESFORCE / HUBSPOT / OTHER]
</context>

<task>
1. Use Lusha to validate every primary contact across the rep's active deals:
   - Still at the company in the same role?
   - Title changed?
   - Email and direct phone still valid?

2. Check each deal for data completeness:
   - Verified primary contact at required seniority?
   - Secondary contacts covering key buying roles?
   - Current headcount, industry, and funding stage on the company record?

3. Score each deal:
   - GREEN: all contacts verified, firmographics current, no gaps
   - AMBER: primary contact verified but secondary contacts missing or stale
   - RED: primary contact departed or unverified, or critical firmographic data missing

4. Build the 1:1 data quality brief:

   ## Rep Data Quality Overview
   Rep name · total deals · GREEN / AMBER / RED · overall quality score

   ## RED deals — address in the 1:1
   Deal name · ACV · what's wrong · recommended fix

   ## AMBER deals — flag for rep to fix this week
   Deal name · what's missing · where to find it

   ## Contacts to update in CRM
   Departed contacts · promoted contacts · title changes

   ## One coaching observation
   Based on the pattern across this rep's pipeline — prospecting gap, multi-thread gap,
   or CRM hygiene habit?

5. Return the full brief — ready to use as the 1:1 opening agenda item.
</task>

<constraints>
- RED deals must be addressed in the 1:1 — not deferred.
- Coaching observation based on the pattern, not a single data point.
- Focus on what affects forecast accuracy — not every minor gap.
- One coaching observation only.
</constraints>

What you'll get back

The situation: A sales manager prepares for a weekly 1:1 with Sarah. Sarah has 5 active deals.


Rep Data Quality Overview

Sarah · 5 active deals · Total ACV: $340K

🔴 RED: 1 deal · 🟡 AMBER: 2 deals · ✅ GREEN: 2 deals

Overall data quality score: 62% — needs attention


RED deals — address in the 1:1


Vantage Enablement · Negotiation · $58K

Primary contact B.N., Sr Director RevOps — departed per Lusha. No longer at the company. This is the only contact in the deal thread. The deal is at Negotiation stage with no active contact.

Recommended fix: Find the replacement contact before the next scheduled call. Use the find the decision-maker prompt. Do not let this deal go another week without a verified contact.


AMBER deals — flag for Sarah to fix this week


Ashford Platforms · Proposal · $95K

Primary contact D.R. verified ✓. No secondary contacts in the deal thread — single-threaded at Proposal stage. CFO mentioned as signatory but not yet introduced.

Fix: Add M.L. (Head of Sales Ops, verified via Lusha) to the thread this week. Ask D.R. to make the CFO introduction before close.


Dunmore Analytics · Discovery · $72K

Primary contact T.K. verified ✓. Company record missing: funding stage not updated (Series B closed 18 days ago), headcount stale (recorded as 480, Lusha shows 580).

Fix: Update CRM fields before next forecast call — funding stage and headcount affect ICP score and deal priority.


Contacts to update in CRM

ContactCompanyChangeAction
B.N.Vantage EnablementDepartedRemove as primary, find replacement
P.M.Meridian AnalyticsPromoted VP → SVPUpdate title field

One coaching observation

Pattern: multi-thread gap, not CRM hygiene.

Sarah’s contacts are generally current and accurate — the B.N. departure is an exception, not a habit. The consistent issue across Sarah’s pipeline is single-threading: 3 of 5 deals have only one contact in the thread, and 2 of those are at Proposal stage or beyond. This isn’t a data entry problem — it’s a prospecting habit. The coaching conversation should focus on when and how to introduce a second contact into a deal, not on CRM hygiene.


Illustrative example — fictional company names used. Run with your own rep’s pipeline to see live results.

Built by: Lusha
Time to build: 3 min
Difficulty: Easy
Tools: Claude, Lusha
Type: Prompt

Why use Lusha in Claude

Lusha in Claude gives the manager a data-grounded opening to the 1:1 rather than a gut-feel conversation about pipeline health. The B.N. departure at Vantage Enablement — a $58K deal at Negotiation with no active contact — is the finding that changes the agenda. Without the check, that deal goes into the weekly forecast as active. With it, the manager walks in knowing the deal is at risk and the first 10 minutes of the 1:1 are spent fixing it rather than reviewing pipeline stage by stage. The coaching observation is equally important: the pattern across Sarah’s pipeline points to multi-threading, not CRM hygiene. That’s a different coaching conversation with a different recommended action.

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


FAQ

  • How is this different from the org-level data quality SLA report?

    The data quality SLA report covers the full sales org — it produces a compliance report across all reps and all accounts. This play is a per-rep brief built specifically for a 1:1 meeting — it adds the coaching observation and formats the output as a meeting agenda rather than an audit report. Different scale, different purpose.

  • Should I share this brief with the rep before the 1:1?

    The RED deal section should be shared — the rep needs to know about B.N.’s departure before the 1:1, not during it. The coaching observation is typically kept for the conversation rather than shared in advance, so the manager can frame it constructively rather than having it land as a written critique.

  • How often should I run this?

    Weekly for reps with deals at Proposal stage or beyond. Monthly for reps in earlier pipeline stages. The Negotiation-stage departed contact is the scenario that justifies a weekly cadence — one week of missed awareness on a deal like that costs real money.

  • What if most deals come back GREEN?

    A GREEN-heavy brief is a positive signal — the rep has good data hygiene and current contacts. The coaching observation in a GREEN pipeline is typically “nothing to flag this week” — which is also useful context for the 1:1 and frees up time for other topics.

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.