Run a pipeline review

Pipeline review automation is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.

A pipeline review is useful in proportion to how uncomfortable it is: the job is to find the deals that are slipping quietly, not to narrate the ones everybody already knows about.

What is in this skill

namemeddicc
descriptionThe MEDDICC qualification framework and what each letter requires before a deal can advance. Use when assessing deal health, preparing a forecast, writing a deal review, or deciding whether a deal is real.
allowed-toolsnone — this skill adds judgement, not reach
compatibilityZealos, Claude Code, Cursor, Codex and any client that reads SKILL.md
licenseFree to use and edit

How it works

  1. 1Sort by staleness rather than by value, because the largest deal in the pipeline is rarely the one nobody has touched in three weeks.
  2. 2Flag every deal whose close date has moved more than once, and say how many times — serial date movement is the single best predictor of a miss.
  3. 3Name deals with no agreed next step. An empty next-step field is not missing data; it is the finding.
  4. 4For each flagged deal, state the one question that would resolve it, so the review produces actions rather than commentary.

The skill itself

---
name: meddicc
description: The MEDDICC qualification framework and what each letter requires before a deal can advance. Use when assessing deal health, preparing a forecast, writing a deal review, or deciding whether a deal is real.
---

# MEDDICC

A deal is qualified when every letter has evidence, not a guess. Say which
letters are unevidenced rather than filling them in optimistically — a
confidently-wrong qualification is worse than an obviously incomplete one.

| | Requires |
|---|---|
| **M**etrics | A number the buyer stated, in their units. "Two days per rep per week", not "efficiency gains". |
| **E**conomic buyer | A named person who can sign without asking anyone. If we have not spoken to them, say so. |
| **D**ecision criteria | What they will compare us on, in their words and their order. |
| **D**ecision process | The actual steps: security review, legal, procurement, board. With dates. |
| **I**dentify pain | What breaks if they do nothing. If nothing breaks, there is no deal. |
| **C**hampion | Someone who sells internally when we are not in the room, and who has something to gain. Tested by asking them to do something. |
| **C**ompetition | Including "do nothing" and "build it ourselves", which win more often than any vendor. |

## How to report

For each letter: **evidenced** (quote the source — call, email, note),
**assumed** (say so), or **missing**.

Then state the single highest-value unknown and the question that resolves it.
One question, not a list.

## Red flags

- Champion who will not introduce you to the economic buyer.
- Metrics we authored rather than heard.
- A decision process with no dates.
- "Everyone loves it" with no named detractor. There is always a detractor.

Who uses it

Sales manager

The Monday review starts from a list of what is slipping rather than a rep-by-rep walk through deals you already discussed last week.

Account executive

You find out a deal has gone quiet before your manager does, which changes the conversation from defending it to fixing it.

Founder

With no sales manager to run the ritual, the ritual runs itself and lands in Slack every Monday morning.

Frequently asked questions

What should a pipeline review flag?

Stale deals, close dates that have moved repeatedly, deals with no next step, and any stage whose exit criteria are unevidenced. Everything else is reporting, not review.

Can it post to Slack?

Yes, if the agent has Slack connected. The skill decides what is worth saying; the agent decides where it goes.

Does this replace a forecast call?

It replaces the first twenty minutes of one — the part spent establishing what the numbers are before anyone discusses what to do about them.

Related skills

Summarize calls and update the CRM

Post-call automation turns a recorded conversation into the three things that outlive it: the commitments each side made, the fields that changed, and the follow-up that has to go out today.

MeetingsCRMZoom/call-recap-format

Brief yourself before every call

A pre-call brief is worth writing only if it changes what you ask: who is in the room, what they are measured on, what happened last time, and the one question you cannot afford to leave without answering.

CoachingMeetingsAccounts/discovery-questions

Run an AI SDR play on new leads

An AI SDR agent is only as good as the definition of a good customer it is working from, which is why the fit criteria belong in a written skill rather than buried in a prompt nobody can find.

ProspectingSDRCRM/our-icp

Triage your inbox by deal impact

AI email triage is worth having only when it sorts by consequence rather than by recency: what blocks a deal, what someone is waiting on you for, and what can be read at the end of the week.

EmailGmailAccount executives/email-rules

Log a call without inventing fields

CRM data hygiene survives AI only if one rule is written down first: a field left blank is a known unknown, while a field filled in by inference is an unknown unknown that will be reported on as fact.

CRMHubSpotSalesforce/crm-field-conventions

Qualify a lead against our ICP

Qualification is a claim about evidence, not a score: a deal is qualified when every criterion has a source you can quote, and unevidenced criteria are named rather than filled in optimistically.

DealsProspectingCRM/meddicc

Skills, in your workspace

Write it once. Every agent follows it.

Twelve built-in skills ship with every workspace, and you can draft your own with AI or import any public SKILL.md from GitHub.

7-day free trial. Set up in minutes. Cancel anytime.