A Vainu playbook

The AI Pipeline Review

Playbook20 prompts33 pages · PDF

20 prompts for the weekly pipeline meeting, ready to copy into Claude or ChatGPT.

Prepare the review from what changed since last week
Inspect each deal against what the buyer said
Send actions with owners before people leave
Check once a month whether the forecast is getting closer

Get the playbook

What is inside

01
Before the meeting. Five prompts that collect what changed, so the meeting starts with questions.
02
In the meeting. Five prompts that put the buyer’s words next to the CRM record.
03
After the meeting. Five prompts that write the follow-up, so managers spend their time on coaching.
04
Once a month. Five prompts that check the forecast, the customers you win and next quarter’s coverage.

Who it's for

Primary

Sales leaders

Run a shorter review
Ask for the evidence behind each deal
Send actions before people leave

Primary

RevOps

Set the prompts up once
Keep stage history and next steps logged
Track forecast error over time

Secondary

AEs

Arrive with answers
See which deals are single-threaded
Get a reason to call stalled deals

Secondary

SDRs

Work the coverage-gap list
Use company events as openers

A sample card

Part 01 · Before the meeting

The weekly pipeline delta.

What changed in the pipeline since last week, in one table.

Prompt

Compare my open pipeline in [CRM] today with its state on [date of the last review]. List every deal that was added, closed won, closed lost, changed stage, changed amount by more than [10]%, or moved its close date. For each, show the owner, the value before and after, and the field that changed. Start with the three changes that move this quarter’s forecast the most.

You need: CRM
You get: A change table sorted by how much each change moves the forecast.
Watch for: If your CRM does not keep a history of amount and close-date changes, the prompt can only see today’s values. Turn field history on first.

Setup: 10 min
Time: ~45 min / week
Run in: Claude, ChatGPT
For: Sales leaders · RevOps

Every number has a source

Every number in the playbook comes from a named source, from Salesforce’s State of Sales report to HubSpot’s developer documentation. Each one is listed on the last page with its link.