Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.minoa.io/llms.txt

Use this file to discover all available pages before exploring further.

This recipe walks you through starting value realization on a closed-won deal: creating a Value Realization Scenario, recording measurements, and reviewing the Value Summary. Guided conversion is covered as an optional step when it helps reshape common pre-sales calculations—you can skip it and still track realized value using monthly values or your own calculation edits. By the end, you’ll have a living record of value delivery that updates as you add measurements.
1

Open your business case

Navigate to the business case for the closed-won deal.
2

Create a Value Realization Scenario

Add a Value Realization Scenario to track realized value.
3

Optionally convert calculations

When useful, use the guided flow—or configure tracking without it.
4

Record measurements

Enter actual metric values for past and current months.
5

Review the Value Summary

See realized value; compare to estimates when a future scenario is available.

​
Open your business case

Start with the business case you used during the sales process. This is important because the Value Realization Scenario builds directly on the calculations you already have—no need to recreate anything.
  1. Navigate to your opportunity
  2. Open the existing business case
If you built multiple business cases during the sales cycle, open the one that best represents the deal that was agreed upon.

​
Create a Value Realization Scenario

Open the scenarios panel on the left side of your business case and click Add Value Realization Scenario.

​
Configure the scenario

1

Name it

Give the scenario a clear name. The default works well, or use something like “Year 1 Actuals” or “Contract Realized Value.”
2

Choose your starting point

Select Copy from existing scenario and pick the future scenario that most closely represents the agreed-upon deal. This pre-populates all use cases and calculations.If you’re tracking against a deal from a different business case (e.g., an expansion), you can also pull use cases from another business case.
3

Set contract terms

Enter the start month and contract duration for the actual contract. These can differ from the future scenario’s terms—set them to match reality.For example, if the deal was supposed to start in June but actually kicked off in August, set August as the start month.
4

Create

Click Create. Your Value Realization Scenario appears in the scenario selector.
Each business case can have one Value Realization Scenario. If you need to track realized value for a completely separate contract, create it in a separate business case.

​
Optionally convert calculations

You do not have to run conversion to use Value Realization. Skip this section if your calculations already have their inputs in an easy to track format. When the guided flow does fit (usually calculations that follow a “baseline × % improvement” approach), use it as a shortcut. With the Value Realization Scenario active, look for a conversion icon in the top-right toolbar of each use case card. It indicates which calculations can use the conversion flow from pre-sales format to post-sales tracking.
1

Open the conversion tool

Click the conversion icon in the top-right toolbar of any use case card to open the conversion modal.
2

Review the suggested metrics

For each calculation, the system suggests which metric to track monthly. Pre-configured use cases (from your Value Framework) show as Ready — just confirm and convert.
3

Select metrics where needed

For calculations that need your input, select the improvement metric — the value you’ll measure each month (e.g., “Avg. Tickets per Day”). For percentage-based calculations, you’ll also confirm the reference metric (the projected improvement percentage).
4

Convert

Click Convert. Your calculations transform: percentage formulas become absolute-value tracking, and your selected metrics become time-series inputs with monthly columns.
If a calculation has all the information it needs (pre-configured metrics, clear input structure), the conversion can happen automatically when you create the scenario. Look for a prompt offering to convert everything at once.
The conversion tool lets you select one metric per calculation. If you want to track two, split the calculation first. The fastest way is to ask the AI Value Engineer:
I need to track two separate metrics for the "[Use Case Name]" use case
in my Value Realization Scenario. Please split the existing calculation
into two separate calculations on the same use case — one that isolates
[first metric, e.g. "average handle time"] and one that isolates
[second metric, e.g. "tickets processed per day"]. Keep all the original
inputs, but divide them so each calculation is driven by a single
trackable metric. Preserve the total benefit across both.
You can also split manually—see Converting Calculations for all options.

​
Record measurements

Once the inputs you care about are set up for tracking (with or without conversion), start entering real data.

​
Backfill historical months

If the contract started several months ago, go back and enter values for months that have already passed:
  1. Switch to the Value Realization Scenario
  2. Open a use case calculation
  3. Find the tracked metric row (the time-series input)
  4. Click the cell for each past month and enter the measured value
Values carry forward automatically. If the metric was 100 in August and 115 in October, just enter those two values—September will use the August value, and November onward will use the October value until you enter something new.

​
Enter current month data

For the current month, simply enter the latest measurement in the appropriate cell. The benefit calculation updates in real time as you type.

​
For each use case

Repeat for every use case with converted calculations. Each tracked metric has its own time-series row where you enter monthly values.

​
Review the Value Summary

With measurements entered, navigate to the Value Summary view to see the full picture.

​
What you’ll see

  • Total realized benefit — The headline number showing total value delivered up to the current month
  • Realized vs. estimated chart — A cumulative benefit chart comparing your actual measurements against the projected curve from a future scenario
  • Per-use-case breakdown — Each use case showing its individual realized benefit and tracking status

​
Using the Value Summary

The Value Summary is your go-to view for customer conversations:
Lead with the realized vs. estimated chart. It instantly shows whether you’re delivering on the promise made during the sales process. Highlight use cases that are outperforming and discuss plans for any that are lagging.
You can toggle whether the estimated value curve from a future scenario appears on the chart. Hide it if realized value is significantly below projections and you want to present a simpler view to the customer.

​
Ongoing tracking

Value realization isn’t a one-time setup—it’s an ongoing practice. To keep your data current:

Monthly cadence

Set a recurring reminder to enter measurements at the end of each month. Consistency is key to building a reliable trend.

Track milestones

Add milestones to document implementation progress alongside financial results. They provide the “why” behind measurement trends.

Share progress

Use the Value Summary in your regular customer touchpoints. The more visible the results, the stronger the renewal and expansion story.

Update as needed

If inputs change (e.g., team size grows, costs shift), update them in the calculation. Time-series inputs handle mid-contract changes naturally.
You’re tracking realized value! For the optional conversion helper, see Converting calculations. Deep dives: recording measurements and tracking milestones.