The Salesforce renewal that produces the strongest outcomes does not begin at the vendor’s scheduled renewal kickoff. It begins twelve months earlier, with structured buyer-side preparation that develops the analytical foundation, the negotiation playbook, and the competitive context well before the formal renewal cycle starts. This guide describes the month-by-month preparation calendar that consistently produces favorable renewal outcomes across the customers we have supported, drawing on patterns from the 500-plus engagements that have contributed to our cumulative $420 million in customer savings.
The twelve-month timeline is not a luxury — it is the minimum window required to complete the analytical work, validate findings with stakeholders, develop competitive intelligence, sequence the negotiation appropriately, and execute the contractual paperwork without rushing. Customers who compress the timeline below six months typically secure outcomes 10–15 percentage points less favorable than customers who run the full twelve-month cycle. The compression cost is often understated in customer-side reviews because it is invisible — the customer never sees the better outcome they could have secured with more time.
Month 12: kickoff and baseline
The cycle begins twelve months before renewal with the internal kickoff. The kickoff establishes the team, the scope, the timeline, and the executive sponsorship. The specific deliverables for month 12:
Renewal team formation. The renewal team typically includes the Salesforce admin lead, the procurement lead, the finance partner, the IT executive sponsor, and the business unit liaisons. The team should meet monthly throughout the cycle.
Executive sponsorship confirmation. The executive sponsor (typically the CFO or CIO) should be briefed on the cycle and committed to the planned approach. Sponsorship at this level becomes consequential in the negotiation phase.
Baseline inventory. The complete inventory of current Salesforce footprint — products, licenses, add-ons, sandboxes, integrations. The baseline is the foundation for everything that follows.
Contract review. A careful read of the current contract, identifying the specific clauses that affect the renewal — renewal price caps, true-up structure, co-term provisions, audit rights, termination clauses.
Timeline establishment. The published cycle calendar with milestones for each phase. The timeline should be shared with the executive sponsor and the team.
Month 11: utilization analysis
Month 11 focuses on the utilization analysis that produces the data foundation. The analysis covers:
Active-user ratios. The 30-day and 90-day active ratios across all license types.
Tier appropriateness. The mapping of user functional patterns to license tier requirements, identifying populations on inappropriate tiers.
Add-on consumption. The usage patterns for add-ons (Sales Cloud Einstein, Service Cloud Voice, CPQ, Data Cloud credits).
Sandbox and storage utilization. The provisioned sandbox count, refresh patterns, and storage consumption patterns.
Integration patterns. The API consumption patterns from integrated systems.
The analysis produces a findings inventory that informs the renewal target. The findings should be quantified in dollar terms with confidence levels.
Month 10: stakeholder validation
Month 10 focuses on validating the utilization findings with business unit stakeholders. The validation conversations:
Present specific findings with supporting data to the relevant business unit leaders. The conversations should distinguish actionable findings from contextual exceptions.
Establish manager attestation on license assignments. The attestation creates the political support for subsequent action.
Identify business unit growth forecasts and changes that affect the renewal scope. The forecasts are essential inputs to the negotiation positioning.
Capture stakeholder objectives for the renewal — specific features needed, specific products to evaluate, specific concerns about the current deployment.
Document the validation conversations for use in subsequent negotiation phases.
Month 9: competitive landscape
Month 9 develops the competitive landscape that creates leverage in the negotiation. Even customers with no realistic migration intent benefit from documented competitive intelligence because the intelligence shapes the vendor’s negotiation posture.
The competitive work covers:
Product-by-product alternatives. For each Salesforce product in the deployment, the credible alternatives and their relative positioning. Sales Cloud has Microsoft Dynamics and HubSpot as alternatives; Service Cloud has ServiceNow and Zendesk; Marketing Cloud has Adobe Experience Cloud and HubSpot; and so on.
Migration cost estimates. The realistic costs of migrating each product, including implementation, data migration, training, and business disruption.
Decision criteria. The specific criteria that would drive a migration decision, used to evaluate the vendor’s renewal proposal.
Reference conversations. Discussions with peer organizations that have evaluated or executed migrations, providing realistic perspectives on outcomes.
Vendor briefings. Optional briefings from credible alternative vendors that document the alternatives in formal terms.
Month 8: financial modeling
Month 8 builds the financial model that supports the renewal target. The model includes:
Current-state cost. The complete current-state Salesforce cost including all license, add-on, sandbox, and support costs.
Optimization scenarios. The cost under different optimization scenarios — aggressive, moderate, conservative.
Renewal scenarios. The cost under different renewal outcomes — vendor proposal, target, walkaway.
Multi-year trajectory. The cost trajectory under each scenario over a three-to-five year horizon.
Migration scenarios. For comparison, the cost of full or partial migration to alternative platforms.
Sensitivity analysis. The cost sensitivity to growth assumptions, escalation rates, and configuration choices.
The model creates the quantitative foundation for the negotiation positioning and supports the executive sponsor’s ability to back the negotiation strategy.
Month 7: target setting
Month 7 establishes the specific renewal targets that the negotiation will pursue. The targets cover:
Total cost target. The specific dollar target for the renewal cost.
Configuration target. The specific license count, tier mix, and add-on configuration.
Contract structure target. The specific clauses to negotiate — renewal caps, true-up structure, audit cooperation, termination flexibility.
Timing target. The specific dates for term start and end, aligned with the customer’s budget and operational cycles.
Walkaway position. The specific point at which the customer would walk from the deal as offered, with the documented consequences of walking.
The targets should be endorsed by the executive sponsor and committed to internally before the vendor conversation begins.
Month 6: vendor kickoff
Month 6 is typically when the vendor expects to begin the renewal conversation. The customer enters the conversation with the analytical foundation, the validated findings, the competitive context, and the targets all in place. The vendor kickoff:
Establishes the formal renewal cycle with defined milestones.
Surfaces the customer’s analytical findings and the implications for the renewal scope.
Identifies the specific products and configurations under discussion.
Communicates the customer’s timeline expectations and the consequences of timeline slippage.
Sets the tone for a collaborative but firm negotiation.
The customer’s preparation work should be visible in the kickoff. The vendor responds differently to customers who arrive with structured analysis than to customers who arrive with general optimization aspirations.
Month 5: initial proposal
Month 5 is typically when the vendor produces the initial renewal proposal. The customer’s evaluation of the proposal should be structured and disciplined:
Compare the proposal to the customer’s target. Identify the specific gaps in cost, configuration, and contract structure.
Identify the assumptions embedded in the proposal — growth projections, product mix, escalation rates, term length.
Evaluate the proposal against the competitive alternatives. The competitive context informs whether the proposal is favorable, neutral, or unfavorable.
Identify the elements of the proposal that may have been included as “negotiating room” that the vendor expects to concede.
Document the initial response and the proposed counter.
Month 4: negotiation rounds
Month 4 typically contains the substantive negotiation rounds. The rounds should be deliberate and sequenced:
Round one: scope and configuration. Negotiate the license count, tier mix, and add-on configuration. The scope discussion is the foundation for the price discussion.
Round two: unit pricing. Negotiate the per-license pricing and the discount structure. The pricing follows the configuration.
Round three: contract structure. Negotiate the renewal caps, true-up structure, audit cooperation, and other structural clauses. The structural clauses determine the multi-year economics.
Round four: bundle and add-ons. Negotiate the bundled add-ons, included services, and optional product additions. The bundle discussion captures additional value.
Round five: final terms. Reach agreement on the final terms, including any holdback items that needed resolution.
Each round should produce documented progress and a clear basis for the next round. Open-ended negotiations that revisit settled items typically produce vendor-favorable outcomes.
Month 3: contract review
Month 3 focuses on the contract paper itself. The substantive negotiation is largely complete, and the work is to ensure that the negotiated terms are captured accurately in the contractual documents. The review covers:
The pricing schedule with explicit clause-by-clause verification.
The renewal mechanism with attention to caps, escalations, and notification requirements.
The true-up structure with explicit definition of pricing basis and timing.
The audit cooperation provisions with attention to the format and frequency of usage data.
The termination clauses with attention to the conditions, notice periods, and consequences.
The service level commitments with attention to the metrics, remedies, and reporting.
The data protection and privacy provisions with attention to evolving regulatory requirements.
The contract review typically involves legal counsel, procurement, and the executive sponsor. The review should produce a marked-up document that captures all remaining issues for resolution.
Month 2: final negotiation
Month 2 resolves the final contractual issues. The substantive negotiation is largely complete, but the contract review typically surfaces specific clauses that need final resolution. The customer should:
Hold firm on the previously negotiated commercial terms.
Negotiate the remaining clauses to acceptable language.
Address any new issues raised in the contract review.
Document the final commitments in preparation for execution.
The vendor often attempts to reopen settled items in the final negotiation phase. The customer should resist these attempts firmly — the resolution of previously settled items in the final phase typically favors the vendor.
Month 1: execution
Month 1 executes the contract. The execution work includes:
Final legal review and signature routing.
Provisioning configuration for the new term.
Communication to affected business units and users.
Documentation of the deal terms for organizational memory and future renewal preparation.
Establishment of the post-renewal tracking that will support the next cycle.
The execution phase is administrative but consequential — errors in execution can undermine the negotiated benefits. The customer should treat execution with the same discipline as the negotiation phases.
Post-renewal: tracking and preparation for the next cycle
The renewal cycle does not end with execution — it transitions into the next preparation cycle. The post-renewal activities:
Continuous utilization tracking against the new contract baseline.
Quarterly reviews of consumption patterns relative to commitments.
Documentation of the deal terms and the negotiation methodology for organizational memory.
Ongoing competitive intelligence refresh.
Early identification of the issues that will shape the next renewal.
The customers who treat each renewal as a fresh start typically underperform the customers who treat the renewal cycle as a continuous discipline.
What to verify in the renewal plan
- The timeline begins twelve months before renewal, not at the vendor’s scheduled kickoff.
- The team includes the right roles with executive sponsorship.
- The analytical foundation is complete before the vendor conversation begins.
- The competitive context is documented even for customers with no migration intent.
- The targets are specific and endorsed by the executive sponsor.
- The negotiation rounds are sequenced deliberately.
- The contract review verifies that negotiated terms are captured accurately.
- The post-renewal discipline sets up the next cycle.
The Salesforce renewal 12-month plan is the discipline that produces consistently favorable outcomes. The customers who follow the discipline typically secure renewal economics 10–20 percentage points more favorable than customers who compress the timeline or skip elements of the preparation. The 34 percent average reduction we secure against opening Salesforce positions reflects in large part the discipline of running the full preparation cycle, not just the negotiation tactics in the final months. The work is repeatable, the methodology is well-defined, and the results compound across cycles as the customer’s renewal capability matures.
Adapting the plan to specific customer contexts
The twelve-month plan described above is a baseline that should be adapted to specific customer contexts. The adaptation considerations:
Account scale. Larger accounts (annual Salesforce spend above $5M) typically need more elaborate preparation cycles, with more granular analytical work and more rigorous validation processes. The twelve-month timeline may stretch to fifteen or eighteen months for the largest accounts. Smaller accounts (under $500K annual spend) may compress the timeline to nine months while still preserving the essential elements.
Contract complexity. Accounts with complex contract structures (multiple products, multiple business units, acquired entities, ramp commitments) typically need additional analytical and legal work compared to single-product, single-unit accounts. The complexity should drive proportional adjustment to the preparation timeline.
Strategic timing. Customers facing strategic inflection points (mergers, divestitures, leadership transitions, major technology transitions) often need preparation cycles that incorporate the strategic context. The strategic timing should drive specific adjustments to the analytical scope and the negotiation positioning.
Competitive context. Customers with active competitive evaluations typically need preparation cycles that integrate the competitive work tightly with the renewal preparation. The integration prevents the renewal conversation from proceeding independent of the competitive context.
Internal capability. Customers with mature internal capability for license utilization analysis can compress some preparation steps; customers building the capability for the first time should allow additional runway. The capability assessment should be part of the initial planning.
The capabilities the plan develops
The twelve-month plan does more than produce a single renewal outcome — it develops capabilities that compound across subsequent cycles. The capabilities:
License utilization analysis discipline. The analytical work in months 11–10 establishes the discipline that supports ongoing optimization between renewals. The discipline persists after the renewal and produces continuous benefit.
Stakeholder relationships. The validation conversations in month 10 build the stakeholder relationships that support ongoing license management. The relationships persist after the renewal and reduce friction for subsequent decisions.
Competitive intelligence. The competitive landscape work in month 9 produces intelligence that informs subsequent strategic decisions, not just the renewal negotiation. The intelligence has value beyond the immediate cycle.
Financial modeling capability. The financial modeling in month 8 establishes a modeling capability that supports subsequent strategic decisions. The capability persists and improves with each cycle.
Negotiation discipline. The sequenced negotiation in months 4–5 builds organizational negotiation discipline. The discipline transfers to other vendor relationships and produces broader value.
Documentation and organizational memory. The documentation work throughout the cycle creates organizational memory that supports subsequent cycles. The memory reduces the preparation burden for subsequent renewals.
The capabilities are perhaps more valuable over time than the single-cycle outcomes. Customers who invest in the full cycle build capabilities that compound across multiple renewals, producing accelerating value across the relationship lifetime.
Common pitfalls in plan execution
Several pitfalls recur across customers attempting to execute the twelve-month plan:
Delayed start. Many customers intend to begin the cycle twelve months before renewal but actually start at six or eight months. The delayed start compresses the analytical work and the validation cycles, producing weaker preparation. The discipline of starting on schedule is essential.
Skipped competitive work. Customers without intent to migrate sometimes skip the competitive landscape work in month 9, treating it as wasted effort. The competitive work creates negotiation leverage regardless of migration intent and consistently produces stronger outcomes than skipping the step.
Unvalidated findings. Some customers treat the analytical findings in month 11 as conclusions rather than as starting points for validation. The validation conversations in month 10 are essential to converting analytical findings into actionable negotiation positions. Skipping the validation produces findings that the vendor can challenge effectively in the negotiation.
Reactive negotiation. Customers who let the vendor drive the negotiation cadence rather than executing their own sequenced approach typically produce weaker outcomes. The discipline of sequencing the rounds deliberately is essential.
Incomplete documentation. Customers who do not document the negotiation methodology and outcomes lose the organizational memory that supports subsequent cycles. The documentation discipline compounds value across renewals.