AI Workflow Unit Economics: Cost per Ticket, Document, Agent Run, and Customer

Executive summary

Teams need to measure unit economics at the workflow level: ticket, document, agent run, customer, resolved case, or completed task.

Technical mechanism

• One business outcome can include many model calls.
• Retries, context, tools, vector lookups, and logs sit outside the headline token price.
• Cloud cost and model cost often scale together.

Business impact

A workflow can look cheap per request while becoming expensive per successful outcome. Finance needs the latter number to price, cap, or kill features.

Detection signals

• No cost per outcome metric.
• Usage growth but unclear margin impact.
• Different teams own product value and cloud/model spend.
• Pricing decisions made without workflow cost.

Recommended fixes

• Define the business outcome.
• Track all paid services per outcome.
• Assign owner and budget.
• Set target cost per successful outcome.
• Review keep / optimize / cap / reroute / reprice / kill monthly.

Olive-One teardown angle

Olive-One builds the spend-to-value map for one workflow and turns it into an executive decision table.