agentleFS
jacobtop-tcgjacobtop-tcg/sales-engineering-skills/skills/stage-exit-criteria/SKILL.md

stage-exit-criteria

Skill0 starsChanged 12 days agoMITView on GitHub

Writes or audits sales stage exit criteria so that each gate requires a customer act with a checkable record, tied to the MEDDICC element it gives evidence for. Use when defining or revising a B2B sales process, checking whether a deal is ready to move stage, or reviewing why deals advance without buying progress.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask of each item: who did it, and where is it recorded?

    line 24
  2. Distinctive:

    Keep the seller work and internal checks needed to qualify the deal, and add the customer confirmation each criterion needs.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sales stage exit criteria

Exit criteria are the conditions a deal must meet before it moves to the next stage. A recap sent by a seller and a recap confirmed by a customer are different exit criteria. Keep necessary internal checks, and make the customer's confirmation explicit wherever a criterion is meant to show buying progress.

Ask for these inputs

  1. The current stage names and the exit criteria for each, as written.
  2. Where criteria are recorded (CRM fields, documents, emails).
  3. Whether the team uses MEDDICC or a variant.
  4. Any rules for how long a deal may sit in a stage.
  5. For a single deal: its current stage and the evidence the team has.

Step 1: Define each stage

For each stage, write four things, as Fleet's handbook does: a probability, a definition of one or two sentences, a timeline (how long a deal may stay before it is reviewed and possibly closed), and the exit criteria.

Step 2: Test every criterion with two questions

Ask of each item: who did it, and where is it recorded?

Distinguish the person who acts from the person who records it. A seller's CRM note can record a customer's confirmation. Sending a recap does not establish that confirmation by itself. Classify each criterion as a seller task or internal check, or as a customer act or agreement.

Step 3: Add the customer act

Keep the seller work and internal checks needed to qualify the deal, and add the customer confirmation each criterion needs. Examples of rewrites:

Seller-task criterionCustomer-evidence version
Recap email sent confirming pain points, stakeholders, next steps, timelineCustomer replies and confirms or corrects the pain points and timeline
Scoping meeting scheduledCustomer accepts the meeting and names who from their side will attend
Economic buyer identified in CRMEconomic buyer confirms what they can approve for this purchase and which business outcome would justify it
ROI measures determined and validatedCustomer confirms the figures the return on investment rests on

Step 4: Place MEDDICC evidence at the gates

MEDDICC has no stages of its own. Decide which elements need supporting evidence before each transition. Keep an unresolved element visible; entry into a later stage is not proof the gap was closed. A field labelled "decision criteria documented" still needs an identified source. If the customer agreed success criteria and a timeline for an evaluation, establish which purchase criteria that evaluation tests and which remain to be confirmed.

Step 5: Set what happens when a deal misses its criteria

Keep the deal in its stage until it meets the criteria, and set a deadline for deciding whether it should remain open. Set early-stage limits around the customer steps you expect instead of copying another company's day counts. Decide what restarts the clock, and specify what new customer commitment or completed step a CRM update must record to count. If the customer has agreed a future milestone, record its owner and date so a planned wait can be told apart from unexplained inactivity.

Output template

A suggested starting point for a contract-led sale. Adapt the stage names and thresholds.

To leave this stageThe customer hasMEDDICC elementWhere it is recorded
DiscoveryDescribed the problem in their own words and confirmed or corrected your recapIdentify painTheir reply to the recap
QualificationPresented the case internally and secured a decision-maker's agreement to the next stepChampionThe decision-maker's reply or the agreed step they take
QualificationConfirmed the figures the business case will rest onMetricsTheir email or the shared case
ScopingConfirmed the purchase criteria, their priorities and how the evaluation will test the relevant requirementsDecision criteriaTheir agreed criteria and evaluation plan
EvaluationConfirmed the authority to approve this purchase and the business outcome needed for that approvalEconomic buyerThe economic buyer's message or dated notes of their confirmation
EvaluationSaid which alternatives they are weighing, doing nothing includedCompetitionTheir words in the recap they confirmed
ProposalAgreed a close plan with owners and dates, approval and signature steps includedDecision process and paper processThe shared plan
NegotiationAgreed the business and legal terms, then signedNone: the deal closesThe signed contract and any purchase order

For each row, also record what the evidence establishes and what remains unconfirmed. A close plan agreed with the customer is a mutual action plan, and each customer step in it needs a named owner at the customer.

For an audit of an existing process, also produce a two-column list per stage: criteria without explicit customer confirmation, and criteria naming a customer action or agreement.

Checks

  • A criterion that a seller can complete alone does not show buying progress.
  • "Sent" (a recap, a contract for signature) is weaker than "confirmed" or "signed".
  • A criterion with no named record cannot be checked.
  • A deal in a late stage with an open early element should show that gap.
  • A stage clock that any CRM edit can restart, without a new customer commitment or completed step on record, cannot tell a planned wait from inactivity.

Based on: Sales stage exit criteria: examples from published processes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.