Score every open opportunity for data completeness before the forecast
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 data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.
A forecast built on unverified contacts is a guess with a spreadsheet attached. This Claude prompt validates every deal contact in a Salesforce or HubSpot opportunities export against live Lusha data — assigns a risk rating per deal, calculates the ACV split by confidence tier, and returns a forecast summary the VP can read in 30 seconds. Run it before every forecast call.
Tools: Claude, Lusha, CRM export (paste)
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
Before the forecast call, I want to score every open opportunity in our CRM for data completeness — whether the deal contacts are verified and reachable, whether the buying group is mapped, and what the data gaps mean for forecast confidence.
My opportunities export:
- CRM: [SALESFORCE / HUBSPOT / OTHER]
- Paste your open opportunities: [PASTE FIELDS — Deal Name, Company, Primary Contact Name and Title, Stage, Close Date, ACV, Last Activity Date]
- Total pipeline value: [DOLLAR AMOUNT OR "CALCULATE FROM ABOVE"]
- Our forecast standard: [e.g. "Every Proposal-stage deal must have a verified economic buyer and a confirmed close date"]
</context>
<task>
1. For each opportunity, use Lusha to validate the primary contact:
- Still at the company in the same role?
- Verified email available?
- Direct phone available?
- Any account signal in the last 30 days: exec departure, M&A, funding, headcount shift
2. Score each opportunity for forecast risk:
- GREEN: primary contact verified, email and phone confirmed, no adverse signal — forecast with confidence
- AMBER: contact still there but title changed, or email only (no phone), or last activity 14+ days ago — flag for review
- RED: contact departed or unverified, or adverse signal detected — remove from forecast or downgrade probability
- CRITICAL: departed contact on a deal at Proposal stage or beyond — immediate action required before forecast closes
3. Calculate the forecast exposure:
- Total ACV at GREEN confidence
- Total ACV at AMBER (needs review)
- Total ACV at RED (at risk)
- Total ACV at CRITICAL (immediate action)
4. Return a forecast data completeness report:
- Deals sorted by stage and ACV
- Risk rating per deal with specific reason
- CRITICAL deals listed first with recommended action per deal
- Total forecast by confidence tier
- Overall data completeness score: % of pipeline meeting the forecast standard
5. One-paragraph forecast summary: what is the verified pipeline, what is at risk, and what needs to happen before the forecast call to improve confidence.
</task>
<constraints>
- ACV at CRITICAL is not pipeline — frame it as revenue at risk, not forecast.
- The forecast summary must include a dollar figure for verified pipeline and a dollar figure for at-risk pipeline.
- AMBER deals stay in the forecast but are flagged — don't remove them.
- If a deal has no primary contact in the export, flag it as CRITICAL automatically.
</constraints>What you'll get back
The situation: A VP of Sales runs this before the monthly forecast call. 9 open opportunities, $567K total pipeline. Forecast standard: every Proposal-stage deal must have a verified economic buyer with confirmed email and phone.
Output from live Lusha run, May 26, 2026:
Data completeness score: 44% — 4 of 9 deals meet the forecast standard
CRITICAL — immediate action before forecast closes
| Deal | Company | Contact | Stage | ACV | Issue |
|---|---|---|---|---|---|
| Highspot enterprise | Highspot | B.N., Sr Dir RevOps | Negotiation | $58K | Contact departed — no verified contact at Negotiation stage |
Replacement found: J.S., VP Revenue Operations — j.s@[highspot].com ✓ Action: Assign J.S. as primary contact in CRM today. Do not include this deal in the forecast until the relationship is re-established.
RED — remove from forecast or downgrade probability
| Deal | Company | Contact | Stage | ACV | Issue |
|---|---|---|---|---|---|
| Salesloft reactivation | Salesloft | — | Discovery | $50K | No contact in export — deal has no identified contact |
Action: Assign a contact in CRM before this deal can appear in the forecast. Use Lusha to find the right person.
AMBER — flagged for review, stays in forecast
| Deal | Company | Contact | Stage | ACV | Issue |
|---|---|---|---|---|---|
| Zendesk renewal | Zendesk | A.L., SVP Sales | Proposal | $180K | Title changed VP→SVP — email only, no phone in CRM |
| Seismic expansion | Seismic | M.C., VP RevOps | Proposal | $95K | Email only — no direct phone |
| Highspot new biz | Highspot | J.S., VP RevOps | Negotiation | $72K | Last activity 18 days ago — above 14-day threshold |
GREEN — forecast with confidence
| Deal | Company | Contact | Stage | ACV |
|---|---|---|---|---|
| Gong expansion | Gong | A.O., AVP Sales | Discovery | $72K |
| HubSpot enterprise | HubSpot | C.O., MD Upmarket | Discovery | $50K |
| Clari new biz | Clari | M.T., VP RevOps | Discovery | $40K |
| Notion expansion | Notion | D.R., Head Sales Strategy | Discovery | $50K |
Forecast exposure by confidence tier:
| Tier | Deals | ACV |
|---|---|---|
| GREEN (verified) | 4 | $212K |
| AMBER (review) | 3 | $347K |
| RED (at risk) | 1 | $50K |
| CRITICAL (action required) | 1 | $58K |
| Total pipeline | 9 | $567K |
Verified pipeline (GREEN only): $212K At-risk pipeline (RED + CRITICAL): $108K
Forecast summary: Of $567K in open pipeline, only $212K — 37% — has fully verified contact data that meets the forecast standard. $347K is in AMBER deals where the contact is still reachable but data gaps exist, primarily missing direct phone numbers and a title change on the Zendesk renewal. $108K is at risk: the Highspot deal has a departed contact at Negotiation stage and the Salesloft deal has no contact at all. Neither should be in the forecast until a verified contact is assigned. To improve forecast confidence before the call: assign J.S. to the Highspot deal, find a Salesloft contact, and add direct phone numbers to the Zendesk and Seismic records.
Contacts verified live via Lusha connector, May 26, 2026. Names masked to initials.
Why use Lusha in Claude
A $567K pipeline that is 37% verified is not a $567K forecast — it’s a $212K forecast with $355K of varying degrees of risk attached. The Highspot CRITICAL flag changes what happens in the forecast call: the deal should not be discussed as a closing deal until a verified contact is in place. The Salesloft RED — no contact at all — is a deal that should never have been in the forecast in the first place. Both of these would have been presented as real pipeline in the forecast call without this check. The forecast summary gives the VP a specific number to lead with rather than a vague “some deals have data quality issues.”
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
Should I share this report with the board or just use it internally?
The forecast summary paragraph is written to be shareable — it’s specific enough for a board slide or a leadership briefing. “37% of pipeline is fully verified, $108K is at risk” is the kind of data point that frames a forecast conversation for any audience. Use the full table for internal RevOps review, the summary paragraph for the forecast call itself.
What if most of the pipeline is GREEN?
That’s the correct result to report — “87% of our open pipeline has verified contacts meeting the forecast standard.” That’s a signal the team is maintaining good CRM hygiene and the forecast is based on real data. Still worth running before every forecast call — one CRITICAL deal caught before the meeting is worth more than the 5 minutes the prompt takes.
Why is AMBER still in the forecast?
AMBER means the contact is still reachable but something is slightly off — a title change, missing phone, or a gap in activity. AMBER deals are worth working, not removing from the forecast. The flag is a coaching note for the rep: update the title in CRM, add the phone number, send a touch before the close date. Removing AMBER deals would understate the real pipeline.
How is this different from the data quality SLA report?
The data quality SLA report is an org-wide audit run monthly or quarterly — it measures compliance against a defined standard across all pipeline. This prompt is a pre-forecast check run before every forecast call — it produces a forecast-ready output with ACV split by confidence tier. Different cadence, different output format, different audience.
Can I run this for a single rep's pipeline before a 1:1?
Yes — paste one rep’s opportunities and the output scopes to that rep’s deals. Combined with the rep account data quality scorecard, this gives a manager a complete pre-1:1 picture: overall data quality score plus deal-level forecast risk.
Ready to build this?
Get started with Lusha and set up this play in minutes.