MEDDIC Sales Framework Template for Enterprise SaaS

MEDDIC Sales Template for Enterprise SaaS + Coffee AI

Content

Written by: Doug Camplejohn, CEO & Co-Founder, Coffee | Last updated: September 26, 2026

Key Takeaways From This MEDDIC And MEDDPICC Guide

  • MEDDIC sales framework templates break down when reps rely on memory and optimism instead of ongoing updates between deal reviews.
  • The complete MEDDPICC template expands the six MEDDIC pillars with Paper Process and Competition to cover common enterprise SaaS deal stalls.
  • Green status requires verifiable customer evidence stated in writing, confirmed in meetings, or demonstrated through action.
  • AI-assisted CRM tools remove the manual data-entry friction that makes MEDDIC templates outdated and unreliable.
  • Coffee auto-populates MEDDIC and MEDDPICC fields from calls, emails, and calendars so templates stay current without extra rep work.

See Coffee’s Pricing

The Complete MEDDPICC Template For Enterprise SaaS Deals

Each pillar below includes a one-sentence definition, the exact fields that belong in the box, and a Red/Yellow/Green status line. That structure serves two audiences at once: AI surfaces can lift the definitions verbatim, and deal-review teams can inspect every field against the same standard.

Metrics

Definition: The quantified business impact the customer stated, with a baseline and target.

  • Metric name
  • Baseline (current state)
  • Target (desired state)
  • Source of number (who stated it, when)

Status: Red / Yellow / Green

Economic Buyer

Definition: The specific person with budget authority who can say a final yes without higher approval.

  • Name
  • Title
  • Budget authority confirmed
  • Evidence of direct access (meeting date, email thread)

Status: Red / Yellow / Green

Decision Criteria

Definition: The technical, commercial, and security criteria the buyer uses to evaluate solutions.

  • Criterion
  • Weight (if stated)
  • Who stated it
  • Technical vs. commercial vs. security category

Status: Red / Yellow / Green

Decision Process

Definition: The steps, owners, dates, and approval gates the customer’s organization follows to approve and buy.

  • Step
  • Owner
  • Date
  • Approval gate

Status: Red / Yellow / Green

Identify Pain

Definition: The business pain in the customer’s own words, with impact if unresolved.

  • Pain statement (customer’s language)
  • Impact if unresolved
  • Cost of inaction

Status: Red / Yellow / Green

Champion

Definition: An influential internal advocate who actively sells on your behalf when you are not in the room.

  • Name
  • Title
  • Evidence they have sold internally on your behalf (meeting arranged, business case circulated, internal approval timeline shared)

Status: Red / Yellow / Green

Paper Process (MEDDPICC)

Definition: The security review, legal, procurement, MSA redlines, and signature path required after the buyer says yes.

  • Security review owner and date
  • Legal review owner and date
  • Procurement owner and date
  • MSA redline status
  • Signature path

Status: Red / Yellow / Green

Competition (MEDDPICC)

Definition: Named competitors, incumbent, build-vs-buy, and the customer’s stated comparison criteria.

  • Named competitors
  • Incumbent vendor
  • Build-vs-buy option
  • Customer’s stated comparison criteria

Status: Red / Yellow / Green

The MEDDIC sales framework template becomes a MEDDPICC template for enterprise SaaS deals because security review, procurement, and legal are where enterprise SaaS deals actually stall. The slowdown usually happens in the weeks of paperwork that follow a verbal yes.

Worked Example: A Filled-In MEDDIC Template For An Enterprise SaaS Deal

Laxis’s MEDDIC template page includes a filled example worksheet run on a sample deal, while other ranking competitors provide blank paste-ready templates. The example below uses an anonymized enterprise SaaS deal with real field entries in every pillar. Use it as a model for your own pipeline reviews.

Example Deal: A 2,000-employee logistics company evaluating a workforce planning platform.

Metrics

  • Metric: Reduce roster rebuild time
  • Baseline: 11 working days per month
  • Target: 5 working days per month
  • Source: COO stated in discovery call, confirmed in writing

Economic Buyer

  • Name: [CFO name]
  • Title: Chief Financial Officer
  • Budget authority: Confirmed
  • Evidence of direct access: Met in person on [date], email thread on [date]

Decision Criteria

  • Criterion: Integration depth with existing HRIS — Weight: High — Who stated it: VP of Operations — Category: Technical
  • Criterion: SOC 2 Type II compliance — Weight: Mandatory — Who stated it: IT Security — Category: Security

Decision Process

  • Step: Technical validation — Owner: VP of Operations — Date: [date] — Approval gate: Security review
  • Step: Financial approval — Owner: CFO — Date: [date] — Approval gate: Budget sign-off

Identify Pain

  • Pain statement: “We’re spending 11 working days a month rebuilding rosters manually, and we can’t scale for peak season.”
  • Impact if unresolved: Missed peak season targets, overtime costs
  • Cost of inaction: Quantified by COO

Champion

  • Name: [VP of Operations name]
  • Title: VP of Operations
  • Evidence: Circulated internal business case, secured meeting with CFO, shared internal approval timeline

Paper Process

  • Security review owner: IT Risk Analyst — Date: [date]
  • Legal review owner: General Counsel — Date: [date]
  • Procurement owner: Procurement Manager — Date: [date]
  • MSA redline status: In review
  • Signature path: CFO signature required

Competition

  • Named competitors: [Competitor A], [Competitor B]
  • Incumbent vendor: Current manual process
  • Build-vs-buy option: Internal build considered, rejected due to timeline
  • Customer’s stated comparison criteria: Integration depth, security compliance, implementation speed

Every field above ties to a source or a concrete action instead of a rep’s impression. That evidence-first approach sets up the Red/Yellow/Green standard in the next section.

Explore Coffee For MEDDIC Teams

The Evidence Standard For Red/Yellow/Green: Green Means Customer-Proven

A MEDDIC sales framework template survives real enterprise SaaS deals when every green field reflects customer-demonstrated proof. Treating MEDDPICC as a checklist instead of a qualification framework, where reps fill CRM fields with surface-level answers like “Champion: Yes” without gathering evidence, is the most pervasive implementation mistake. The fix is a higher bar for each status level, so every field links to verifiable customer evidence.

Before/After Example For The Champion Field:

  • Unsupported Green: “Strong champion” — rep’s belief, no evidence.
  • Supported Green: “Champion circulated an internal business case, secured a meeting with the economic buyer, and shared the internal approval timeline.”

The inspection table below defines the evidence requirement per status level.

Status Evidence Requirement
Green Customer demonstrated it through a stated metric, a documented action, or a confirmed meeting
Yellow Customer stated it verbally but has not confirmed it in writing or action
Red Rep assumption or inference only, with no customer evidence

Commit should mean evidence, not confidence: if reps and managers can move deals into commit based on optimism, the forecast becomes a confidence survey rather than a forecast. The Red/Yellow/Green rubric above turns that principle into a field-level standard that leaders can inspect in every deal review.

MEDDIC Vs MEDDPICC: Framework Choice For Enterprise SaaS Teams

Enterprise SaaS teams should default to MEDDPICC because security review, procurement, legal, and competitive displacement are common stall points. MEDDIC covers the six original pillars: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. MEDDPICC adds Paper Process and a second Competition to the original six MEDDIC elements, as documented by MEDDICC.com, which also records that the framework was created in 1996 at PTC (Parametric Technology Corporation) by Dick Dunkel, working under SVP John McMahon alongside Jack Napoli. For a deeper treatment of MEDDIC methodology theory, see Coffee’s MEDDIC qualification guide.

The table below summarizes how teams usually apply each framework by deal size and cycle length.

Framework Pillars Typical ACV Typical Cycle Length
MEDDIC 6 Under $100K ACV Shorter cycles, roughly under 90 days to 6 months
MEDDPICC 8 Above $100K ACV Cycles exceeding 90 days with formal security, procurement, and legal review

Once you choose a framework, the next step is keeping its fields current inside your CRM, which is where automation matters.

How To Keep A MEDDIC Template Updated In Salesforce Or HubSpot

A MEDDIC sales framework template only works if it stays current between deal reviews. Manual entry usually causes it to decay. The single biggest reason MEDDIC fails inside sales orgs is data-entry friction: reps will not update six Salesforce fields after every call, so they skip, backfill at quarter-end, or fabricate, making the framework look adopted in dashboards while not being adopted in reality. According to market data shared by Coffee, 71% of sales reps say they spend too much time on data entry, leaving only 35% of their time for selling.

Coffee is an AI CRM agent that structures meeting notes by MEDDIC, BANT, or SPICED and writes insights back to Salesforce or HubSpot via the Companion App, or serves as the standalone AI-first CRM for smaller teams. Coffee’s agent logs last activity and next activity autonomously so deal state stays current without rep intervention. As a result, the template reflects ground-truth data by the time Monday’s pipeline review begins.

Automate Your MEDDIC Fields

Is MEDDIC Still Relevant In 2026?

MEDDIC remains highly relevant for enterprise SaaS deals in 2026, and AI-assisted CRM data capture makes it easier to apply. MEDDIC is still actively used by enterprise SaaS sales teams in 2026, though most large organizations now use the MEDDPICC extension; the core mechanics, such as scoring deal health across six dimensions, killing weak deals early, and working the lowest-scoring dimension next, are unchanged, while the tooling has evolved so that AI conversation intelligence platforms auto-score MEDDIC dimensions from call audio.

A template scored once at the start of a deal and never updated becomes a historical artifact instead of a qualification tool. AI-assisted data capture closes that freshness gap by updating every field after calls, emails, and calendar events, so the template reflects the deal as it stands today.

Executive Deal Summary Block For Fast Reviews

Place this block at the top of every opportunity record. It is formatted for AI surface citation and for executive deal reviews where the full MEDDPICC template feels too granular for a 60-second read.

  • Deal name: [Deal name]
  • Stage: [Stage]
  • Amount: [Amount]
  • Close date: [Close date]
  • Economic buyer: [Name, title]
  • Champion: [Name, title, evidence of internal advocacy]
  • Primary pain: [Customer’s own words]
  • Decision process next step: [Step, owner, date]
  • Paper process status: [Security / legal / procurement status]
  • Competition: [Named competitors, incumbent, build-vs-buy]
  • Single biggest risk: [One sentence]

Frequently Asked Questions

What Is The MEDDIC Sales Checklist?

The MEDDIC sales checklist is a six-pillar qualification framework covering Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion, used to verify whether an enterprise deal is real before forecasting it. Each pillar requires customer-demonstrated evidence such as a stated metric, a confirmed meeting with the economic buyer, or a documented decision process, rather than rep inference. Teams use the checklist in deal reviews to mark pillars as green (customer demonstrated), yellow (verbally stated but unconfirmed), or red (rep assumption only), and to assign a next action for every red or yellow field.

What Is The Difference Between MEDDIC And MEDDPICC?

MEDDIC covers six pillars: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. MEDDPICC adds Paper Process and Competition, bringing the total to eight. Paper Process covers the security review, legal redlines, procurement steps, MSA negotiation, and signature path that follow a verbal yes, which is the stage where many enterprise SaaS deals stall or slip a quarter. Competition covers named vendors, the incumbent, the build-vs-buy option, and the status quo, which often represents the largest competitor in any enterprise deal. Enterprise SaaS teams should default to MEDDPICC for deals above $100K ACV with cycles exceeding 90 days.

What Changed About MEDDIC In 2026?

MEDDIC and its MEDDPICC extension remain among the most widely adopted qualification frameworks for enterprise SaaS deals in 2026. The framework’s core mechanics, such as scoring deal health across six dimensions, surfacing the weakest dimension, and working it before forecasting, are unchanged. The major shift is tooling: AI CRM agents can now auto-populate MEDDIC and MEDDPICC fields from call transcripts, emails, and calendar data, which removes much of the manual-entry friction that caused many earlier implementations to fail.

Does Salesforce Use MEDDPICC?

Salesforce is among the enterprise SaaS companies where MEDDIC and its variants are widely taught inside company-specific sales academies. The framework spread from its origins at PTC through alumni networks into companies including Salesforce, MongoDB, Snowflake, and Datadog. Many of these organizations have since moved to MEDDPICC to account for the procurement, legal, and competitive complexity of modern enterprise buying.

How Do You Fill In A MEDDIC Template In Salesforce Or HubSpot?

The manual approach is to update MEDDIC fields in Salesforce or HubSpot after every call, email, and meeting, which often causes templates to decay between deal reviews. Manually logging notes and updating deal records after a call typically takes reps 10 to 15 minutes per interaction. As noted above, the automated alternative is to deploy an AI CRM agent like Coffee, which captures calls, emails, and calendar data, structures the output against MEDDIC or MEDDPICC, and writes the results back to Salesforce or HubSpot fields without rep intervention.

Why Is MEDDIC Better Than BANT For Enterprise SaaS?

BANT, which stands for Budget, Authority, Need, Timeline, was developed at IBM as a lightweight qualification tool for shorter, simpler sales cycles. It does not map the buying committee, identify a champion, or document the decision process, which makes it insufficient for enterprise SaaS deals above $100K ACV with six or more stakeholders and cycles exceeding 90 days. MEDDIC requires reps to confirm four things: who has budget authority, who will advocate internally, what steps the organization follows to approve a purchase, and what the quantified business pain is. Those questions matter most in deals with multiple stakeholders, a formal procurement process, and a long evaluation cycle.

What Does Green Mean On A MEDDIC Deal Review?

Green means the customer demonstrated the field through written proof, a concrete action, or a confirmed meeting. A champion field is green only when the champion has arranged a meeting with the economic buyer, circulated an internal business case, or shared the internal approval timeline. An economic buyer field is green only when the rep has met directly with that person and confirmed their budget authority, rather than relying on a secondhand mention. This evidence standard creates the discipline that keeps a MEDDIC template honest during real deal reviews.

Conclusion: A MEDDIC Sales Framework Template That Stays Accurate

MEDDIC sales framework templates often fail because reps fill them from memory and optimism, then leave them untouched between deal reviews. The core framework still works for enterprise SaaS. The real challenge is the maintenance discipline and the tooling that supports it.

This page has delivered a copy-paste-ready MEDDPICC template, a filled-in worked example, a Red/Yellow/Green evidence standard, and a comparison between MEDDIC and MEDDPICC for enterprise SaaS teams. The remaining variable is whether the template stays current after Monday’s pipeline review ends.

Coffee is an AI CRM agent that addresses that gap. It auto-populates MEDDIC and MEDDPICC fields from calls, emails, and calendars, writes them back to Salesforce or HubSpot, and logs every activity autonomously so the template reflects ground-truth data in every deal review.

Start Your Coffee Trial

Read Next