# Deal Review Questions: Ask What the Buyer Did, Not What the Rep Feels

https://salesbond.app/blog/deal-review-questions-buyer-action/
Published: 2026-10-01 · Updated: 2026-10-26

The one deal review question that replaces most of the others: what has the buyer done since we last looked at this deal? A meeting they showed up to, a stakeholder they brought in, a document they signed, a question they answered on their own time. If the honest answer is “nothing”, then the stage, the close date and the forecast category are opinions, and the review should say so out loud.

A deal review is a manager and a rep going through one open deal to test whether its stage, close date and forecast category are backed by what the buyer has done. Some teams call it deal inspection. Everything else in it is a way of checking that first answer against the record. Below are six questions for one deal, each paired with the place in Pipedrive where the answer should already be sitting, so you read first and ask only about the gaps. The set is built for a manager with three to fifteen reps who has to get through the whole pipeline in one sitting, not for an enterprise forecast call with a slide per account.

## Why “what did the buyer do” beats “what’s your next step”

Most question lists for deal reviews are rep-facing. What’s your next step? How confident are you? What’s the pain? Those questions measure the rep’s story, and a rep with a good story and a quiet buyer sounds exactly like a rep with a real deal.

Buyer action is harder to narrate. Either the finance lead joined the call or she didn’t. Either [the security questionnaire came back](https://salesbond.app/blog/sales-security-questionnaire-pipedrive/) or it is still sitting in their inbox. You can argue about confidence for ten minutes, you cannot argue about whether a meeting happened.

If the buyer has a shared page for the deal, our note on a [digital sales room for a small team](https://salesbond.app/blog/digital-sales-room-small-team-crm-tracking/) covers what to read from it.

If you want a short list of what counts as buyer action, we keep it to [six buying signals worth logging](https://salesbond.app/blog/buying-signals-pipedrive-deals/) in Pipedrive.

We think the manager’s job in a review is to stand in for the buyer. The rep already represents the deal. Somebody has to represent the evidence, and the only person in the room who can do that without taking it personally is you.

One boundary before the questions. This is the per-deal question set, the part that repeats for every deal you open. How the meeting itself is shaped lives in the [15-minute weekly pipeline review](https://salesbond.app/blog/weekly-pipeline-review-15-minutes/), and the rep’s development conversation belongs in a [1-on-1 that isn’t a status update](https://salesbond.app/blog/sales-1-on-1-agenda/). Keep them apart. A review that turns into coaching takes forty minutes and covers four deals.

## Read the deal before you ask

Open the deal in Pipedrive before the rep starts talking. Not during, before. The record will answer some of the questions for you and will tell you which ones are actually worth asking.

The same habit works for the rep before a customer call: [a ten-minute prep from the deal record](https://salesbond.app/blog/ai-sales-call-prep-pipedrive/).

Start with the activities. The last activity marked done tells you when anything happened at all, and its type tells you what: a call is not an email, and an email you sent is not a reply you received. Then the next planned activity. Does it have a date, and does the subject line contain a verb and a person, or does it just say “follow up”? If the next step is vague, you already know one of your questions.

Then the people on the deal: the linked person and the Participants section in the deal’s sidebar. One name since discovery is a fact worth noticing before anyone says the word “champion”. If there is only one name, check whether that person is a [sales champion](https://salesbond.app/blog/sales-champion-pipedrive-deals/) or only a polite contact. Then the synced emails and notes from the last week, with one thing in mind: who sent the last message, us or them. Then the stage history: when the deal entered its current stage, and how many times the expected close date has moved since the deal was created. Since the August 2026 update, Pipedrive shows the [days in stage on the deal progress bar](https://salesbond.app/blog/pipedrive-progress-bar-days-in-stage/), so the first half of that takes one glance.

That is about two minutes of reading per deal, and it changes the conversation. You walk in knowing which of the six questions the record already answers and which it doesn’t. Often it is only one.

## Six deal review questions and the Pipedrive field that answers each

![Six deal review questions, each paired with the place in Pipedrive where the answer already lives](https://salesbond.app/wp-content/uploads/2026/10/deal-review-questions-2.png)

1. What has the buyer done since the last review? Read the activities marked done and the synced emails, but read them from the buyer’s side. A good answer lists things the buyer did: they replied, they forwarded, they booked, they introduced. A weak answer lists things we did: we sent, we called, we left a message. If the only activity in the window is outbound, the answer to this question is “nothing”, however busy the rep has been. This is the question that decides whether the other five are worth asking.
2. Who on their side is involved now, and who is missing? The linked person and the deal’s Participants answer the first half. If that is still one person at proposal stage, the deal is [single-threaded](https://salesbond.app/blog/single-threaded-deals/), and the question becomes who the rep has asked to meet and what the answer was.
3. What is the next step, and did the buyer agree to it? Where it lives: the next planned activity, with a date. The test is whether the step is on the buyer’s calendar as well as the rep’s. “Send the revised quote Tuesday” is our step. “Call with their ops lead Tuesday, invite accepted” is a shared step. The [next-activity habit](https://salesbond.app/blog/pipedrive-next-activity/) makes this a ten-second check instead of a conversation.

On question 3, note that [an opened proposal link is not a step](https://salesbond.app/blog/pipedrive-smart-docs-view-tracking/) either: it is a view with no name on it, as we explain for Smart Docs.

1. What problem are they solving, in their words? “Interested in our product” is not a problem. “Two reps re-key every order into the ERP and the owner found out last month” is a problem, and a deal with that sentence in it’s notes behaves differently from one without it. You find it in the discovery notes, or in a custom field for pain if the team keeps one.
2. How will they decide, and what has to happen before a signature? You are looking for a sequence with names in it: security review, legal, the budget owner, procurement. That sequence belongs in the deal notes or in a [one-page mutual action plan](https://salesbond.app/blog/mutual-action-plan-small-teams/) attached to the deal. If there is nothing, don’t try to build it in the review. Ask the rep to go and ask the buyer, and move on to the next deal.
3. Why this stage, and why this close date? The stage history and the expected close date hold the record here. “Are you confident” invites a feeling. Ask instead which buyer action put this deal in this stage. A deal in negotiation where the buyer has not seen a price is in the wrong stage. A [close date that has moved twice](https://salesbond.app/blog/pushed-close-dates-pipedrive/) without a buyer action in between is a guess with a calendar attached. The answer to question one usually settles this one too, which is why it comes first.

Six questions, but you will rarely ask all six about one deal. The record answers two or three before the rep opens their mouth. You ask about the gaps, and you ask question one every single time.

## A weak answer and a strong answer to the same question

Take a made-up deal: Northwind, proposal stage, close date at the end of the month. You ask what the buyer has done since last week.

Weak answer: “They’re really engaged. I spoke to Dan last Thursday and he said it’s looking good, they just need to get it in front of the VP. I’m following up on Friday.”

Read it again and count the buyer’s actions. There are none. Dan talking is not Dan doing. The VP is a plan, not a person, and she is not a participant on the deal. The follow-up is ours. Every verb in that answer belongs to the rep or to a feeling, and yet it sounds fine, which is exactly the problem with rep-facing questions.

Strong answer: “Dan forwarded the proposal to their VP of Operations on Tuesday and copied me. She replied the same day asking about the onboarding timeline. I’ve booked a short call with both of them for Monday; the invite’s accepted and it’s in the deal.”

Three buyer actions, a new stakeholder who now belongs in the deal’s Participants, and a next step on the buyer’s calendar. The deal may still slip. But it is a deal, and the stage and close date have something underneath them.

There is a third answer, and it beats the weak one: “Nothing since last week. I’ve sent two emails and left a voicemail.” That is an honest reading of the record, and it gives you more to work with than enthusiasm does. The rep is not the problem here; the deal is. Which brings you to the decision.

## When the review ends with a status change, not a plan

A review that ends with “okay, chase them” has produced nothing the buyer can see. If the answer to question one is “nothing” for the second review in a row, the deal does not get a plan. It gets a decision, and the decision is one of four.

Move it back a stage, to the last stage the buyer’s actions actually support. Or keep the stage, push the close date and drop it out of [commit](https://salesbond.app/blog/commit-vs-best-case-forecast/) so the forecast stops leaning on it. Or [mark it lost with a reason](https://salesbond.app/blog/when-to-close-a-deal-lost/), which is the right call more often than it feels. Or keep it as it is, with a dated test the buyer has to pass: “if the VP has not taken the call by Friday, it’s lost”, written into the next activity so the test runs itself.

Which of the four depends on whether the deal is [stalled or already dead](https://salesbond.app/blog/stalled-deals-vs-dead-deals/), and the difference is mostly a question of whether the the buyer has gone quiet after acting or never acted at all. Either way, moving a deal back a stage is not a punishment for the rep. It is bookkeeping. The stage was wrong, and now it is right.

Two things stop managers from doing this. The first is that it feels harsh in front of the team. It isn’t, if the rule is the same for everyone and is announced before the review, not during it. The second is that the forecast number drops. It was going to drop anyway, just later and with less warning. If your team scores deals, the six questions above are what a [deal health score](https://salesbond.app/blog/deal-health-score/) is made of; the review is where the score meets a person who can act on it.

None of this needs a slide or a second meeting. It needs a manager who is willing to say “the buyer hasn’t done anything” out loud, and a rep who learns to say it first.

## FAQ

### What is a deal review?

One manager, one rep, one open deal, and one test: are the stage, the close date and the forecast category backed by what the buyer has actually done? It is narrower than a pipeline review, and it is not a coaching session.

### What is the difference between a deal review and a pipeline review?

A pipeline review looks across all open deals for coverage, movement and slippage. A deal review opens one deal and asks for evidence. On a small team both fit in one [weekly meeting](https://salesbond.app/blog/weekly-pipeline-review-15-minutes/): the pipeline view picks the deals, and the six questions get asked about each.

### Which deals need a deal review?

Every deal in commit, every deal with a close date this month, and any deal where the buyer has done nothing since the last review. The rest can wait a week.