Score every open opportunity for data completeness before the forecast

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

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

Replacement found: J.S., VP Revenue Operations — j.s@[h***s***].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

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

GREEN — forecast with confidence

Forecast exposure by confidence tier:

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 [Customer support SaaS] renewal. $108K is at risk: the [Sales enablement SaaS] deal has a departed contact at Negotiation stage and the [ Sales engagement SaaS] 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 [Sales enablement SaaS] deal, find a [Sales engagement SaaS] contact, and add direct phone numbers to the [Customer support SaaS] and Seismic records.

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