Skip to main content
Fluency tracks the outcome of every agent run, giving you a continuous record of hours saved, errors reduced, and cycles completed — all queryable through the Assistant. This guide explains how to measure ROI at the initiative level, the team level, and the organization level.

​
Initiative-level ROI

Open any active or completed initiative to see its running impact metrics. The Initiatives dashboard surfaces four core figures for every initiative:
  • Cumulative hours saved — the total time reclaimed across all completed runs since deployment, calculated from the difference between the pre-automation cycle time and the post-automation cycle time.
  • Runs completed — the total number of workflow runs the agent has processed, giving you a clear picture of operating volume.
  • Exceptions handled — the number of runs that required human intervention, along with the exception rate as a percentage of total runs. Tracking this over time shows whether the agent is becoming more capable as it accumulates run data.
  • Projected vs. actual impact — a comparison between the savings Fluency projected at the opportunity stage and what the deployed initiative has actually delivered. This gap view is one of the most useful signals for understanding whether your automation program is performing as expected — and for surfacing initiatives that are over- or under-delivering relative to plan.

​
Using the Assistant for ROI queries

The Assistant lets you query your initiative data in natural language, without building reports manually. Open the Assistant from the sidebar and ask questions directly. Here are examples of the queries you can run:
  • “How many hours did the Invoice Processing initiative save last quarter?”
  • “What is the total ROI across all Finance team automations?”
  • “Which initiative has the highest variance between projected and actual savings?”
  • “Show me a month-over-month trend for cycle time on the Onboarding workflow.”
The Assistant returns structured responses — tables, bullet summaries, and narrative text — formatted for direct use in presentations or reports. You can follow up with clarifying questions in the same session: for example, after asking for total ROI, you can ask “Break that down by initiative” or “Which team contributed the most?” and the Assistant will refine its answer without requiring you to start over.

​
Building a board-ready report

1

Open the Assistant

Select Assistant from the left sidebar to open a new query session.
2

Ask for the ROI summary you need

State your request in plain language — for example: “Generate a Q2 ROI summary for all active initiatives.” Be as specific as you need: you can scope by team, time period, initiative type, or any combination.
3

Review the structured output

The Assistant formats its response as a combination of tables (for numerical data), narrative paragraphs (for context and interpretation), and bullet summaries (for executive consumption). Review the output for accuracy — if any figure looks unexpected, ask the Assistant to explain its calculation or drill into a specific initiative.
4

Export the report

Click Export to download the Assistant’s output as a formatted document. Fluency generates a clean file — no reformatting, no copy-pasting into a template.
5

Share with stakeholders

Send the exported report directly to your stakeholders. The document is structured for executive audiences — clear metrics at the top, initiative-level detail below, and supporting data available on request. No additional editing is required before sharing.

​
Continuous improvement loop

Measuring ROI isn’t the end of the cycle — it’s the input for the next one. As your initiatives accumulate run data, Fluency feeds that information back into Work Explorer and the Opportunities module. You’ll see two kinds of signals emerge:
  • Refinement signals — existing workflows that the agent is handling well but where further optimization is possible, such as reducing exception rates or expanding the scope of automation within a workflow.
  • New opportunity signals — adjacent workflows or process variants that Fluency has now seen enough of to identify as strong automation candidates.
Review the Opportunities module regularly — monthly at minimum — to identify your next wave of automation candidates. The most effective automation programs treat this as a continuous loop rather than a one-time project.

​
Key metrics to track

Use these metrics to build a consistent measurement framework across your automation program:
MetricDescription
Hours saved per monthTime reclaimed per initiative and in aggregate, based on cycle time reduction across all completed runs
Cycle time reductionThe before-and-after comparison for average cycle time on each automated workflow
Exception rateThe percentage of runs that required human intervention; a declining rate over time indicates the agent is handling edge cases more effectively
Rework eliminationReduction in rework cycles — workflow runs that previously required re-execution due to errors or incomplete outputs
Cost savingsFinancial impact calculated from hours saved multiplied by your organization’s configured loaded labor rate
Your implementation team can help you configure labor rate assumptions in your account settings so that financial savings estimates reflect your actual cost structure. Accurate labor rates are the single most important input for producing financial ROI figures that hold up to scrutiny in budget reviews and board presentations.

​
Next steps

Explore the Assistant

Learn everything the Assistant can do — from ad hoc ROI queries to scheduled reporting and cross-initiative analysis.

Back to the Beginning

Return to the Fluency introduction to revisit the full platform overview or share it with a new team member getting started.