Skip to content

Commit 6f32baf

Browse files
authored
Update ROI analysis for proposed AI solution
1 parent f07128f commit 6f32baf

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

learn-pr/wwl/evaluate-costs-benefits-ai-powered-business-solution/includes/3-create-roi-analysis-proposed-ai-solution-business-process.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Creating a rigorous ROI analysis is essential for evaluating whether an AI solut
66

77
- Productivity and efficiency metrics
88

9-
- Costsavings calculations
9+
- Cost savings calculations
1010

1111
- Total cost of ownership (TCO)
1212

@@ -20,7 +20,7 @@ Creating a rigorous ROI analysis is essential for evaluating whether an AI solut
2020

2121
- **Define a defensible ROI scope** for an AI solution mapped to a single business process, with clear baselines and guardrails.
2222

23-
- **Quantify time and cost savings** using an agent-level savings model (perrun and pertool) and translate savings into financial benefits that align to enterprise KPIs.
23+
- **Quantify time and cost savings** using an agent-level savings model (per-run and per-tool) and translate savings into financial benefits that align to enterprise KPIs.
2424

2525
- **Build a complete ROI model** that balances benefits against **total cost of ownership (TCO)** across infrastructure, development/integration, data quality, expertise, and ongoing operations.
2626

@@ -54,7 +54,7 @@ Most process gains fall into three buckets:
5454

5555
Support each lever with _observations you can measure_ (e.g., the step the agent automates, the decision it accelerates, or the draft it prepares).
5656

57-
### 3. Quantify savings with the Savings Calculator (perrun and pertool)
57+
### 3. Quantify savings with the Savings Calculator (per-run and per-tool)
5858

5959
Use the agent **Savings** capability to estimate and then track time or money saved. You can configure:
6060

@@ -72,7 +72,7 @@ Admins can disable money based savings; if so, keep tracking _time_ and convert
7272

7373
- _Fully loaded labor rate_ (currency/hour) for the role(s) impacted.
7474

75-
- _(Optional)_ Tool specific time/cost deltas when using the pertool model.
75+
- _(Optional)_ Tool specific time/cost deltas when using the per-tool model.
7676

7777
**Savings model (example)**
7878

@@ -99,7 +99,7 @@ The calculator stores these estimates and shows trends over time so you can adju
9999

100100
- Show more lines
101101

102-
**Evidence to calibrate your ranges.** Early field studies on Copilotstyle tools show measurable time reductions in common knowledge work (e.g., faster document creation and reduced time spent reading email). Use these as _directional_ anchors when setting optimistic/expected/conservative ranges—always validated against your baseline.
102+
**Evidence to calibrate your ranges.** Early field studies on Copilot style tools show measurable time reductions in common knowledge work (e.g., faster document creation and reduced time spent reading email). Use these as _directional_ anchors when setting optimistic/expected/conservative ranges—always validated against your baseline.
103103

104104
### 5. Model TCO (the five cost drivers)
105105

@@ -151,7 +151,7 @@ _Sensitivity bands_<br>Create **optimistic / expected / conservative** cases by
151151

152152
- Quality/rework effects (use error rate deltas).
153153

154-
**Why add ranges?** Stakeholders can see upside and risk. Use the researchanchored directional effects on knowledge work time as justification for your bands while keeping your _own telemetry_ in the driver's seat.
154+
**Why add ranges?** Stakeholders can see upside and risk. Use the research anchored directional effects on knowledge work time as justification for your bands while keeping your _own telemetry_ in the driver's seat.
155155

156156
### 7. Package the executive one slide
157157

0 commit comments

Comments
 (0)