Founders
How to model inference costs for AI workflow automation before launch
AI workflow automation: Estimate inference cost from a defined workflow, not a headline price for a model.
Estimate inference cost from a defined workflow, not a headline price for a model. Count requests, input and output sizes, retries, tool calls, and the mix of configurations. Keep vendor prices dated and separate them from fictional exercise assumptions.
Start with the decision
Build a per-completed-task cost bridge. Add failure and retry scenarios, then compare the estimate with observed logs once available. Include related hosting and human delivery costs in a broader margin model rather than renaming inference cost as total cost.
The illustrative scenario
This is an educational workbook. The company or fund and all numerical inputs below are fictional. They are not ADIN results, customer claims, market benchmarks, or a forecast.
The fictional product routes purchase requests through a small operations team. A requester supplies context, a budget owner approves spending, and an administrator maintains the workflow. Exceptions are common enough to affect adoption.
Automating a step can move work to the exception queue rather than remove it. Keep proposed actions, approvals, and completed actions separate in the event history.
A monthly cost bridge with visible assumptions
For this exercise, assume 740 completed units in a month, 11 minutes of human work per unit, and a fictional labor rate of $30 per hour. The labor rate, service cost, and revenue are invented inputs. They are not current vendor prices, customer results, or a suggested commercial offer. Automating a step can move work to the exception queue rather than remove it. Keep proposed actions, approvals, and completed actions separate in the event history.
The bridge subtracts only the costs shown. The remainder is not an accounting gross margin or profit figure: other expenses, taxes, timing differences, and classifications are outside this simplified model. A negative result is useful information about the assumptions, rather than evidence that an entire product category cannot work.
Now change one input. If the workflow requires twice the review time, the human-work line doubles even when the provider's unit price stays constant. If volume rises, distinguish a genuinely fixed cost from a cost that will step up. Reconcile the model with observed delivery logs before using it to support a pricing or fundraising claim.
| Item | Illustration |
|---|---|
| Completed workflow units | 740 |
| Assumed revenue for this month | $2,400.00 |
| Variable service cost | 740 × $0.12 = $88.80 |
| Listed fixed delivery cost | $520.00 |
| Human work at an assumed $30/hour | $4,070.00 |
| Remainder after these listed costs | -$2,278.80 |
Use this worksheet
Answer the questions with a source, date, owner, and next action. Mark an unknown as unknown. Use public or permissioned information and involve a qualified specialist when a question requires expertise beyond the team’s competence.
- What is one completed task?
- How many calls does it require?
- What retries occur?
- Which prices are current?
- What costs are outside inference?
Questions specific to this scenario
- Who approves a purchase?
- Which exceptions stop the workflow?
- How are manual overrides recorded?
Inspect request histories, approval timestamps, exception reasons, manual overrides, and changes in process ownership. Include requests that stalled or were withdrawn.
A concrete next test
Follow one request that passes normally and one that needs an exception. Ask the requester, approver, and administrator what each can see and change. Record whether automation removes work or increases the burden on the person managing stalled requests.
Interpret the result
The model is a planning tool whose uncertain inputs should remain visible. A cheaper model can cost more per completed task if it increases retries or correction work, so compare the full workflow before switching.
Compare the full request-to-decision process with the current system. A faster initial classification can hide a slower approval or correction stage.
Sources and method
These primary resources provide background for the concepts. The fictional scenario, calculations, and worksheet are ADIN educational examples; the sources do not report or validate those invented results. Reviewed October 11, 2026.