AI FinOps, Model Routing & Outcome Attribution

Why 'cost per token' is the wrong unit

The public FinOps signal in 2026 is unusually strong. r/CIO threads in April and June 2026 asked how to budget for AI subscriptions in 2027, how to track usage across departments, and how to route lower-priority work to cheaper models. The unit of the conversation has moved.

'Cost per token' is a vendor metric. 'Cost per successful workflow' is a management metric. The instrumentation that gets you from the first to the second is the FinOps program.

The four components

An AI FinOps program has four components, all required:

• Cross-provider log normalization — one event stream across Copilot, Anthropic, OpenAI, Bedrock, and self-hosted, with user, team, workflow, task type, model, tokens, latency, and outcome fields.
• Quality floors — per-workflow accuracy, latency, and containment thresholds defined with the process owner.
• Routing — rules or lightweight learned routers move calls to the cheapest model that meets the floor. Shadow mode validates before active mode switches.
• Outcome attribution — every routed call ties to a downstream business signal so 'what did we get for it?' is a query, not a debate.

Budget by workflow, not by seat

Seat-based AI budgeting is a procurement artifact of the copilot era. It does not tell finance whether the money produced anything. Workflow-based budgeting attaches caps + alerts + overrides to named workflows — finance close assistant, support triage, engineering PR review — and reports cost per successful completion against them.

The migration from one to the other is not a spreadsheet exercise; it requires the routing proxy and the outcome-attribution table to be in place first.

Shadow-first, active-second

Every routing change begins in observe-only mode. The proxy logs what it would have routed to, without actually changing production behavior, long enough to validate that quality floors hold. Only then does traffic switch.

This is the practice that separates FinOps engagements that deliver cost reduction from FinOps engagements that quietly degrade quality.

6–10 week implementation sequence

• Weeks 1–3: cross-provider log normalization + workflow-to-call mapping.
• Weeks 4–5: quality floors + shadow-routing configuration.
• Weeks 6–7: active routing + budget caps + alerts.
• Weeks 8–10: outcome-attribution dashboard + handoff.

Failure modes to avoid

• Fragmented logging — normalize first; workflows without traceable outcomes are surfaced for redesign, not routed blindly.
• Poor quality labels — set floors per workflow with the process owner.
• Black-box downgrades — teams can see routing reasons and escalate to frontier when quality demands.
• Proxy latency — run in-region, warm-cached, with a fallback direct-call path when the quality floor requires it.