.01
Value is volume times the cost of a miss
A workflow is valuable when it runs often and when delay or error costs real money: late payments, lost discounts, unhappy customers, audit findings. How impressive the AI looks does not count. Drafting a job description is clever; clearing two thousand invoice exceptions a month is valuable.
Rule of thumbMultiply monthly volume by minutes per case, then ask what one mistake costs.
.02
Effort hides in systems and exceptions
The model is rarely the hard part. Effort comes from the number of systems the agent must read and write, the state of the data in them, and how many unwritten rules people apply to the odd cases. Count those before you estimate.
Rule of thumbEach extra system roughly adds an integration, an access review and a round of testing.
.03
Risk sets the checkpoint, not the go or no-go
Higher risk does not rule a workflow out. It changes where a person approves, what the agent may do alone and what the audit trail must show. Start low-risk to learn, then bring the same controls to higher-stakes work.
Rule of thumbAutomate up to about 80% of a task and keep people on decisions with financial, legal or customer risk.