Make the Economics Work
How to estimate the full cost of an AI workflow, choose a pricing unit and assess a product's commercial position.

On this page
A document-processing product can extract information in seconds, but the bill includes more than the model call. Some documents need retries; others need a person to resolve an ambiguous field. Someone also has to maintain the integration and support customers when it fails.
Estimate those costs alongside the value customers receive. As the product is used, replace the assumptions with observed review effort, failures and operating costs.
Price the whole task

For a defined period, estimate the cost of model input and output, retrieval, tools, infrastructure, retries, checks, human review, escalation, support and failure recovery. Include the operating work needed to maintain context, evaluation and integrations. Some costs may be shared across tasks; state how they are allocated.
A useful measure is:
Cost per accepted outcome = total attributable workflow cost ÷ number of outcomes accepted as useful or correct.
Define the denominator carefully. An extracted field is not necessarily an accepted result. If there are no accepted outcomes, the measure is undefined; inspect the failure and total cost rather than reporting zero.
Suppose a hypothetical pilot costs $120 across 100 attempts and produces 60 accepted outcomes. Its illustrative cost is $2 per accepted outcome. That estimate depends on what the $120 includes and on the quality of the acceptance check. It is not a forecast for another product.
Compare the result with the existing workflow, including the value of time, quality and customer impact. Test a range of task volumes, failure rates, review times and usage patterns. Current provider prices and caching rules are inputs to the estimate; verify them when making the decision.
Check data and operating feasibility
Identify the information the system needs, its source and the permission to use it for the intended purpose. Consider representativeness, freshness, sensitive data, retention and access. A system that works on a convenient sample may fail on the tasks or user groups encountered in production.
Involve privacy, legal, security and domain specialists where the data or consequence requires it. The governance chapter covers the operating questions. A useful product also needs an owner for context, review, incidents and changes after release.
Choose the unit customers understand
| Approach | Potential fit | Question to test |
|---|---|---|
| Subscription or seat | Ongoing access and predictable usage | Does the price remain fair if usage or the customer's workflow changes? |
| Usage | A measurable unit of consumption | Can customers anticipate and control their bill? |
| Outcome | A result both parties can define and verify | Who determines success, and who bears the cost of failed attempts? |
| Hybrid | A combination of access and variable work | Can customers understand the price and forecast the total? |
Automation may change the number of people using a product, the volume of work or the value of each task. Model these scenarios rather than assuming that every efficiency gain removes a seat or that outcome pricing automatically improves margin. Include incentives for sales, implementation and support in the design.
Examine what can make the product durable
A capable model alone is rarely the whole customer proposition. Consider how the product reaches the right users, fits their workflow, earns trust and improves from permitted evidence. Integrations, domain knowledge, service and relationships can be valuable, but each has costs and obligations.
A learning loop exists only when the team has permission to use feedback, can distinguish useful signals from noise and uses the evidence to improve the product. More usage or a larger data set is not automatically a competitive advantage.
Ask what a customer would lose if the product disappeared, what another solution could reasonably reproduce and whether the difference benefits the customer rather than merely making exit difficult. The go-to-market chapter covers the route from discovery to continued use.
Choose complexity when it earns its cost
A managed model, self-hosted model or combination may each fit a different task. Compare them on representative quality, latency, privacy, reliability and total operating effort. Routing between models or adding a reviewing agent can improve some workflows, but it also adds development, context, evaluation and incident costs.
Start with the simplest approach that meets the requirements. Add routing or additional review when evidence shows the improvement exceeds its cost. The harness chapter explains the technical choices.
v3.1 · Updated Oct 2026