Finance · All retail
Compute Spend Governance
AI spend climbing by team. Caps per department, routes to the cheapest model.
Trigger condition
A department passes 80% of its monthly compute budget before 80% of the month has elapsed.
Write-back
Routing policy updated in the Ward layer for the named workloads; budget alert and cap recorded against the department.
Every write is gated on an approver role you name. Nothing runs unattended.
Procedure
- Attribute spend to department, user and query pattern, so the conversation is about workloads rather than a single total.
- Identify the queries paying for a premium model without needing one, which is where most of the overage sits.
- Model the routing change: which workloads move tier, and what it does to answer quality on the eval set.
- Alert the department owner at 80% with the options: reroute, raise the cap, or stop. Never silently degrade quality.
- Close when the department lands inside budget with eval scores held.
Outcome metric
Cost per query for the department over 30 days with answer quality held on the eval set. Both, or the change is reverted.
The case closes on this number, not on the action being taken. A playbook without a close condition is a dashboard.
The rest of Finance
Vendor Invoice Dispute
Invoice ≠ receipt or contract price. Drafts the dispute packet for AP.
COGS recovery
Margin Leakage Audit
Margin bleeding across categories. Ranks the recoverable dollars.
Gross margin
Markdown Stop-Loss
Markdowns past the point of recovery. Proposes the floor.
Margin
Freight & Accessorial Audit
Freight and accessorials off-contract. Flags the recoverable spend.
COGS recovery
Run Compute Spend Governance on your data.
Pick three playbooks from the catalog. We wire them against your system of record for the pilot.
御社のデータに何が隠れているか、確認する。
お客様のオペレーションについてお聞かせください。デモまたはPoCをご提案します。