Procurement is the stage of the SaaS sales cycle that is most commonly underestimated, least frequently planned for, and most often responsible for deals slipping quarters. A verbal yes from the Economic Buyer is not a closed deal. Between that conversation and a signed contract lies a process — legal review, security assessment, vendor onboarding, budget approval workflow, contract redlines — that can take anywhere from two weeks to six months depending on the company's size, maturity, and internal complexity.
The reps and teams who navigate procurement well don't get surprised by it. They map it early, surface it explicitly in MEDDPICC qualification as the Paper Process element, and manage it with the same deliberate attention they give to champion development and EB engagement.
---
---
The P in MEDDPICC — Paper Process — is the specific element that covers everything required to go from verbal agreement to signed contract. It should be established no later than Stage 3, not at Stage 5 when you're trying to close.
Paper Process discovery questions:
- "When a decision like this gets made internally, what does the process look like from verbal agreement to signed contract? Who needs to be involved at each step?"
- "Does [Company] have a formal vendor approval process? Is there a procurement or vendor management team we'd be working with?"
- "What's the typical timeline from when a contract goes into legal review to when it comes back? Have you had experience with that process recently?"
- "Is there a security review or IT approval required for new software vendors? Who leads that?"
- "Are there standard contract terms your legal team requires, or do you typically work from vendor paper?"
- "What's the approval threshold — is there a deal value above which additional approvals are required?"
Map every answer into the deal record. Build a Paper Process timeline that shows every step from current state to signature — with owners, estimated durations, and dependencies.
---
Every person who touches the contract on the buyer's side is a procurement stakeholder. Map them before they appear unexpectedly:
| Stakeholder | Role in Process | Relationship Status | Owner |
| --- | --- | --- | --- |
| Champion | Internal sponsor, drives urgency | Engaged | AE |
| Economic Buyer | Final commercial approval | Engaged | AE + Manager |
| Procurement Lead | Vendor onboarding, commercial terms | Not yet engaged | AE via champion |
| Legal Counsel | Contract review and redlines | Not yet engaged | AE via champion |
| IT Security | Security questionnaire, technical review | Not yet engaged | SE via champion |
| Finance | Budget approval, PO issuance | Not yet engaged | AE via EB |
| Data Privacy/DPO | GDPR/data processing review | Not yet engaged | AE via champion |
Each stakeholder who hasn't been engaged is a risk. The procurement process cannot be fully mapped until every stakeholder is identified — and it cannot be confidently managed until every stakeholder has been introduced to the business case.
---
Don't wait for procurement to receive the contract and start asking questions. Ask the champion to introduce you to the procurement lead before the contract is issued: "Would you be able to introduce me to [procurement contact] so I can answer any questions they have upfront and make their process as smooth as possible?"
A procurement stakeholder who has been briefed on the business case and has a direct relationship with the vendor processes contracts faster than one who encounters the contract cold.
Play 2: Send a vendor information package proactivelyMost procurement processes require standard vendor information — company registration, insurance certificates, security certifications (SOC 2), financial information, and data processing agreements. Assemble this package before it's requested and offer it proactively: "I've put together a standard vendor package that covers the information procurement typically needs — registration, SOC 2 certificate, DPA, and insurance. Happy to send that over to whoever needs it to get the vendor setup started in parallel with legal review."
Getting vendor onboarding started before the contract is signed removes a step from the critical path.
Play 3: Provide security questionnaire supportSecurity reviews are among the most time-consuming procurement steps. Most enterprise SaaS vendors have a completed version of the most common security questionnaires (VSA, SIG, CAIQ). Offer it proactively: "If your IT security team sends over a questionnaire, our security team can typically turn it around in 48 hours — we've completed most standard formats before and can share our pre-completed responses as a starting point."
Play 4: Engage legal before redlinesAsk the champion to share your standard contract with legal before they review it, with a specific note from the champion: "Can you ask your legal team to flag any sections they anticipate wanting to discuss before they send formal redlines? That way I can connect them directly with our legal team to resolve standard positions quickly rather than going through multiple redline cycles."
Direct legal-to-legal dialogue on standard positions is significantly faster than champion-mediated redline exchanges.
Play 5: Build the Mutual Action Plan around procurement stepsThe MAP should include every procurement milestone as a named step with an owner and a date — not just the selling steps. Example:
| Step | Owner | Target Date |
| --- | --- | --- |
| EB approval of commercial terms | Champion + EB | Week 1 |
| Contract issued to legal | AE | Week 1 |
| Vendor onboarding form submitted | AE | Week 1 |
| Security questionnaire submitted | SE | Week 2 |
| Legal redlines returned | Prospect Legal | Week 3 |
| Redlines resolved | AE + Legal | Week 4 |
| PO issued | Finance | Week 5 |
| Contract signed | EB | Week 5 |
A MAP with procurement steps mapped to dates gives both the champion and the procurement team a shared timeline — and makes slippage visible and discussable rather than invisible and assumed.
---
Response: "Is there a way to move our contract to the front of the queue? The business case we've built with [EB] is time-sensitive — there's a compelling event around [date]. Would it help if [EB] spoke with the head of legal directly to prioritise?"
Escalating through the EB is faster than waiting in the queue.
"We need to go through an RFP process."Response: Participate — but manage it actively. Ask for the evaluation criteria before the RFP is published if possible. Ensure your champion is involved in scoring. Request a presentation slot rather than written responses only. And understand whether this is a genuine open evaluation or a process being run for compliance purposes after a decision has already been made.
"Our security team has concerns about data processing."Response: Engage directly. Don't let the champion mediate technical questions. Request a 30-minute call with the IT security team and your security/solutions engineer: "We deal with this regularly — it's usually faster to have our security team speak directly with yours. Can we set up 30 minutes?"
"The contract needs to go through our parent company's approval."Response: Map the parent company process as a second procurement layer — who, what, timeline. Don't assume the subsidiary's approval authority extends to the contract value of this deal.
---
Brazn tracks the Paper Process element of MEDDPICC as a named, scored dimension of deal qualification. Deals where the Paper Process is undefined or incomplete are flagged as close date risks — giving the rep and manager visibility into procurement exposure before it creates a surprise. In the forecast review, deals where the Paper Process is below the minimum completeness threshold are called out specifically — because they are the deals most likely to slip despite positive champion and EB signals.
---
####
Book a demo to see how Brazn AI fits into your sales stack.
About the Author
Alex Margarit, Sales AI Expert, SaaS Sales Leader, BMC, ServiceNow, Docusign — 25+ years in SaaS sales.