Case Study4 min readBoris, FounderPublished , updated

    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.

    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. The same review is offered as a fixed-price SaaS license audit.

    Same turnover, two licensing structures, two very different licence counts.

    Turnover disguised as growth

    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.

    The structural ask

    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.

    What changed at signing

    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.

    Applying this beyond Salesforce

    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.

    Common questions

    A licence that can be deprovisioned from a departing employee and reassigned to their replacement, rather than staying permanently tied to one named individual.

    Each departure leaves a seat attached to someone who has left, so the replacement needs a new licence. Over a year of normal attrition, that reads as growth on the renewal.

    No. It exists on major CRM platforms but it is not the default contract shape, so it has to be raised specifically at renewal.

    During renewal negotiation, before the new term is signed. Mid-term changes to licensing structure are far harder to get.

    Keep reading

    Let's look at your next renewal together.

    Thirty minutes with the founder. We map your upcoming renewals, flag the notice windows that are about to close, and you decide whether Venduris is worth your time.

    Show me my exposure