.png)
Deal inspection is the process of examining an individual opportunity against qualification criteria, buyer engagement evidence, and pipeline progression data to determine whether the deal is real, at risk, or dead. It is the most important skill a sales manager develops, and the one most managers do poorly because they rely on the rep's narrative instead of the deal's evidence.
The difference between a pipeline review and a deal inspection is depth. A pipeline review scans 3 to 5 deals in 30 minutes, assessing health and assigning next actions. A deal inspection goes deep on a single deal for 10 to 15 minutes, stress-testing every qualification element, verifying buyer evidence, and identifying the specific gap that will prevent this deal from closing if left unaddressed.
Sales leaders who run disciplined deal inspections do not have fewer forecast surprises by accident. They have fewer surprises because they caught the gaps 3 weeks before the close date, when intervention was still possible. This guide provides the framework, the questions, and a practical approach to running deal inspections that surface truth rather than optimism.
Not every deal needs a formal inspection. Inspections are high-value time investments that should be reserved for deals where the stakes justify the depth.
Inspect before committing to forecast. Any deal a rep wants to move to "commit" or "best case" should survive a deal inspection first. If it cannot withstand 10 minutes of qualification scrutiny, it does not belong in the forecast.
Inspect when a deal enters late stage. Deals moving from evaluation to negotiation or proposal stage deserve inspection because late-stage failures are the most expensive. A deal that dies in discovery costs the rep a few hours. A deal that dies in negotiation after weeks of solution design, pricing work, and executive involvement costs everyone significant time and creates forecast gaps.
Inspect when something feels off. Experienced managers develop intuition about deal health. When something does not feel right, even if the rep's status update sounds positive, that is the signal to inspect. The rep says "it is going great" but the deal has not advanced a stage in three weeks. The buyer "loves the product" but has not introduced the economic buyer. The close date is "next month" but no mutual action plan exists.
Inspect new reps' top deals. First-year reps need deal inspection more than anyone because they have not yet developed the judgment to self-assess deal quality. Inspecting their top 3 deals weekly builds the muscle for self-inspection over time.
The core principle of deal inspection is simple: evidence over narrative. Reps tell stories about their deals. Stories are optimistic by nature. Evidence is neutral. A good deal inspection replaces "I think" with "the buyer said" and "we believe" with "the data shows."
The framework below uses MEDDPICC as the qualification backbone because it is the most widely adopted enterprise sales methodology and because each element maps to a specific inspection question. If your team uses BANT, SPICED, or a custom framework, the principle is identical: inspect each criterion against conversation evidence, not rep interpretation.
Allocate 15 minutes per deal. That is enough time to inspect thoroughly without turning it into an interrogation. The manager drives the questions. The rep provides evidence. Both agree on the gap and the action.
Minutes 1-2: Deal Overview
The rep gives a 2-minute summary: what the deal is, where it stands, what the proposed timeline is, and what they believe the primary risk is. This is the only narrative portion. Everything after this is evidence-based.
Sybill's deal workspace provides this overview without the rep needing to prepare it. The workspace shows current stage, last activity date, key stakeholders engaged, qualification criteria status, and recent call summaries in a single view. The manager can read the deal's state before the inspection even starts.
Minutes 2-12: The 8 Inspection Questions
Each question maps to a MEDDPICC element and requires the rep to cite conversation evidence, not opinion.
Minutes 12-15: Gap Identification and Action
The manager and rep identify the single most critical gap and agree on the specific action to close it before the next inspection.
What you are testing: Whether the buyer has articulated a measurable business impact that justifies the investment. "They want to improve efficiency" is not a metric. "They are losing 6 hours per rep per week to manual CRM updates, which equals $180,000 annually across their 20-person team" is a metric.
Evidence required: A specific number, dollar amount, or measurable outcome the buyer stated in a call. Not an ROI model the rep built. Not a value assumption from a marketing deck. A number the buyer owns.
How Sybill surfaces the evidence: CRM Autofill populates the Metrics field from conversation data. If the buyer quantified impact on a call, it is in the CRM. If the field is empty after multiple conversations, that is the gap. Ask Sybill: "What metrics or business impact has the buyer quantified in the Acme deal?"
If the gap exists: Coach the rep to quantify the pain in the next conversation. "You mentioned your team spends significant time on manual reporting. Can you help me understand what that looks like in hours per week and how that affects your pipeline visibility?"
What you are testing: Whether the rep has identified and engaged the person who can sign off on the budget. "The VP likes it" is not confirmation. "The VP confirmed she has budget authority for purchases up to $50K and will sign the PO" is confirmation.
Evidence required: Name, title, and direct engagement evidence. Has the economic buyer attended a call? Responded to an email? Confirmed their role in the decision?
How Sybill surfaces the evidence: CRM Autofill logs stakeholder information from every call, including names, roles, and engagement level. The deal workspace shows all contacts who have participated in conversations. If the economic buyer has never appeared in a call or email thread, the deal is single-threaded at best, unqualified at worst.
If the gap exists: Develop a plan to get the economic buyer into the conversation. Ask the champion: "To make sure we build a strong business case for your leadership, would it make sense to include [economic buyer name] in our next conversation?"
What you are testing: Whether the rep knows what the buyer will use to evaluate and choose between options. Decision criteria include functional requirements, technical requirements, pricing constraints, implementation timeline expectations, and vendor evaluation criteria.
Evidence required: Specific criteria the buyer stated in a conversation. "They care about ease of use" is vague. "The buyer said their three requirements are Salesforce integration within 30 days, SOC 2 compliance, and pricing under $100 per user per month" is evidence.
How Sybill surfaces the evidence: Magic Summary captures requirements, evaluation criteria, and buyer priorities from every call. CRM Autofill populates the Decision Criteria field with specifics from conversations. Ask Sybill: "What decision criteria has the buyer mentioned for the Acme deal?"
If the gap exists: The next call needs an explicit question: "When your team evaluates solutions, what are the three to five requirements that will determine your decision?"
What you are testing: Whether the rep can map the buyer's internal path from "we want this" to "the contract is signed." This includes who approves, in what sequence, what documents are required, and how long each step takes.
Evidence required: A specific process the buyer described. "They need to go through procurement" is insufficient. "The champion presents the business case to the VP, the VP approves and routes to procurement, procurement requires three competitive bids and takes 2 to 3 weeks, legal reviews the contract in parallel, and the CFO signs anything over $25K" is a mapped process.
How Sybill surfaces the evidence: CRM Autofill writes Decision Process and Paper Process fields from conversation data across multiple calls. These fields, built incrementally as the buyer reveals more of their process, are the direct evidence for this question. Ask Sybill: "What has the buyer told us about their purchasing process?"
If the gap exists: This is often the most critical gap to close. Without a mapped decision process, every close date is a guess. The rep needs to ask: "Can you walk me through what happens on your side between deciding to move forward and having the contract signed?"
What you are testing: Whether the buyer has articulated a pain that is specific, quantified, and connected to a business priority. "They are frustrated with their current tool" is sentiment, not pain. "Their current tool does not integrate with Salesforce, which means reps spend 2 hours per day on manual data entry, which their VP has identified as the biggest barrier to hitting Q3 targets" is identified, quantified pain connected to a business priority.
Evidence required: A specific pain statement from the buyer, ideally with quantification and connection to a business initiative with executive sponsorship.
How Sybill surfaces the evidence: Magic Summary captures pain points as structured data from every call. CRM Autofill populates pain fields with specific buyer statements. The deal workspace shows the accumulated pain evidence across all interactions. If the pain field contains generic descriptions after multiple conversations, the rep has not gone deep enough.
If the gap exists: Coach the rep on the three-layer pain questioning technique: surface-level pain (what is broken), business impact (what it costs), and personal impact (how it affects the buyer's goals and credibility).

What you are testing: Whether someone inside the buyer's organization is actively working on your behalf. A champion is not someone who likes your product. A champion is someone who is selling internally for you: presenting the business case, navigating procurement, overcoming internal objections, and keeping the deal moving when you are not in the room.
Evidence required: Specific actions the champion has taken on your behalf. "She is very enthusiastic" is not evidence. "She presented our ROI analysis to her VP last Tuesday and scheduled a follow-up with procurement for Friday" is evidence of active championing.
How Sybill surfaces the evidence: Stakeholder tracking in the deal workspace shows who has been engaged across calls and emails. Magic Summary captures when the buyer mentions internal actions they have taken. Ask Sybill: "What internal actions has [champion name] taken on the Acme deal?"
If the gap exists: Either the champion is not actually a champion (they like you but are not willing to spend political capital), or the rep has not enabled them with the materials they need to sell internally. Provide the champion with a concise business case, competitive differentiation summary, and ROI data they can present without you in the room.
What you are testing: Whether the rep knows who else the buyer is evaluating, what the buyer thinks of the alternatives, and how the rep is positioning against them.
Evidence required: Specific competitors the buyer mentioned and the buyer's stated evaluation of them. "They are also looking at Gong" is awareness. "They said Gong's pricing is too high for their team size and they are concerned about the 6-month implementation timeline" is competitive intelligence you can act on.
How Sybill surfaces the evidence: Magic Summary flags competitor mentions from every call with context. CRM Autofill populates competitive intelligence fields. Ask Sybill can query across all conversations: "What has the buyer said about competitors in the Acme deal?" This surfaces not just that competitors were mentioned but what the buyer said about them, which is what you need to position against.
If the gap exists: The rep needs to ask directly in the next conversation: "Are you evaluating other solutions alongside ours? I ask because understanding what you are comparing helps me make sure I am addressing the things that matter most to your decision."
What you are testing: Whether the rep understands the operational steps between "yes, let us do this" and a signed contract and PO. Paper Process is where deals die silently. The buyer is enthusiastic, the champion is active, the product is a fit, and then the deal sits in legal review for 6 weeks because nobody mapped the process.
Evidence required: Specific steps, owners, and timelines for contract routing, legal review, procurement, and signature. "They need to go through legal" is insufficient. "Legal reviews all vendor contracts and typically takes 10 to 14 business days. The contract goes to legal after the VP signs the budget approval form. The CFO signs contracts over $25K, and she is available the first and third week of each month" is mapped Paper Process.
How Sybill surfaces the evidence: CRM Autofill writes Paper Process from conversation data. This is one of the fields most commonly left empty in CRM because reps forget to ask about it or the buyer reveals it incrementally across calls. When Sybill captures it automatically across multiple conversations, the field accumulates the full picture.
If the gap exists: Ask the buyer: "Once your team decides to move forward, what is the process for getting a contract signed? Who reviews it, how long does each step typically take, and is there anything we should prepare on our side to speed things up?"
The biggest failure mode for deal inspections is tone. A manager who fires 8 MEDDPICC questions at a rep like a compliance checklist creates an adversarial dynamic where the rep learns to have answers ready rather than gaps visible.
Three principles keep inspections collaborative:
Lead with the evidence, not the question. Instead of asking "Do we have an economic buyer?", open with "I see from the deal record that the VP of Sales attended the first call but has not been on a subsequent call. What is our plan to re-engage her?" This shows you have already looked at the data and are problem-solving, not interrogating.
Sybill's deal workspace gives the manager this evidence before the inspection starts. CRM fields populated from conversations, stakeholder engagement history, and Magic Summaries from recent calls are all visible without asking the rep to narrate the deal's history.
Identify the single most critical gap. Every deal has multiple gaps. A deal where Metrics, Economic Buyer, and Paper Process are all unconfirmed has three gaps, but only one of them is the next bottleneck. Identify which gap will block the deal first and focus the action plan on that one. Telling a rep to "go confirm the economic buyer, quantify the metrics, and map the paper process" before the next call is a to-do list they will not complete. Telling them to "get the VP on the next call and confirm budget authority" is one action they will execute.
End with the manager's commitment. Deal inspection should not be one-directional. If the gap is "we need executive engagement," the manager should offer: "I will send a peer-level email to their VP introducing myself and referencing the business case. You schedule a call that includes both of us." When the manager has skin in the game, the inspection feels like coaching, not evaluation.
The practical barrier to disciplined deal inspection is time. A manager with 8 reps, each carrying 20 to 30 deals, cannot inspect every opportunity. Even inspecting only the top 3 deals per rep at 15 minutes each means 6 hours per week of deal inspections alone.
AI reduces this in two ways.
First, it eliminates prep time. In a traditional inspection, the manager spends 5 to 10 minutes per deal scanning CRM fields, checking recent activity, and reviewing call notes before the conversation with the rep. When CRM Autofill keeps every field current and Magic Summary provides structured call outputs, the manager walks into the inspection already informed. Prep time drops from 5 to 10 minutes to under 2 minutes per deal.
Second, it pre-qualifies which deals need inspection. Ask Sybill enables queries that surface inspection-worthy deals automatically. "Which commit deals have unconfirmed economic buyers?" "Which deals closing this month are missing a mapped decision process?" "Where is competitive intelligence incomplete?" These queries identify the deals that need inspection before the manager selects them manually, ensuring the highest-risk gaps get attention first.
The combination means a manager can inspect more deals in less time, with better evidence, and focus the human conversation on strategy and coaching rather than data gathering.

The best deal inspections do not start with a question to the rep. They start with evidence from the conversations. Sybill populates MEDDPICC fields from actual calls, surfaces qualification gaps automatically, and gives managers the deal-level visibility to inspect with precision rather than intuition.
Start free with Sybill and see which deals in your pipeline survive evidence-based inspection.
Deal inspection is the process of examining an individual sales opportunity against qualification criteria, buyer engagement evidence, and progression data to determine whether the deal is real, at risk, or should be removed from the pipeline. Unlike a pipeline review that covers multiple deals at surface level, deal inspection goes deep on a single deal for 10 to 15 minutes, stress-testing every qualification element against conversation evidence rather than rep narrative.
Inspect deals at three trigger points: before a rep moves a deal to commit or best case in the forecast, when a deal enters late stage (negotiation or proposal), and when something about a deal feels off despite a positive status update. Additionally, inspect your newest reps' top 3 deals weekly to build their self-inspection skills. Not every deal needs inspection. Reserve it for high-stakes opportunities where the depth justifies the time investment.
MEDDPICC is the most widely adopted framework for deal inspection because each element (Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, Competition) maps to a specific, inspectable question. The framework works regardless of deal size or industry. Teams using BANT or SPICED can apply the same principle: inspect each criterion against conversation evidence, not rep interpretation.
A pipeline review is wide and shallow, covering 3 to 5 deals in 30 minutes, assessing overall pipeline health, and assigning next actions. A deal inspection is narrow and deep, examining a single deal for 10 to 15 minutes, verifying every qualification criterion against evidence, and identifying the single most critical gap. Pipeline reviews happen weekly. Deal inspections happen at specific trigger points (forecast commitment, stage advancement, manager intuition).
AI improves deal inspections by eliminating preparation time and pre-surfacing qualification gaps. Sybill's CRM Autofill keeps MEDDPICC fields current from conversation data, so the manager sees the deal's qualification status before the inspection starts. Ask Sybill identifies which deals need inspection by surfacing unconfirmed qualification criteria across the pipeline. The result is that managers inspect more deals in less time with better evidence, focusing the human conversation on strategy rather than data gathering.
Every inspection should end with three outputs: identification of the single most critical qualification gap, a specific action plan to close that gap (with owner and deadline), and a manager commitment if executive involvement, competitive positioning guidance, or internal escalation is needed. The action item carries forward to the next inspection or pipeline review. If the gap remains open at the next check, it becomes a serious risk signal that the deal may not close as forecasted.
Deal inspection is the process of examining an individual sales opportunity against qualification criteria, buyer engagement evidence, and progression data to determine whether the deal is real, at risk, or should be removed from the pipeline. Unlike a pipeline review that covers multiple deals at surface level, deal inspection goes deep on a single deal for 10 to 15 minutes, stress-testing every qualification element against conversation evidence rather than rep narrative.
Inspect deals at three trigger points: before a rep moves a deal to commit or best case in the forecast, when a deal enters late stage (negotiation or proposal), and when something about a deal feels off despite a positive status update. Additionally, inspect your newest reps' top 3 deals weekly to build their self-inspection skills. Not every deal needs inspection. Reserve it for high-stakes opportunities where the depth justifies the time investment.
MEDDPICC is the most widely adopted framework for deal inspection because each element (Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, Competition) maps to a specific, inspectable question. The framework works regardless of deal size or industry. Teams using BANT or SPICED can apply the same principle: inspect each criterion against conversation evidence, not rep interpretation.
