← Consumption & Cost · free tool, nothing leaves your browser
Scope AI Tasks
Plan a Cowork run, cost it against your own measured consumption, and export a named request someone can actually approve. Built for the conversation that happens before the run, not the invoice that arrives after it.
The request
What it does
The multiplier people forget. A weekday job is 260 runs a year.
A per-person automation multiplies by seat. This is where a cheap plan becomes the biggest line on the bill.
Calibration — your numbers, not ours
Run it once, read the actual consumption for that run, put it here. Leave blank and the cost stays honestly unknown.
From your own agreement. Optional — the credit total works without it.
Per run, doing it by hand. Be honest — an inflated number is the first thing an approver will challenge.
Only if your organisation publishes one. Otherwise leave it and report hours, which is harder to argue with anyway.
What is driving the cost
On the numbers. The per-run credit figure is yours — measured in your own tenant, not a published rate, because no public factor-to-credit mapping exists. Everything after it is arithmetic you can check: runs per year, credits per year, hours saved. That annualisation is the point. Nobody mis-estimates one run; they mis-estimate 260 runs times 100 people. Uncalibrated, this page says the cost is unknown rather than filling the gap with a guess. Cost-shape rubric adapted from the Cowork Cookbook D365 Recipe Planner (CC-BY-4.0).