Technical Discovery for Sales Engineers: MEDDIC, MEDDPICC, and the Discovery-Call Bar in 2026

MEDDIC and MEDDPICC: the canonical qualification framework

MEDDIC is the qualification framework that anchors modern enterprise-SaaS technical discovery. Per MEDDIC Academy, the six elements decompose as follows, with concrete examples for an enterprise-SaaS deal in the data-platform segment:

1. Metrics. The quantified business outcome the prospect expects from the purchase. Example: cut nightly ETL runtime from 4 hours to under 30 minutes; reduce on-call pages from the data team by 60 percent (BLS). If the prospect cannot name the metric, the deal is unqualified; the SE's job is to surface this in the first call.
2. Economic buyer. The single person with sign-off authority on the contract. In an enterprise data-platform deal this is typically the VP Data, the CTO, or the CIO depending on company size. Not the champion; not the manager who scheduled the call.
3. Decision PROCESS. The buying workflow the prospect's company uses: who evaluates, in what order, with what gates, on what timeline. PROCESS comes before CRITERIA in the canonical MEDDIC ordering for a reason: the order in which gates fire determines what evidence the deal needs at each stage.
4. Decision CRITERIA. The technical and business criteria the prospect uses to evaluate vendors. Example: SOC 2 Type II required; SSO via Okta; row-level security on the warehouse layer; sub-second query latency at p95 against a 10TB dataset. The SE owns surfacing the technical sub-set of the criteria.
5. Identify pain. The specific technical or business pain that triggered the search. Pain is the why-now anchor; without it, the deal drifts. The SE listens for compounding pain (the current-state cost is rising) versus static pain (the prospect has lived with this for years and may again).
6. Champion. The internal advocate who has the authority and the willingness to drive the deal through their org. Champions sell internally; coaches give information but do not advocate. The SE tests the champion-versus-coach distinction by asking the prospect to take a specific action that requires internal political capital.

MEDDPICC adds two elements MEDDIC Academy treats as canonical for enterprise deals:

• Paper process. The legal, procurement, and security-review track. In 2026 enterprise-SaaS deals this is the load-bearing close-date predictor: the SOC 2 / ISO 27001 review, the redlines on the MSA, the procurement cycle, the DPA negotiation. Senior SEs map the paper process in the first or second call rather than discovering it in week six.
• Competition. The incumbent vendor and the alternatives the prospect is evaluating. The SE's job is to surface the competitive set honestly; deals lost to competitors the SE never identified in discovery are forecast-discipline failures.

MEDDICC (single C) adds only Competition. Most enterprise-SaaS sales orgs in 2026 default to MEDDPICC because Paper process is the variable that moves close dates more than any other.

The discovery call: what to ask and what to listen for

The Sales Engineer owns a specific sub-set of the discovery-call surface. The Account Executive owns the commercial discovery (budget cycle, decision-maker access, urgency drivers, competitive context); the SE owns the technical-fit qualification, the technical decision criteria, the technical pain, and the technical champion-and-detractor mapping.

Question patterns the senior SE uses on the first discovery call:

• Anchor on current-state pain, not future-state vision. Walk me through what your team did last Tuesday when the ETL job failed at 3 AM. Who got paged? What did they do? How long did it take? The current-state-pain narrative is the closest the SE gets to ground truth. Future-state vision is aspirational and rarely predictive of buying behavior.
• Ask for the technical decision criteria explicitly. What does the evaluation look like on your end? Who's going to review the architecture? What technical questions will they need answered before they sign off? If the prospect cannot articulate criteria, the deal is unqualified at the technical-CRITERIA layer.
• Map the champion-and-detractor surface. Who else on your team will be involved in this decision? Is there anyone who thinks the current setup is fine and we shouldn't change it? The detractor question is the highest-signal question on the call. The detractor exists; the question is whether the SE finds them in the first call or in the third demo when they show up to ask hostile questions.
• Test the champion's authority and willingness. If we wrap up here and you wanted to move forward, what would your next step internally look like? The champion who can name the next internal step is real; the champion who punts to I'll need to think about it is a coach.
• Listen for non-verbal disengagement. Long pauses before the prospect answers, deflection to good question, let me get back to you, the camera-off pattern, the multitask tells (typing while talking). The senior SE adjusts the call in real time when disengagement signal compounds; the mid-level SE plows through the demo deck.

Per O*NET SOC 41-9031 (BLS), the top skills for the occupation include Active Listening, Critical Thinking, and Judgment and Decision Making. These three map directly onto the discovery-call surface: Active Listening for the current-state-pain narrative, Critical Thinking for the technical-fit assessment, Judgment for the deflect-or-pursue call at the end of the meeting.

What separates senior+ discovery from mid-level

Compensation tracks the discipline. Per levels.fyi /t/sales-engineer, May 2026 median total compensation is $197,000 with the 25th-75th percentile at $143,000-$262,925 and the 90th percentile at $300,000. The delta between the 50th and 90th percentiles is almost entirely a discovery-discipline delta. Five behaviors separate senior+ discovery from the mid-level baseline:

1. Deflecting misqualified deals before the AE invests cycles. The senior SE ends discovery calls early when MEDDIC fails on Metrics, Economic buyer, or Pain. The mid-level SE pushes through to a demo because they asked for one. Demos to unqualified prospects burn the SE's most valuable inventory (calendar time during the buying season) and degrade pipeline quality across the territory.
2. Reading non-verbal disengagement signals in real time. The senior SE notices the second the prospect's body language shifts and redirects: I'm going to stop and ask; how is this landing? Is this the conversation you needed to have today? The mid-level SE finishes the scripted agenda regardless of the prospect's engagement state.
3. Identifying the technical detractor early. Every enterprise deal has a detractor; the senior SE finds them in the first call by asking explicitly. The mid-level SE meets the detractor in the third demo when they show up to torpedo the architecture review. Detractors found early can be converted, neutralized, or worked around; detractors found late close the deal at zero.
4. The discipline of saying no to a deal. When the technical fit is poor, the senior SE recommends the AE walk away. The math is: pursuing a poor-fit deal at 15 percent (BLS) close probability for two quarters is worse than killing it in week one and replacing the cycles with two new discoveries at 50 percent close probability. The mid-level SE pursues every deal the AE puts on the calendar.
5. Holding the line on success criteria. The senior SE refuses to start a POC without written success criteria signed by the technical evaluator. The mid-level SE starts the POC on a handshake and finds out in week six that the criteria moved.

This is the senior bar: discovery discipline is the upstream lever on quota attainment. Per RepVue SE compensation data, the top-quartile SEs at the same company on the same product run their discovery-to-close ratio at 2-3x the median; the difference is almost entirely qualification rigor at the front of the funnel, not demo or POC craft at the back.

The discovery-and-research pre-call workflow

The 2026 senior SE invests 30 minutes of pre-call research before every discovery call. The research compounds: it surfaces the prospect-specific signal that anchors the call, signals competence to the prospect inside the first 90 seconds, and reduces the discovery-question burden during the call itself. The canonical workflow:

1. LinkedIn research on the meeting attendees (10 minutes). Title, tenure, prior roles, recent posts. The tenure data calibrates expectations: a VP Data 18 months into the role is still building their initial-spend mandate; a VP Data 6 years in has institutional inertia working against any vendor change. Recent posts surface current priorities and language patterns the SE can mirror.
2. Company-news scan (5 minutes). Funding rounds, acquisitions, layoffs, exec changes, product launches in the last 90 days. A company that just raised a $200M Series D is in growth mode; a company that just laid off 15 percent (BLS) is in cost-discipline mode. The discovery call's economic-buyer narrative changes accordingly.
3. GitHub and engineering-blog deep-read (10 minutes). Tech-stack signal, language preferences, architectural patterns. A prospect whose engineering blog praises Rust and shows production deployments of Rust services has different integration concerns than a prospect whose stack is Java-on-Spring. The SE who walks in with the tech-stack inferred is materially ahead of the SE asking what does your stack look like?
4. Prior-quarter earnings call review for public companies (5 minutes). Read the investor-letter section, scan the Q&A for analyst questions about technology investment, look for explicit mentions of the buying-category. Public companies' management commitments on earnings calls are load-bearing context for the economic-buyer narrative; the SE who quotes the CFO back to the prospect's CFO is operating at a different level than the SE who relies on marketing-page copy.

The discipline is non-optional at senior+. The SE who skips pre-call research and asks generic discovery questions burns the prospect's first-call patience on context-gathering the SE could have done before the call. The 30-minute pre-call investment triples discovery quality and is the single highest-ROI behavior in the SE workflow.

Common discovery anti-patterns and how to avoid them

Five anti-patterns recur across SE discovery work and degrade close rates predictably:

• Feature-dumping during discovery. The SE who answers the prospect's first open-ended question with a 10-minute product monologue has converted the discovery call into a premature demo. Discovery is question-asking work; feature presentation is downstream. The fix: when the prospect asks tell me about the product, the senior SE redirects with I'd love to; before I do, can I ask what specifically you'd like me to address? I'd rather show you the parts that matter to your situation than walk through the generic tour.
• Treating discovery as an information-extraction interview. The SE who runs discovery as a unilateral question-list (question 1, question 2, question 3) burns the prospect's patience and surfaces shallow answers. Discovery is a collaborative diagnosis: the SE proposes a hypothesis (given what you've described, my guess is the binding constraint is X; does that match what you're seeing?) and the prospect either confirms or corrects. The hypothesis-and-correction loop produces the depth that question-list discovery cannot.
• Missing the economic buyer. The SE accepts the prospect's framing that my manager will sign off, don't worry about it and never gets the economic buyer in the room. Six weeks later the deal stalls because the actual sign-off authority has questions that were never answered. The fix: the senior SE asks for a second-call meeting with the economic buyer present as a standard step, framed around I want to make sure the architecture conversation lands with everyone who needs to hear it.
• Conflating champion with detractor (or with coach). The SE assumes the engaged person on the call is the champion, fails to test for advocacy, and discovers in week eight that the champion was a coach who provided information but never advocated internally. The fix: test champion status by asking the prospect to take a specific action that requires internal political capital (an introduction to the economic buyer, a calendar invite to a security-review meeting, a forwarded email to the procurement contact). Champions take the action; coaches deflect.
• Skipping decision-process mapping. The SE collects criteria without mapping the order of gates and the timeline. The deal moves into a demo before the SE knows whether security review fires before or after the technical evaluation, whether procurement requires a 60-day or 90-day cycle, whether legal redlines on the MSA are typically 2 weeks or 2 months. The fix: the PROCESS-before-CRITERIA ordering in MEDDIC is deliberate. Map the workflow first; the criteria are easier to qualify against once the workflow is explicit.

Each anti-pattern has the same root cause: the SE optimized for the immediate-call outcome (the prospect was happy, they asked for a follow-up) rather than for the close-cycle outcome (this deal will close on the predicted date at the predicted ACV). Discovery is the upstream lever on the close cycle; senior SEs run discovery for the close, not for the meeting.