How to use the worksheet
Enter values in the light fields. Use one currency and one time horizon throughout. Calculate each category with the formula shown, then move the result into the summary table. The worksheet neither saves nor sends any data.
1. Input assumptions
| Code | Assumption | User value | How to use it |
|---|---|---|---|
| Horizon and volume | |||
| A1 | Number of months analysed | Use the same period for every recurring cost. | |
| A2 | Cases / operations per month | Use realistic demand rather than theoretical maximum throughput. | |
| A3 | Model calls per case | Include retries and intermediate steps. | |
| Inference cost | |||
| B1 | Average cost of one model call | Use the same currency as every other line item. | |
| Retrieval and storage | |||
| C1 | Average retrieval cost per case | Search, embeddings and usage-dependent traffic. | |
| C2 | Storage and indexes per month | Databases, vectors, logs and copies needed for operation. | |
| Data preparation and refresh | |||
| D1 | Data preparation — one-off cost | ETL, cleaning, mapping, permissions and versioning. | |
| D2 | Data refresh per month | Changes to documents, sources, metadata and indexes. | |
| Evaluations and monitoring | |||
| E1 | Evaluation design — one-off cost | Golden set, metrics, acceptance criteria and edge cases. | |
| E2 | Cost of one full evaluation run | People, tooling, result analysis and decision-making. | |
| E3 | Planned releases / changes over the full A1 period | Enter the total over the full A1 period, not a monthly cadence. | |
| E4 | Monitoring and tooling per month | Logs, alerts, dashboards, observability and retention. | |
| Operational support | |||
| F1 | Support hours per month | Triage, user support, updates and operating decisions. | |
| F2 | Internal cost per hour | Use the full cost of work, not take-home pay. | |
| F3 | Monthly incident reserve | Analysis, rollback, communication and restart. | |
| Cost of errors and remediation | |||
| G1 | Expected errors per month | Base the assumption on a sample, pilot or historical data. | |
| G2 | Average cost of one error | Correction, customer service, delay and possible harm. | |
| G3 | Other remediation work per month | Items not represented by G1 × G2. | |
| H1 | Uncertainty buffer (%) | Apply it when scope or volume is not yet stable. | |
2. Manual formulas and summary
| Category | Formula | User result |
|---|---|---|
| Inference cost | A2 × A3 × B1 × A1 | |
| Retrieval and storage | (A2 × C1 + C2) × A1 | |
| Data | D1 + D2 × A1 | |
| Evaluations and monitoring | E1 + E2 × E3 + E4 × A1 | |
| Operational support | (F1 × F2 + F3) × A1 | |
| Errors and remediation | (G1 × G2 + G3) × A1 | |
| Subtotal before buffer | Sum of the six categories | |
| Uncertainty buffer | Subtotal × H1% | |
| TCO over period A1 | Subtotal + buffer |
TCO is an assumptions model, not a guaranteed forecast. Record the source of each number and update the model after a pilot and whenever volume, model, data or quality requirements change.
3. Audit scoping brief
This brief does not calculate a price. It shows why an audit of a short, stable process can require a different scope from a multi-stage process with exceptions, several systems and a high error cost. Complete it before discussing an offer.
Save the worksheet as PDF and describe the process. After qualification, we will prepare the scope, assumptions, schedule and price for that specific case.
Send the process scope
To save a PDF: Print → Save as PDF