"We're Consolidating Vendors This Year" — How to Not Be on the Cut List

"We're consolidating vendors this year."

I have heard that sentence in every flat-budget year I have ever sold through, at Dell, at AWS, and in the businesses I have built and sold. It arrives politely. It sounds like a decision that has already been made somewhere above the person saying it, which is exactly why reps accept it and move on. It is the softest no in enterprise software and it closes more pipeline than any competitor does.

Here is the thing most reps miss. The same eleven words mean two completely different things depending on whether you are trying to open an account or keep one. If you answer a new-logo consolidation objection with a renewal save motion, or the other way round, you will lose. So the first job is diagnosis, not rebuttal.

Same words, two different problems

When a prospect who has never bought from you says "we're consolidating," they almost never mean they are ripping tools out. They mean we are not adding logos this year. Procurement has put a freeze on net-new suppliers, or the CFO has told every department head that headcount and tooling spend are flat, or somebody got burned by a sprawl audit and now every new vendor requires a security review, a legal review, and a signature two levels above the buyer. It is a process objection wearing the costume of a strategy objection.

When an existing customer says it, they mean something much more dangerous. Somebody has a spreadsheet. Every tool in the stack is a row. There is a column for annual cost and a column, usually badly filled in, for what the tool does. Someone is going to rank those rows and draw a line, and everything under the line gets non-renewed. Your logo is on that spreadsheet whether you like it or not, and the person who decides where you land is probably not on your call.

Those are different fights. Let me take them in order.

New deals: you are not asking for money, you are moving it

The instinct when you hear "no new vendors" is to argue about value. Reps start listing outcomes. They talk about ROI. They send a case study. None of that touches the actual blocker, because the blocker is not "we don't believe you're worth it," it is "there is no mechanism for me to add a line item right now."

So stop trying to add a line item. Find the one you replace.

This is the reframe that unlocks flat-budget years: new spend requires approval, displaced spend requires a decision. Those go to different people and move at different speeds. A department head who cannot get sign-off on twenty thousand dollars of new tooling can very often reallocate twenty thousand dollars they are already spending, because that money is already in the budget and already approved. You are not asking the CFO for anything. You are asking your buyer to change what they point existing money at.

That means your discovery has to change shape. You are no longer only asking what problem they have. You are asking what they are currently paying to solve it badly.

The questions that actually move this

When I hear consolidation on a first or second call, I stop selling and start mapping. Something close to this:

"That makes sense, and honestly a lot of the teams I talk to are doing the same thing. Can I ask how the consolidation is actually being run? Is there a list, and who owns it?"

That question does more work than anything else in this post. There is almost always a person and almost always an artifact. Sometimes it is a director in RevOps. Sometimes it is a procurement analyst nobody in the sales conversation has ever met. Sometimes it is the CFO's chief of staff with a spreadsheet nobody else has seen. You need the name.

Then:

"When you look at what you're spending today on [this problem area], what's on that list? I'm not going to pitch against any of it, I just want to know whether what we do overlaps with something you already own or sits next to it."

And the one that matters most:

"If this were funded by killing something else rather than by new budget, would that change who has to approve it?"

Ask that out loud. The answer tells you whether you are dealing with a freeze on money or a freeze on suppliers, and those have different escape routes. If it is a money freeze, displacement works. If it is a supplier-count freeze — genuinely, someone has said "we will have fewer contracts at the end of this year than we started with" — then displacement is the only thing that works, and you had better be able to name the contract that goes away.

Being specific about what you replace

Vague displacement is worthless. "We can probably replace two or three point solutions" is a sentence buyers have heard from every vendor and believe from none. You need to be able to say: this contract, this renewal date, this amount, and here is the piece of it we do not cover so you know I am not overselling.

That last part is what makes it credible. When I have run this well, the honest limitation is what sold it. "We replace the coaching and call review piece entirely. We do not do the dialer. So if you go this route you keep the dialer contract and drop the other one." Buyers relax when you draw the boundary yourself, because the alternative — discovering the gap in month three — is the thing they are actually afraid of.

If you cannot name the line item you displace, you are a net-new logo in a year when net-new logos do not get bought, and the honest move is to qualify the deal to a later quarter rather than burn six weeks of forecast on it.

Renewals: your champion has one sentence, and you are not there when they say it

Now the harder one.

When consolidation hits a renewal, the deal is not decided in your QBR. It is decided in a twenty-minute internal meeting you are not invited to, where somebody goes down the list and your champion has to say why you stay. They get one sentence. Maybe two. If that sentence is "the team likes it" or "we've used them for a while," you are gone, and you will find out in an email three weeks later that starts with "unfortunately."

So the entire renewal motion in a consolidation year is one job: give your champion a defensible sentence and the evidence behind it, before the meeting happens.

Not after. Not when they tell you the review is scheduled. Before. By the time your champion tells you there is a consolidation review, the spreadsheet already exists and your row already has a number in it. You are now arguing against an anchor.

Find out who owns the list

Same question as the new-deal side, different urgency. "Who's running the consolidation exercise?" is a completely reasonable thing to ask a customer you have a relationship with, and most champions will tell you. Ask it in a QBR when there is no threat in the air, because the answer is more honest then.

What you are looking for is whether the decision-maker is someone who has ever used your product. Usually they are not. Usually they are finance or ops, and they are ranking by cost per something — cost per seat, cost per user, cost per outcome if you are lucky enough to be in a category where outcome is measurable. That person does not care about your feature set. They care whether the number in the cost column is justified by something in the value column, and if the value column is empty for your row, the empty cell decides it.

So your job is to fill that cell in your champion's handwriting, not yours.

Get your usage data into their hands early

This is unglamorous and it is most of the work. Pull the actual usage. Who logs in, how often, which teams, which workflows. Pull whatever outcome data exists — tickets closed, calls reviewed, deals sourced, incidents caught, whatever your product actually produces. Then hand your champion a one-page version they can paste into a slide without editing it.

Two rules for that page. First, it has to be honest, including the parts that are bad. If a team stopped using you in Q2, say so and say why, because your champion will get asked and being blindsided in that meeting is how champions decide to stop defending you. Second, it has to be in their language, not yours. Nobody in a consolidation review says "strong platform adoption." They say "the support team runs their entire escalation path through it and we'd have to rebuild that in Jira."

The switching-cost sentence is often the strongest one you have, and it is not a dirty trick. It is true. Real work has been built on top of you. Make that work visible.

When the account is already wobbling and you can feel the renewal slipping, the conversation gets more structured, and I would run something close to the save call script for a renewal you are six weeks from losing rather than improvising it. If you are selling into security and the consolidation pressure is coming from a SOC that has already shifted work to a platform vendor, the cybersecurity version of that save call handles the "our SIEM does that now" branch specifically, which is a different objection than pure cost.

The seat problem

Here is where a lot of renewals die quietly. Consolidation reviews love unused seats. An unused seat is the easiest thing in the world to point at, it requires no product knowledge to criticise, and it makes the cost-per-active-user number look terrible.

If you know that report is coming, get ahead of it. Reclaim the dead seats yourself and propose the reduction before they find it. Yes, that shrinks the contract. It also converts you from "expensive and half-used" to "right-sized and fully used," and the second one survives the meeting. I would rather renew smaller and stay in the account than defend a seat count I know is indefensible. The upsell conversation that survives a seat utilization report works on exactly this logic — you cannot grow an account whose utilization story is embarrassing, so fix the story first, then grow.

Multi-year terms: when it is the trade and when it is the trap

Somebody on your team will suggest a multi-year deal as the consolidation answer. Sometimes they are right.

A multi-year term is the right trade when the consolidation pressure is genuinely a this-year budget event and your champion is secure. You are giving up some annual price increase in exchange for taking your row off the spreadsheet for the next two review cycles. That is a real, good trade, and finance often likes it because it gives them a predictable number. Ask for something in return — a case study, an executive reference, a wider deployment — so it does not read as pure discounting.

It is a trap in three situations, and I have watched all three.

The first is when your champion is not secure. A multi-year contract signed by someone who leaves in six months is not protection, it is a bigger, more visible line item for their replacement to attack, and "we're locked in" is a phrase that makes new leaders angry rather than compliant.

The second is when the multi-year comes with a discount deep enough that you have permanently reset your price in that account. You have not saved the renewal, you have pre-negotiated every future one from a lower floor.

The third is when it is being used to avoid a conversation. If usage is bad and the relationship is thin, a longer term does not fix that, it just moves the reckoning to a date when you will have less leverage and less attention on the account. In that case you need the save conversation with a sales leader who has already half left far more than you need a longer contract.

My rule: multi-year protects a healthy account from a budget event. It does not rescue an unhealthy one from a value problem.

Never trash the platform they are consolidating onto

One more thing, and reps get this wrong constantly.

In most consolidations there is a winner — a big platform vendor everyone is standardising on. The temptation is to attack it. Tell them the platform's version of your module is thin, half-built, a checkbox on a slide. Sometimes that is even true.

Do not do it. Somebody senior chose that platform. Attacking it means telling your champion their leadership made a bad decision, and asking a champion to argue that in a room full of their bosses is asking them to spend political capital they do not have on you. They will not do it. They will just stop returning your emails.

The language that works is coexistence, not competition. "That's a good platform and I'd standardise on it too. The question is whether the piece we handle is something you want to run through it or run alongside it." Then be specific and factual about the gap without editorialising. Where the platform genuinely does the job, say so. Concede the ground you cannot hold and defend the ground you can, because a rep who concedes nothing is a rep nobody believes about anything.

And get comfortable with a smaller footprint. A narrowed contract that survives the consolidation is a live account you can grow back next year. A full contract you defended to the death and lost is a logo on someone else's win report.

What I would do this week

If you own accounts renewing in the next two quarters, go and ask every one of them who owns the consolidation list, before they bring it up. Then rehearse the answer to "we're consolidating" until it does not sound like a flinch — because the reason most reps lose this objection is not strategy, it is that they hear it, pause a half-second too long, and the buyer hears the pause. That is what we built DrillCall for: running the same objection at you until the response is automatic and the pause is gone. I would drill this one before your next renewal call rather than after it.

Consolidation is not a rejection. It is a resource decision made by somebody with incomplete information, and you have most of the missing information. Get it to the person holding the pen, in a sentence they can repeat, before the meeting where it matters.