Deal review prep
@dealdesk/deal-review-prep
Prepare the weekly deal review: one page per deal with MEDDICC gaps, the real next step, risks, and the questions a manager should ask. Works from an opportunity export (HubSpot, Salesforce, or any CSV) plus notes, and ranks deals by what needs attention.
SkillRevOpsv1.0.0 (latest)
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1---
- 2name: deal-review-prep
- 3description: Prepare for the weekly deal review or pipeline call. Builds one page per deal with MEDDICC gaps (metrics, economic buyer, decision criteria, decision process, paper process, identified pain, champion, competition), the real next step with a date, risks, and the three questions a manager should ask, then ranks deals by what needs attention. Works from an opportunity CSV export from HubSpot, Salesforce, or any CRM, plus pasted notes. Use when the user says "prep my deal review", "get ready for pipeline review", "which deals are at risk", "MEDDICC check on my commit deals", or "one-pagers for Friday's forecast call".
- 4license: MIT
- 5---
- 7# Deal review prep
- 9Gives a manager or rep one honest page per deal before the weekly review. The point is to find the gaps early: a commit deal with no economic buyer is a best-case deal with optimism.
- 11## When to use
- 13- The day before a weekly deal review, forecast call, or QBR.
- 14- A rep wants a self-check on deals they plan to call commit.
- 15- Not for pipeline cleanup across hundreds of deals (use a hygiene kit for that). This is for the 5 to 25 deals that matter this week.
- 17## Inputs
- 191. An opportunity export at `data/opportunities.csv` (see the kit's `examples/opportunities.csv`). Useful columns, any names: id, name, owner, amount, stage, close date, forecast category, next step, next step date, last activity date, and one column per MEDDICC element if the CRM has them.
- 20 - HubSpot: export deals from a saved view with these properties.
- 21 - Salesforce: an Opportunities report with Next Step, Forecast Category, and your MEDDICC fields.
- 222. Optional notes in `data/notes/` (call notes, email threads, the rep's own update). Notes beat empty CRM fields.
- 233. Which deals: ask "all open deals closing this quarter", "my commit and best case", or a list. Default: forecast category Commit or Best Case, closing in the current quarter.
- 25Map the user's column names once and say which columns you used. If there are no MEDDICC columns, derive what you can from notes and mark the rest as unknown.
- 27## Steps
- 291. Load the deals and filter to the review set. Note today's date.
- 302. For each deal, score each MEDDICC element:
- 31 - **Strong**: specific and verified (a named role, a number, a date, met or confirmed).
- 32 - **Weak**: vague, unconfirmed, or from one source ("unconfirmed", "follow up", a title with no meeting).
- 33 - **Missing**: empty or unknown.
- 343. Check the next step. A good next step has an action, an owner, and a date within 14 days. "Follow up" with no date is missing.
- 354. Flag risks. Always check: close date in the past or within 14 days with a weak paper process; no activity in 14+ days; Commit with a missing or weak economic buyer or champion; amount changed without a stage change; competition unknown late in the cycle; close date moved before (if notes say so).
- 365. Rank deals: Commit with gaps first, then largest amount with gaps, then the rest.
- 376. Write `out/deal-review-<YYYY-MM-DD>.md` with the format below and show the summary table in chat.
- 39## Output format
- 41```markdown
- 42# Deal review, 2026-11-04
- 44| Deal | Owner | Amount | Close | Category | MEDDICC (8) | Top risk |
- 45| --- | --- | ---: | --- | --- | --- | --- |
- 46| Contoso Robotics: new logo | Rep B | $120,000 | 2026-12-15 | Best Case | 1 strong, 3 weak, 4 missing | No economic buyer, no dated next step |
- 48## Contoso Robotics: new logo ($120,000, Best Case, closes 2026-12-15)
- 50**Call:** keep as Best Case. Not commit until an economic buyer meeting is booked.
- 52| Element | Status | Evidence |
- 53| --- | --- | --- |
- 54| Metrics | Missing | No number on the pain |
- 55| Economic buyer | Missing | |
- 56| Champion | Weak | Ops manager, unconfirmed |
- 58**Next step:** "Follow up" (no date). Needs a dated, owned action.
- 59**Risks:** no activity for 23 days; two competitors and no decision criteria.
- 60**Ask the rep:**
- 611. Who signs, and when will you meet them?
- 622. What happens for them if they do nothing this quarter?
- 633. What is the next meeting on the calendar?
- 64```
- 66## Guardrails
- 68- Only use facts from the export and notes. Mark anything you inferred as "inferred".
- 69- Do not change any CRM record. If the user wants updates, list them as suggested edits.
- 70- Keep the tone coaching, not blaming. Gaps are questions for the rep, not verdicts.
- 71- Do not paste the whole export into chat. Summaries only.
