Practice · IV.

Salesforce. Renewal and seat economics.

The Sales Cloud and Service Cloud renewal anchor, the Data Cloud consumption commitment, the MuleSoft Anypoint Platform and Tableau scope, the user-type reconciliation, the Agentforce expansion, and the multi-year discount design. Six commercial conversations that compound across the renewal window. Independent buyer-side advisory across the full Salesforce estate. Shelfware identified, user types reconciled, contractual instruments negotiated against documented usage.

Speak with a Senior Advisor Engagement models
Salesforce licensing advisory

Salesforce renewals compound. Year over year.

Every renewal that closes without a position paper hands the publisher a baseline for the next renewal. The opportunity to reset the baseline closes for another three to five years.

Where the practice intervenes
Six points on the Salesforce contract cycle.
Pre-renewal
i.
Estate reconstruction
Nine months before the renewal anchor, the Salesforce estate is reconstructed across Sales Cloud, Service Cloud, Marketing Cloud, Data Cloud, MuleSoft, Tableau, Slack, Heroku and Industries clouds. User types, edition mix, add-on entitlement and consumption metrics are mapped. The position paper governs the renewal commercial conversation.
User reconciliation
ii.
User type mapping
Salesforce user-type classification across Standard, Platform, Service Cloud, Identity, Customer Community and Partner Community is reconciled against documented usage. Reclassification opportunities are identified. Shelfware seats are documented. The user position is filed before the renewal commercial letter is returned.
Data Cloud
iii.
Consumption commitment design
Salesforce Data Cloud credit-based consumption is sized against documented ingestion, harmonisation, segmentation and activation workloads. Credit conversion rates, discount tiers and consumption ramp are designed. The Data Cloud commitment is scoped to the workload, not to the publisher's preferred ramp.
MuleSoft / Tableau
iv.
Adjacent product scope
MuleSoft Anypoint Platform entitlement against documented integration volumes, and Tableau Creator, Explorer and Viewer scope against documented analyst populations. Adjacent product entitlement is reconciled and renegotiated against the master Salesforce agreement.
Agentforce
v.
AI expansion scope
Salesforce Agentforce and Einstein AI consumption-based pricing is sized against documented use cases at user-population level. Pilot scope, expansion criteria, dollarised business case and exit terms are documented before the AI commitment is approved.
Renewal close
vi.
Multi-year discount design
The renewal closes against a multi-year commitment with documented discount tiers, price protection, contraction rights and renewal anchor terms. The closing contract is reviewed clause by clause. The senior advisor sits opposite the publisher's account team for the full negotiation.
Where the work concentrates
Active mandate areas across the Salesforce book.
All case studies →
Renewal preparation
Anchor, discount, price protection
Renewal anchor strategy, discount benchmarking, price protection on level commitments, contraction rights, mid-term price increase protection.
Read →
User-type reconciliation
Standard, Platform, Identity, Community
User-type classification across Standard, Platform, Service Cloud, Identity, Customer Community and Partner Community. Reclassification opportunities and shelfware identification.
Read →
Data Cloud commitment
Credits, consumption, harmonisation
Data Cloud credit-based consumption design, credit conversion rates, ingestion and harmonisation scoping, activation workload sizing.
Read →
Agentforce and AI
Pilot scope, ROI, exit terms
Agentforce and Einstein AI consumption-based pricing, pilot scoping, business case documentation, expansion criteria, exit and pause terms.
Read →
MuleSoft and Tableau
Anypoint, Creator, Explorer, Viewer
MuleSoft Anypoint Platform entitlement against documented integrations, Tableau user-type scope, adjacent product renegotiation against master agreement.
Read →
Shelfware identification
Cancellation, contraction, swap
Shelfware seat identification at user-population level. Cancellation rights, contraction rights, product swap rights at the renewal anchor.
Read →
I.
Named senior advisor
The senior advisor named on the engagement letter leads every Salesforce conversation. No leverage model, no rotation of junior consultants, no anonymous correspondence with the publisher. The advisor signs every position document.
II.
Counter-signed positions
Every written counter-position to Salesforce is signed by the senior advisor and counter-signed by a second partner before transmission. Two named signatures on every position document for the full five-year retention period.
III.
Independent on every clause
Admodum holds no commercial relationship with Salesforce. No reseller margin, no implementation partner referral, no AppExchange placement. We do not work both sides.
IV.
Six conversations, one position
Sales Cloud, Service Cloud, Data Cloud, MuleSoft, Tableau, and Agentforce negotiate against each other across the renewal anchor with a single integrated position paper. The senior advisor sits opposite the publisher for the full negotiation.
V.
Five-year retention
Every position paper, counter-position, and closing memorandum is retained inside the firm for five years from engagement close. The buyer can request source workings at any point in that window.
VI.
Reset the baseline every cycle
Every Salesforce renewal closes with a written baseline reset. The closing position, the contractual amendments accepted, and the live obligations carried forward are tied into the next renewal preparation cycle through the Renewal Programme.
$240M
Salesforce Spend Advised
58
Renewals Closed
23%
Median Discount Uplift
31
Data Cloud Designs
100%
Named Advisor
"
The publisher's opening renewal position was a twenty-eight percent increase against the prior term, with a forced uplift on Data Cloud credits we had not consumed. After the position paper, the close was a six percent increase with documented contraction rights on shelfware seats.
Chief Revenue Officer
Global Software Group · Renewal Q3 2025
Operating principles
How the practice is run.
Renewal before the publisher's letter.
Salesforce renewals are won inside the position paper, not inside the publisher's renewal letter. The position paper is filed nine months before the anchor. The publisher's pricing letter is returned only after the buyer's position is on file.
User type by population.
Salesforce user-type reconciliation is documented at user-population level. Different populations carry different entitlement needs. The right mix of Standard, Platform, Service Cloud, Identity and Community user types is documented per population with reclassification paths.
Data Cloud to the workload, not the ramp.
Salesforce Data Cloud credit-based consumption is sized against documented ingestion, harmonisation, segmentation and activation workloads. The commitment is scoped to the workload reality, not the publisher's preferred consumption ramp.
Shelfware is contractual, not optional.
Shelfware seats are identified at user-population level and addressed through contractual contraction rights at the renewal anchor. Contraction rights, product swap rights, and cancellation rights are negotiated into the closing contract.
Questions

Asked before engagement.

How do we control the Salesforce renewal uplift?

With usage evidence and timing. An active-user audit strips shelfware before the negotiation, benchmarking sets the discount target, and Salesforce's 31 January fiscal year-end provides the calendar leverage. Multi-year terms are traded only against uplift caps and flexibility clauses.

What do we do about unused Salesforce licences?

Reclaim them before renewal, not after. Login history and feature-usage data identify inactive seats and over-provisioned editions; the corrected seat mix becomes the renewal baseline. Mid-term reductions are rarely available, which is why the renewal window is the only reset point.

How are Data Cloud and Agentforce priced?

On consumption credits rather than seats. Credit burn is difficult to forecast from a standing start, so commitments should be sized on pilot telemetry with contractual protections on rollover and re-rating.

How are engagements priced?

Three frameworks: fixed fee for scoped deliverables, contingency tied to verified savings, and an annual retainer for continuous coverage across every vendor. The model is agreed on the first call, which is always complimentary, and independence is warranted in writing on every engagement letter.

Independence
Admodum is not a partner, reseller, or affiliate of any software vendor. No reseller margin, no referral commission, no audit subcontract from any publisher.
Salesforce licensing advisory

Open a Salesforce conversation.

Practice across Sales Cloud, Service Cloud, Data Cloud, MuleSoft, Tableau, and Agentforce. Independent. Buyer-side only. Engagement structured as fixed fee · contingency · annual retainer.