> ## 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.

# The usual approach

> Identify the right business case, align it with what the customer agreed, then add a Value Realization Scenario

Most teams follow the same practical sequence: find the account and business case, sanity-check the model against the deal, then create the Value Realization Scenario. This page walks through that flow.

## 1. Identify the account and business case

Start from the **account or opportunity** you are responsible for and open the business case you will use for tracking.

**You already have a business case from the sale**

* Prefer the business case that reflects the **deal that was actually signed**—especially if you had multiple versions during the cycle.
* If the renewal or expansion is on a **different opportunity** in your CRM, you can still use the original business case, or [create a new one and copy scenarios](/pages/value-realization/introduction#where-to-track-same-business-case-or-a-new-one) so the record matches the new opportunity.

**No business case exists yet**

* Create a business case first and add the use cases and calculations you need. Value Realization builds on that structure; see [Getting started: Create a business case](/pages/getting-started/create-business-case) and [Scenarios](/pages/business-case/scenarios).

**Upsell, renewal, or new logo**

* The same Value Realization workflow applies; what changes is **CRM context** and how you will **use the story** in the next commercial conversation. For pitching expansion or renewal with proof points, see [Upsells and renewals](/pages/value-realization/upsells-and-renewals).

## 2. Review the business case

Before you add a Value Realization Scenario, confirm the model matches what you and the customer agreed.

**If there are multiple future scenarios**

* Decide **which scenario** best represents the plan you are measuring against—often the rollout or “live” plan that matches the signed contract.

**Use cases and timeline**

* Check that **use cases in scope**, **contract start**, and **duration** line up with the agreement (including phased rollout if you modeled it that way).
* If the business case is out of date, update it now so measurements and the [Value Summary](/pages/value-realization/measurements#the-value-summary) tell a coherent story.

## 3. Create the Value Realization Scenario

When the business case reflects the deal, add a **Value Realization Scenario**: set the real contract window, copy from the future scenario you chose, then [record measurements](/pages/value-realization/measurements) as data is available. Use the optional [Converting Calculations](/pages/value-realization/converting-calculations) helper only when it fits your model—many teams also rely on [monthly values](/pages/value-realization/measurements#how-time-series-inputs-work) or direct calculation edits instead.

<CardGroup cols={2}>
  <Card title="Scenarios reference" icon="book-open" href="/pages/business-case/scenarios#value-realization-scenarios">
    How Value Realization Scenarios work and how to add one
  </Card>

  <Card title="Hands-on recipe" icon="list-check" href="/pages/recipes/create-value-realization-scenarios">
    Step-by-step: create the scenario and enter your first measurements
  </Card>
</CardGroup>

## Next in the docs

<CardGroup cols={2}>
  <Card title="Measurements" icon="chart-line" href="/pages/value-realization/measurements">
    Record monthly values and use the Value Summary
  </Card>

  <Card title="Milestones" icon="flag" href="/pages/value-realization/milestones">
    Track rollout checkpoints alongside financial impact
  </Card>
</CardGroup>