Negotiating redeployable Salesforce seats: avoiding 100 new licences a year
Named-user licensing quietly charges you for staff turnover. Converting part of the seat pool to a redeployable structure stopped that at renewal.
I spent years on the vendor side of enterprise software, and named-user licensing is one of the more quietly expensive defaults in enterprise CRM contracts. Not because the pricing is unfair, but because of what happens to those licences when the workforce behind them does not stay still.
The situation
The contract used standard named-user licensing: each seat tied to a specific individual, standard practice for CRM platforms like Salesforce. The organisation had meaningful annual turnover in the roles using the platform, with regular hiring and attrition in customer-facing teams. Under a named-user structure, every departure and every replacement meant, functionally, provisioning a new named licence, since named seats are not automatically reusable the moment someone leaves.
Same turnover, two licensing structures
Close to 100 new licences a year
Turnover stops buying licences
Redeployable seats are a real structure on platforms like this, but they are not the default paperwork. The ask has to be made at renewal.
Why this was quietly expensive
Run the maths forward. With turnover at the observed rate, the organisation was on track to need close to 100 new named licences every year. Not because headcount was growing by 100, but because seats tied to departed employees were not cleanly freed up and reassigned without friction, and the default renewal path would have priced that churn as if it were net new growth.
What we negotiated instead
The ask going into the renewal was specific: convert a meaningful portion of the seat pool from strictly named-user licensing to a model where seats can be reassigned, deprovisioned from a departing employee and reprovisioned to their replacement, without each swap requiring a new licence purchase. This is a real licensing structure for platforms like this, but it has to be negotiated. It is not the default contract shape.
The outcome
The renewal secured a redeployable seat structure for the relevant licence pool. Turnover in those roles stopped translating directly into new licence spend, because a leaver's seat could go to their replacement without triggering a fresh purchase. Based on the observed turnover rate, that avoided close to 100 net-new named licences a year, spend that would otherwise have been baked into every future renewal as if it were organic growth.
The takeaway
Named-user licensing punishes any organisation with real turnover in the roles using the tool, because every departure looks, contractually, like it needs a brand new seat. If your workforce in those roles moves meaningfully, asking specifically for a redeployable or pooled structure can be the highest-leverage ask in the entire renewal.