For the complete documentation index, see llms.txt. This page is also available as Markdown.

Dynamic Value Text

Dynamic Value Text lets you combine written narrative with live values from your ROI Model.

Instead of presenting every result as an isolated number, you can place Inputs and Outputs directly inside a sentence or statement.

For example:

Based on the current assumptions, the organisation could generate £850,000 in annual benefit with a payback period of 8.4 months.

When the referenced values change, the dynamic values within the statement change with them.

This makes Dynamic Value Text useful for creating more explanatory and presentation-focused ROI Models.

Where you can use Dynamic Value Text

Dynamic Value Text is available under both:

  • Inputs

  • Outputs

In the Components panel it appears as:

Dynamic Value Text

When configuring the component, the drawer is titled:

Text

How Dynamic Value Text works

A Dynamic Value Text component contains a combination of:

Literal text

and

Dynamic value tokens

Literal text is the wording you write yourself.

Dynamic tokens reference existing Inputs or Outputs in the model.

For example, you might construct:

Your estimated annual saving is [Annual Saving].

Here:

Your estimated annual saving is

is literal text, while:

[Annual Saving]

represents a live value from the model.

Add Dynamic Value Text

To create a Dynamic Value Text component:

  1. Open Show Components.

  2. Choose Dynamic Value Text from Inputs or Outputs.

  3. Write the required wording in the text composer.

  4. Insert dynamic values using Input References or Output References.

  5. Configure the presentation settings if required.

  6. Set a Visibility Condition if needed.

  7. Select Save.

The component is then added to the model.

Write the narrative first

A useful approach is to write the statement as you want the end user to read it before inserting the dynamic values.

For example:

By reducing manual processing, your organisation could save £500,000 annually.

Then replace the value that needs to change dynamically with the appropriate Output reference.

This generally produces clearer statements than starting with a collection of calculation tokens and trying to build wording around them.

Insert an Input value

Use Input References when the statement should include a value entered or selected by the user.

For example:

Based on an annual volume of [Annual Volume] transactions...

If the user changes Annual Volume, the value displayed within the statement can change accordingly.

Input references are useful when you want to repeat an important assumption as part of the narrative.

Insert an Output value

Use Output References when the statement should contain a calculated result.

For example:

The proposed solution could generate [Annual Saving] in annual savings.

This allows calculated Outputs to become part of the explanatory narrative rather than appearing only as standalone result components.

Combine Inputs and Outputs

A single Dynamic Value Text component can combine narrative with references to Inputs and Outputs.

For example:

At [Annual Volume] transactions per year, the model estimates an annual benefit of [Net Annual Benefit].

This can make the relationship between assumptions and results easier to understand.

Create executive value statements

Dynamic Value Text is particularly useful for summarising important results.

For example:

The proposed investment could deliver [Net Benefit] in net annual benefit, representing an ROI of [ROI] with payback achieved in approximately [Payback Period].

This can provide a concise explanation of the business case before users explore the detailed calculations underneath it.

The objective isn't to repeat every Output in sentence form.

Use Dynamic Value Text where narrative genuinely helps explain the significance of the results.

Editing text

Literal text within the composer can be edited.

Where applicable, you may see:

Double click to edit this

Double-click the relevant text token when you need to revise its wording.

The composer also provides controls including:

  • Backspace

  • Delete

  • Clear

Use these when constructing or restructuring the statement.

Token colours

You can apply colour to selected tokens within the Dynamic Value Text composer.

You can also remove previously applied colour.

Use token colour selectively.

For example, highlighting an important calculated value can help distinguish it from the surrounding narrative.

Avoid applying several competing colours within the same statement unless they communicate something meaningful.

Text alignment

Use Text Alignment to control how the statement is positioned.

Choose an alignment that fits the surrounding model structure and the purpose of the statement.

For example, a prominent value statement may be presented differently from supporting explanatory text.

Font size

Use Title font size to control the size of the Dynamic Value Text.

More prominent statements can use greater visual emphasis, while supporting narrative should remain consistent with the surrounding content.

Use font size to reinforce information hierarchy rather than simply making every statement large.

Background

A Dynamic Value Text component can also have a configured Background.

A background can help separate an important statement from surrounding calculations.

For example, you might use Dynamic Value Text as a prominent summary above a group of detailed Results.

Keep the overall model styling consistent when using backgrounds.

Attached Resources

Dynamic Value Text can also be configured with Attached Resources.

This allows supporting resources associated with the Calculator to be surfaced alongside the statement.

If there are no available asset links, ROI Studio may display:

No asset links available for this calculator.

Attached Resources can also use the available Pill style presentation.

For more information, see Attached Resources.

Conditional visibility

Dynamic Value Text supports Visibility Condition.

This means a statement can appear only when the required condition is satisfied.

For example, different explanatory statements could potentially be shown according to values within the model.

When using conditional narrative, make sure the statement still accurately describes the results shown to the user.

For more information, see Conditional Visibility & Calculate on Hidden.

Dynamic Value Text vs standard Outputs

Use a standard Output when the primary objective is to display a calculated value.

Use Dynamic Value Text when the value benefits from explanatory context.

For example:

Standard Output

Net Annual Benefit £850,000

Dynamic Value Text

The proposed solution could generate £850,000 in net annual benefit based on the current assumptions.

Both can be useful within the same model.

Dynamic Value Text vs Cards

Cards are useful for making individual KPIs prominent.

Dynamic Value Text is useful for explaining what those KPIs mean together.

A Results area might therefore contain:

Dynamic Value Text

The proposed solution could generate [Net Benefit] in annual value and achieve payback in [Payback Period].

Cards

Net Benefit | ROI | Payback

This creates a combination of narrative and supporting headline metrics.

Keep statements readable

Avoid placing too many dynamic values into one sentence.

A statement such as:

With [Value A], [Value B], [Value C], [Value D], [Value E] and [Value F], the result is [Value G]...

can quickly become difficult to understand.

Instead, decide what the user actually needs to learn from the statement.

Use several shorter statements or supporting Outputs when necessary.

Preview Dynamic Value Text

Always Preview Dynamic Value Text before publishing.

Change relevant Inputs and check that:

  • Dynamic values update as expected

  • The sentence still reads naturally

  • Values appear in the intended position

  • The wording remains accurate at different values

  • Styling doesn't overwhelm the surrounding content

  • Conditional statements appear when expected

A statement that reads correctly with the initial assumptions may become awkward when those assumptions change.

Write for the buyer

Dynamic Value Text is most effective when it explains the business meaning of the calculation.

Prefer:

Automating these interactions could save [Hours Saved] agent hours each year, generating approximately [Annual Saving] in annual labour value.

rather than:

Hours Saved = [Hours Saved], Annual Saving = [Annual Saving].

The underlying calculations can already present the numbers.

Dynamic Value Text should help communicate what those numbers mean.

Best practices

When using Dynamic Value Text components:

  • Write the sentence for the end user first.

  • Insert dynamic references where values belong.

  • Use Inputs when an assumption needs to be referenced.

  • Use Outputs for calculated results.

  • Keep statements concise.

  • Avoid overcrowding sentences with dynamic tokens.

  • Use colour and backgrounds selectively.

  • Use Dynamic Value Text to explain results, not simply duplicate them.

  • Preview with different Input values.

  • Make sure the wording remains accurate as values change.

Last updated