Beat Procurement and Legal Delays in Deals
Procurement and legal review quietly push enterprise deals past quarter-end. Use these tactical plays to compress cycles and protect your forecast.
Why procurement and legal delays kill more deals than pricing objections
By the time your champion forwards you to procurement, you've already won the technical sale. Yet a striking share of enterprise deals slip at least one quarter after verbal commitment, and procurement and legal review is consistently among the biggest causes — often outranking budget reallocation and competitive re-evaluation.
The root cause isn't malice or incompetence on the buyer side. Enterprise procurement teams are managing far more SaaS contracts than they were a few years ago, while legal headcount has barely grown. Your deal is queued behind dozens of others, and every redline cycle adds days — sometimes weeks.
The AEs who consistently hit quota in this environment aren't faster talkers — they're better operators. They treat procurement and legal as a separate sales motion with its own stakeholders, timeline, and close plan. Here's how to do it.
Engineer the procurement runway before you need it
The biggest mistake AEs make is waiting until the MSA is requested to start the procurement conversation. By then, you've lost your leverage and your timeline.
Pre-qualify procurement early. On your second or third call with the champion, ask three questions verbatim:
- "Walk me through the last SaaS contract under $250K you signed — how long did it take from verbal commitment to signature?"
- "Who specifically owns vendor onboarding, and are they at capacity right now?"
- "Do you have a preferred MSA template, or will we be working from ours?"
A buyer who answers "I don't actually know" is telling you the deal will take far longer than they think — assume months, not weeks. Build that into your forecast immediately.
Get your paper in front of legal before pricing is final. This sounds counterintuitive, but high-performing enterprise AEs routinely send draft MSAs to buyer-side legal during the technical evaluation phase, framed as: "So we don't lose time at the end, would your legal team be open to reviewing our standard terms in parallel?" This can compress the back-half timeline by weeks.
Map the signatories. For a $150K deal, expect 4-7 people in the approval chain: procurement analyst, procurement manager, legal counsel, InfoSec reviewer, finance approver, business owner, and signatory. Get names. Without names, you have no escalation path when things stall.
Tactical plays for breaking specific stalls
Once you're in the procurement gauntlet, generic follow-ups ("just checking in!") accelerate nothing. Here are the four most common stalls and how to break each one.
Stall 1: "It's with legal." (No motion for 10+ days.) Send your champion a one-paragraph email they can forward verbatim to legal, including: a specific question about a specific clause, your willingness to accept their paper for clauses X and Y, and a proposed 30-minute redline call. Calls compress what email cannot — a single working session typically resolves what 3 weeks of redline exchanges cannot.
Stall 2: InfoSec review. This is now one of the longest single bottlenecks in enterprise deals — vendor security assessments routinely add weeks to the cycle, and the wait stretches further whenever the reviewer comes back with clarifying questions. Combat it by pre-loading your SOC 2 Type II, ISO 27001, recent pen test summary, SIG Lite, and CAIQ into a shared folder before the request comes. If you have a Trust Center (Vanta, Drata, etc.), send the link with your proposal, not after.
Stall 3: "Procurement says we need three competitive bids." This is rarely a real requirement — it's a category-tier policy that often has exemptions. Ask your champion to push procurement on whether this is a sole-source exemption category (security tooling, compliance, anything with switching cost evidence). Provide a one-page sole-source justification draft. These requests succeed surprisingly often when the champion advocates for the exemption.
Stall 4: Year-end procurement freeze. Most enterprises freeze new vendor onboarding in the last 2 weeks of their fiscal year. If your deal hits that window, you're not closing — you're closing 6 weeks later. Either accelerate hard to clear the freeze, or stop discounting against a fake urgency and re-plan for the new quarter.
The mutual close plan that actually works
Most "mutual close plans" are glorified Gantt charts that nobody opens. The version that works in 2026 has four specific characteristics:
- It names individuals, not roles. "Sarah Chen, Procurement Manager — reviewing by 6/12" beats "Procurement — review."
- It includes buyer-side dependencies first. Putting your own action items at the top signals you don't understand the bottleneck.
- It has explicit decision gates. "If MSA redlines exceed 5 substantive changes, we schedule a joint working session" forces a path rather than infinite email loops.
- It's reviewed weekly on a 15-minute standing call. Not "as needed." Standing calls survive holidays, sick days, and reorgs.
Here's the genuine insight most AEs miss: the close plan isn't a project management tool, it's a commitment device. When your champion verbally agrees to a date in front of their procurement counterpart, the social cost of slipping increases dramatically. The plan exists to create that moment, not to track tasks.
The reliable way to compress procurement cycles is unglamorous: (a) build the close plan during the demo cycle, not after, and (b) hold a recurring 15-minute Friday call with the champion and procurement lead until signature. Teams that adopt just those two habits routinely shave weeks off their procurement phase. No new tools. No new discounts. Just operational discipline.
The takeaway
- Qualify procurement risk during discovery, not after verbal. Ask your champion the three diagnostic questions on your next second call this week — they will tell you whether to forecast the deal for this quarter or next.
- Pre-load InfoSec and legal artifacts before they're requested. Build a single shared folder template with SOC 2, ISO 27001, MSA, DPA, and pen test summary that goes out with every proposal. This alone can cut 2-4 weeks off your average cycle.
- Replace status-check emails with a standing 15-minute weekly call between you, your champion, and procurement. It feels excessive until you watch your forecast accuracy climb sharply over a couple of quarters.
Put this into practice
Use our free AI tools to apply these tactics immediately.
Explore free sales tools ↗Keep reading
Build a Mutual Action Plan Buyers Actually Use
A mutual action plan only works if the buyer co-owns it. Here's how to build a MAP that survives past the demo and forces real commitment.
When to split a deal into multiple CRM opps
Splitting a deal into multiple opportunities keeps your pipeline honest. Here's the test to apply, five scenarios that warrant it, and when to resist.
Why Deals Stall Between Stages 2 and 3
Deals stalling between stage 2 and 3 usually fail on problem, sponsor, or timing. Here's how to diagnose which one is breaking your pipeline.