The habit I used to have
Early in my career, I walked into every negotiation with one number in my head. The lowest price I could get. I’d spend the whole conversation steering toward that number, and I counted it a win if I got there.
It took years of running procurement for large capital programs to see what that habit was costing me. Price is the easiest thing to measure, so it’s the thing everyone leans on. But it’s rarely the thing that determines whether a deal actually works out.
Why price-first thinking falls apart
Here’s the problem with chasing the lowest number first. A vendor who cuts price to win a contract has to make that margin back somewhere. Sometimes it’s slower delivery. Sometimes it’s a thinner bench of people assigned to your account. Sometimes it’s a supplier who quietly deprioritizes you the moment a bigger client calls.
You don’t see any of that in the negotiation. You see it six months later, when a delivery slips or a change order shows up that nobody flagged at signing.
I’ve sat across from vendors who could hit whatever number I wanted, and I learned to be suspicious of that. If someone agrees to your price too fast, ask what they’re planning to hold back to make it work.
What I negotiate on instead
I still care about price. It’s on the list. It’s just not first anymore. The order I actually use, in rough priority:
Process. Can this vendor tell me exactly how they’ll deliver, step by step, and does that process hold up under a schedule change? A supplier with a vague process is a supplier who will surprise you later.
People. Who is actually doing the work, not who is in the sales meeting. I ask for names. I ask how long those people have been with the company. Turnover mid-contract is one of the most common things that quietly wrecks a project timeline.
Product. Does what they’re offering actually match the specification, or does it match a version of the specification that’s easier for them to deliver.
Place. Where is this coming from, and what does that mean for lead time and risk if something disrupts the supply chain.
Price comes last, not because it doesn’t matter, but because it only means something once I know what I’m paying for.
A choice I’d make differently now
If I’m choosing between two vendors, one with a lower price and a weaker process, and one with a higher price and a process I can actually verify, I take the second one almost every time. Not automatically. I still run the numbers. But a gap in process is a gap that shows up later as cost anyway, usually as a change order or a delay, and by then you’ve lost your leverage to negotiate it away.
The exception is when the scope is simple and the risk of variation is low. If I’m buying something standard, with a clear spec and a short delivery window, price can move back up the list. The more complex and long-running the contract, the more that order matters.
What this looks like in practice
When I sit down with a vendor now, I ask about their process before I ask about their price. I want to hear how they’d handle a schedule slip before I hear what number they’ll land on. If their answer to a hard question is smooth and rehearsed, I ask a harder one.
I also negotiate slower than I used to. Early on, I wanted to close fast because closing fast felt like progress. Now I’d rather take an extra week and get the process questions answered than save that week and pay for it later in a dispute.
None of this means price doesn’t get negotiated hard. It does. But it gets negotiated last, once I know the deal is actually built on something solid. A low number attached to a weak process isn’t a good deal. It’s a deferred cost with a due date I don’t control.
The short version
If you’re new to procurement, or just new to negotiating anything with real stakes, resist the pull toward the number first. Ask about process. Ask about the people who’ll actually do the work. Ask where things are coming from. Get to price once you know what you’re buying, not before.