Paper Process

Paper process is the administrative gauntlet between "yes" and signed contract: procurement intake, vendor onboarding, security review, legal redlines, signature authority, and PO issuance. It is the second P in MEDDPICC, added when the original MEDDIC framework kept losing quarters to deals that were technically won and contractually nowhere. A rep who cannot recite the customer's paper process step by step does not have a close date — they have a hope with a calendar attached.

How Paper Process Is Identified

Qualifying the paper process means getting answers to five concrete questions, ideally by the second meeting:

1. Who signs? Name and title, not "legal."
2. What reviews are required? Security, infosec, privacy, procurement — each one is a queue with its own SLA.
3. Is a PO required, and what triggers it? Some companies need 30 days just to issue one.
4. Are we an approved vendor? If not, onboarding alone can take 2-6 weeks.
5. Are there spending thresholds that change the approval chain? A $95K deal and a $105K deal can have completely different signature paths.

The output belongs in the CRM as a dated checklist, not a note that says "with legal."

A Worked Paper Process Example

An AE gets a verbal yes on September 10 for a $120K annual contract and sets the estimated close date to September 30. Her champion then reveals the real sequence: security questionnaire (10 business days), procurement vendor setup (15 days), legal redlines (2-3 rounds), CFO signature for anything over $100K, then PO issuance. That is 8-10 weeks minimum. The deal closes November 22 — a clean win that shows up as a Q3 deal slippage and a missed quarter. The deal was never in trouble. The forecast was, because the paper process was qualified in September instead of June.

When Sales Teams Use Paper Process

Enterprise AEs map it during discovery and update it at every stage exit. Sales managers interrogate it in deal reviews for any opportunity tagged commit — "walk me through the paper process" is the fastest way to expose a fabricated close date. RevOps uses paper-process fields to build realistic close-date models instead of trusting rep-entered dates, which skew optimistic by 3-4 weeks on average. Deal desk and legal teams care because late-stage surprises (a security review nobody scoped) are what turn a 45-day cycle into a 90-day one.

Limitations and Common Paper Process Misconceptions

The biggest misconception is that paper process starts after the decision. In enterprise deals it runs in parallel, and reps who wait for the verbal yes before engaging procurement hand the buyer's legal team a contract with zero context and zero urgency. A second failure mode is champion-dependence: the champion says "legal is fast here," the rep writes it down, and nobody verifies with procurement directly. Champions describe the paper process they wish existed. Third, paper process qualification does not shorten the process — it makes the timeline honest. Reps sometimes avoid asking because an 8-week answer ruins a quarter-end close date, which is exactly backwards: the deal slips either way, but only one version lets the manager forecast it. The exploit to watch is paper-process laundering — a rep claims "stuck in legal" for a deal that actually stalled on the business side, because procurement delay carries no blame and no inspection.