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

# Keep Value Docs in Sync with the Business Case

> Numbers in your one pager and value story docs update when the business case does.

## Update the business case once. Every doc follows.

Business cases change. A champion pushes back on an input. Finance wants a more conservative number. A use case gets cut.

Before, every change meant going back through the one pager, the exec summary, and every other doc to fix the numbers by hand. Miss one and the customer sees two different numbers for the same deal. That costs you credibility fast.

Now the values in your docs are linked to the business case. When the use cases or numbers in the business case change, the one pager and every value story doc that references them update too.

![A Value Story One Pager with highlighted values pulled live from the business case](https://mintlify.s3.us-west-1.amazonaws.com/minoa/images/live-references-one-pager.png)

Every highlighted value is pulled live from the business case.

## What stays in sync

The highlighted values are references, not typed-in text. Using the one pager above:

| Reference | Example |
| - | - |
| Total benefit | \$3,890,167 |
| Investment | \$2,482,500 |
| Payback | 11 months |
| Use case names | Automated Customer Success Support |
| Use case benefit | \$3,570,000 |
| Cost of inaction | Pulled the same way when the doc uses it |

The use case table is live too. Add or remove a use case in the business case and the table follows.

## Why it matters

> **One set of numbers**
>
> The customer sees the same number in the business case, the one pager, and the PDF. No conflicting figures floating around their org.

> **No rework when the deal moves**
>
> Adjust an input live on the call. The docs are already current by the time you hit send.

> **The story keeps up with the account**
>
> As the business case gets updated through the customer journey, the value story docs stay current with it.

## How it works

**1. Build or update the business case**

The business case is the source of truth. Use cases, inputs, investment, and payback all live there.

**2. Generate the doc**

When the agent creates a one pager or any value story doc, the numbers come in as live references. They show up highlighted.

**3. Change the business case**

Update an input. Swap a use case. Adjust the investment. Every doc on the deal that references those values updates with it.

**4. Share it**

PDF export, preview, present mode, and the customer's view all show the current numbers.

## Making edits

Two ways to do it. Your call.

> **Ask the agent**
>
> Tell it what you want. The agent writes the numbers in as live references.
>
> * "Add the payback period to the exec summary."
> * "Rewrite the summary to lead with developer productivity."
> * "Make this customer facing for the CFO."

> **Edit it yourself**
>
> Type anywhere like a normal doc.
>
> To add a live value, type `/` and pick **Synced tags**. Then choose Annual benefit, Payback, Cost of inaction, or a specific use case.

> [!NOTE]
>
> To change a referenced number, change it in the business case, not the doc. Click any highlighted value to jump to where it comes from.

## Tips

> **Use a synced tag, not a typed number**
>
> If you type a number in by hand, it won't update. Any time a sentence includes a value from the business case, drop in a synced tag instead.

> **Reread the story after big changes**
>
> The numbers update on their own. The narrative around them might not. If you cut a use case or the payback moves a lot, reread the summary or ask the agent to refresh it.

> **Placeholders before you quantify**
>
> If the business case doesn't have numbers yet, tags show as placeholders like "Annual benefit" or "Payback." They fill in once the case is quantified. Your customer never sees a placeholder.

> [!TIP]
>
> The business case holds the numbers. The docs help supplement the value story.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.