GTMGO TO MARKETPLAYBOOKS
← All playbooksRevenue operations · Field guide

Evidence-based pipeline review

Review deal evidence, buyer progress, and next decisions instead of narrating CRM stages.

When to use this

Use for a weekly forecast and coaching review when deal stage descriptions are obscuring buyer reality.

Before the working session

Run the process

01

Establish the math

Calculate remaining target and pipeline coverage using an explicit win-rate assumption. Segment by product, deal size, or stage where conversion differs.

02

Inspect buyer evidence

For each material deal, ask what the buyer did, who agreed to the decision path, what proof remains, and which approval or budget event is dated. Separate seller actions from buyer commitments.

03

Apply risk flags

Flag repeated close-date pushes, one-thread relationships, missing economic owner, silent evaluations, security or procurement not started, and dependence on one oversized deal.

04

Choose an intervention

For each exception, assign one next buyer-facing action, owner, date, and expected evidence. Record the forecast category change and revisit it next week.

Fictional worked example

Fictional example: A $120k opportunity is marked commit because a demo went well. The review finds no buyer-owned evaluation date and no security review. It moves to upside until the buyer confirms milestones and schedules the security intake.

Failure checks

Working worksheet

WEEKLY PIPELINE EXCEPTION REVIEW
Period / target / booked / remaining:
Qualified pipeline / win-rate assumption / coverage:
Segment or stage differences and source of rates:
Deal / value / current forecast category / previous category:
Buyer decision and date / evidence / approval path:
Risk flag and evidence gap:
Next buyer action / owner / due date / evidence expected:
Forecast impact / review date:

See more fictional examples → · Open planning tools →