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

Editable workbook and filled example

Decide which opportunities deserve an action or forecast change using buyer evidence, stage exit criteria and unresolved dependencies.

Download editable Word workbook ↓

What you will complete

  • Review period and accountable owner
  • Stage definitions and evidence standard
  • Forecast decision to be made
  • Data cutoff and source
  • Excluded or stale records
  • Next review date

Use approved internal references rather than copying customer information into a public tool. A seller activity does not establish buyer progress. Record the evidence that would change the stage or date.

Fictional filled evidence record

Opportunity and claimed stageBuyer evidence and recencyMissing exit criterion
Fictional evaluation A; validation stageSponsor confirmed test question last weekNo buyer reviewer or test acceptance date

Fictional action record

Decision and rationaleBuyer next eventAction owner and due dateForecast consequence
Keep in validation; acceptance unconfirmedSponsor names test reviewerAccount lead; next joint meetingDo not infer close date from seller task

Decision and next review

Keep evaluation A in validation and mark its date unconfirmed. A test is scheduled, but the buyer has not agreed who accepts it or what passes.

Account lead secures a buyer-owned acceptance event. Review the forecast when that event is confirmed or the dependency remains unresolved.

The Word file includes editable response fields and blank tables. These examples are invented and do not represent a real buyer or employer.

See more fictional examples → · Open planning tools →