Audience: Salesforce Partners projecting multi-year usage in a customer estimate.
Learn how the Ramping step models Year-Over-Year (YOY) usage growth, how to set the number of years, and how ramping builds on the Year 1 consumption baseline.
Use this once Year 1 is set and the deal needs to cover several years. It explains what ramping projects, how to choose how many years the estimate covers, and how that projection reaches the totals.
Year-Over-Year (YOY) Ramping models the customer's expected increase in usage in the years after Year 1. It projects how Flex Credit consumption grows each year from the Year 1 baseline you set in the Consumption step. 100% reflects that Year 1 baseline rate at steady state.
On the Ramping step, set the Number of Years the estimate should cover. The calculator then projects usage and cost for each year up to that number.
No. The step opens with default growth assumptions already in place, so you can advance without touching them. When you do, a "Proceed with Default Settings?" prompt appears; confirm to continue, or go back and adjust the growth per year.
Change them whenever the customer has a view of their own adoption curve, since the defaults are generic and the projection they produce drives every year after Year 1.
Ramping determines the per-year usage that feeds the Totals step. The combined total on the Totals step reflects all the years you configured here, not just Year 1.
Example of a multi-year projection: A partner sets the Number of Years the estimate should cover. The calculator keeps the Year 1 consumption baseline and, at default, projects stable usage for the later years. They then adjust the Year-Over-Year (YOY) figures if the customer expects usage to grow, and those years feed the multi-year total on the Totals step.
How many years to model, and what growth is realistic for a given customer, are commercial judgements — take them to your Partner Account Manager. If the step itself does not behave as described here, open a support case in Partner Community.
005459664

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.