The Procurement Navigation Playbook

Here is the deal you know intimately.

Champion bought in. Economic buyer gave verbal in week 14. Business case approved at the business unit level. You put it in forecast at 90%.

Then the MSA went to legal. Three weeks passed. Procurement sent a 40-point redline. Your legal team spent two weeks responding. Procurement came back with another pass. A security assessment got triggered because the deal crossed a data threshold nobody told you about. The security review alone takes four to eight weeks. Your Q3 close date is gone. Your Q4 close date is now in question. Your manager asks for an update every Monday and you have the same answer every time: "Waiting on procurement."

This is not bad luck. This is a predictable sequence that you could have compressed to three weeks if you had asked four specific questions in month one.

That is what this playbook is about.

Before we go further: if you have a live deal stuck in procurement right now and you want to know specifically where the blockage is and what move to make today, the diagnostic identifies the pattern and routes you to the right play in 90 seconds.

---

Most reps think procurement delays are about bureaucracy. They are wrong.

Procurement delays are almost always caused by one of three things:

Incomplete information at intake. Procurement cannot route your deal for the right reviews until they understand what your product touches. If your product accesses, processes, or stores sensitive data, it triggers a security review. If it involves a multi-year commitment over a certain dollar threshold, it requires CFO sign-off. If it integrates with a regulated system, it may require compliance review. The procurement team does not create these requirements at the last minute. They were always there. The problem is that nobody in the evaluation surfaced them until the contract arrived.

No internal owner driving the process. Your champion owns the business case. Procurement owns the contract process. These two people rarely speak to each other directly, and when they do, it is usually because something is broken. The deals that move fast through procurement have a single internal owner who is actively managing both sides of that gap.

Legal language designed for the seller. Most vendor MSAs are written to protect the vendor. Unlimited liability clauses, auto-renewal terms, aggressive IP language, data ownership provisions that favour the vendor, termination penalties. Enterprise procurement teams have seen every version of this. When they receive a contract that is heavily seller-favoured, they redline everything. Not because they are being difficult. Because their job is to protect their company, and your contract told them they needed to.

Every day a deal sits in procurement is a day it can die. A new budget freeze. A leadership change. A competing initiative that suddenly needs funding. Your champion loses energy. Your EB forgets why this was urgent.

The reps who close deals fast do not have better lawyers. They do not have more favourable contracts. They eliminate surprises before procurement ever sees the deal, and they create an internal owner who treats the procurement process like a project with a deadline.

---

These questions get asked in month one, during or immediately after discovery. Not in month four when you are negotiating terms.

Question 1: "What does your vendor approval process look like for a purchase at this size and scope?"

You are mapping the exact steps your deal will go through before a purchase order is issued. You want to know: what approvals are required, at what dollar thresholds does it escalate, who owns each stage, and what is the typical timeline from contract submission to PO.

The answer to this question tells you immediately whether you have a 30-day close or a 90-day close. It also tells you who else needs to be involved in the evaluation that you have not met yet.

Question 2: "Does your team conduct a security or vendor risk review for solutions that access [describe what your product touches]?"

You need to know whether a security assessment is in your future before it ambushes you in month five. If your product processes any form of sensitive or regulated data, the answer is almost certainly yes.

When the answer is yes, the follow-up is: "What documentation does your security team typically require to complete that review, and when in the process does it usually begin?" Then you proactively send that documentation in week two of the evaluation, not in week eighteen.

Most security reviews require some combination of: SOC 2 Type II report, penetration test results, data processing agreement, information security policy, and answers to a standard security questionnaire. If you do not have these documents ready to send on day one, get them ready. The review cannot start until the documentation is submitted. Every day of delay in submitting documentation is a day of delay in your close.

Question 3: "Who from your legal and procurement team typically gets involved in contracts at this stage, and when do you like to bring them in?"

You want to meet the procurement lead before the contract goes to them. Not to influence the process. To understand it. To find out what their standard redlines are, what their typical timeline looks like, and whether there is a preferred contract format or template that moves faster than your standard MSA.

Many enterprise procurement teams will tell you directly that they prefer to use their own paper rather than the vendor's MSA. If they will tell you that in month two, you can prepare for it. If you find out in month five when they reject your contract and send you their 80-page template, you are starting a negotiation from scratch on a timeline you cannot control.

Question 4: "Has your company purchased solutions from vendors of our size before, and are there any compliance or regulatory requirements that would apply to this type of purchase?"

This surfaces industry-specific requirements that neither your champion nor your champion's manager may be fully aware of. Regulated industries like financial services, healthcare, and government have procurement requirements that go well beyond standard security reviews. HIPAA, GDPR, FedRAMP, SOC 2, specific data residency requirements. The average IT vendor RFP process takes 6 to 10 weeks for most organisations, but in heavily regulated environments that number extends to 12 or more weeks, with additional time required for compliance reviews.

If your prospect is in a regulated industry and you do not surface these requirements in month one, you will discover them in month five. At that point, you have two choices: delay the deal or sign a contract that commits you to compliance standards you are not sure you meet. Neither is good.

---

Nobody talks about this one. Every top enterprise AE uses it.

Your champion owns the business case. They do not own the contract process. The person who can actually move a deal through procurement is the procurement lead themselves.

The Procurement Champion play is simple: you treat the procurement professional with the same attention and respect you give your business champion. You learn what they care about, what slows them down, and what they need from you to do their job well. And then you give them exactly that.

Most reps treat procurement as an obstacle. They send contracts at the last minute. They respond to redlines slowly. They escalate to their legal team and then wait. They treat the procurement professional as a gatekeeper to be managed rather than a person to be helped.

The reps who close fast do the opposite.

They email the procurement lead directly in week three of the evaluation: "I understand you will be involved in the contract process for this. I wanted to introduce myself early and understand what you typically need from vendors to make this process as smooth as possible. What format works best for your team? What documentation do you need upfront? Is there anything from our side that would make your review faster?"

That email does two things. It signals that you understand how enterprise procurement works, which makes you credible. And it gives you direct access to the person who will determine your close date.

The procurement lead will almost always tell you:

- Whether they prefer vendor paper or their own paper

- What their standard security questionnaire looks like (and let you pre-fill it)

- What their typical review timeline is and what extends it

- Whether there are any deal-specific requirements you should know about now

This conversation saves you four to six weeks on the back end of almost every enterprise deal.

---

Contract negotiation kills deals that were already won. Not because the terms are irreconcilable. Because the process is so slow and frustrating that one side eventually decides the deal is not worth it.

Here is the framework that compresses negotiation from weeks to days.

Step 1: Categorise the redlines before you respond.

When procurement sends a 40-point redline, do not forward it to your legal team and wait. Before legal touches it, you categorise every item:

Category A: Standard redlines you have seen before and already have approved language for. These are not negotiations. They are template swaps. Your legal team should be able to resolve Category A items in 24 hours.

Category B: Redlines that require business judgment, not legal judgment. Liability caps, payment terms, auto-renewal language, data ownership. These are decisions your management team needs to make, not negotiations that should sit in legal review.

Category C: Redlines that are genuinely complex and require legal analysis. These are usually rare. In a typical 40-point redline from a mid-market enterprise, fewer than five items will fall into Category C.

When you send your response, you address Category A and B items in full and flag Category C items explicitly: "The following items require additional discussion. Can we get on a 30-minute call with our respective legal teams to resolve these directly?" That call compresses weeks of back-and-forth into a single conversation.

Step 2: Never respond to a redline in writing without a call scheduled first.

Every written exchange adds at least one round of review to the process. A single 45-minute call between your legal team and their procurement or legal lead will resolve more issues than three rounds of written redlines.

Your champion can make this call happen: "I want to make sure we are not slowing down your legal team's process by going back and forth in writing. Can we set up a 45-minute call between our legal teams this week to resolve the outstanding items directly?"

Step 3: Create a single-source redline tracker.

Every open item, the proposed language from each side, and the owner of each item in a single shared document. Both sides can see the status of every item in real time. Nothing gets lost in email threads. Nothing requires a summary email to figure out where things stand.

The tracker also creates accountability. When every open item is visible to both parties, items do not sit unresolved for three weeks without someone asking why.

Step 4: Set a mutual close date at the start of negotiations.

"Based on our evaluation timeline, we are targeting a signed agreement by [date]. I want to make sure we structure this process to hit that date. Does that timeline work for your team?"

A procurement professional who has agreed to a target date will work to that date. A procurement professional who has no deadline will move at whatever speed is comfortable for their workload.

The target date becomes a shared project milestone, not a sales pressure tactic. Frame it that way and it will be treated that way.

---

If you have a deal stuck in procurement right now with a close date approaching, here is the sequence.

Day 1: Map the actual blockage.

The deal is not stuck in "procurement." It is stuck at a specific step. Security review pending documentation. Legal redline awaiting response. CFO approval threshold triggered. DPA negotiation open. Identify exactly which step is blocking, who owns it, and what specifically needs to happen to advance it.

If you do not know the answer to these questions, your first call is with your champion to get that map.

Day 2: Get your champion's manager involved.

Your champion should not be the only person applying internal pressure to procurement. Their manager has more political capital and more urgency around the close date. The framing for your champion: "I want to make sure we have the right people aligned internally to hit [close date]. Would it make sense to get [their VP] involved in a brief status call with procurement this week to make sure there are no blockers we can clear?"

Day 3: Send the executive brief.

A one-page summary, addressed to your champion's VP or the CFO if appropriate, showing: the business case summary, the outstanding procurement items and their status, the close date target, and the cost of a one-quarter delay. That last item is the urgency anchor. "If this closes in Q3 instead of Q2, the cost to the business is [quantified]. Here is the specific issue that requires attention to stay on track."

This brief gives your champion's executive a specific action to take. Not "please help move this along" but "these three items need decisions by [date] to close this quarter."

Day 5: Establish a weekly procurement status call.

With your champion and the procurement lead. Every week. Same time. Fifteen minutes. The agenda is: what is the status of each open item, who owns the next action, and what is the target date for resolution.

Most deals that die in procurement die because nobody is actively managing the process on a weekly cadence. Your champion is focused on the business outcome. Procurement is focused on risk mitigation. Nobody is focused on velocity. That is your job.

---

Look at every deal in your pipeline with a close date in the next 90 days.

For each one, ask: do I know exactly where it is in the procurement process, who owns each outstanding step, and what the specific next action is with a date attached?

If the answer is no for any of them, those deals are not at the close date you have them at. They are at the close date of whatever procurement decides to make time for.

The Discovery Architect includes the procurement discovery script you run in month one: the exact four questions above plus eight supporting questions that surface every requirement before it can ambush your deal. It also includes the redline categorisation framework as a working template, the executive procurement brief, and the mutual action plan structure that embeds procurement as a tracked milestone from week one.

Tactical Tier is $197. War Room at $497 includes a 1-on-1 audit of your specific stalled deal. Both have a 30-day guarantee.

---

In your next discovery call:

Ask the four procurement questions. Document the answers in your CRM, not in your head.

Identify the procurement lead by name and email before you leave discovery.

In week three of every evaluation:

Email the procurement lead directly. Introduce yourself. Ask what they need upfront.

Submit your security documentation proactively rather than waiting for the request.

When the contract goes to legal:

Categorise every redline before forwarding to your team.

Schedule a joint legal call within five business days.

Create a shared redline tracker.

Set a mutual close date with the procurement lead.

For stalled deals right now:

Map the exact blockage today.

Get your champion's manager involved by day two.

Send the executive brief by day three.

Establish a weekly status call.

Next week: account prioritisation. How to know which deals in your territory deserve your best hours and which ones are costing you the quarter.

Active readers only.

Dingo

P.S. The Boston rep from Tuesday's email. The $620K deal that died in Q3 and closed in Q4. Here is what actually changed. In Q3, she discovered the security review requirement in week 16 when the contract hit procurement. The review alone took six weeks. In Q4, she asked the security question in week two, submitted all documentation in week three, and the review was complete before the contract was even drafted. Same procurement team. Same requirements. Fourteen weeks compressed to three. The four questions are the entire difference. The full script is in the Discovery Architect.