The Mid-Market Pipeline Review Workshop — 60-Min Training in 2027

The Tuesday that made the workshop necessary

Picture a mid-market SaaS company: roughly $30M ARR, average deal size around $45,000, sales cycles of 60 to 90 days, three pods of five account executives each reporting to three frontline managers. Quarter-end is eleven days out. The CRM says $6.2M is in the current-quarter pipeline against a $1.8M number. On paper that is a 3.4x cushion. The VP of Sales walks into the Monday forecast call comfortable.

By Thursday the number has quietly moved to $1.35M and nobody can explain when it happened. The autopsy is always the same set of findings. Eleven deals sat in "Negotiation" with close dates that had been pushed at least twice. Six of the largest opportunities had no documented economic buyer — the only contact on the record was the person who filled out the demo form in April. Four deals were "verbally committed" with no mutual action plan, no procurement contact, and no security review started, in an organization where security review alone historically takes 18 days. Two deals were duplicates created by different reps working the same parent account under slightly different names.

None of that is a forecasting problem. It is an inspection problem. The weekly pipeline call had become a recital: each rep reading their top five deals aloud, the manager nodding, occasional coaching that amounted to "can you get them on a call this week?" Nobody was asked to produce evidence. Nobody was allowed to be wrong out loud. And because the meeting had no agreed structure, the loudest, most articulate rep sounded the most credible regardless of whether their deals were real.

The workshop exists to break that pattern in a single sitting. Sixty minutes is not arbitrary — it is the longest block you can reliably get from a full frontline sales org without competing with customer calls, and it is short enough that it can be repeated quarterly without becoming another thing people dread. The constraint forces the design: you cannot teach a methodology in an hour, but you can install one inspection ritual and prove it works on live deals in front of the people who have to run it. That is the entire ambition. One ritual, demonstrated on real pipeline, with named owners walking out.

The mid-market qualifier matters more than it looks. Enterprise sales teams usually already have deal-review machinery — MEDDIC scorecards, deal desks, quarterly business reviews with a full command-plan template. Transactional SMB teams move too fast for deal-by-deal inspection and are better served by cohort-level conversion math. Mid-market sits in the gap: deal sizes large enough that each one matters to the number, cycle lengths long enough that a stalled deal can hide for six weeks, but headcount and ops support too thin to sustain a heavyweight process. The workshop is calibrated for that middle: rigorous enough to catch fiction, light enough that a manager with eight direct reports and their own pipeline can actually run it every week.

There is a second, quieter reason to run this as a workshop rather than a memo. Pipeline hygiene rules distributed as documentation get read once and ignored. The behavior changes when a manager watches a peer manager push back on a deal in front of the room, sees that the rep survives the interaction, and understands that the same standard will be applied to their own pod next Tuesday. Social proof does the enforcement work that a policy document cannot.

How the 60 minutes actually breaks down

The agenda below is the version that survives contact with a real sales floor. Each block has a hard timebox, a named facilitator, and a physical artifact that exists at the end of it. If a block produces no artifact, it was theater.

Minutes 0–10: the framing block. Open with the delta, not the philosophy. Put two numbers on the screen: what the pipeline said 90 days ago for this quarter, and what actually closed. In most mid-market orgs that gap runs 30 to 50 percent, and showing it removes the need to argue that a problem exists. Then introduce exactly one framework — the stage exit criteria — and nothing else. The most common failure of pipeline training is teaching MEDDPICC, mutual action plans, multi-threading, and forecast categories in the same hour. Pick the one that unblocks the others. For a team with stage inflation, that is exit criteria. For a team with accurate stages but wild close dates, it is the mutual action plan.

Minutes 10–35: live deal teardowns. This is the load-bearing block. Three deals, roughly eight minutes each, chosen in advance by the facilitator — never volunteered. Choose one deal that looks strong and is, one that looks strong and isn't, and one genuinely ambiguous deal where the room will disagree. The rep presents for two minutes maximum, then the room interrogates against the exit criteria for four, and the facilitator spends the last two making the rescoring explicit: this deal moves from Commit to Best Case because the economic buyer has never been on a call, and here is the specific action that would move it back.

Minutes 35–50: the forecast math block. Take the rescored deals and roll them up. Show what happens to the quarter number when three deals shift categories. This is where the abstraction of "pipeline quality" becomes a number a manager owns. Walk the coverage calculation live — required bookings divided by historical stage-to-close conversion, not a folklore 3x multiplier — and let the team see how sensitive the answer is to the conversion rate you plug in.

Minutes 50–60: commitments. Every deal touched during the hour leaves with a named owner, a specific next action, and a date. Not "follow up" — "get the CFO on a 30-minute call by Thursday or move this to next quarter." The facilitator reads them back aloud. Somebody writes them into the CRM before anyone leaves the room.

Two facilitation details make or break the teardown block. First, the facilitator must ask the same questions in the same order for all three deals. Varying the interrogation lets the room read favoritism into it, and reps immediately start optimizing for which manager is asking. Second, the rescoring has to happen in the room, out loud, with the rep present. Rescoring a deal privately after the meeting teaches reps that the meeting is a performance and the real judgment happens elsewhere — which is precisely the dynamic you are trying to kill.

The numbers worth putting on the screen

Vague appeals to "better hygiene" do not change behavior. Specific, locally-sourced numbers do. Pull these from your own CRM before the workshop; the point is not to match anyone else's benchmarks but to know your own.

Stage-to-close conversion by stage. For each pipeline stage, what fraction of deals that entered it eventually closed won? This single table replaces every coverage rule of thumb. If deals entering your Negotiation stage close at 55 percent, then $1M in Negotiation is worth $550K, and the 3x coverage folklore is irrelevant. Mid-market teams commonly find their late-stage conversion is far lower than assumed — because stage inflation means "Negotiation" contains deals that have never seen a contract.

Stage aging. Median days a deal spends in each stage, and the distribution. The useful output is a staleness threshold: if the median deal spends 14 days in Proposal and a specific deal has been there 60, that deal is not a slow deal, it is a dead deal that nobody has buried. A common working rule is to flag anything past twice the median and force an explicit decision — advance, downgrade, or close-lost.

Close-date push count. How many times has the close date on this opportunity moved? Empirically this is one of the strongest single predictors available in a mid-market CRM, and almost nobody surfaces it. Deals pushed twice convert dramatically worse than deals pushed zero times. Make the push counter a visible field on the review sheet.

Contact breadth. Number of distinct contacts at the account who have participated in a meeting or replied to email in the last 30 days. Single-threaded deals are the standard mid-market failure mode: the champion goes on parental leave, changes jobs, or gets reorganized, and a six-figure deal evaporates. Set a floor — for deals above your average size, require at least three engaged contacts including someone with budget authority.

Forecast accuracy by manager and by rep. Track called-number versus actual over several quarters. The interesting signal is not just the error magnitude but its direction and consistency: a rep who is reliably 20 percent optimistic is easy to correct for, while a rep whose error swings wildly is genuinely unpredictable and needs deal-level inspection, not a coefficient.

Slippage rate. Of deals forecast to close in a quarter, what percentage closed in a later quarter versus closed lost? High slippage with low loss means your close dates are fiction but your qualification is fine. High loss means the opposite. These require completely different interventions, and teams routinely misdiagnose one as the other.

For the workshop itself, a few operational numbers: cap attendance at roughly 12 to 15 people. Below eight, there is not enough disagreement to make the teardowns interesting; above 15, most people become spectators and the hour turns into a lecture. Three deals in 25 minutes is the ceiling — teams that try five end up at four minutes each, which is enough time for the rep to present but not for the room to push back, which defeats the purpose.

Budget prep honestly. A facilitator needs 60 to 90 minutes to pull the reports and pre-read the three chosen deals. If you skip that prep and pick deals live, the block collapses, because half the time will be spent on the facilitator reading the opportunity record aloud.

What you give up by choosing this format

Every training format trades something away. Being explicit about it makes the choice defensible when someone asks why you didn't do the full-day version.

Sixty minutes versus a half-day methodology rollout. The half-day gets you actual framework fluency — reps can run MEDDPICC unassisted afterward. The hour gets you one behavior. If your problem is that reps genuinely do not know how to qualify, the hour is insufficient and you should not pretend otherwise. If your problem is that they know how and don't do it consistently, the hour is better, because the half-day version front-loads teaching and usually runs out of time before the practice block, which is the part that changes anything.

Live deals versus case studies. Case studies are safer, more controllable, and let you engineer a clean teaching moment. They also carry a fatal flaw: reps discount them. "That's not how our deals work" is the universal response, and it is often correct. Live deals are messier and carry real interpersonal risk — you are critiquing a named person's work in front of their peers — but they are the only version that transfers. Mitigate the risk by warning the three selected reps privately beforehand and framing selection as instructive rather than punitive.

Manager-led versus enablement-led. Enablement facilitators are better trained and more consistent. Managers carry authority the org actually responds to. The compromise that works: enablement designs the workshop and facilitates the first run, then hands the recurring 30-minute version to managers with a one-page script. If enablement owns it permanently, it never becomes part of how the team operates — it stays a program that happens to them.

Synchronous versus asynchronous. An async version — recorded walkthrough plus a worksheet — scales to a distributed team across time zones and costs almost nothing to repeat. It also removes the disagreement, which is where the learning lives. A defensible hybrid: async pre-work covering the framework definitions, synchronous hour spent entirely on teardowns. That reclaims the framing block and gives you four deals instead of three.

Uniform versus segmented. Running one workshop for all pods is efficient and creates a shared standard. But a pod selling into healthcare with 120-day procurement cycles has genuinely different inspection needs than a pod selling into fast-moving tech. If your segments diverge that much, run one shared framing session and separate teardown blocks per segment.

The failure modes that show up every time

The workshop becomes a status meeting. Symptom: reps present deals and nobody asks a hard question. Cause: the facilitator is asking open-ended questions like "how's this one looking?" instead of criteria questions like "who signs this, and when did you last speak to them?" Fix: write the interrogation questions down and read them off the sheet. Scripted questions feel awkward for the first two deals and then become invisible.

Public humiliation. Symptom: after the first workshop, reps sandbag — they stop putting real deals in the CRM at all, or they only surface deals they are certain about. Cause: the teardown targeted the rep instead of the deal. Fix: the facilitator's language should be about evidence, not judgment. "What evidence do we have that the budget is approved?" not "you don't really know if they have budget." And the facilitator should tear down one of their own deals first, publicly, before asking anyone else to.

Nothing changes on Wednesday. Symptom: great workshop, zero follow-through. Cause: no recurring ritual was installed. The hour is a demonstration, not the process. Fix: schedule the 30-minute manager-led version on the calendar before the workshop ends, and have the first one occur within seven days while the memory is fresh.

Rescoring gets quietly undone. Symptom: deals downgraded during the workshop are back in Commit by Friday. Cause: the rep owns the forecast category and no one is auditing changes. Fix: make category changes require a comment, and have the manager review the change log weekly. This is a five-minute report, not a governance program.

The framework becomes the point. Symptom: three months later the team can recite the acronym and the forecast is still wrong. Cause: compliance was measured instead of outcomes. Fix: measure forecast accuracy and slippage, not scorecard completion. A fully-filled scorecard on a dead deal is worse than no scorecard, because it launders a bad deal as inspected.

Bad data undermines everything. Symptom: the teardown stalls because nobody trusts the stage or the close date in the CRM. Cause: you ran training before ops. Fix: if duplicate accounts, missing contact roles, or unmapped stages are widespread, spend two weeks on data cleanup first. Training on top of untrustworthy data teaches the team that the CRM is optional, which is the opposite of the intended lesson.

Only the top deals get inspected. Symptom: the number still misses despite clean top-five reviews. Cause: in mid-market, the miss usually comes from the middle of the distribution — twelve $40K deals that all slip, not one $500K deal that dies. Fix: rotate the selection. Inspect by stage age or push count rather than by size at least every other session.

Where this ritual connects to the rest of the revenue system

The workshop does not live alone. Upstream, marketing-sourced pipeline that enters at a stage nobody validated will corrupt the review no matter how well it is facilitated — so the exit criteria for the first sales-accepted stage should be agreed jointly with demand gen, and the same evidence standard should apply to a deal an SDR passed as to one a rep sourced. Downstream, the commitments from the hour should flow into the same task system the team already uses; a commitment tracked in a separate workshop spreadsheet dies within two weeks.

There is a natural pairing with renewals and expansion. Mid-market customer success teams face a structurally identical problem — a renewal book where everything is "green" until 30 days out — and the same 60-minute format ports cleanly by swapping stage exit criteria for renewal risk criteria: executive sponsor still employed, product usage trending flat or down, open escalations, contract terms. Teams that run both often merge them quarterly so the new-business and retention pictures get inspected against one standard.

Finally, the data produced by consistent reviews is worth more than the reviews themselves. After two quarters of disciplined rescoring, you have a labeled dataset — deals a human judged strong or weak, matched against outcomes — which is the input any predictive scoring effort needs and almost never has. Teams that skip the ritual and buy the scoring tool first end up training a model on the same optimistic stage data that caused the problem.

Related questions

How often should the full 60-minute version run?

Quarterly for the full facilitated version, with a 30-minute manager-led cadence weekly in between. More frequent full sessions produce diminishing returns; the recurring short version is what actually sustains the behavior change between quarters.

Should reps see the deal selection in advance?

Tell the three selected reps privately a day ahead so they can prepare evidence, but do not publish the list to the room. Advance notice reduces defensiveness without letting the whole team rehearse.

Does this work for a team of four reps?

Partially. With fewer than eight participants there is not enough disagreement to make teardowns productive. Combine pods, include customer success and sales engineering, or run it as a manager-only session focused on inspection technique.

What if leadership won't give up the hour?

Run it as a replacement for one existing forecast call rather than an addition. The pitch is a swap, not a new meeting, and the forecast call is usually the least productive hour on the calendar anyway.

FAQ

What does the facilitator actually need to prepare?

Three chosen opportunities with their full record pre-read, a stage aging report, a stage-to-close conversion table pulled from the last four quarters, and a written list of five to seven interrogation questions. Roughly 60 to 90 minutes of prep. Skipping the pre-read is the single most common reason the teardown block fails.

Who should be in the room?

Frontline sales managers, the reps whose deals are being reviewed, and ideally a sales engineer and someone from revenue operations. Cap it at 12 to 15. Senior leadership attendance is a judgment call — their presence raises the stakes usefully but can also suppress the honest disagreement the format depends on.

How do you keep it from becoming a blame session?

Interrogate the evidence, not the person. Every question should be answerable with a fact — who signed, when they last replied, what the procurement timeline is — rather than requiring the rep to defend their judgment. Have the facilitator tear down one of their own deals first.

What if the CRM data is too messy to review?

Fix ops first. Duplicate accounts, missing contact roles, and stages that mean different things to different pods will derail the hour. Two weeks of cleanup before the session is a better investment than running the workshop on data nobody trusts.

Is this different for a sales-led versus product-led motion?

The structure holds, but the criteria change. In a product-led motion the strongest evidence is usage — seat expansion, feature adoption depth, active accounts inside the customer — rather than meeting attendance. Swap the exit criteria for usage thresholds and the same hour works.

How do you measure whether the workshop worked?

Forecast accuracy variance quarter over quarter, slippage rate, and the count of deals sitting past twice their median stage age. All three should improve within two quarters. Do not measure scorecard completion rates — teams optimize for whatever you count, and completed scorecards on dead deals are pure noise.

Sources

• https://hbr.org/2015/07/a-sales-process-that-works
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.gartner.com/en/sales
• https://www.salesforce.com/resources/articles/sales-pipeline/
• https://www.hubspot.com/sales-pipeline
• https://www.forrester.com/blogs/category/b2b-sales/
• https://hbr.org/2017/03/how-to-forecast-sales-more-accurately
• https://www.atlassian.com/team-playbook

Related on PULSE

• How to build stage exit criteria your reps will actually use
• Forecast categories explained: Commit, Best Case, Pipeline
• Mutual action plans for mid-market deals
• Diagnosing slippage vs. loss in a missed quarter
• Running a 30-minute weekly pipeline inspection