> ## Documentation Index
> Fetch the complete documentation index at: https://irisdocs.prescientlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Presenting ROI

> Present expected value as a decision model with assumptions and scenarios rather than a guaranteed saving.

Lead with the business mechanism, not the headline percentage.

## Recommended structure

1. **Current cost or constraint**
2. **Proposed intervention**
3. **Operational change expected**
4. **Financial conversion**
5. **Implementation and ongoing cost**
6. **Conservative/base/upside scenarios**
7. **Key sensitivities**
8. **Measurement plan after launch**

## Example talk track

> The base case assumes the new workflow affects 70% of current cases and reduces handling time by eight minutes. The most important uncertainty is adoption, so we have also shown the case at 50%. This is expected capacity value, not guaranteed salary reduction.

## CFO questions to anticipate

* What is the source of the baseline?
* Which assumption matters most?
* What happens if adoption is lower?
* What costs are excluded?
* When would the benefit be realised?
* How will we measure it after implementation?

## Avoid

* one precise number with no sensitivity;
* calling capacity cash saving;
* ignoring implementation effort;
* presenting model-generated values as independently verified facts.