Why We Halve Your Renegotiation Number

When SeatCompress tells you that renegotiating your Salesforce contract is worth $240,000 a year, the underlying math found twice that. The full number, $480,000, is real too. It just belongs in a different place: the negotiation email, not the board deck. The dashboard's year-one realistic figure multiplies your theoretical renegotiation leverage by 0.5 before you ever see it, and that halving is one of the more important honesty decisions in the product.

This is the renegotiation-side companion to a factor we already explained on the deploy side, why deploy-agent realization is 0.4, not 1.0. Same principle, different lever. The number that survives contact with reality is not the number on the vendor's page or the theoretical maximum in a spreadsheet. It is the discounted one, and pre-discounting it is what keeps a CFO from committing the board to a figure procurement cannot deliver.

The problem: the theoretical number is a trap

The theoretical renegotiation number is easy to compute and dangerous to trust. It is:

unused seats times per-seat rate times 12

You have 400 Salesforce seats nobody logs into, at $100 a seat, and that is $480,000 a year of pure waste. The instinct is to write "$480K in Salesforce savings" into the annual plan and move on.

Then procurement actually sits down with the Salesforce rep, and the $480,000 does not show up in the new contract. It never does. Not because the waste was not real, but because a renewal is a negotiation, and the vendor has moves. They will trade a seat reduction for a multi-year lock. They will hold you to a minimum commitment that floors how far the seat count can drop. They will offer a discount on rate instead of a cut in seats, which looks like a win and preserves their revenue base. The theoretical number assumes you get all of the waste back. The real world hands you some of it.

A CFO who put $480,000 in the plan and delivers $240,000 has a variance problem and a credibility problem. Both were avoidable.

The methodology: 40 to 60 percent, so 0.5

The 0.5 is not a guess and it is not pessimism. It is the midpoint of a range that shows up consistently in procurement outcome data.

Procurement aggregators publish what actually happens when companies take a seat-reduction ask into a renewal. Vendr, Spendflo, and Tropic all report outcome data of this kind. The realized reduction consistently lands at 40 to 60 percent of the theoretical ask, after the vendor pushback, the multi-year lock trades, and the minimum-commitment floors have all been applied. The full theoretical cut is the opening position. The settled outcome is roughly half of it.

We took the midpoint of that range and shipped it as the constant. Every renegotiate action in the SeatCompress action plan gets multiplied by 0.5 before it reaches the year-one hero number on your dashboard. It is the same discipline as the 0.4 we apply to agent deployments and the 1.0 we apply to skip-the-agent decisions (not spending is the most fully realized saving there is). Each action type gets the discount its evidence supports.

The result is a dashboard that usually shows two numbers: a larger theoretical figure and a smaller realistic one. Both are true. They answer different questions. The theoretical answers "how much waste is in this contract." The realistic answers "how much of it will actually be in next year's budget." A CFO needs the second number to make a commitment and the first number to make an argument.

The two numbers do two different jobs

This is the part worth internalizing, because it changes how you use both numbers.

The theoretical figure is the ask. It goes in the negotiation. When your procurement team opens the Salesforce renewal, they open at the full $480,000: 400 unused seats, here is the utilization data, we are not paying for seats nobody uses. You never open a negotiation at your own discounted expectation. You open at the defensible maximum and let the vendor negotiate you down toward the number you actually expected. The theoretical figure is the anchor, and it belongs in the renegotiation playbook and the email that starts it.

The realistic figure is the plan. It goes in the budget. When you tell the board what SaaS renegotiation will deliver next year, you commit to the $240,000, because that is the number that survives the vendor's moves. Committing the board to the ask instead of the plan is how a finance team ends the year explaining a $240,000 miss on a number that was never achievable.

The mistake we designed against is collapsing these two into one. Plenty of tools show you the theoretical number, call it "potential savings," and leave you to figure out that "potential" is doing a lot of load-bearing work. We would rather show you both and tell you which one to take to which meeting.

A worked example: Salesforce at an 8,000-employee company

Concrete numbers. An 8,000-employee company runs Salesforce at $100 a seat a month. They hold 1,500 contracted seats. Their identity provider shows 1,100 of those seats actually active in the last month. That is 400 unused seats.

Theoretical renegotiation value:

400 times $100 times 12 = $480,000 per year

That is the waste, and that is the opening ask. Now the realistic figure the dashboard puts in front of the CFO:

$480,000 times 0.5 = $240,000 per year

So the year-one hero number is $240,000. That is what goes in the plan. The $480,000 goes in the email to the Salesforce account team, backed by the utilization data. Procurement negotiates. The vendor trades, floors, and locks. And the settled outcome lands somewhere in the 40 to 60 percent band the data predicted, which is why the plan was built on the midpoint of it.

If procurement is good and the leverage is strong, they beat the $240,000 and the CFO reports a positive variance. If the vendor is stubborn and holds a minimum commitment, they land near it. Either way, the number in the plan was defensible on the day it was committed, which is the only property that matters twelve months later.

What the CFO does with this

Three moves, this quarter.

Separate the ask from the plan on every renewal. Compute the theoretical waste, unused seats times rate times twelve, and use it as your opening position. Then discount it to roughly half for the number you actually commit to. Do not let the opening ask leak into the budget.

Anchor the ask in data, not indignation. The reason the theoretical number works as an opening position is that it is backed by utilization: this many seats, this many logins, this much waste. The rate side of the same conversation, where you push a per-seat or per-employee rate toward the peer median, follows the same rule. The ask is aggressive and sourced. The plan is discounted.

Report the realistic number to the board and keep the theoretical in reserve. If you beat the plan, that is a good quarter. If you had committed to the theoretical, the same outcome would have been a miss. The 0.5 is what turns the same procurement result into a win instead of a shortfall.

We halve your renegotiation number because the halved number is the one that comes true. The full number has a job, and it is a good job, but that job is written in an email to a vendor, not a line in a plan you have to defend.

Try the free calculator, 15 seconds, no signup. The renegotiation number it shows you is already discounted to the plan. The theoretical sits underneath it, ready for the email.