FrameworkBusiness Cases

The 60-Second Deal Review

The typical deal review takes an hour and still misses the risk. This one takes a minute, because it reads a three-sentence deal story and seven yes/no questions on what the buyer has actually done.

By Nate Nasralla6 min read
The short answer

A 60-second deal review swaps the hour-long "walk me through this one" for two parts: a three-sentence deal story (the change, the named project and its date, and the differentiator the buyer confirmed) and seven yes/no questions on what the buyer has done. It's fast because the evidence is specific, and the earliest no tells the manager exactly what to coach next.

On this page
    Questions answered

    Frequently asked questions

    What should a deal review include?

    Two things: a short deal story and the evidence behind it. The story covers what’s changing in the buyer’s business, which executive funded which project by what date, and the differentiator the buyer confirmed. The evidence is seven yes/no questions on what the buyer has done, from a written problem statement to a backdated plan they’re sticking to.

    How do you use this in a weekly pipeline review?

    Have each rep read their three sentences, then answer the seven questions yes or no. Forecast on the yeses, move any deal back a stage when its evidence doesn’t match, and agree on one conversation that would turn the earliest no into a yes before next week.

    How does this fit with MEDDPICC?

    It sits on top of it. MEDDPICC fields describe the deal from the seller’s side, and the seven questions ask what the buyer has done to back each one up, like a funded project behind the economic buyer or written confirmation behind the decision criteria.

    Simplify complex sales: get the latest frameworks.

    Short, practical frameworks for executive messaging, business cases, multithreading, and sales enablement.

    © Nate Nasralla · Complex sales training & advisory

    Why do deal reviews take an hour and still miss the risk?

    In just 60 seconds, I can tell you if a deal's going to get a decision or get deleted. Which is roughly 59 minutes faster than the typical deal review.

    You've probably sat through the typical one. The VP says, "Walk me through this one, it's big for our quarter," and the rep starts on the play-by-play. The manager adds something to sound on top of it, the rep goes into more detail, and the VP drifts back to their inbox until they finally look up and ask, "Okay, so when are we meeting their exec?" Then somebody notices it's been an hour.

    When I say it should take a minute, the pushback is usually some version of, "But you don't know our product! You don't know our business!" Exactly. Neither does the executive your champion is trying to win over, and if what they hear doesn't hook them in the first minute, they'll move on.

    What goes in a 60-second deal review?

    Two parts, plus links to the work behind them.

    Part 1: the deal story, in three sentences. It pulls from your business case and reads a lot like a soundbite, opening on the change in the buyer's world:

    [Company] is experiencing [significant change in their business / market], which means [negative outcomes].

    [Executive] tasked [high-influence champion] with driving [a named project / strategic initiative] in response, with a target rollout date no later than [critical event].

    Compared to [alternatives, deal threats], [Executive] confirmed [direct quote about our unique/competitive differentiator] will enable [direct quote about positive outcomes].

    Part 2: seven questions on what the buyer has done. Answer each one yes or no, and note where each yes came from:

    1. Do we have a written problem statement built with the buying team's own data?
    2. Do we have direct comments or edits from them, either confirming or correcting our POV?
    3. Do we have no less than 3 buying roles confirming our impact to a specific, exec-level metric?
    4. Did the buying team exec fund a project or internal initiative to do something? Do we know that internal project name and team?
    5. Did the project team set a specific go-live date that, if missed, means a worse outcome?
    6. Do we have written confirmation they've stopped exploring other alternatives? Because they see we have a specific differentiator that other options don't?
    7. Has the buying team stuck to a "backdated" set of tasks/milestones? Are we ahead or behind of where we thought we'd be?

    Then link the full business case, its scorecard, and the mutual action plan, so anyone who wants to go deeper can. And when the review ends on "so when are we meeting their exec?", the executive brief is how you prep for that meeting.

    How do you read a deal review in 60 seconds?

    Pick up a few deal reviews and look at them side by side, and the differences jump out fast. Five reads cover the story:

    Once you've run a few, each of those reads takes 10 or 12 seconds, which is how the whole thing lands at about a minute. (Less time than it takes to brew a cup of French press, which I drank a lot of while writing about this.)

    Doesn't a one-minute review cut corners?

    It would, if the minute were doing the work. But the speed comes from the seven questions underneath the story, and every one of them points at something the buyer did. A written problem statement, three people confirming a metric, and a go-live date on their calendar all exist or they don't, and you can't talk your way into a yes.

    Which means you forecast on the yeses. A deal in your commit column with a few no's on the list isn't a commit, whatever the CRM stage says, so move it back a stage. Moving a deal backward is never fun, I know, and it's also how you build a forecast leadership can trust.

    And when the evidence isn't there yet, the review doesn't get shorter by skipping it. The no's become the agenda, and the time goes to the gap.

    How should a manager coach from it?

    Coach the earliest no. The seven questions follow the order a deal moves through its stages, so a gap early in the list usually explains the gaps after it. (If you've also scored the business case, the lowest-scoring section and the earliest no usually point at the same gap. When they don't, start with the earlier one.)

    Each no points at one conversation:

    Then next week's review starts with whether that no turned into a yes.

    What does a scored deal look like?

    Remember Morgan, from the forwardable email guide? She's a running example in Selling With (the scoring here is illustrative): a marketing manager at a high-growth startup, whose CMO, John, wants customer acquisition cost below $5K before the company raises its Series B. Her team would have to ramp content tenfold to get there, and they're already stretched.

    The rep's three sentences:

    1. The company is heading into a Series B on a capital-efficient growth story, which means CAC has to drop below $5K with a content team that's already stretched.
    2. John tasked Morgan with driving "capital-efficient growth," with content ramped 10x by 12/31.
    3. Compared to ...

    And that's where the rep stops, because nobody on the buyer's side has named the alternatives, let alone confirmed why this approach beats them. So the answers look like this:

    So it's not a commit. The manager skips the play-by-play and coaches question #3: who else might this project impact that hasn't weighed in yet? Get two more people confirming the CAC problem, and the rest of the list has something to stand on.

    Your move this week

    1. Write the three sentences for your biggest deal, and notice which one you can't finish.
    2. Answer the seven questions yes or no, and write down where each yes came from.
    3. Bring both to your next pipeline review, and ask your manager to coach the earliest no.