60-Min Sales Training: Mid-Market Deal Strategy Review in 2027

What a mid-market deal strategy review actually is, and why it earns its hour

A deal strategy review is not a forecast call, and confusing the two is the single most common reason these sessions die. A forecast call asks "will this close, and when?" A strategy review asks "what do we not know, and what are we going to do about it?" The first is an accounting exercise the CRO needs. The second is a coaching and planning exercise the rep needs. When you merge them, the rep spends the hour defending a commit date instead of thinking, and everyone leaves with the same information they walked in with.

The mid-market segment is where this format pays off most. In SMB, deals are too fast and too numerous for hour-long reviews — the cycle is often two to six weeks, the ACV doesn't justify the labor, and the coaching that matters is call-level, not deal-level. In enterprise, deals are big enough that they usually already have a named account team, an executive sponsor on your side, and a standing weekly cadence. Mid-market sits in the gap: deals typically run 45 to 120 days, involve three to eight stakeholders across two or three functions, and carry enough ACV that losing one hurts the quarter — but not enough attention that anyone is watching them closely between stage changes. That combination is exactly where a structured hour finds money.

Three things make the mid-market flavor distinct. First, the buying committee is real but undocumented. There is a champion, an economic buyer who has never spoken to you, a security or IT reviewer who appears in week six, and often a finance gatekeeper who appears the week you send paper. Nobody in the deal has mapped them, because the rep has been talking to the champion and the champion has been reassuring. Second, procurement is semi-formal. It may be a one-page MSA redline handled by an operations manager, or it may be a full security questionnaire and a SOC 2 review — and the rep usually finds out which in week eight. Third, the competitor is frequently "do nothing" or "the spreadsheet we already have," which never appears in a competitive-battlecard exercise but wins more mid-market deals than any named rival.

A good review surfaces all three. The point of the hour is not to make the rep feel supported; it is to convert soft assumptions into either evidence or an action that produces evidence. The output of a healthy session is a short list of things you will *learn* in the next ten days, not a longer list of things you *believe*. When a manager runs this well, the same rep starts pre-empting the questions and the review time drops, which is the real success metric.

The word Training matters here in a specific sense: this is a training format disguised as a working session. The rep is not being taught a framework in the abstract; they are applying one to a live opportunity with real money on it, under a coach's eye. That is why retention beats classroom sales enablement by a wide margin — the reasoning gets attached to a deal the rep already cares about. It is also why the format scales across the team: reps who sit in on other people's reviews absorb the pattern of questions and start running it internally.

One structural warning before the mechanics. This hour must be scheduled and protected. The most common failure is the "we'll do it when we need it" approach, which means it happens only when a deal is already in trouble — at which point the review becomes a rescue attempt with a fraction of the available levers. Put it on a cadence: one deal per rep per two weeks in mid-market, more often in a compressed quarter.

The step-by-step process for the hour

Run the clock visibly. Put a timer on screen. The discipline is the product — a review that runs long is a review that got emotional, and emotional reviews produce reassurance rather than plans.

Pre-work, 15 minutes before, done by the rep. The rep submits a one-page deal brief into the shared doc or CRM at least 24 hours ahead: account name, ACV, close date, current stage, the compelling event as the buyer stated it, a stakeholder list with names and roles, the last three interactions with dates, and the single biggest risk in the rep's own words. If the brief is missing, the review does not happen — reschedule it and let the silence do the teaching. Managers who run the review anyway are training the team that pre-work is optional, and the format degrades within a month.

Block one: facts, 10 minutes. The rep narrates the deal chronologically with no interruption for the first five minutes. Manager takes notes, asks nothing. This is harder than it sounds and it is essential — interrupting early anchors the whole session on the manager's first hypothesis. In the back half of the block, the manager asks only clarifying, non-leading questions: dates, names, exact words the buyer used. "What did she actually say?" is the highest-yield question in this block. Anything that starts with "I think they..." gets flagged as an assumption, not a fact, and goes in a separate column.

Block two: gap-hunting, 20 minutes. Now you run the deal against a qualification framework — MEDDPICC, SPICED, Command of the Message, or whatever the org has standardized on. The framework choice matters far less than consistency; a team that runs one framework badly beats a team that switches quarterly. Score each element as evidence-backed, assumed, or unknown. Be brutal about the distinction. "The champion said the CFO is on board" is *assumed*. "The CFO joined a 20-minute call and asked about implementation timing" is *evidence*. In mid-market, expect the honest score to come out with three to five unknowns in a deal the rep called 80% likely. That gap is the whole point of the exercise.

Block three: moves, 20 minutes. For each of the top three gaps, design a specific action with an owner, a date, and a defined signal that tells you whether it worked. Not "get to the economic buyer" — that is a wish. Instead: "Ask the champion for a 20-minute call with the VP Finance to validate the payback assumption; request it by Thursday; the signal is whether the meeting is on the calendar within five business days." The signal is the part everyone skips and the part that makes the next review fast. If the meeting isn't booked in five days, you have learned something real about champion strength without waiting three more weeks.

Block four: commitments, 10 minutes. Read back every action, owner, and date. Update the CRM live, on screen, while everyone is still in the room — deal reviews whose outputs live in a manager's notebook produce zero organizational memory. Set the check-in date. Then ask one closing question: "What would have to be true for this deal to slip a quarter?" The answer is usually the risk nobody wanted to name in block two.

mermaid flowchart TD Q["Deal is at risk or high value"] --> R{"What is the actual gap?"} R -->|Missing information| S["60-min deal strategy Review"] R -->|Rep skill execution| T["Call coaching with recording"] R -->|Needs people or budget| U["Escalation and pursuit plan"] R -->|Not enough deals| V["Pipeline generation plan"] S --> W{"Evidence improved by next session?"} W -->|Yes| X["Continue cadence, shorten review"] W -->|No, after 3 reviews| Y["Disqualify or push out"] </invoke>

A second axis is who runs it. Frontline managers should run the standing cadence. Peers can run a lighter version — a 30-minute rep-to-rep review is surprisingly effective for mid-market deals and builds the muscle faster than manager-only sessions, because the rep must articulate the deal to someone with no authority over their number. Reserve senior leadership involvement for the escalation path; a VP dropping into routine reviews changes the candor economics instantly.

Adjacent to all of this: the same structure transfers cleanly to renewals and expansions, which most mid-market teams review far too casually. A renewal at risk deserves the identical hour — facts, gap-scoring against adoption and stakeholder evidence, three moves, commitments. The only change is that the "compelling event" question becomes "what changed since they bought?" Customer success teams that borrow this format tend to catch churn signals four to eight weeks earlier than a health-score dashboard alone, because a human is forced to distinguish evidence from assumption about whether the original champion still works there.

The upstream effect is worth planning for too. Once reps know the review will demand named stakeholders and a stated compelling event, discovery calls change. Reps start asking approval-path questions in call two instead of call six, because they know they will otherwise sit in a room and have no answer. That behavioral drift upstream is arguably a larger return than any individual deal saved — and it is the reason to run the format on healthy deals, not only sick ones.

Related questions

How is this different from a pipeline review?

A pipeline review scans many deals for coverage, stage distribution, and forecast accuracy. A strategy review goes deep on one deal to find missing information and design next moves. Different cadence, different attendees, different output. Running them in the same meeting reliably degrades both.

Should the rep or the manager pick the deal?

The rep picks by default, which raises engagement and surfaces the deals they are genuinely uncertain about. The manager reserves an override roughly once a month for a deal the data flags — long time-in-stage, single-threaded, or unusually large relative to the rep's average.

What if the rep gets defensive?

Usually a signal that the format has drifted toward forecast policing. Restate the purpose out loud, ban commit-date talk for the hour, and have the manager go first by naming their own uncertainty about the deal. Recording the session for the rep's own review also helps.

Does this work for remote and hybrid teams?

Yes, and often better. A shared screen with the brief and framework scorecard keeps everyone anchored to the same artifact. Keep cameras on, keep attendance at four or fewer, and update the CRM live on the shared screen so the commitments are visible as they are made.

How soon should results show up?

Expect process signals within two to three weeks — more named stakeholders per deal, fewer single-threaded opportunities. Outcome signals like reduced slippage and better stage conversion typically need a full cycle, so 60 to 120 days in a mid-market motion before the comparison is meaningful.

FAQ

Which qualification framework should we use?

Whichever one your team already knows, applied consistently. MEDDPICC, SPICED, and Command of the Message all work for mid-market. The value comes from scoring the same elements every time so gaps are comparable across deals and across reps. Switching frameworks mid-year costs you a quarter of comparability and buys you almost nothing.

Can we run this in 30 minutes instead?

Yes, for a second review of a deal you have already worked, or for peer-to-peer sessions. Compress to five minutes of facts, ten of gap-hunting, ten of moves, five of commitments. The first review of any deal needs the full hour, because building the stakeholder map and the honest framework score is what takes the time.

Who should own updating the CRM afterward?

The rep, live in the meeting, on the shared screen. If it is deferred to "after the call," it happens for roughly half of reviews and the organizational memory disappears. Live updating also exposes CRM field friction — if it takes six clicks to log a stakeholder, you have just found a RevOps backlog item worth fixing.

What do we do when the rep has no answer to a key question?

Write "unknown" and make it the top action. An unknown that is named and assigned is the most valuable output of the hour. The failure mode is letting the rep speculate their way to a plausible-sounding answer, which converts a known gap into a false assumption and removes it from the action list.

How do we keep leadership from turning it into a forecast call?

Separate the meetings on the calendar with different names, different attendees, and different artifacts, and give leadership a genuinely useful forecast call so they do not need to mine the review for numbers. If a senior leader must observe, brief them beforehand that they are observing, not questioning.

Is it worth reviewing deals we expect to win?

Yes, and teams skip this to their cost. Healthy deals are where you find the surprise unknowns cheaply, and they are the best training material because the rep is not defensive. A quarterly rotation that includes at least one confident deal per rep tends to surface the most durable process improvements.

Sources

• https://hbr.org/2012/07/the-end-of-solution-sales
• https://hbr.org/2015/03/making-the-consensus-sale
• https://www.gartner.com/en/sales/insights/b2b-buying-journey
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.salesforce.com/resources/research-reports/state-of-sales/
• https://www.gong.io/resources/
• https://hbr.org/2017/03/a-refresher-on-a-b-testing
• https://sloanreview.mit.edu/topic/marketing-sales/

Related on PULSE

• How to build a mid-market qualification scorecard your reps will actually use
• Pipeline review vs. deal review: which meeting fixes which problem
• Multi-threading playbook: getting past a single champion in mid-market
• Renewal risk reviews: adapting deal strategy sessions for customer success
• Forecast accuracy: separating commit hygiene from deal coaching