How do you coach a rep to handle a prospect who wants to bypass procurement entirely

The two paths a rep can take when a prospect says "skip procurement"

Every rep facing this moment is really choosing between two operating modes, and most of them pick badly because the wrong one *feels* faster in the first week.

Path A — Ride the bypass. The rep accepts the champion's framing: "I have budget authority, I've signed for tools like this before, procurement will just slow us down." The rep sends a short-form order form or clickwrap MSA, the champion signs, and the deal books. This path is not automatically wrong. Under a genuine spend threshold — commonly $10k–$25k annually at mid-market companies and sometimes $50k+ at large enterprises with delegated card programs — many organizations genuinely do not require a procurement cycle. Departmental SaaS purchases on a corporate card are a real and legitimate motion. If the champion is a VP with a signed delegation of authority, riding the bypass is fine and the rep should not manufacture friction.

Path B — Run the parallel track. The rep says yes to the champion's speed goal but no to the champion's method. Instead of avoiding procurement, the rep pre-loads it: pulls security questionnaires, W-9s, SOC 2 reports, insurance certificates, and standard redlines into a single packet, and asks the champion to open a ticket *now* while the technical evaluation is still running. The deal closes in the same quarter, but the paperwork risk is retired in parallel rather than discovered at the end.

The trade-off is not "fast versus slow." It is discovered risk versus deferred risk. Path A moves the discovery of procurement requirements to the worst possible moment — after verbal commitment, often after a start date has been communicated internally, and frequently inside the last two weeks of a quarter when nobody has slack. Path B moves that discovery to week two, when it costs a Slack message instead of a slipped forecast.

There is a third framing worth naming because reps stumble into it accidentally: the covert bypass, where the champion asks the rep to keep the deal off procurement's radar deliberately — split invoices under a threshold, misclassify the line item, or route through an existing vendor's contract. That is not a sales tactic to be coached; it is a request to help a person violate their own employer's controls. The correct rep behavior is to decline warmly, keep the champion, and escalate the deal path. A rep who agrees has traded a renewal and a reference for one signature.

How to decide which path fits the deal in front of you

The decision is mechanical once the rep collects four facts. Coaching should focus on *getting those four facts in one call*, not on debating philosophy.

Fact 1 — Annual contract value versus the stated threshold. Ask directly: "What's the dollar amount above which your finance team requires a purchase order?" Most champions know it. If they don't, that itself is the answer — a champion who cannot name the threshold has probably never bought at this size.

Fact 2 — Signature authority in writing. "Are you the signer, or does someone above you sign?" A champion who says "I can get it signed" is not a signer. Reps should be taught to hear the difference.

Fact 3 — Data and access footprint. If the product touches customer PII, payment data, source code, or production systems, security review is effectively mandatory regardless of dollar value. Many companies enforce security review at $0 when data leaves the building. A $9,000 deal that ingests CRM records will still hit InfoSec.

Fact 4 — Existing paper. Ask whether the company already has an MSA, a reseller agreement, or a marketplace relationship (AWS, Azure, GCP, or a procurement platform) that the purchase could ride on. This is the single highest-leverage question in the conversation, because riding existing paper genuinely does skip most of the cycle — legitimately.

The mermaid above is the coaching artifact itself. Managers should have reps walk the tree out loud on a call review rather than memorize a script. When a rep can name which branch they are on and why, the objection stops being scary.

One more decision input that does not fit cleanly in a tree: how the champion talks about procurement. "Procurement takes forever here" is a process complaint and is workable. "I don't want procurement involved because they'll make us look at three vendors" is a competitive signal — the champion is trying to protect a sole-source outcome, which means the rep is winning but on fragile ground. "My finance guy is difficult" from a champion who cannot name that person is often a fabricated blocker hiding a much earlier deal stage than the rep believes.

Concrete numbers behind each path

Reps respond to arithmetic better than to principle, so coaching should quantify both routes with ranges the rep can sanity-check against their own pipeline.

Cycle-time math. In practice, a departmental purchase under threshold with no security review closes in roughly the time it takes to get a calendar slot with the signer — often 3 to 10 business days from verbal. A full procurement cycle at a mid-market company typically runs 3 to 6 weeks; at a large enterprise with legal redlines and a security questionnaire, 6 to 14 weeks is a realistic band, and regulated industries (financial services, healthcare, government) routinely exceed that. The critical number is not the length of the cycle — it is when the clock starts. A rep who opens procurement in week 2 of an 8-week evaluation adds zero days to the deal. A rep who opens it in week 8 adds the entire cycle.

Rework cost of a failed bypass. When a bypass fails after signature — the invoice hits AP, AP rejects it for no PO, and the deal reverses into a procurement cycle — the rep loses the original cycle time *plus* the full procurement cycle *plus* credibility. Worse, the reversed deal frequently triggers a competitive bake-off that never would have happened if procurement had been engaged voluntarily, because a procurement team that discovers a vendor already selected without them has an institutional incentive to prove it can find alternatives or extract concessions.

Discount exposure. Procurement teams are measured on savings, and a team engaged late has less to work with than a team engaged early — but engaged *last*, at the point of signature with a start date already committed internally, they have maximum leverage. Reps should understand this inversion: the later procurement enters, the more discount they can extract, because the buyer's own urgency becomes the lever. Typical asks land in the 5–15% range for a first-year deal, and can go materially higher when the vendor has visibly conceded on timeline.

Multi-threading math. Single-threaded deals — one champion, no other contacts — carry substantially higher slip and loss rates than deals with three or more engaged stakeholders. The bypass request is almost always a single-threading symptom. Coach the rep to treat "let's keep this between us" as equivalent to "this deal has one point of failure," and to price it in the forecast accordingly: single-threaded deals should not sit in Commit.

The packet cost. Building the reusable procurement packet is a one-time RevOps investment, typically 8–20 hours of cross-functional work (Legal, Security, Finance, Sales Enablement). It contains: current SOC 2 Type II or equivalent, a completed standard security questionnaire (CAIQ or SIG Lite), W-9, certificate of insurance, DPA template, sub-processor list, standard MSA plus a pre-approved fallback redline set, and a one-page "how to buy us" document written for the buyer's procurement analyst. Once built, it turns a two-week questionnaire scramble into a single email. This is the highest-ROI artifact RevOps can hand a sales team facing bypass requests, and it directly removes the champion's stated reason for wanting to skip the process.

Threshold reality check. Reps should be taught that stated thresholds and enforced thresholds differ. Many companies have a written $5,000 PO threshold that is enforced inconsistently below $25,000, and a hard stop at any amount involving a multi-year commitment or auto-renewal. Multi-year and auto-renew clauses trip procurement review at almost every company regardless of annual value, because the total contract value — not the annual value — is what governs. A rep quoting a three-year deal at $8,000/year is quoting a $24,000 commitment and should expect review.

The language that actually works on the call

Coaching this objection fails when it becomes a script. It works when the rep internalizes four moves and improvises the words.

Move 1 — Agree with the goal, not the method. "Totally with you on speed — my job is to get this live for your team, not to make you fill out forms." This is not a concession; it removes the adversarial framing before the rep says anything the champion might hear as resistance.

Move 2 — Make procurement the rep's problem, not the champion's. The champion's real objection is almost never "procurement exists." It is "procurement means *I* have to do work I don't have time for." The rep should explicitly take that work: "Here's what I'll do — I'll send you a single email you can forward. It has everything they'll ask for. Your only job is to hit forward and tell them it's a priority." This single reframe resolves a large share of bypass requests outright.

Move 3 — Use a third-party story instead of a warning. Never say "if you skip procurement your deal will die." Say instead: "A team at a similar company did it that way last year and the invoice got kicked back by AP in month two — they ended up doing the full cycle anyway, but with a live system they had to pause. I'd rather not put you in that spot." The rep is protecting the champion, not lecturing them. If the rep does not have a real story, they must not invent one — a general statement about how AP rejections work is honest and nearly as effective.

Move 4 — Ask the question that surfaces the real blocker. "If we did it your way and it worked, great. What happens if AP kicks it back — who do you have to go to?" The answer names the stakeholder the rep needs. Champions will often volunteer the CFO, controller, or procurement lead's name here without realizing they have just handed over the second thread.

There is also a set of things reps should stop saying. "Can you introduce me to procurement?" puts the burden on the champion and reads as the rep trying to go around them. Better: "Would it help if I handled the vendor onboarding paperwork directly with whoever owns it, so it doesn't eat your week?" Similarly, reps should avoid "our legal team requires..." framing, which sounds like the vendor is the obstacle. The framing should always be: *your* process, *my* work, *our* timeline.

Finally, coach the rep on what to do when the champion refuses anyway. The answer is not to fight. Proceed on the champion's path *and* quietly build a second thread — an executive sponsor, a technical stakeholder, an existing customer contact who moved to this company. The rep never tells the champion they doubted them. They simply ensure the deal does not have exactly one heartbeat.

Implementation and sequencing for the manager

Turning this into repeatable rep behavior is a RevOps and enablement job, not a pep talk. The sequence below is how the capability actually gets built.

Week 1 — Instrument the signal. Add a required CRM field capturing procurement status on every opportunity above the team's median deal size: Not required (under threshold), Existing paper, Engaged, Not yet engaged, Champion requested bypass. That last value is the one that matters — it turns an invisible conversation into a reportable event. Without it, managers only learn about bypass requests during post-mortems on slipped deals.

Week 2 — Build the packet. Assemble the artifacts listed earlier into a single shareable link with a stable URL, owned by RevOps and reviewed quarterly. Stale SOC 2 reports and expired insurance certificates are a common and embarrassing failure mode.

Week 3 — Gate the forecast. Establish the rule that no deal above threshold enters Commit while procurement status reads Not yet engaged or Champion requested bypass. This is the enforcement mechanism. Coaching alone does not change rep behavior; forecast category rules do, because they change what the rep gets asked about in every pipeline review.

Week 4 — Run call reviews on the specific moment. Pull three recordings where a prospect raised the bypass and review them as a team. Score against four criteria: did the rep ask the threshold question, did the rep take the work rather than assign it, did the rep get a second name, did the rep log the outcome. Repeat monthly.

Ongoing measurement. The metric that proves this works is not "bypass requests avoided." It is median days from verbal to signature, segmented by the week procurement was engaged. If deals where procurement entered in weeks 1–3 close materially faster than deals where it entered in weeks 7+, the rep has a number to quote on the next call — and that number is far more persuasive than any coaching language. RevOps should publish that segmentation monthly.

Territory and segment nuance. Enterprise reps need the parallel-track motion as a default. SMB reps working sub-$15k deals with 2-week cycles will destroy their velocity if they force procurement into every deal, and coaching them identically is a mistake. The coaching should be calibrated to segment: mid-market and enterprise get the full sequence; SMB gets the threshold question and the data-footprint question only, then moves on.

What to do about the champion who was right. Sometimes procurement genuinely is not required, the bypass works, and the deal closes clean. Managers must not punish this outcome or the field will stop reporting bypass requests honestly. The CRM field should record the outcome, and deals where Not required (under threshold) proved accurate should be used to refine the team's threshold guidance for that account segment. The goal is calibration, not compliance theater.

Related questions

Should a rep ever agree to split an invoice to stay under a threshold?

No. Splitting invoices to evade a control is expense fraud from the buyer's side and makes the vendor complicit. Decline warmly, keep the relationship, and offer a shorter initial term or smaller scope as a legitimate way to land under the threshold.

What if procurement is genuinely the reason past deals died at this account?

Treat it as intelligence, not a reason to avoid them. Ask what specifically failed — security questionnaire, redlines, or a competitive requirement — and pre-solve that exact item before the ticket opens.

How do you know if a champion actually has signature authority?

Ask who signed their last comparable purchase and what the dollar amount was. Champions with real authority answer instantly and specifically. Vague answers mean the authority is aspirational.

Does riding an existing MSA really skip the cycle?

Often yes. An amendment or order form against an executed master agreement typically skips legal redlines entirely and may skip security review if the scope is unchanged. Always confirm the scope match with the buyer's contract owner.

What should the rep log in CRM after a bypass conversation?

The stated threshold, the named signer, the data footprint, whether existing paper exists, and the second stakeholder's name. Five fields, one minute, and the deal stops being single-threaded on paper.

FAQ

Is a prospect asking to bypass procurement a buying signal or a warning sign?

Both, and reps should hold the tension. It signals genuine urgency and champion enthusiasm — nobody tries to skip paperwork for a product they don't want. It also signals that the deal is single-threaded and that the champion may not fully understand their own company's controls. Treat the enthusiasm as real and the process claim as unverified.

How do you handle a prospect who insists procurement will kill the deal on price?

Separate the concern into two parts. If they mean procurement will negotiate, that is normal and the vendor should have a prepared concession ladder. If they mean procurement will reject the vendor entirely, that is a qualification or requirements problem the rep needs to surface now, not at signature. Ask which one they mean.

What is the fastest legitimate way to shorten a procurement cycle?

Engage early and pre-load. Opening the ticket in week two of the evaluation costs nothing and runs the clock in parallel. Sending the complete packet unprompted removes the most common two-week delay, which is waiting on a security questionnaire response.

Should the rep contact procurement directly without the champion's permission?

No. Going around the champion damages the relationship that carries the deal. Offer to take the paperwork burden directly with the champion's blessing — "would it help if I worked with them so it doesn't eat your week" — and let the champion make the introduction.

How should RevOps report on bypass attempts?

With a single picklist value on the opportunity record and a monthly report on cycle time segmented by the week procurement was engaged. That segmentation converts a coaching argument into a data point the rep can quote on a live call, which is what actually changes behavior.

Does this coaching change for renewals and expansions?

Yes. Expansions on an executed agreement often genuinely bypass the full cycle via an order form, and forcing a new process is a self-inflicted wound. But a material scope change, a new data type, or a multi-year renewal usually re-triggers review — so the rep should still ask the data-footprint and total-contract-value questions.

Sources

• https://hbr.org/2015/03/making-the-consensus-sale
• https://www.gartner.com/en/sales/topics/b2b-buying-journey
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/the-new-b2b-growth-equation
• https://www.nist.gov/cyberframework
• https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2
• https://cloudsecurityalliance.org/research/cloud-controls-matrix
• https://sfmagazine.com/articles/2019/june/segregation-of-duties-and-internal-controls/
• https://www.cips.org/knowledge/procurement-topics-and-skills/
• https://www.ismworld.org/supply-management-news-and-reports/

Related on PULSE

• How do you multi-thread a deal that only has one champion?
• What should a security questionnaire response packet include?
• How do you set forecast category rules that reps actually follow?
• When should a rep escalate to an executive sponsor?
• How do you shorten enterprise sales cycles without discounting?
• What CRM fields actually predict deal slip?