Cost per completed workflow is meaningful only when “completed” means the intended business outcome. Dividing the bill by answered calls can make a cheap but ineffective receptionist look efficient.
Define the numerator and denominator together
Workflow unit cost divides attributable operating cost by correctly completed workflows for a defined cohort. Include the cost categories relevant to the deployment, such as telephone transport, speech services, model usage, infrastructure, and downstream messaging.
For a proposed dashboard, separate variable usage cost from fixed operating expense and staff review effort. Decide how failed calls, retries, transfers, and asynchronous work are attributed. Show the accounting window and any excluded categories beside the result.
A saved request, a confirmed appointment, and a resolved support issue are different workflow outcomes. Choose one definition per metric and retain counts for the other stages rather than combining unlike work into one denominator.
Calculate a fictional weekly example
Suppose an intake pilot incurs 120 currency units of attributable usage and completes 60 correctly populated, confirmed service requests. Usage cost per completed request is two units. If 100 calls were answered, reporting 1.2 units per answered call answers a different question.
Now add 30 units of staff review effort under the team’s stated accounting method. The broader operating cost becomes 2.5 units per completed request. These illustrative figures demonstrate scope, not current vendor pricing or measured project savings.
| Cost question | Required attribution |
|---|---|
| Which calls consumed usage? | Interaction and provider usage references |
| Which retries increased spend? | Parent operation and attempt counts |
| Which outcomes completed? | Authoritative records and quality checks |
| Which costs arrived late? | Invoice reconciliation and adjustment |
| Which work needed staff? | Reviewed effort under a defined method |
Compare similar cohorts. After-hours intake and staffed daytime transfers may have different call lengths and completion patterns, making a blended average hard to interpret.
Keep quality beside cost
A shorter conversation may reduce usage while omitting required details. A cheaper model may increase staff cleanup. Show unsupported promises, duplicate effects, and unresolved work alongside unit cost so optimisation does not remove necessary safeguards.
Exact per-call attribution may be limited by provider billing granularity or delayed invoices. Label estimates and reconcile them later. Do not imply financial precision that the available data cannot support.
This cost model is proposed. The HVAC operations case study demonstrates an intake workflow without claiming measured savings. Pair it with staff pilot scorecards.
Workflow cost FAQ
Should failed calls be excluded from cost?
No. Their attributable cost belongs in the numerator even when they produce no completed workflow.
Is cost per minute enough?
It describes usage efficiency, but does not establish the cost of a correct business outcome.
Can staff time be included?
Yes, if the estimation method and scope are explicit and kept comparable across periods.