# Pipeline stage exit criteria: a template for B2B teams

https://krokul.com/en/blog/pipeline-stage-exit-criteria/ · Krokul Team · Updated 2026-11-13

A head of sales who reads the same forecast with different stage names in every rep’s head needs one rule per stage. This template defines what must be true before a B2B deal moves on.

**Short answer.** Exit criteria are the facts that must be true before a B2B deal leaves a pipeline stage. Write two to four verifiable criteria per stage, each one a field or a document a colleague can check, such as a confirmed budget or a named decision maker, and keep early stages lighter than late ones.

## When a B2B pipeline needs exit criteria

Exit criteria are the second layer of a working pipeline, after the stages themselves, and the guide to [building a B2B sales pipeline that predicts revenue](https://krokul.com/en/blog/topics/sales-pipeline/) treats them as the step that makes stage probabilities believable. A stage without a rule is a column name, and every rep fills it with a different meaning.

- Two reps put deals in Proposal sent, one after a call and one after a signed scope.
- The forecast uses stage probabilities, yet half of the deals in late stages have no budget on record.
- A deal comes back from a colleague on holiday and nobody knows what was agreed.
- New hires ask what “qualified” means and get three different answers.
- Deals sit in Negotiation for weeks because nobody can say what would move them out.

- **Exit criteria** — Exit criteria are the conditions that must be true before a deal may leave a pipeline stage for the next one.
- **Stage gate** — A stage gate is a check on the move between two stages: the deal passes when its exit criteria are met and waits when they are not.
- **Verifiable criterion** — A verifiable criterion is a statement a colleague can confirm from a record, such as an amount, a date or a document, without asking the rep.

## How to write exit criteria for each pipeline stage in five steps

Writing exit criteria for a pipeline stage means turning the stage’s purpose into a short list of facts that someone else can check. The steps below take about an hour per pipeline with the sales team in one room.

### 1. Name the question each stage answers

Give every stage one question that its exit answers. Inquiry asks whether this is a real company with a real need, Qualified asks whether the budget, the decision maker and the timing exist, and Proposal sent asks whether the client has seen a priced offer.

A stage that answers no question is a candidate for merging with its neighbour.

### 2. Turn each answer into checkable facts

Write the facts that prove the answer, each as a field or a document. “Budget confirmed” becomes an expected amount and a date by which the client decides. “Decision maker known” becomes a contact on the deal with that role.

Reject phrases such as “good fit” or “client is interested”. Nobody else can verify them, so they cannot gate a move.

### 3. Keep to two to four criteria per stage

Four criteria are the working ceiling. Five or more turn the pipeline into a form, reps start filling fields with placeholders, and the data loses its value.

Keep the early stages light. The first stage can ask for a company and a source, and each later stage adds the next piece of evidence.

> **Tip.** Collect each fact once. A criterion that repeats a field from an earlier stage is already covered by that stage.

### 4. Add the questions the client has to answer

Some facts come from the client, such as budget, timing and who signs. Send them as a short questionnaire after the first call and treat complete answers as one criterion.

The guide on qualifying B2B inquiries with a shared questionnaire shows how to write those questions so that clients answer them.

### 5. Test the criteria on ten closed deals

Take five won and five lost deals and ask when each criterion became true. A criterion that was already true for a deal that was lost at once removes nothing, and a criterion missing from most won deals is too strict.

Adjust the list, then publish it to the team as a one-page table and move to the next pipeline.

## What is a good exit criteria template for a B2B sales pipeline

A good template lists one row per stage with the criteria, the place where each fact is recorded and the person who owns it. Copy the table and replace the stage names and the facts with your own process.

Example: exit criteria template for a six-stage B2B sales pipeline:

| Stage | Exit criteria (all true) | Where it is recorded | Owner |
|---|---|---|---|
| Inquiry | Company named; source known; responsible rep assigned | Company, source and responsible fields on the deal | Rep |
| Qualified | Expected amount set; decision maker added as a contact; client answered the qualification questions | Expected amount, contact, questionnaire | Rep |
| Needs analysis | Requirements written in a comment; planned close date set; next contact date set | Comment, planned close date, next contact | Rep with presales |
| Proposal sent | Priced proposal attached to the deal; currency set; discount recorded if any | Quote document, currency and discount fields | Rep |
| Negotiation | Open objections listed in a comment; next contact within seven days; amount updated after changes | Comment, next contact, expected amount | Rep |
| Contract signed | Signed contract on file; final amount equals the contract; start date known | Contract document, expected amount, planned close date | Rep and head of sales |

Read the table from the right. Each criterion lands in a place where a colleague can find it, and a criterion without a place is a wish. Companies with tenders or long onboarding add a second pipeline with its own rows instead of stretching this one.

## How to check a deal against its exit criteria on an example

The example checks five deals that reps want to move to Proposal sent. That stage asks for three criteria: a priced proposal, a decision maker on the deal and a next contact date.

Example: five deals checked against the three exit criteria of Proposal sent:

| Deal | Priced proposal | Decision maker | Next contact date | Criteria met |
|---|---|---|---|---|
| Deal A | Yes | Yes | Yes | 3 of 3 |
| Deal B | Yes | No | Yes | 2 of 3 |
| Deal C | Yes | Yes | No | 2 of 3 |
| Deal D | No | No | Yes | 1 of 3 |
| Deal E | Yes | Yes | Yes | 3 of 3 |

Pass rate = deals meeting every criterion ÷ deals checked. Two of five deals pass, which gives 40%. The other three go back with a named gap: Deal B needs a decision maker, Deal C needs a date and Deal D needs a proposal. The 40% shows how much of the pipeline in this stage was real before the check, and the share rises as reps learn to prepare the facts before they drag a deal.

## Which exit criteria mistakes let weak deals through

- Writing opinions as criteria. “Client seems keen” cannot be checked, so replace it with a date the client agreed.
- Setting ten criteria on the first stage. Reps skip the pipeline for quick inquiries, so keep the first stage to company, source and responsible rep.
- Using the same criteria on every stage. Each stage adds a new fact, so a later stage that repeats an earlier row adds no control.
- Leaving the rules on paper. A rule that lives only in a slide is forgotten by the next quarter, so put it where the deal is edited.
- Never reading the exceptions. A gate that is skipped often points at a wrong criterion, and a gate nobody skips may be too soft.

## A checklist for reviewing exit criteria each quarter

Review the criteria four times a year with the data from closed deals. The conversion by stage described in the guide on funnel conversion by stage tells you which stage to review first.

- Every stage has one question and two to four checkable criteria.
- Every criterion has a field or a document where it is recorded.
- The stage with the lowest conversion is reviewed first.
- Criteria that were true for almost every lost deal are removed.
- Criteria missing from most won deals are made lighter or moved to a later stage.
- New reps get the one-page table on their first day.

## How Krokul enforces exit criteria on every move

Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. A stage there has a Required fields setting in its Stage discipline section, and a deal does not enter the stage while those fields are empty.

An admin picks the fields in the pipeline settings. The list covers the expected amount, planned close date, next contact date, contact, client company, source, responsible person, comment, name, currency and discounts, together with the company’s own custom fields and a “qualification complete” condition for the questionnaire from the template above. The server checks the move, so a drag on the board and a change in the deal card meet the same rule. A zero or a switched-off toggle counts as filled, and a required field cannot be hidden from the card.

When a rep drags a deal and fields are missing, the board opens a form with exactly those fields. The rep fills them and the deal moves in the same step. A deal that jumps over a stage also meets the requirements of the open stages it skipped, grouped by stage, and a move backwards adds no requirements from the stages in between. Imports, automations and inbound integrations are not held by the gate, so incoming inquiries keep flowing.

![Pipeline settings: stage list with probability and day limit, and a badge with the number of required fields on Proposal sent](https://krokul.com/img/en/blog/pipeline-stage-exit-criteria-settings.webp)

Conditional rules cover the exceptions. A rule such as “when the amount is above 100,000, require a comment” adds fields only for those deals. Admins and managers see the gate at work in the funnel report, where a block lists attempts to skip required fields by person for the chosen period. The page on [pipelines with stage gates in Krokul](https://krokul.com/en/solutions/pipelines/) shows how this fits with stalled deals and lost reasons.

## Frequently asked questions

### How many exit criteria should a stage have?

Two to four. Fewer than two gives no control, and more than four pushes reps to fill fields with placeholders. Early stages can use two and late stages four.

### What is the difference between exit criteria and entry criteria?

Entry criteria describe what must be true when a deal arrives, and exit criteria describe what must be true when it leaves. In a linear pipeline the exit of one stage is the entry of the next, so write one list and call it exit criteria.

### Should exit criteria block a deal or only warn?

Block on the facts that feed the forecast, such as the amount, the date and the decision maker, and warn on the rest. A rule that blocks too much teaches reps to avoid the pipeline.

### Do exit criteria slow reps down?

They add a minute at the move and remove the rework that follows a weak deal. Keep the early stages light so that a fast inquiry reaches the pipeline with a company, a source and an owner.

### Who owns the exit criteria?

The head of sales owns them, with reps and presales proposing changes at the quarterly review. One owner keeps the table consistent across pipelines.

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs
