Deal Inspection Brief

Walk into the deal review with the inspection already done — MEDDIC gaps, multi-threading, competitor footprint, and the one question that exposes the risk.

RevOps - Deal inspection

MEDDIC gaps, competitor footprint, and the question that exposes the risk

3
Missing MEDDIC elements
Pressure-tested with HG data
Datadog confirmed installed via technographic.
Economic buyer not yet identified.
ElementStateEvidence
MetricsKnowndeal context
Econ buyerMissingno exec contact found
CompetitionKnownDatadog installed (HG tech)
The one question
'Who signs the PO when the VP Eng's budget runs through finance?' — the economic buyer is the biggest Missing element, and the deal can't close without them.

Overview

Produce a single-deal inspection brief that combines pasted CRM deal context with HG firmographic, technographic, and intent enrichment — surfacing MEDDIC/qualification gaps, the competitor's installed footprint, and the multi-threading state so a manager runs a sharper deal review.

Use cases

  • Deal reviews that interrogate, not recap

    Most deal reviews are the rep reading the CRM aloud. This brief arrives with the qualification already scored and the account already fact-checked against HG data, so the manager spends the meeting on the actual gap.

  • Catch the phantom competitor read

    A rep says 'we're up against Datadog.' Technographic either confirms Datadog is installed or shows it isn't — turning a hallway rumor into a fact the review can act on.

View workflow prompt
# Deal Inspection Brief

## Parameters

- `{{domain}}` *(required)* — The deal's account domain. Example: `cisco.com`
- `{{deal_context}}` *(required)* — Pasted deal context (stage, amount, close date, champion, known competitor, current next step). Example: `Stage: Proposal; $250k; close 2026-06-30; champion: VP Eng; competitor: Datadog`
- `{{qualification_framework}}` *(optional)* — The qualification framework to inspect against. Example: `MEDDIC`

## Purpose
Inspect a single deal at {{domain}} against {{qualification_framework}} using {{deal_context}} as the rep's stated picture, then pressure-test it with HG firmographic, technographic, and intent data — so the deal review interrogates the gaps instead of re-reading the CRM.

## Process
1. **Frame the deal** — restate {{deal_context}} as a one-paragraph deal snapshot. Flag any qualification element the rep did not provide.
2. **Qualification gaps** — score the deal against {{qualification_framework}} (default MEDDIC). For each element, mark Known / Assumed / Missing based only on what {{deal_context}} states.
3. **Account reality check** — `company_firmographic` + `company_technographic` for {{domain}} to confirm the account can actually buy at this size and whether the named competitor's tech is installed (validates or contradicts the competitive read).
4. **In-market check** — `company_intent` to confirm the account is researching the category; a Proposal-stage deal with no intent is a yellow flag.
5. **Multi-threading** — `contact_search` for the buying committee; compare to the champion named in {{deal_context}} and list who is missing.

## Output Format
Markdown with:
- `# Deal Inspection — {{domain}}`
- `## Deal Snapshot` (one paragraph)
- `## Qualification Scorecard` (table: element | Known/Assumed/Missing | evidence)
- `## Account Reality Check` (firmographic + competitor footprint)
- `## Multi-Threading Gaps` (committee map vs. current contacts)
- `## The One Question` (the single question that most exposes the deal's risk)

## Quality Checklist
- Every Known/Assumed/Missing call cites either {{deal_context}} or an HG tool
- Competitor footprint claim cites `company_technographic`
- The 'one question' targets the biggest Missing element, not a generic close question
- No invented champion sentiment — only what {{deal_context}} states