Via (transformation planning)

Via: plan your agentic workforce transformation

Via is transformation planning software that plans, prices and tracks the move of work to AI agents. Via models human and AI-agent roles per task, so you decide with a business case.

Illustrative data

How Via plans, prices and tracks the move of work from people to AI agents.

What the animation shows, step by step
  1. Your team documents a process and its tasks in Via: who does each task today, how long it takes and how often it happens.
  2. Via ranks the tasks by current cost and by manual hours. Your team decides which tasks should move.
  3. For each task, your team sets the future performer: a human role or an AI-agent role, each with an hourly cost. Via recalculates hours and cost for the future state and shows the share of future hours planned for AI-agent roles.
  4. The business case sets investment against savings quarter by quarter, with cumulative cash flow, return on investment and the payback point.
  5. Your team turns pain points into change requests with implementation and rollback plans. Change requests are grouped into initiatives, which move across a delivery board.
  6. Each month, your team enters the actual savings, and Via compares them with the forecast.

Via plans and tracks the change. Via does not build or run AI agents, and it receives no data automatically from Opus (task mining) or Favus (process mining). Figures in the animation are illustrative.

What is agentic workforce transformation?

Agentic workforce transformation is the planned move of specific tasks from people to AI agents, based on evidence of how the work is done today. The move needs a business case first and tracked results after.

An agentic workforce is one in which AI agents carry out defined tasks alongside people, while people set goals and oversee the work. An AI agent is software that uses AI to complete multi-step tasks with limited supervision.

Without a costed picture of today's work, a plan to hand tasks to AI agents is hard to approve and harder to track. Via plans, prices and tracks the move: current and future performers per task, a business case, and forecast against realized savings.

Model today's and tomorrow's way of working

Via records the current and the future way of working for every task, side by side. Each task has a performer, a human role or an AI-agent role with an hourly cost, plus its time, automation share and FTE.

Your team documents your processes, at up to three levels, and the tasks within them: time, volume, frequency, applications used and business rules. Enter them in forms or an editable grid, or import a whole program from a JSON file.

Via's process and task graphs show how the work flows. Switch a task graph between current and future state to see which tasks the plan gives to AI-agent roles. Your team draws and documents these graphs; this is process modeling, not mining from system logs.

One task in Via, today and in the plan: entering supplier invoices in the ERP system (illustrative values)
Recorded per taskCurrent stateFuture state (plan)
PerformerAP clerk (human role)Invoice-entry agent (AI-agent role)
Time per invoice10 minutes2 minutes
Manual vs automated shareRecorded for todayPlanned for the future state
FTE (full-time equivalents)1.20.2
Annual hours at 12,000 invoices a year2,000400
Annual cost2,000 hours × the AP clerk role's hourly cost400 hours × the agent role's hourly cost

Illustrative values Your team enters the times, volumes and hourly costs in Via. Via calculates the annual hours and cost from them.

See human vs AI-agent hours and cost

Via calculates annual hours, cost and savings for every task and process, both today and in the plan. Via also shows AI hour adoption: the share of future hours planned for AI-agent roles.

Filter the figures by process level, initiative, role or the automation-potential rating your team gives each task, and export them to Excel.

  • AI hour adoption

    The share of future-state hours that the plan gives to AI-agent roles. So you can see how far the plan moves work to AI agents.

  • Human vs AI-agent hours

    Hours worked by human roles and by AI-agent roles, today and in the future state. So you can see how the mix of work changes.

  • Cost by role

    Annual cost for each human and AI-agent role, before and after the change. So finance partners can see where the savings come from.

  • Where to look first

    Your five costliest tasks and processes, and the tasks with the most manual hours today. Via ranks them; your team decides which work moves.

Test options before committing

Via lets you test options before you commit to a plan. Move work from one role to another, automate tasks by a percentage or remove them, and compare the hours and cost with your baseline.

Scenarios are for exploring and are not saved. When your team settles on an option, it sets that option as the future way of working for each task.

  • Switch work between roles

    Move the work of one role to another, for example from a human role to an AI-agent role. Apply it to all processes, to selected processes or to selected tasks.

  • Automate or remove tasks

    Cut the time of selected tasks by a percentage, or take tasks out of the process altogether.

  • Change volume and rework

    Adjust workload and rework to see how sensitive the cost is to each.

  • Compare with the baseline

    See baseline and scenario hours and cost side by side, by process and by role.

Build the business case and prioritize

Via takes your team from a pain point to a costed, prioritized business case. The business case shows investment and savings by quarter, with ROI, payback period and cumulative cash flow.

Via also lists the pain points that have no change request yet, so you can see which problems are still unaddressed.

  1. Log the pain point

    Record a problem against a task or process, with its severity. Via shows the current and future cost of each pain point, and the savings.

  2. Raise a change request

    Describe the fix, with its type, automation type, implementation plan and rollback plan. Add one-time or recurring costs and the savings it should bring.

  3. Group it into an initiative

    Group change requests into initiatives, each with an owner, effort, complexity, dates, estimated cost and business benefits.

  4. Compare value against effort

    Plot initiatives by net cumulative savings against low, medium or high effort. Your team sets the order; no algorithm scores the initiatives.

  5. Read the business case

    See investment and savings for each quarter of the program, with net and cumulative cash flow, ROI, payback period and gross margin.

Deliver and track the value

Via plans delivery on Kanban boards, a Gantt timeline and a change calendar, then compares forecast savings with the actual savings your team records. Each change request has fields for an implementation plan and a rollback plan.

  • Kanban boards

    Move initiatives and change requests across columns you configure.

  • Gantt timeline

    Plan initiatives over time, with their change requests shown when you want them.

  • Change calendar

    See every scheduled change in one calendar.

  • Change-request workflow

    Move each change request from Backlog through submission and review to Approved or Rejected, then to Scheduled, Implemented and Closed.

  • Value realization

    Each month, enter the actual savings and budget spent for each initiative, plus another KPI if you track one. Via shows forecast against realized savings and the variance, month by month and cumulatively.

How actuals get into Via Your team enters actual savings each month; Via compares them with the forecast.

Via Program Roadmap in month view with five initiatives, each with a start date and duration, and three of their bars on a timeline from August 2025
Program roadmap, month viewDemo data

Via, Opus and Favus together

Via is where your team turns what Opus and Favus show into a costed plan for moving work to AI agents. Opus, Favus and Via are the three products of Optimus Hive, on one platform.

AI-agent designs are drafted in Agent Studio in Opus, for your team to review. Agent Studio needs an AI provider set up for your workspace, and its AI drafts are not part of the free trial. In Via, your team then sets up the matching AI-agent role, its hourly cost and the tasks it will take on.

How findings reach Via Nothing flows into Via automatically: your team brings the findings across.

Earlier in the method

Opus: see how the work is done

Opus is task mining software that records how people work on Windows desktops, so you know what each task involves and costs. Your team can use those task times and costs when it sets up the baseline in Via.

Earlier in the method

Favus: see how the process runs

Favus is process mining software that turns event logs from your business systems into process maps, so you see how end-to-end processes really run. Your team can log what it finds as pain points in Via.

How Opus, Favus and Via fit together

Via FAQ

Transformation leaders and finance partners ask what Via does, what it does not do, and how it supports decisions about moving work to AI agents.

Does Via build or deploy AI agents?

No: Via plans, prices and tracks the move of work to AI agents, but it does not build, deploy or run them. In Via, an AI agent is a role with an hourly cost that your team assigns to tasks in the future-state plan. AI-agent designs are drafted in Agent Studio in Opus, for your team to review. Agent Studio needs an AI provider set up for your workspace, and its AI drafts are not part of the free trial.

How does Via help us decide which tasks move to AI agents first?

Via lists the candidates by cost, and your team makes the decision. The list shows your five costliest tasks and processes, and the pain points that have no change request yet. The value-against-effort chart compares initiatives by net savings and effort, and a simulation shows what each option would cost before you commit.

What does the business case in Via contain?

Via's business case sets investment against savings for each quarter of the program, with net and cumulative cash flow, ROI, payback period and gross margin. Each change request carries its own one-time or recurring costs and its expected savings. Each initiative shows its value forecast and the change requests behind it.

Can we redesign a process in Via before AI agents take on its tasks?

Yes: in Via, every task has a current and a future way of working. Your team can redesign the process in the future state before assigning any task to an AI-agent role. You can set each task's future performer, time and automation share, and edit the task flow in Via's graphs. A simulation shows the cost of removing tasks or switching roles before you commit.

How does Via track whether the planned savings are achieved?

Via compares forecast savings with realized savings for each initiative, month by month and cumulatively, and shows the variance. The actual figures come from your team, which enters the savings achieved and the budget spent each month. Via does not measure savings automatically, so agree early where the actual figures will come from.

Does Via give us a framework for an agentic transformation program?

Yes: Via structures the work as a program that goes from baseline to tracked value. A program holds your processes and tasks with their current and future way of working, then pain points, change requests and initiatives. Initiatives are prioritized and planned on Kanban boards, a Gantt timeline and a change calendar, and value realization tracks forecast against actual savings.

Plan the move to AI agents on a costed business case

Request a demo and tell us which work you want to move to AI agents. We'll show you how Via models it, prices it and tracks the savings.