How should a 2027 sales org define pipeline stages?

Question

Pulse RevOps · The Machine · Accepted Answer

## Direct Answer

A 2027 sales org defines pipeline stages by **mapping 5 to 7 stages that reflect buyer commitment levels, attaching explicit entry-and-exit criteria to each stage, and applying weighted probabilities for forecast purposes**. Pavilion's 2026 Pipeline Stage Benchmark of 287 GTM teams set the modal at **6 stages** with weights of 10/25/50/75/90/100 percent. The 2027 best practice: stages reflect **what the buyer has done**, not what the seller has done; transitions require **objective evidence**, not seller opinion; the same stage map applies across all segments with optional sub-stages for enterprise complexity. The CRO and VP RevOps publish the stage map; RevOps audits stage hygiene monthly; first-line managers enforce stage discipline in pipeline reviews. Without precise stage definitions, forecasts wobble, coaching becomes vague, and AEs game the stages to please their managers.

## 1. The 2027 Standard 6-Stage Map

### 1.1 Stage definitions

- **Stage 1 — Qualification (10 percent weighted)**: Lead qualified as ICP fit; initial buyer engagement; named champion identified.
- **Stage 2 — Discovery (25 percent)**: Pain validated; economic buyer engaged; budget timeline confirmed; named decision criteria captured.
- **Stage 3 — Evaluation (50 percent)**: Technical validation in progress; MEDDPICC fields complete (Metrics, Economic Buyer, Decision Criteria, Decision Process, Pain, Champion, Paper Process, Competition); proposal in progress.
- **Stage 4 — Proposal (75 percent)**: Proposal sent; mutual close plan agreed; champion advocating internally; identified procurement process.
- **Stage 5 — Negotiation (90 percent)**: Verbal yes; contracts in legal review; security and procurement substantially complete.
- **Stage 6 — Closed Won (100 percent)**: Counter-signed contract.

### 1.2 The weighting logic

Weighted probabilities reflect historical conversion rates from each stage. The 2027 modal weights (10/25/50/75/90/100) reflect Pavilion's 2026 benchmark across B2B SaaS:

- 10 percent of Stage 1 deals close.
- 25 percent of Stage 2 deals close.
- 50 percent of Stage 3 deals close.
- 75 percent of Stage 4 deals close.
- 90 percent of Stage 5 deals close.

If your historical data shows different conversion rates, adjust weights accordingly. A common 2027 pattern in enterprise B2B SaaS: 8/22/45/68/85 weighted because longer cycles produce slightly lower per-stage conversion.

```mermaid
flowchart TD
    A[Lead arrives] --> B[Stage 1 Qualification 10 percent]
    B --> C{Pain validated?}
    C -- Yes --> D[Stage 2 Discovery 25 percent]
    C -- No --> E[Disqualify]
    D --> F{Technical eval started?}
    F -- Yes --> G[Stage 3 Evaluation 50 percent]
    G --> H{Proposal sent?}
    H -- Yes --> I[Stage 4 Proposal 75 percent]
    I --> J{Verbal yes?}
    J -- Yes --> K[Stage 5 Negotiation 90 percent]
    K --> L[Stage 6 Closed Won 100 percent]
```

## 2. Entry And Exit Criteria

### 2.1 Why explicit criteria matter

Without explicit entry-and-exit criteria, AEs move deals based on optimism. Pavilion's 2026 stage-hygiene research found that **explicit criteria correlate with 28-percent better forecast accuracy** than narrative-based stages.

### 2.2 The 2027 criteria template

For each stage:

- **Required activities** (e.g., "Discovery call completed with economic buyer").
- **Required artifacts** (e.g., "Mutual action plan documented").
- **Required data fields** (e.g., "MEDDPICC fields populated above 80 percent").
- **Required external evidence** (e.g., "Email reply from champion confirming next step").

### 2.3 Example — Stage 3 Evaluation entry criteria

To enter Stage 3:

- Pain validated and quantified in dollars or time.
- Economic buyer engaged (call or email confirmation).
- Named decision criteria documented.
- Budget timeline confirmed.
- Technical validation start date scheduled.

To exit Stage 3 (move to Stage 4):

- Proposal sent.
- Mutual close plan accepted by champion.
- Champion confirmed advocacy.

### 2.4 Audit and enforcement

RevOps audits 30 deals per month sampled across regions and segments. Deals violating stage criteria (e.g., Stage 4 deal with no proposal sent) get flagged. First-line managers correct the AE in their next 1:1.

## 3. Segment And Motion Variations

### 3.1 Velocity SMB

SMB velocity deals (under US$25K ACV, under 30-day cycles) use a **compressed 4-stage map**:

- Stage 1 — Inquiry (25 percent).
- Stage 2 — Demo (50 percent).
- Stage 3 — Proposal (80 percent).
- Stage 4 — Closed Won (100 percent).

Forcing SMB through 6 stages produces noise.

### 3.2 Enterprise complexity

Enterprise deals (US$200K+, 6+ month cycles) sometimes use **sub-stages within Stage 3 Evaluation**:

- Stage 3A — Technical Validation.
- Stage 3B — Security Review.
- Stage 3C — Legal Review Started.

Sub-stages produce more granular pipeline visibility for long cycles.

### 3.3 PLG-led motion

PLG-led deals add a **Stage 0 — Product Trial**:

- Stage 0 — Trial Active (5 percent w

How should a 2027 sales org define pipeline stages?

Direct Answer

1. The 2027 Standard 6-Stage Map

1.1 Stage definitions

1.2 The weighting logic

2. Entry And Exit Criteria

2.1 Why explicit criteria matter

2.2 The 2027 criteria template

2.3 Example — Stage 3 Evaluation entry criteria

2.4 Audit and enforcement

3. Segment And Motion Variations

3.1 Velocity SMB

3.2 Enterprise complexity

3.3 PLG-led motion

4. Common Stage Design Mistakes

4.1 Mistake — too many stages

4.2 Mistake — stages defined by seller activity

4.3 Mistake — narrative stage transitions

4.4 Mistake — same weights across all segments

4.5 Mistake — no closed-lost analysis

5. Stage Maintenance Over Time

5.1 Annual review

5.2 Continuous calibration

5.3 The CRO scorecard

FAQ

Sources

How should a 2027 sales org define pipeline stages?

Direct Answer

1. The 2027 Standard 6-Stage Map

1.1 Stage definitions

1.2 The weighting logic

2. Entry And Exit Criteria

2.1 Why explicit criteria matter

2.2 The 2027 criteria template

2.3 Example — Stage 3 Evaluation entry criteria

2.4 Audit and enforcement

3. Segment And Motion Variations

3.1 Velocity SMB

3.2 Enterprise complexity

3.3 PLG-led motion

4. Common Stage Design Mistakes

4.1 Mistake — too many stages

4.2 Mistake — stages defined by seller activity

4.3 Mistake — narrative stage transitions

4.4 Mistake — same weights across all segments

4.5 Mistake — no closed-lost analysis

5. Stage Maintenance Over Time

5.1 Annual review

5.2 Continuous calibration

5.3 The CRO scorecard

FAQ

Sources

What does the score mean?