---
title: Total Cost of Workflow Ownership (TCWO) — Step 3 of the Cromus 4-Step Framework
description: TCWO is Cromus's adaptation of TCO for AI workflows — the true per-outcome cost over time, accounting for API spend, human review, optimization gains, and model deprecation. Step 3 of the measurement framework.
canonical: https://cromus.ai/total-cost-of-workflow-ownership
source_html: https://cromus.ai/total-cost-of-workflow-ownership
---

# Total Cost of Workflow Ownership (TCWO)

> **Step 3 of the 4-step AI workflow measurement framework.**

TCWO is Cromus's adaptation of Total Cost of Ownership (TCO) for AI workflows. It measures the **true per-outcome cost** of a workflow over its operational lifetime — not just the API invoice for a single run.

---

## What TCWO measures

TCWO extends Baseline Cost per Workflow (Step 1) across time and scale:

| Component | What it captures |
|-----------|----------------|
| **Cumulative API spend** | Per-run cost × run volume over the measurement period |
| **Optimization gains** | Savings from Croms™ reduction (model downgrades, parallelisation, deduplication) |
| **Model deprecation risk** | Expected cost of migration when a model is deprecated (registry tracks deprecation dates) |
| **Maintenance overhead** | Time spent updating prompts, fallback policies, and SKILL.md files |
| **Human review at scale** | Fully-loaded human cost that scales with run volume |
| **Error correction at scale** | Expected failure cost scaled by volume and failure rate |

---

## TCWO vs. per-run cost

Per-run cost (Baseline) tells you what a single execution costs today. TCWO tells you what a workflow *programme* costs over a quarter or year — including the hidden costs most teams never account for.

| Metric | What it answers |
|--------|----------------|
| Baseline Cost per Workflow | "What does one run cost?" |
| Croms™ | "How much of that is preventable?" |
| **TCWO** | "What does this workflow cost to *own* at scale?" |

---

## How Cromus computes TCWO

From a compiled SKILL.md and Croms™ analysis:

1. Project per-run cost × declared run volume
2. Apply optimization recommendations to compute the TCWO after optimization (TCWO-post)
3. Add model deprecation risk (weighted by deprecation probability from registry metadata)
4. Surface TCWO-pre vs. TCWO-post comparison with the dollar value of applying each optimization

The output is a deterministic projection — no LLM calls, same input always produces the same TCWO.

---

## Why TCWO changes optimization decisions

Some optimizations look small per run but are large in TCWO terms. Parallelising two steps saves $0.003/run — $10.95/month at 100 runs/day — but $131.40/year. At 1,000 runs/day, that is $1,314/year from a single structural change.

TCWO makes these dynamics visible before any code is changed.

---

## Part of the 4-step framework

| Step | Name | What it produces |
|------|------|-----------------|
| **0** | Workflow Classification | Tier map of AI touchpoints |
| **1** | Baseline Cost per Workflow | Fully-loaded per-run cost |
| **2** | Croms Analysis | Preventable waste score |
| **3** | **Total Cost of Workflow Ownership (TCWO)** | True per-outcome cost over time |

---

## Related pages

- [Workflow Classification →](/workflow-classification)
- [Baseline Cost per Workflow →](/baseline-cost-per-workflow)
- [Croms™ — preventable AI workflow waste →](/croms)
- [Interactive Demo →](/demo)