Skip to content

Cost and Estimated Value

The Decisions & Value segment answers the two questions every funding conversation starts with: roughly what will this cost to run, and what is it worth? Both figures are deterministic models over the design, not AI guesses, and both say where their numbers come from.

Indicative Run Cost

The cost summary estimates monthly run cost from the design's components and scale signals, with the drivers listed so you can see which choices dominate. It is deliberately indicative: a consistent basis for comparing design options and revisions, not a quote. Once delivery starts, actuals belong to your cloud billing; the estimate's job is the decision before that.

Estimated Value Delivered

The value model estimates what the designed solution delivers per year, built from workstreams: the kinds of work the solution performs or replaces, each valued using your organization's own rates.

  1. Configure rate presets once in Settings → ROI (what an hour of each workstream is worth to you).
  2. Each package's value panel maps the design onto workstreams with counts and assumptions you can adjust.
  3. The result shows one-time and recurring value plus a risk-adjusted band, so the range is honest about uncertainty.

Value rolls up across packages at the platform level, which is how the portfolio view can say what the governed pipeline is worth in total.

Make the Numbers Yours

Both models are only as good as their inputs: set your ROI rates and keep scale signals (like expected volumes in the requirements) realistic. The business case reuses these figures verbatim; tuning them here tunes every document downstream.