All videos
The platform · 1:31
Measure what a workflow is worth
Runs, success rate and cost in Analytics and Overview, and the value model behind ROI.
Transcript
0:00Measure what a workflow is worth
Support replies drafts an answer to each customer message. Its Analytics tab shows what that work is worth. Runs counts production runs of the live version in the period. Test runs and drafts are left out. Success rate is the share that succeeded. One message had no order number, so its run failed. Running cost is what OAIZ billed for the AI, tools and compute, including failed and test runs. Configure value sets the value model, Sam’s estimate of what one run is worth. Direct monetary value is a fixed amount per run. Time saved fits Sam’s replies better. Each reply replaces six minutes of manual work, at an hourly labour cost of 45 euros. Apply from sets when the estimate starts. Only successful production runs from then on earn value. Save it. Time saved, Net value and ROI now appear for this workflow. ROI is net value as a percentage of running cost. Net value is labour value minus that cost. How value is calculated shows the qualifying runs and the formula behind the estimate. Activity, Overview adds up every workflow: runs, success rate, running cost and estimated value. The Workflows table lists each one. Support replies now has a value model, and View opens its Analytics.
