Unit of Work: The AI Productivity Metric That Actually Maps to ROI

Unit of Work is an AI productivity metric that measures the value of a completed task divided by the token cost required to produce it. Unlike raw consumption metrics — tokens used, API calls made, hours estimated saved — Unit of Work ties AI spend directly to delivered business outcomes. For any SMB owner who approved an AI budget this quarter and is now being asked whether it was worth it, Zach Johnson at Argentix argues that Unit of Work is the only metric that produces an honest answer.

Expressed formally:

$U_w = \frac{T}{t_{ic} + t_{oc}}$

Where:

• $U_w$ — Unit of Work, the productivity ratio you are trying to maximize.
• $T$ — the completed task: one unit of business value delivered, defined by you (one qualified lead, one resolved ticket, one drafted proposal).
• $t_{ic}$ — token input cost: everything you sent the model (prompt, context, retrieved documents, conversation history).
• $t_{oc}$ — token output cost: everything the model generated to deliver the result.

A higher $U_w$ means more business value per token spent; a lower one means tokens are being burned without proportional return.

The hardest part is being honest about what $T$ actually is. $T$ is not "an answer from the model" or "a generated paragraph." $T$ is a unit of completed work that someone in your business would otherwise have done. One qualified sales lead. One support ticket resolved without escalation. One first-draft proposal that a human only needed to edit, not rewrite. $T$ must be defined at the level of business outcome, not AI output — because a model can produce a thousand tokens of confident-sounding text that delivers zero $T$.

Most "AI productivity" metrics fail in the same way: they measure inputs (tokens consumed, prompts written, agents deployed) or vanity outputs (responses generated, hours estimated saved). These are easy to grow and impossible to falsify, which is exactly why they appear in vendor decks. Unit of Work is harder to game because both sides of the ratio are real: $T$ has to actually exist (a real ticket closed, a real lead qualified), and the denominator comes straight from your provider's billing API. If $U_w$ trends down month over month, your AI is getting more expensive without getting more productive, and no slide deck can hide that.

Unit of Work composes naturally across multi-step agent workflows. If a workflow has five steps, the total $t_{ic} + t_{oc}$ is the sum of every step's input and output cost. $T$ is still one completed unit of business value at the end. This means you can measure $U_w$ for an entire automation pipeline and compare it against a single-shot prompt or a human-only baseline, side by side, in the same units.

Most SMBs are flying blind on AI ROI because the metrics they have access to are either too coarse (subscription cost versus revenue) or too granular to mean anything (tokens per call). Unit of Work sits exactly where decisions get made, and it changes three specific conversations you are probably having this quarter.

Vendor evaluation. Two AI tools both cost $200 per month and both "automate customer email triage." On paper they look interchangeable. Measure $U_w$ across a week of real tickets and one of them will produce three times the resolved tickets per token spent. That is not a pricing question — both tools cost the same — it is a productivity question. Without Unit of Work, you would never see the gap. With it, the vendor decision becomes obvious in the first sprint.

Workflow optimization. If you are running agentic workflows — chains of model calls where the output of one step feeds the next — Unit of Work tells you which step is dragging the ratio down. Maybe the retrieval step is pulling 8,000 tokens of context for a question that needed 800. Maybe a verification step is calling Opus when a Haiku call would suffice. You cannot find these inefficiencies by looking at the workflow as a whole; you find them by measuring $U_w$ at every step and chasing the worst offender.

Leadership reporting. Boards and owners do not want to hear about tokens. They want to hear "for every dollar we spent on AI this quarter, we resolved 14 customer tickets, qualified 6 leads, or drafted 3 proposals." Unit of Work, multiplied by your provider's billing, gets you there. It is the only AI metric that maps cleanly to the language leadership already speaks: cost per outcome. Once you can report cost per outcome with a straight face, the AI conversation stops being theological and starts being operational.

The reason this matters this quarter — not next year — is that AI spend is accelerating faster than AI measurement. Most teams are buying tools, deploying agents, and approving expansions without a single unified metric tying spend to delivered work. Six months from now, the businesses that can answer "what is your $U_w$?" will be the ones still running their AI programs. The ones that cannot will be the ones explaining to their board why they paused them.