Written by: Doug Camplejohn, CEO & Co-Founder, Coffee | Last updated: September 20, 2026
Key Takeaways For Running Real Enterprise Deals
- Map the Decision Process as three parallel tracks (technical evaluation, business approval, and paper process) from the first call to forecast accurately.
- Use direct discovery questions to identify named approvers, veto holders, and historical deal-killers instead of relying on vague buyer assurances.
- Build a Mutual Action Plan backward from the buyer’s go-live date and assign named owners on both sides for every milestone.
- Validate real progress with written milestone confirmations and treat silent deadline slips as stalled deals that need investigation.
- Coffee automatically structures MEDDIC data in your CRM so Decision Process milestones are captured after every interaction without manual entry.
See How Coffee Captures MEDDIC Automatically
What The Decision Process In MEDDIC Really Covers
The Decision Process in MEDDIC is the sequence of steps from “we like it” to “money moves.” It defines who approves what, in what order, and on what timeline. In MEDDIC, the Decision Process dimension is this sequence, and a strong version includes named approvers with named approval dates, a CFO date two to four weeks before contract close, and a mutual action plan signed by the champion.
This element is hard to operationalize because the information lives in the buyer’s head, not in the rep’s CRM. A rep can know the acronym cold and still have a Decision Process field that reads “they said they move fast,” which does not support a reliable forecast.
The framework was reverse-engineered at PTC in the mid-1990s from the habits of its best closers. The core principle remains simple: progress shows up as confirmed steps in the approval path, not as good feelings about a demo.
The Three Tracks Of An Enterprise Buying Process
If engagement alone does not define progress, the next question is what real progress looks like inside a buyer’s organization. Enterprise deals move along three tracks at once rather than through a single linear path. Technical, commercial, operational, and organizational evaluation happen in parallel, so one track can advance while another remains blocked. Mapping all three tracks from the first discovery call creates a realistic forecast.
Technical And Social Evaluation. This track covers demos, proof of concepts, stakeholder alignment, and end-user buy-in. Technical evaluation typically lasts four to eight weeks and is driven by the technical buyer and end users. The common failure is a successful pilot that produces no next step. When the champion cannot name what happens after the POC concludes, the business approval path was never mapped. Ask the champion to describe the next internal meeting after the pilot readout. If they cannot, the deal has stalled in this track regardless of demo quality.
Business Approval. This track covers business case review, budget allocation, and executive sign-off. Enterprise deals often stall between technical evaluation and business case when the champion cannot get internal alignment without economic buyer engagement. A common pattern is a champion who “represents” the economic buyer for months while the actual budget holder has never heard the price. If the buyer cannot name who signs, the economic buyer has not been engaged.
Paper Process. This track covers security review, legal redlines, procurement sign-off, vendor onboarding, and PO issuance. Per Ebsta/Pavilion 2025, deals without a confirmed paper process slip 38% of the time in the final 30 days. A deal can sit for weeks after a verbal approval because no one mapped the procurement sequence. When no one on the buying side can describe the steps between verbal agreement and countersigned contract, the paper process is unmapped and the close date is fiction.
These three tracks run in parallel. A deal can be technically approved, commercially stalled, and paper-process-unmapped at the same time. A simple workflow diagram that shows all three tracks with their distinct owners and exit criteria becomes a powerful artifact in week two of a deal.
Discovery Question Scripts That Surface The Real Approval Path
The questions below help you uncover the buyer’s actual approval sequence. Each question includes an example of a strong answer and a weak answer so you can hear the difference. The question “What happens if this slips past that date?” acts as an honesty test for any stated deadline.
“Walk me from today to the day we sign. What are the steps, who has to approve, and roughly when?”
Strong Answer: “Security review takes two weeks, then legal redlines, then the CFO signs. She signs anything over $50K.” Weak Answer: “I’m not sure, our procurement team handles that.”
“Who has the authority to say no to this deal, even after you’ve said yes?”
Strong Answer: “Our CISO has veto rights on any new SaaS vendor, and our CFO has to countersign anything above $100K.” Weak Answer: “I think I have the authority to approve this.”
“Has anyone tried to buy something like this before? What slowed it down or stopped it?”
Strong Answer: “We tried to buy a similar platform two years ago and it died in legal. They had issues with the data processing agreement.” Weak Answer: “Not that I know of.”
“Does this need legal, security, or procurement review? Who owns each of those, and how long do they typically take?”
Strong Answer: “Legal takes about three weeks, InfoSec runs a questionnaire that usually takes two weeks, and procurement needs a vendor registration form before they’ll issue a PO.” Weak Answer: “Probably, but I’ve never bought something at this price point before.”
“What’s driving the timeline you have in mind?”
Strong Answer: “We need this live before our January sales kickoff, which means signed by November 15.” Weak Answer: “We’d like to move quickly.”
“What happens if this slips past that date?”
Strong Answer: “We lose the budget. It goes back to the pool at year-end.” Weak Answer: “It would be unfortunate, but we’d figure it out.”
“When were you planning to introduce us to the person who signs?”
Framing the economic-buyer access question as “when” assumes access is normal and surfaces resistance early. Strong Answer: “I can set up a call with our CFO next week.” Weak Answer: “I’d need to check if that’s appropriate at this stage.”
“Is there a budget cycle or renewal we should be working around?”
Strong Answer: “Our fiscal year ends March 31 and budget has to be committed by February 15.” Weak Answer: “I’m not sure how our budget works for something like this.”
Apply the deadline honesty test to every date in the deal. When a stated deadline carries no consequence if it slips, treat it as a preference in your forecast.
How To Build A Mutual Action Plan For Enterprise Deals
Once discovery has surfaced the approval sequence, the next step is to put dates and owners on it. A Mutual Action Plan (MAP) is built backward from the buyer’s go-live date. Milestone due dates should be reverse-engineered from the buyer’s goal line and target date rather than from the seller’s sales cycle. If the steps do not fit before the date, the date is fiction, and discovering that in week two beats discovering it in week eleven.
An enterprise MAP has six parts: a goal line, six to twelve milestone rows, a named owner column, reverse-engineered dates, a status field (on track / at risk / overdue / done), and a biggest-risk row. Owner names should appear as a named person plus role, such as “Sarah (IT),” prefixed with “Buyer” or “Seller” so accountability stays clear.
Assign owners on both sides as named individuals. A plan where every owner sits on the seller’s side functions as a to-do list with an audience. In a composite $180K enterprise deal, eleven of fourteen MAP rows belonged to the buyer, which shows how a true MAP shifts work onto the buying side.
The MAP should live where the buyer can edit it, such as a shared document, a Digital Sales Room, or a collaborative workspace. Buyer behavior on the shared plan is a progress signal. A buyer who adds rows, moves a date earlier, or edits the plan unprompted shows real engagement, while a buyer who never touches a shared plan signals the opposite.
Update the MAP whenever the buying committee changes. New stakeholders get their own rows with owners and dates. Stale rows that have passed without completion and without explanation trigger escalation. A stale MAP erodes trust on both sides and signals that the process has become theater.
How To Test For Real Progress Versus False Engagement
Progress in an enterprise deal shows up as a milestone confirmed in writing. A buyer who adds a row to the MAP and accepts ownership advances the deal. A buyer who only attends calls and says “this looks great” does not.
Real progress leaves a paper trail. A security questionnaire is submitted and acknowledged. A legal review date is confirmed by the legal team rather than the champion. A budget approval appears in an email. An economic buyer meeting is booked with a named agenda. False engagement leaves only impressions, such as a responsive champion who cannot name the next internal step, a demo that generated enthusiasm but no follow-up, or a close date that has moved twice without explanation. The difference is whether the buyer’s organization produced an artifact.
Common Mistake: Treating a friendly meeting as advancement. The rep’s job is to convert activity into verified advancement through the buyer’s actual approval sequence.
When a deadline passes silently and the buyer’s promised answer never arrives, treat the deal as stalled. Investigate the cause by asking whether an internal meeting was cancelled, a new stakeholder appeared, or the budget changed. The real deal lives inside the buying committee’s internal state, and the only way to see that state is to ask directly.
What The Paper Process In MEDDPICC Includes
The Paper Process in MEDDPICC is the administrative, legal, and procurement path a deal follows from verbal agreement to signed contract. It forms the final and most underestimated stage of the enterprise buying process. MEDDICC Ltd defines Paper Process as “the series of steps that follow the Decision Process in how you will go from Decision to signature,” including security review, legal redlines, privacy assessment, procurement, vendor onboarding, and countersignature.
The sub-steps of the Paper Process in a typical enterprise SaaS deal are:
- Security Review: The buyer’s InfoSec team evaluates the vendor against security requirements, often through a questionnaire. Enterprise security questionnaires often contain 200 or more questions and add significant time and coordination work.
- Legal Redlines: The buyer’s legal team reviews and redlines the MSA, DPA, and any service-level terms. Contracts in complex sales often spend more than 100 days in legal and procurement queues before sign-off.
- Vendor Onboarding And Procurement: Procurement validates sourcing policy, requires vendor registration forms, and then generates the purchase order.
- PO Issuance And Countersignature: The purchase order is issued, routed for executive countersignature, and the contract executes.
Deals often stall here because the commercial decision is complete while operational approval gates remain uncleared and invisible to the forecast. According to Gartner’s Enterprise Contract Velocity Report 2024, 27% of enterprise SaaS deals that reach contract stage experience a delay of more than 30 days due to paper process factors such as procurement requirements, legal review, and approval hierarchies that were never identified during evaluation.
The MEDDPICC paper process should start earlier than most teams expect. Send the security questionnaire in week one. Share standard contract terms early so legal can review in parallel with the evaluation. Ask about procurement timelines before you forecast a close date. Running Paper Process activities in parallel with final evaluation activities allows organizations to close 15 to 20 days faster than running the process sequentially.
Common Mistake: Waiting to discuss the paper process until the deal feels “ready to close.” By that point, the security questionnaire queue may already be three weeks long and the quarter already out of reach.
Instrumenting The MEDDIC Decision Process In Your CRM
Decision Process tracking often decays because it depends on manual data entry and reps rarely keep up. MEDDIC adoption usually fails on data-entry friction, since reps will not update six Salesforce fields after every call and instead skip, backfill at quarter-end, or fabricate. A field filled in at quarter-end reflects history rather than a live forecast.
Coffee’s agent solves this problem at the source. Instead of asking reps to act as data entry clerks, Coffee automatically creates and enriches contacts and companies from email and calendar, logs activity, and structures notes according to MEDDIC, BANT, or SPICED. Qualification data enters the system consistently after every interaction, and the Decision Process field reflects what buyers actually said on calls.
Coffee’s Pipeline Compare feature visualizes week-over-week changes and highlights progressed deals, stalled opportunities, and new additions. This turns pipeline reviews into strategic discussions. Managers can see which Decision Process milestones moved, which stalled, and which remain blank without asking reps to build spreadsheets.
Coffee works as a standalone AI-first CRM or as a companion app on top of Salesforce or HubSpot. The agent handles data capture, and the pipeline intelligence surfaces the patterns.
Validation Signal: The Decision Process works when buying-committee fields are populated in the CRM after every meaningful conversation, MAP milestones stay current, and deal reviews surface stalls early because the system captured the data automatically.
Start Instrumenting Your Decision Process
MEDDIC Versus MEDDPICC: How Paper Process Fits In
In the base MEDDIC model, the paper process activities such as procurement, legal, security, and IT review live inside the Decision Process element. MEDDPICC elevates Paper Process to its own explicit element. In a MEDDIC shop, a rep who has mapped the Decision Process thoroughly has usually mapped the paper process as part of that work. In a MEDDPICC shop, the paper process becomes a separate qualification gate with its own score, discovery questions, and CRM field.
For deals above $100K ACV that involve formal procurement, security review, and legal redlines, MEDDPICC’s separation of the two elements helps teams qualify risk more clearly. It forces explicit mapping of the paper process instead of assuming it sits inside a generic Decision Process field.
FAQ
How Often Should I Update The Mutual Action Plan?
Review the MAP at the start of every buyer-facing call with a quick status check on what is done, what is at risk, and what comes next. Internally, any deal with more than three stakeholders on the buying side deserves a weekly sync. A plan that goes two weeks without review quickly loses relevance and trust. Send the recurring calendar invite for the weekly MAP review while you are on the call. When a milestone slips, update the MAP in front of the buyer so the change stays collaborative.
Who Owns The Decision Process On The Sales Side?
The account executive owns the Decision Process map and keeps it current after every meaningful conversation. The sales manager inspects that map in weekly one-on-ones by asking for evidence behind the Decision Process field. The manager asks what the buyer said, in which meeting, and where it is documented. The manager also owns escalation when the Decision Process remains incomplete on a deal in the commit forecast.
What If The Buyer Will Not Name The Economic Buyer?
Use the “when” framing from the discovery section and then pay attention to the response. If the champion deflects repeatedly, treat that behavior as a qualification signal. The champion may lack the influence to make the introduction or may feel less committed to the deal than the forecast suggests. A champion who will not spend fifteen minutes mapping their own buying process or making a single introduction behaves more like a coach. Ask directly what would need to be true for them to set up a short call between your team and their CFO. Their answer reveals both political capital and the real barrier to economic buyer access.
How Early Should The Paper Process Start?
Begin paper process discovery in the first or second qualification call, before pricing is final and well before a verbal yes. Ask who owns legal review, how long security questionnaires usually take, and whether procurement requires competing bids. As covered above, week one is the right time to start the formal steps. The real risk of waiting is a deal that finishes evaluation late in the quarter and then discovers a six-week legal review cycle that pushes it out of the budget window.
How Does The Decision Process Change As Deal Size Grows?
At lower ACVs, the Decision Process often involves one or two approvers, a short legal review, and a light procurement step. As deal size grows, the Decision Process expands into a multi-track committee. Each track gains its own owner, timeline, and exit criteria. Gartner’s B2B buying journey research puts a typical complex B2B purchase at six to ten stakeholders, while Forrester’s State of Business Buying puts the average enterprise buying group at around thirteen people. Above $100K ACV, the economic buyer usually sits at a divisional CFO or VP level rather than as the champion’s direct manager. The MAP should reflect this reality with separate milestone rows, named owners, and status fields for each track.
Conclusion
The MEDDIC Decision Process functions as a live map of how the buying committee approves, reviews, and signs. This article walked through the three tracks of an enterprise buying process, the discovery questions that surface them, the MAP that sequences them, the progress tests that validate them, the paper process that often delays them, and the CRM instrumentation that keeps everything current without extra rep effort.
A deal that looks healthy in the CRM because the rep had three good calls differs from a deal where the economic buyer has been met, the paper process has been mapped, and MAP milestones stay current. The discipline that separates those two deals comes from a Decision Process that is mapped, tested weekly, and supported by a system that captures data automatically.
Put The Decision Process To Work
