TLDR:
Ramping allows you to assign a % reduction to the total calculated benefit for a period of time. Typically added to the first few months or quarters of a contract to account for standard adoption times of your platform. To add a ramp: click Add Phase and adjust the default 100% value to a % greater than zero. The ramped total applies to all use cases within the phase.What is a Phase?
A business case calculates the financial benefit a customer will receive from using your product. That hinges on one critical idea: they must actually use your product. Adoption of the product likely won’t happen all at once. The best practice is to rollout in phases, this typically means one of two things:- Allowing certain teams, departments, or geographies to get started then gradually releasing it to the wider organization.
- Activating certain features or products before others.
What is Ramping?
In Minoa, you can do this using the timeline feature. Click the button to Add a phase. A phase has a start and end month and defaults to 100% ramping. This means that all use cases on the timeline that fall within a phase will be calculated to achieve 100% of their total benefit. If you set the ramping value to less than 100%, say 50%, it means that during the months of the phase the active use cases will be calculated at 50% of their total benefit.How to Add Ramping
Let’s look at an example:
I’ve built a business case for how Acme Co. will benefit from working with Minoa. There are two use cases in the business cases: Pre-Sales Business Case Automation - Saving time on building each business case. Post-sales Upsell and Renewal - Providing a more sophisticated pitch for renewing the contract While we know that Acme Co. will benefit from both of these use cases, we know that pre-sales will deliver value faster. So we might say that the post-sales use case gets activated 1-2 quarters after the start of the contract. So the pre-sales use case starts on day one, but based on what we’ve seen from rollouts at similar companies, we believe they’ll get 25% of the benefit in the first month, and 80% by month two. This might be due to the enablement necessary to teach sellers how to use the tool, or the length of the sales cycles requiring more time to actually experience the benefit of the product. In this scenario, we’ve added both use cases to our timeline already. Now we can add two phases: 1. Initial Rollout - Starts at month one and ends at month two. We’ll add a 25% ramp to this phase. 2. Expanded Rollout - Starts at month two and lasts two months. Let’s add an 80% ramp to this second phase. We don’t need to add a phase to the rest of the contract, but you can if it helps with clarity. By default, the rest of the months in this contract will be calculated at 100% of total benefit.How does Ramping Impact my Calculation?
You’ll notice that your Calculated Benefit changes when you add ramping. This is because the benefit of the use cases have now been adjusted to account for the Initial and Extended rollouts. You can place your cursor inside of the Calculated Benefit box to view the phases from anywhere in your business case. If you want to save your phases and ramps but not show them to a prospect just yet, you can always set the Timeline to hidden by clicking on the tab and selecting “Hidden” from the visibility menu. A hidden timeline won’t show up for external users and your use cases will return to their original totals.Advanced Ramping
For more granular control over how value ramps across the contract, open the Ramping Modal by clicking “Add Ramp” or “Edit Ramp.” You can find this button above the timeline, in the menu when clicking on a month header, or in the menu when clicking on a use case bar. The modal gives you a spreadsheet-style table where each row is a use case and each column represents a time period. Click any cell to type a ramping percentage between 1% and 100%. The modal has three tabs so you can work at the level of detail that fits your deal:Monthly
Monthly
The Monthly view gives you full control — one column for every month of the contract. Each cell maps directly to a single month’s ramp value for that use case.This is the most precise view. Use it when you need to model a specific adoption curve, for example ramping from 25% in month one, to 50% in month two, to 80% in month three before reaching full value.
- Cells outside a use case’s active range are disabled and shown as ”—”.
- Year and quarter boundaries are marked with heavier borders so you can orient yourself in longer contracts.
- Navigate with arrow keys, Tab, or click directly into any cell.
Yearly
Yearly
The Yearly view groups months into 12-month blocks (Year 1, Year 2, etc.), so you can set ramping at a higher level without touching every individual month.If all months within a year share the same ramp value, the cell shows that value and you can edit it directly. If the months have different values (e.g. you set varying monthly ramps earlier), the cell shows Mixed with a range like “20% → 100%”. Editing a mixed cell will overwrite all the monthly values in that year — you’ll get a confirmation prompt before anything changes.
- Use the reset button in each year’s column header to clear all ramping for that year back to 100%.
- Great for longer contracts where you want to say “Year 1 is at 60%, Year 2 is at full value.”
By Phase
By Phase
The By Phase view maps directly to the phases you’ve defined on the timeline. Each column represents one phase, with its title and date range shown in the header.Just like the Yearly view, cells show a single value when all months in the phase share the same ramp, or Mixed with a range when they differ. Editing a mixed cell overwrites the monthly values for that phase after confirmation.
- This tab is only available when you have at least one phase on the timeline. If no phases exist, you must first create one on the timeline tab.
- Use the reset button in each phase header to clear ramping for that phase.
- This is the most natural view when your ramping story aligns with your rollout phases—set Phase 1 to 30%, Phase 2 to 70%, and let the rest run at full value.