Paper Process Is a Stage, Not a Surprise
Deals don't slip in the last two weeks — they were built to slip months earlier. Map legal, security, and signature authority as early as decision criteria.
The Slack message went out on a Tuesday: "Verbal yes from the EB! 🎉 Signature by the 28th." The deal moved to Commit. The VP counted it. The AE started thinking about the next one.
On Thursday, a paralegal in the buyer's legal operations team replied-all to a scheduling thread with one question: "Has this vendor completed onboarding? I don't see them in the system."
They had not. Nobody on the account team knew the system existed. Over the following days the team discovered, in order: a vendor registration process with a three-week nominal SLA; a security questionnaire owned by a GRC analyst nobody had met; an MSA redline cycle that ran through outside counsel; and — the final discovery — that the executive who gave the verbal yes had signature authority up to $500K, and this was a $1.4M contract, which meant a committee that convened monthly and had just convened.
The deal signed eleven weeks later, in a new fiscal year, after the budget that funded it survived a re-approval fight it should never have had to survive. The post-mortem blamed "legal delays."
Legal was not late. Legal ran exactly on its published timelines. The seller discovered those timelines after the verbal yes instead of three months before it. The deal didn't slip in the last two weeks. It was built to slip in month two, when nobody asked the question.
The most neglected letter in MEDDPICC
MEDDPICC gives paper process its own letter — P — sitting right there between Decision Process and Identified Pain. And on scored deal reviews, it is reliably the lowest-evidence letter on the sheet. Sellers can recite the decision criteria from memory and produce a champion's verbatim quote about the pain, and when you ask about paper process the answer is some version of "standard stuff, legal and procurement, shouldn't be a problem."
That answer is a 0 wearing a 2's clothing. And under the rule that the lowest letter is the deal's real score, that deal is a 0 — no matter how beautiful the other seven letters look.
Here is why the neglect is so systematic. Everything else in the deal feels like selling — pain, value, champions, competition, the demo, the proof of value. Paper process feels like admin. It has no drama, no whiteboard moment, no win to celebrate. So sellers defer it, the way everyone defers admin, until it becomes the only thing left between them and the number. At which point it is no longer admin. It is the deal.
The correction is a reframe: paper process is a stage of the sale, not the paperwork after the sale. It has stakeholders you have not met, criteria you have not seen, and veto power you have not measured. A GRC analyst with a fourteen-week third-party risk queue is every bit as much a decision-maker as the economic buyer — she just decides when, not whether. And in a deal funded by this fiscal year's budget, when and whether are the same question.
Map it when you map the decision criteria
The timing rule is simple and non-negotiable: you map the paper process in the same stage you map the decision criteria — early-to-mid deal, while the evaluation is still being designed, months before anyone says yes.
This feels premature to most sellers. It isn't, for two reasons.
First, the information is not sensitive. Asking "how does a purchase like this actually get signed here — what are the steps between a yes and a signature?" costs nothing and threatens no one. Champions answer it readily, and when they can't answer it, that is a finding — a champion who has never bought anything this size before is a champion who needs a co-pilot in procurement, and you want to know that in month two, not week nineteen.
Second, the durations don't compress just because you discovered them late. A fourteen-week third-party risk review takes fourteen weeks whether you start it in April or October. The only variable under your control is the start date. Early mapping is what lets you run paper in parallel with the evaluation — security dossier submitted while the POV is still running, MSA in redlines while the executive readout is being scheduled — instead of in sequence after the win, where every step lands directly on the critical path.
The map itself needs exactly three properties, and vagueness in any of them means you don't have a map:
Named steps. Not "legal review" — the actual sequence: vendor registration, security/GRC questionnaire, third-party risk assessment, data-processing agreement, MSA redlines, order form, signature routing. Every large buyer's sequence is different, and the differences are where the weeks hide.
Named owners. A human being per step, with a name, not a department. "Legal" is not an owner. "Priya Sharma, senior counsel, commercial contracts" is an owner — someone your champion can walk down the hall to, someone whose queue can be asked about, someone who can be met before your contract lands in her inbox. A step without a named owner is a step whose duration you are guessing.
Real durations. Not hoped-for durations — published SLAs and historical actuals. Ask the disarming question: "When you bought your last comparable tool, how long did paper take, end to end?" The answer is almost always longer than anyone in the room expected, and it is the single most clarifying data point in the whole exercise.
And one question that deserves its own line because it kills more quarter-end forecasts than any other single omission: who has signature authority at this contract size, and what does their calendar look like? A verbal yes from someone $900K short of authority is not a yes. It is a warm introduction to a committee.
Put it in the MAP, backward from their date
A paper-process map that lives in the AE's notes is trivia. It becomes an operating instrument when every step goes into the Mutual Action Plan — Template 8 — as dated milestones with a customer owner, a vendor owner, and exit evidence, sitting in the same table as the POV milestones and the executive readout.
And the MAP's cardinal rule applies with full force: work backward from the customer's go-live, not your quarter end.
This is not a courtesy. It is the entire mechanics of urgency. A timeline built backward from your fiscal Q4 is your problem, and buyers can smell a vendor's quarter from three time zones away; every date on that plan is negotiable because none of them belong to the customer. A timeline built backward from their date — the regulator's deadline, the product launch, the fiscal window their budget dies at the edge of — makes every paper milestone a shared obligation. "Security review must start by June 3rd or your October go-live moves" is a sentence your champion will fight for internally. "We need signature by the 28th" is a sentence they will apologize for.
Run the arithmetic in the room, with the champion, on the shared document: go-live October 1. Deployment and onboarding, four weeks — signature by September 1. Signature routing and committee calendar, two weeks — legal complete by mid-August. Redlines, three weeks; risk review, six weeks in parallel; vendor registration gating everything, three weeks. Suddenly the math says paper must start in mid-June — while the proof of value is still running. Nobody in that room will ever again think of paper as the thing that happens after the win. The dates just taught them it's the thing that happens during it.
There is also a quiet diagnostic buried in this exercise: asking the customer to put names and dates against their own paper process is a champion test. A real champion goes and gets the names. A hopeful contact says "I'll have to check" and never does. Either way, you learn something in month two that most sellers pay to learn in week nineteen.
What leaders should inspect
If you run a team, the letter to pull first in any deal past mid-stage is P — and the standard is specific:
- Show me the paper steps, owners, and durations — written in the MAP, not recalled from memory. Recalled is assumed. Assumed is a 1.
- Who has signature authority at this amount, and when does the relevant committee meet? If the answer is "the EB signs it," ask how the team knows the threshold. Silence is your answer.
- What date did security review start, and how does it compare to the technical-win date? Parallel is health. Sequential is a slip that hasn't been announced yet.
- Whose go-live are we working backward from? If the honest answer is "our quarter end," the MAP is a wish list wearing a table format.
And one forecast rule that pays for itself in the first quarter you enforce it: no deal enters Commit with Paper Process below 2 — confirmed steps, named owners, dated milestones in a customer-confirmed MAP. Not because the rule is elegant, but because every "surprise" legal slip you have ever eaten was a P scored on hope.
Three moves for this week
- Audit P across your Commit column, today. For every committed deal, ask for the named paper steps, the owner of each, and the signature-authority threshold. Every blank you find is a slip you just caught early enough to matter.
- Add a standing paper-process block to your MAP template. Vendor registration, security/GRC, risk review, DPA, MSA, order form, signature routing — pre-printed, so the conversation with the customer starts from a checklist instead of a blank page.
- Ask one live champion the historical question: "How long did paper take on your last purchase this size?" Then rebuild that deal's timeline backward from the customer's go-live with the real number. If the signature date moves, it was always going to move — you just found out while you can still do something about it.
Deals do not die in legal. They die months earlier, in the silence where the question "how does paper actually work here?" was never asked. Ask it early, name the owners, date the steps, and anchor the whole thing to the customer's calendar — and the last two weeks of your quarter become the most boring part of the deal.
Which is exactly what they should be.
Go deeper. This essay draws on The Value Engine: How Elite Enterprise Sales Teams Turn Buyer Pain into Forecastable Revenue by Rudy M. Celekli — the complete operating system, demonstrated end-to-end on one $8.9M enterprise deal, including the parallel paper track that compressed a fourteen-week risk review into six. The companion Field Toolkit includes the Mutual Action Plan (Template 8) and the MEDDPICC scorecard, free to download. Get the book and the Toolkit at the link in the footer.
