"Procurement Handles It From Here" — Don't Let the Technical Win Become a Price Grind
The technical win is not the deal. Here is how to pre-agree the business case, build a concession ladder, and hold your number once procurement takes over.
You spent eleven weeks earning a yes. The technical evaluation went your way. Security signed off. The VP said, in a room with witnesses, "this is the one." You updated the forecast. And then you got the email.
"Great news — we're moving forward. Looping in Dana from procurement, she'll handle it from here."
That sentence is the sound of your margin leaving the building. Because Dana was not in any of the eleven weeks. Dana did not watch the demo. Dana does not care that your integration saves the ops team a manual reconciliation every Friday. Dana is measured on one thing, and it is the delta between the number on your quote and the number on the signed order form.
This is the moment where good reps discover they were running a great sales process and no negotiation process at all.
The handoff is a reset, not a step
Here is the mental mistake almost every rep I have watched makes. They treat procurement as the last stage of a deal that is already won. Paperwork. Formality. "We just need to get through legal and finance."
It is not the last stage of your deal. It is the first stage of a different deal, with a different counterparty, a different scoreboard, and no memory of anything you built. Every argument you won upstairs has to be re-won downstairs, except now you cannot use the arguments that worked upstairs, because value language does not move procurement. Dana is not going to reward you for reducing risk. She is going to ask what your floor is.
And the structural problem is worse than that. Your champion has already gotten what they wanted. They picked the vendor. They won the internal fight. From their point of view, the deal is done and the only remaining question is how much money the company spends, which is not their money. So they go quiet. Not out of malice — out of completion. Their job ended at selection. Yours has three more weeks to run and you are now doing it alone.
What procurement is actually paid to do
Spend a minute on the other side of the table, because it changes how you talk.
Procurement people are usually measured on savings against a benchmark. They have to show a number at the end of the quarter that says "I extracted this." That number is their performance review. It is not personal, it is not adversarial in the way it feels, and it is completely predictable. Which means it is also solvable, if you understand what you are solving for.
Dana does not need you to be cheap. Dana needs to be able to demonstrate that she moved you. Those are different problems. A rep who understands that will structure a deal where procurement gets a visible, documentable win that does not cost much. A rep who does not will get ground down on unit price, because unit price is the only lever anyone has put on the table.
The second thing to understand: procurement's strongest weapon is time. They will slow down. They will go silent for six days. They will come back on the twenty-eighth of the month with a number and an implied deadline. This is not disorganization. It is leverage, and it works because your quarter has an edge and theirs does not.
Almost all of the work happens before the handoff
Everything I am about to describe is easier to do in week six than in week twelve. If you are already in the grind, skip ahead — but come back, because the fix for your next deal lives here.
Get the business case in writing, in their words
While you are still the trusted advisor, before anyone says the word "procurement," you build a one-page business case with your champion. Not a deck you send. A document you write together, on a call, with them talking and you typing.
It contains what the problem costs them today, in their own numbers. What changes when it is fixed. Who signed off on that. Then you send it to them and ask a specific question:
"Can you reply to this and tell me anything I got wrong? I want to make sure it's your numbers, not my version of your numbers."
When they reply "looks right," you now own a written artifact, generated by the customer, that states the value of the deal in the customer's own language. That email is the single most useful thing you can carry into a procurement conversation. When Dana asks for a discount, you do not argue about price. You forward the business case and say, "here's what your team put together on the value side — I want to make sure whatever we land on still lets them hit this."
Procurement can push on your price. It is much harder for them to push on their own colleague's stated numbers.
Make the buyer say the ROI number out loud
Writing it down is good. Hearing them say it is better, because people defend positions they have voiced.
So somewhere in the evaluation, when the technical win is close but not sealed, you ask the question directly:
"If this works the way we've scoped it, what's it worth to the business in a year? Rough is fine — I'm not going to hold you to a decimal point."
Then you shut up. The silence is uncomfortable and you let it sit. Whatever number they say, you write it down and read it back. "Okay, so meaningfully more than what we're talking about spending. That's useful for me to know."
You have just done two things. You have anchored the conversation on value rather than cost, and you have given your champion a sentence they can repeat when procurement asks them whether they really need this vendor. Champions who have articulated the ROI themselves defend deals. Champions who only heard your version of the ROI forward your email to Dana and go back to their day.
Set terms expectations while you are still the hero
This is the step reps skip, and it is the cheapest one.
Before the handoff, while you are still the person who solved their problem, you say something like this:
"Before this goes to your finance team — a heads-up on how we work, so nothing surprises you. Our pricing is built on an annual term with standard payment terms. There is room to move on structure — term length, timing, how we phase the rollout — but the unit price is set by the size of the deployment, not by negotiation. I'd rather tell you that now than have your procurement team spend two weeks discovering it."
That paragraph does an enormous amount of work. It tells the champion what is negotiable and what is not, before anyone has an incentive to test you. It frames your discipline as helpfulness rather than stubbornness. And when Dana later says "we always get a discount from vendors," your champion is the one who says "they told me up front that the price is structural."
You want your terms position to arrive in procurement's inbox from inside the building, not from you. This is the same mechanic that runs underneath the SaaS pricing negotiation script for holding price after the technical win — the terms conversation is won in the evaluation, not in the negotiation.
You are already in the grind. Now what.
Fine. The email came, the handoff happened, and Dana has opened with a number that made you inhale sharply. Here is the sequence.
Slow it down before you respond to anything
The worst thing you can do is answer the discount request in the same conversation it was made. Every rep's instinct is to defend, and defense in a live call means concession, because you are outmatched — Dana does this all day and you do it a few times a quarter.
So do not negotiate on the first call. Use the first call to gather:
"Before we talk numbers, help me understand your process. What do you need to be able to show internally to sign this off? Are you comparing us against another quote, or against a budget figure? And what's the actual date this needs to be done by on your side?"
Those three questions tell you almost everything. If they are comparing against a competitor quote, you have a positioning problem. If they are comparing against an internal budget number, you have a scoping problem and possibly a phasing solution. If they cannot articulate a real deadline, their time pressure is manufactured and you can stop panicking.
Then: "Let me take this back and see what's possible with the structure. I'll come back to you Thursday." You are allowed to leave the room. Procurement does it to you constantly.
The concession ladder
Before you respond, write the ladder down. Not in your head — on paper, before the call, because under pressure you will improvise and improvisation is expensive.
The ladder is every concession you are willing to make, ordered from cheapest to most expensive, with the thing you want in return written next to each one. Cheap concessions first. You never open with the expensive rung.
At the cheap end sit things that cost you nothing and look like movement: implementation timing, onboarding sessions, a training block, access to a premium support tier for the first period, a slightly later start date so the first invoice lands in their next fiscal year. Procurement can write "secured additional onboarding at no cost" in their savings summary and it is a real line item to them.
In the middle sit structural trades: a longer term in exchange for a better rate, annual prepay instead of quarterly, a smaller starting scope with a contracted expansion, a phased rollout that lowers the year-one figure without touching the unit price.
At the expensive end sits actual unit price movement, and it should be the last rung, reached only with something substantial coming back the other way.
Most negotiations that go badly go badly because the rep started at rung four. They heard a discount request and immediately went to price, and once you have moved on price, nothing below it on the ladder has any value anymore. You have shown that price is negotiable, and the only remaining conversation is how negotiable.
Never discount without taking something back
This is the rule that carries the most weight and it is not about the money. It is about what a free concession teaches.
If you give a discount because they asked, you have taught them that asking works. There will be another ask. There will be an ask at renewal. There will be an ask from a different division next year, because Dana will tell them what she got.
So every movement comes with a counterweight, stated in the same breath:
"I can get to that number. What I'd need in exchange is a two-year term instead of one, and a signed order form by the end of the month. If the term stays at one year, the price stays where it is. Both of those are fine outcomes for me — which do you want?"
Notice the structure. You are not refusing. You are pricing. You are behaving like someone whose number reflects something real rather than someone who inflated a quote in anticipation of being beaten down. And you are giving them a choice between two acceptable outcomes rather than a yes/no, which keeps the conversation collaborative.
Things worth asking for: term length, prepayment, a reference call, a written case study, logo rights, an introduction to a sister business unit, a shorter notice period on renewal, a committed expansion date, or simply speed. Speed is a real concession and reps forget it is worth money.
Keep your champion in the room
The quiet champion is what actually kills these deals, more than the discount request itself.
Do not let the handoff be a handoff. When the email comes, you reply to both of them:
"Dana, great to meet you — I'll get you everything you need. Sarah, I'd like to keep you on the thread. There are a couple of scope decisions in here that affect what your team gets on day one, and I don't want those getting decided without you."
That is not a manipulation, it is true. Procurement negotiations routinely trade away things the end user actually needed — a module, a support tier, a number of seats — and the end user finds out in month two. Saying so out loud gives your champion a legitimate reason to stay engaged and gives you an ally who understands that a cheaper deal may be a worse deal for them.
Then keep feeding them. Every time procurement pushes, you go to your champion with a specific question: "They've asked us to drop the onboarding package to hit a number. Before I answer — how much does your team need that? I'd rather protect it and find the money elsewhere." You are making them a participant in the trade-off instead of a spectator to the price fight. This is the same dynamic behind the legal pricing negotiation script for holding your number when the firm has already chosen you: the partner who chose you is the only person who can tell procurement that the cheap version is not the version they picked.
The lines that actually hold
A few that I keep coming back to.
When they open with a flat discount demand: "I understand — that's your job and I'd expect you to ask. Here's mine: I need to be able to explain to my own finance team why this deal is different from the others. Tell me what you can give me on term or timing, and I'll see what I can do on the number."
When they claim a competitor is cheaper: "They might be. Are they cheaper for the same scope? Send me what you've got and I'll tell you honestly where we're more expensive and why. If the answer is that we're more expensive for the same thing, that's a real conversation."
When they say the budget is fixed: "Okay, then let's not fight about price — let's fight about scope. What can we take out of year one and add in year two so the year-one number fits your budget?" Phasing beats discounting almost every time, because it protects your unit economics and gives them a number they can approve.
When they go silent for a week: do not chase with "just checking in." Go back to your champion. "Haven't heard from Dana — is this still on track for the date you needed?" Let the internal deadline do the work.
And when you have genuinely reached your floor, say so once, plainly, and stop: "That's the number. I'd rather lose this cleanly than sign something I can't support you on for two years." Then be willing to mean it. The regulated-industry versions of this — the ones where the buyer has committees, audit trails and a mandate to document competitive tension — get more specific, which is why the financial services script for holding your number after a wealth management technical win exists as its own thing.
What I would do next
The reason most reps fold in procurement is not that they lack the words. It is that they have never said the words out loud before the moment they needed them, so the first attempt happens live, against a professional, with the quarter on the line. Reading a concession ladder is not the same as delivering one while someone is silent on the other end waiting for you to fill the gap.
So I would take the three or four lines above that match your current open deals, and I would run them until they are boring. That is exactly what we built DrillCall for — you practice the procurement call against a buyer who pushes back, goes quiet, and asks for the discount again after you have already answered, so the twelfth time you say "the price stays where it is" it comes out flat and calm instead of apologetic.
Win the room, then win the paperwork. They are two different jobs.