Skip to main content
Once Work Explorer has mapped your workflows, Fluency’s Opportunities module analyzes that data and surfaces the processes most ready for AI or automation — ranked by impact, with the evidence you need to prioritize and justify every decision. Select Opportunities from the left sidebar. Fluency presents a ranked table of automation candidates derived directly from your discovered workflows. Each row represents a single opportunity, showing the workflow name, owning team, automation type, confidence score, estimated hours saved per month, and projected financial savings. The table is sorted by impact by default, with the highest-value opportunities at the top. Fluency generates and updates this list continuously — as new workflow data arrives, scores are recalculated and new candidates appear automatically.

Understanding the opportunity score

Each opportunity carries two key signals that tell you how strong a candidate it is: Confidence score — expressed as a percentage, this reflects how likely automation is to succeed based on the workflow’s structural characteristics and execution data. A high confidence score means the workflow is well-structured, executes consistently, and has clear automation potential. A lower score may indicate the workflow needs more run data, has high variability, or involves complex exception handling that warrants review before automating. Automation type — Fluency classifies each opportunity into one of five categories:
TypeDescription
AgenticEnd-to-end execution by an AI agent with judgment and decision-making at each step
WorkflowStructured sequence automation with defined rules and branching logic
ProcessPartial automation of a broader manual process
APIIntegration-based automation connecting systems via their APIs
RPARobotic process automation for UI-driven or legacy system interactions
The automation type informs both the implementation approach and the level of human oversight you’ll want to maintain at deployment.

Reading an opportunity detail view

Click any opportunity row to open its detail view. The detail view is organized into several sections:
  • Workflow map with proposed automation steps — the same map you see in Work Explorer, now annotated to show exactly which steps the agent will handle, which will remain human-led, and where handoffs between the agent and your team will occur.
  • Projected outcomes per step — for each automated step, Fluency shows the expected input, the action the agent will take, and the expected output. This gives you a precise picture of what the agent does — not just a high-level summary.
  • Cycle-level impact — how automation is projected to affect the total cycle time for a single workflow run, expressed as an absolute reduction (e.g., “reduces cycle time from 4.2 hours to 1.1 hours”).
  • Required systems — the tools and platforms the agent will need to interact with to execute this opportunity.
  • Hours saved per month — based on current run volume and projected cycle time reduction.
  • Financial savings estimate — calculated from hours saved and your organization’s configured labor rate assumptions.

Building your automation roadmap

1

Sort by Time Saved or Confidence Score

Use the column sort controls to find your quick wins. Sorting by Time Saved surfaces the highest-volume, highest-impact candidates first. Sorting by Confidence Score surfaces the opportunities most likely to succeed — a strong starting point if you’re deploying automation for the first time.
2

Filter by team or department

Use the team filter to align your roadmap with your current business priorities. If your organization is focused on Finance efficiency this quarter, filtering to Finance opportunities lets you build a focused, defensible roadmap for that team without losing visibility into the broader picture.
3

Review the top candidates in detail

Open the detail view for your top three to five candidates. Review the projected outcomes at each step, confirm the automation type matches your deployment capabilities, and check the required systems list against what your team has access to.
4

Use the Assistant to generate a roadmap narrative

Open the Assistant from the sidebar and ask it to synthesize your top opportunities into a structured roadmap. For example: “Show me the top 5 automation opportunities for the Finance team with ROI projections.” The Assistant returns a formatted output — including confidence scores, time saved, and financial impact — that you can use directly in a stakeholder presentation.
5

Share the roadmap for approval

Use the Share button to export the roadmap output or generate a shareable link. Stakeholders with Fluency access can view the live opportunities list; others receive a formatted document they can review offline.

Committing to an opportunity

When you’re ready to move forward with an opportunity, click Commit on its detail view. Committing converts the opportunity into an Initiative — Fluency’s deployment unit for AI agents. When you commit, Fluency automatically generates the agent configuration for that initiative based on the opportunity’s workflow map, projected steps, and system requirements. You don’t start from a blank configuration — you start from a pre-built plan grounded in your actual workflow data. The next step is to review that plan, run it in preview mode, and deploy.

Common questions

Opportunities are updated continuously as new workflow data arrives from Work Explorer. If run volume increases, scores are recalculated. If a workflow’s structure changes, the opportunity reflects that change. You don’t need to manually refresh or re-run an analysis — the opportunities list always reflects the current state of your workflows.
Yes. Use the Dismiss action on any opportunity to remove it from your active list. Dismissed opportunities are hidden by default but are never deleted — you can restore them at any time by toggling the “Show dismissed” filter. Dismissing an opportunity is useful when a workflow is intentionally kept manual for policy, compliance, or strategic reasons.
A confidence score above 85% indicates the workflow has strong structural patterns, executes consistently across runs, and has clear, well-defined inputs and outputs — all of which make it a strong automation candidate. Scores below 85% are still worth reviewing, but may benefit from additional data accumulation or some upfront process cleanup to reduce variability before you deploy an agent.

Next step

Deploy AI Agents into Your Workflows

Learn how to convert a committed opportunity into a deployed Fluency Initiative — from reviewing the agent’s plan to activating autonomous execution in your live workflows.