Use a business denominator
Token, seat, request, and compute prices are useful engineering inputs. They do not reveal whether the service produces an accepted business result. Cost per successful outcome divides the complete allocated cost by cases that meet the agreed quality and business acceptance definition without avoidable rework.
Define success before calculating cost
| Workflow | Possible successful outcome |
|---|---|
| Knowledge resolution | Answer accepted as correct, authorized, current, sufficiently complete, and supported by usable citations. |
| Document processing | Record completed with required fields and no avoidable correction or exception. |
| Case triage | Case routed to the correct queue within the service target and without a critical misrouting. |
| Decision support | Recommendation improves the agreed business-weighted loss or service outcome and is usable by the decision owner. |
| Bounded action | Intended final state is verified, authorized, within budget, and free of unacceptable side effects. |
Include the costs that disappear from demos
- Discovery, process redesign, data preparation, integration, security, legal and control work.
- Licenses, model consumption, infrastructure, storage, networking, and vendor minimums.
- Human review, exception handling, correction, appeals, support, and training.
- Evaluation, regression tests, monitoring, incident response, change, and revalidation.
- Failure loss, duplicate work, delay, customer impact, rollback, transition, and decommissioning.
Run sensitivity scenarios
| Scenario | Question |
|---|---|
| Low adoption | Do fixed platform, integration, and support costs become stranded? |
| High volume | Do pricing tiers, rate limits, latency, queues, and human-review capacity remain viable? |
| Adverse quality | How do retries, review, escalations, complaints, and correction change unit cost? |
| Vendor or model change | What revalidation, migration, regression, and downtime cost is triggered? |
| Exit | What does parallel operation, data export, replacement, and decommissioning cost? |
Time saved is not automatically cash
Saved effort may become avoided hiring, lower external spend, more throughput, faster revenue, improved service, reduced risk, or simply unused capacity. The value case should name the capture mechanism, owner, timing, and any downstream constraint that prevents the benefit from reaching the operating or financial result.
Decision rule
Scale only when the cost per successful outcome is justified by the measured business value and risk reduction, and when the result remains acceptable under plausible downside scenarios. A cheaper unit of technology that produces more failure is not an economic win.
