Founders
How to model inference costs for AI document processing before launch
AI document processing: 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 extracts invoice data for an accounts payable team. Staff review exceptions before information enters the accounting system. Supplier formats and duplicate documents make the input stream uneven.
A misplaced decimal or duplicate record can matter more than an average extraction score. Define the fields and events that require review before comparing workflows.
A monthly cost bridge with visible assumptions
For this exercise, assume 1800 completed units in a month, 5 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. A misplaced decimal or duplicate record can matter more than an average extraction score. Define the fields and events that require review before comparing workflows.
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 | 1800 |
| Assumed revenue for this month | $2,100.00 |
| Variable service cost | 1800 × $0.06 = $108.00 |
| Listed fixed delivery cost | $380.00 |
| Human work at an assumed $30/hour | $4,500.00 |
| Remainder after these listed costs | -$2,888.00 |
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
- Which fields require exact agreement?
- How are duplicate invoices handled?
- Who signs off on reconciliation?
Use permissioned documents, field-level corrections, duplicate flags, and reconciliation results. Keep document type and supplier format visible instead of relying on one blended score.
A concrete next test
Select permissioned invoices from different supplier formats and include a duplicate. Trace each field through correction and export to reconciliation. Ask the accounts payable owner which error would block use even if most fields were extracted correctly.
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 correct, reconciled records with the current process. Include document intake, exception review, and corrections after export in the time and cost model.
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.