MEDDPICC is not a close plan or a cadence. It is a diagnostic that answers one question for every open opportunity: do we actually know enough about this deal to call it winnable, or are we hoping?
MEDDPICC is an enterprise sales qualification framework with eight criteria: Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, and Competition. It extends the older MEDDIC method by adding Paper Process (legal and procurement) and Competition. Sales teams use it to score complex, multi-stakeholder deals and expose risk before the quarter closes. Reps who qualify with MEDDPICC forecast more honestly and lose fewer deals in the final weeks.
The six things to know before rolling MEDDPICC out, and the one failure mode that turns a good framework into dashboard theater.
MEDDPICC stands for Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, and Competition. Each letter is a specific question the rep is expected to answer with evidence from the account. The framework was built at PTC and refined at companies like MongoDB and Snowflake for high-ACV, multi-stakeholder enterprise sales.
MEDDIC (the original six-letter version) handled Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, and Champion. As enterprise deals got longer and procurement got heavier, two letters were added. Paper Process covers legal, security, and procurement review. Competition covers who else the buyer is evaluating and why they might choose them.
MEDDPICC is overhead for a transactional sale. It is leverage for an enterprise one. Use it when the deal involves multiple stakeholders, custom procurement, a security review, legal redlines, and a sales cycle measured in quarters. For SMB velocity sales under thirty days, MEDDIC or BANT is usually enough.
Every criterion maps to a specific question. If the rep cannot name the economic buyer, that is a risk. If the paper process is unknown ninety days from close, that is a bigger risk. MEDDPICC exposes the holes in a deal story early, when there is still time to fill them, instead of in the last week of the quarter when it is too late.
Most teams rate each letter zero (no information), one (surface answer), two (confirmed with the account), or three (documented and defensible). An opportunity with twenty-four possible points and a sixteen-point score is in better shape than one with a twenty-point score where Economic Buyer and Paper Process are both zero. The pattern of gaps matters more than the sum.
The framework dies the moment reps treat the fields as a form to fill in before the pipeline review. MEDDPICC is a coaching tool. Scores are supposed to open a conversation between the rep and the manager about which gaps to close next, which stakeholders to meet, and whether the deal should still be forecast. Without that coaching layer, the fields become dashboard theater.
Every MEDDPICC criterion is a question with a specific, verifiable answer. The point is not to memorize the acronym. The point is to replace vague deal narrative ("the customer loves us") with evidence ("the VP of Engineering, who owns the two hundred fifty thousand dollar budget line, has committed to a June decision and will sponsor the security review"). The eight questions below are what every opportunity in an enterprise pipeline should be able to answer before it is called a commit.
The quantified business outcome the buyer expects. Hours saved per rep, deals won per quarter, cost reduced per month, cycle time cut by a measurable percentage. Metrics are the number the champion will carry into the executive meeting to defend the purchase. A deal without a metric is a feature pitch.
The one person with discretionary authority over the money. Not the user, not the influencer, not the procurement contact. The economic buyer can say yes without asking anyone else. If the rep cannot name this person, has not met them, or is relying on a champion to represent them, the deal has an authority gap that will surface at the worst time.
The explicit requirements, technical, functional, financial, and vendor-related, that the buyer will use to compare options. Decision criteria are usually a mix of must-haves and nice-to-haves. The rep should know which criteria the champion wrote, which ones the economic buyer added, and which ones a competitor seeded.
The steps, meetings, approvals, and reviews between today and signature. Who meets when, who signs off at each gate, which committee hears the final recommendation. A rep who knows the decision process can map the next thirty, sixty, and ninety days. A rep who does not is forecasting a close date they invented.
The second P is what MEDDPICC added to MEDDIC. Enterprise deals do not close when the economic buyer says yes. They close when legal signs the MSA, security approves the vendor risk assessment, procurement issues the PO, and finance books the spend. The paper process is often the longest stretch of a deal and the one reps understand least.
The specific, named pain the buyer is willing to spend money to resolve. Pain is not interest. Pain is the quarterly board slide where a KPI is red, the executive who got yelled at, the deal that was lost because the system failed. If the rep cannot name a pain the buyer has already quantified, the opportunity is a nice-to-have in disguise.
A champion has personal credibility, access to power, a reason to want the deal to happen, and the willingness to spend political capital advocating for it. A coach is helpful but will not fight for the deal. A champion will. Verifying a champion is the single highest-leverage activity in enterprise selling.
The second C is the other half of what MEDDPICC added. Competition includes other vendors, the status quo (do nothing), and internal builds. The rep needs to know who the champion secretly prefers, what the economic buyer has used before, and which criteria a competitor is quietly setting in their favor. Pretending there is no competition does not make it go away.
Qualification frameworks are tools, not religions. The right question is which tool fits the deal shape in front of you. MEDDPICC is designed for high-ACV, multi-stakeholder sales where the loss of a single deal matters and the cycle gives you time to work the account properly. Running MEDDPICC on a two-week SMB sale is overhead that will not pay for itself. Running BANT on a nine-month enterprise deal will leave the rep blind to the risk that actually kills the opportunity.
MEDDPICC is overkill for a thousand-dollar seat sale. It earns its complexity when the contract value is high enough that losing one deal materially changes the quarter. In practice, teams usually adopt MEDDPICC on new business deals above fifty thousand dollars annual value, with heavy enforcement above one hundred thousand.
Enterprise cycles have room for MEDDPICC because they have the time to run proper discovery, hold multiple stakeholder meetings, work through security and legal, and build the business case. Short cycles compress that work out of existence and favor leaner frameworks like MEDDIC or straight pain-based discovery.
MEDDPICC pays off when the buying committee includes a user champion, a technical evaluator, an economic buyer, a procurement contact, a legal reviewer, and often a security team. The framework is a map through that complexity. In a single-owner purchase, most of the letters collapse into one person and the overhead is wasted.
Deals that run through formal procurement with an MSA, a security questionnaire, a DPA, and a vendor risk review are exactly where the Paper Process letter earns its place. If the buyer is a mid-market company that just emails a signed order form, MEDDPICC's P is low-value and MEDDIC covers the deal fine.
MEDDPICC's second C matters most when the buyer is actively evaluating alternatives. If the account is single-source (a renewal, a sole-source expansion, a cross-sell with no comparable alternative), the Competition letter is thin and the framework gets lighter.
Enterprise commits sit at the top of the forecast and move the number. The cost of a wrong call is enormous. MEDDPICC exists to make that call defensible. For transactional deals that smooth out across hundreds per quarter, individual qualification depth matters less because the law of large numbers absorbs the error.
A framework that lives in a slide deck is a framework nobody uses. MEDDPICC succeeds when it lives in the CRM as structured fields on the opportunity, is scored at every stage, and shows up in the pipeline review as the primary language managers and reps speak. The practical shape below is what high-performing enterprise teams run, and it is the same shape a CRM should enforce by default.
Each of the eight letters gets a score. Zero is no information. One is a surface answer the rep believes. Two is confirmed with the champion or buyer directly. Three is documented in writing, with a date and a source. The score is only as good as the evidence behind it, so the CRM field should require a note, not just a number.
A pipeline stage can require specific MEDDPICC minimums. For example: cannot move past Qualified until Pain and Champion are at two or above. Cannot move past Proposal until Economic Buyer and Paper Process are at two or above. The CRM enforces the gate, so stages stop being a vibe and start being a contract.
Pipeline review becomes "walk me through the MEDDPICC on your top three commits." The conversation moves from "how are you feeling?" to "which letter is the weakest, and what is the plan to raise it by next week?" This is where qualification turns from documentation into coaching, which is the only shape in which it actually improves win rate.
A deal with twenty-two out of twenty-four MEDDPICC points, three on Economic Buyer, Paper Process, and Champion, is a different forecast risk than a deal with the same stage and amount but zeros on Economic Buyer and Paper Process. Weighting the forecast by MEDDPICC depth, not just stage, produces a more honest number for leadership.
A simple report filters open commits where Economic Buyer or Paper Process is scored one or lower. Those are the deals the quarter will embarrass you on. The sales leader starts the week on that report, not on the full pipeline, and the account team gets two weeks to raise the score before the deal is pulled from the commit.
Lost deals get a MEDDPICC review on the way out. Which letter was weakest? Was Competition under-scored? Was the Decision Process actually understood? The pattern across many losses tells leadership which stage, which letter, and which coach needs attention. Loss analysis is the feedback loop that turns MEDDPICC into a learning system, not a static form.
MEDDPICC does not fail because the framework is wrong. It fails because teams install the fields without installing the behavior. The failure modes below are the ones that show up every quarter in companies that rolled MEDDPICC out six months ago and are quietly wondering why forecasting still slips. Each one has a fix, and each fix is a behavior change, not a software change.
Reps fill in the eight fields the hour before pipeline review, with whatever numbers avoid an awkward conversation. The data is noise. The fix is to require evidence per field, review the evidence in deal reviews, and reward honest ones and twos over fictional threes. A low score with a real plan beats a high score with no proof.
If the manager cannot articulate what a two looks like on Economic Buyer versus a three, reps will not either. MEDDPICC requires manager fluency. Dedicated coaching sessions, calibration meetings where several managers score the same anonymized deal, and leader-led examples are what install the framework in practice.
MEDDPICC is diagnosis. A close plan is prescription. Teams that confuse the two end up with reps filling out an eight-field checklist and no actual plan to raise the weakest letters. The correct flow is to score, identify the weakest letter, then build a specific plan (meeting, email, event, demo) to raise it.
MEDDPICC without pipeline-stage enforcement is a dashboard. Reps advance deals through stages regardless of score, and the framework becomes advisory. Stage gates (cannot advance to Proposal until Pain, Champion, and Economic Buyer are at two or above) are what give the data weight.
Forcing MEDDPICC on a two-week SMB sale is where sales adoption goes to die. Reps correctly see it as overhead, hate the ritual, and the data quality collapses even on the enterprise deals where it would help. The fix is explicit scope: MEDDPICC on deals above a threshold, lighter frameworks below.
If MEDDPICC data is captured during the deal and never looked at after the deal closes lost, the organization loses the chance to learn where the framework missed. A quarterly loss review that reads MEDDPICC scores against outcomes is what turns qualification from a ritual into a system that gets smarter.
A spreadsheet is where MEDDPICC starts and where MEDDPICC dies. Running it properly requires the CRM to model the eight letters as structured fields on every opportunity, enforce them at stage transitions, surface the gaps in reports, and keep the scores versioned so coaching can see progress over time. The patterns below are what a modern CRM should ship out of the box, not what a Salesforce admin has to build in a two-month customization project.
Each letter is a numeric field on the opportunity, zero to three. Each one has an accompanying text field for the evidence note. The CRM renders them as a MEDDPICC panel on the deal page so the rep sees the full qualification picture, not a scatter of individual fields.
A pipeline stage declares which letters must be at a given score before an opportunity can advance. Moving to Proposal requires Pain and Champion at two or more. Moving to Negotiation requires Economic Buyer and Paper Process at two or more. The CRM blocks the transition and tells the rep which letter is below gate.
When a rep raises Paper Process from zero to two over three weeks, that is the exact movement a coach wants to see. The CRM should snapshot MEDDPICC scores daily and chart the trend per letter per deal, so pipeline reviews see momentum, not just a static number.
The pipeline Kanban shows a quick MEDDPICC pill on each card: twenty-two of twenty-four, or sixteen of twenty-four with two zeros. Managers scan the board for the weak deals in two seconds, instead of opening each one. The red deals get the hour of coaching, the green deals get a nod.
If a letter has not been updated in thirty days on an open commit, the rep gets a nudge and the manager gets a report line. Qualification data decays. The buyer's decision process changes, the champion leaves, procurement adds a new reviewer. The CRM should enforce freshness, not just capture.
When a deal closes won or lost, the MEDDPICC scores freeze on the record. Loss reports slice by weakest letter, by stage at loss, by competitor named in the Competition field. The team learns which gaps cost real revenue, and the next quarter's coaching focuses there.
Strkr lets sales teams model MEDDPICC as per-opportunity fields, enforce required scores at every pipeline stage, and track score history over time. The whole revenue motion lives in one tool, so qualification data stops living in a side spreadsheet.
MEDDPICC stands for Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, and Competition. It is a sales qualification framework used for complex enterprise deals, especially those with multiple stakeholders, long cycles, and formal procurement. Each letter is a specific question the rep is expected to answer with evidence from the account.
MEDDIC is the older six-letter version: Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, and Champion. MEDDPICC adds two letters. Paper Process covers legal, security, and procurement workflow. Competition covers other vendors and the status quo. The additions reflect how enterprise deals changed as procurement got more formal and competitive evaluations became standard. For sales under thirty days with no formal legal review, MEDDIC is often sufficient.
Use MEDDPICC for high-ACV, multi-stakeholder enterprise deals with sales cycles of six months or longer, formal procurement, and real competitive evaluation. It is overhead for transactional SMB sales under thirty days, where lighter frameworks like BANT or straight pain discovery fit better. Many teams run MEDDPICC on deals above fifty thousand dollars annual value and lighter qualification below that threshold.
Most teams rate each of the eight letters from zero to three. Zero means no information. One is a surface answer the rep believes but has not verified. Two is confirmed with the champion or buyer directly. Three is documented in writing with a date and a source. The maximum score is twenty-four. The pattern of weak letters matters more than the raw total, so a score of twenty with zero on Economic Buyer is worse than sixteen with twos across the board.
Checkbox mentality. Reps fill in the eight fields minutes before pipeline review with whatever numbers avoid an uncomfortable conversation, and the data becomes noise. The fix is to require evidence per field, review that evidence in deal reviews, and reward honest low scores backed by a plan over inflated scores backed by nothing. Manager coaching, not more fields, is what makes the framework work.
They solve different problems. BANT (Budget, Authority, Need, Timeline) is a lightweight early-stage inbound qualifier for high-volume, short-cycle sales. MEDDPICC is a deep-stage qualifier for complex enterprise deals. Many teams use BANT or similar fit scoring at the top of the funnel to decide which leads become opportunities, then switch to MEDDPICC once the opportunity is in active evaluation.
In the CRM, as structured fields on every opportunity, with validation rules that enforce minimum scores per pipeline stage. Spreadsheet-based MEDDPICC drifts within a quarter: the fields are copied from an old deal, the scores are not updated, nobody runs reports off them. CRM-native MEDDPICC with per-stage gates, score history, and pipeline-board visibility is what turns the framework from a document into an operating system.
Field configuration takes a day. Behavior change takes a quarter or two. The sequence that works: pilot with a small enterprise team for one quarter, calibrate manager scoring on anonymized deals, add stage-gate validation on the second quarter, run loss review at the end of the second quarter, then expand to the full enterprise segment. Teams that try to install MEDDPICC in a single kickoff week usually see it decay into a checkbox exercise within sixty days.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
