AI tool costs

Weave tracks what your team spends on AI coding tools such as Claude Code, Cursor, GitHub Copilot, and Codex, by tool and, where the tool’s data allows, by engineer and team, and divides that spend by the code output attributed to AI to give a cost per output. Each cost comes from the provider’s billing data, token counts priced at list rates, or seat costs you enter, and is labeled with how it was measured. Your organization’s AI tool costs and cost per output can be benchmarked against organizations of a similar size or in your industry. For most tools, cost is pulled automatically once you connect the integration, so there’s nothing to enter by hand. You only enter cost manually in three cases: for seat-based tools that report no usage data, to set the per-unit rate on usage-priced tools (where Weave already pulls the usage volume for you), and to record a flat-rate seat plan such as Claude Code Max, with an optional included allowance.

​

How cost is collected

Cost comes from one of three sources, depending on the tool. It matters which one a tool uses, because it determines whether the dollar figure is your actual invoice or an approximation: For some tools the dollar amount is a hybrid: real usage volume (e.g. ACUs or credits) multiplied by a rate you configure in Weave.

​

Cost by tool

Tools with per-user cost attribute spend to individual engineers and teams. Modal reports only workspace-level billing, so its spend stays organization-wide and is not allocated to active users. Flat subscriptions use their configured member assignment or activity-based allocation.

​

Entering subscription details

For seat-based tools, and to set the rate for hybrid tools like Codex and Windsurf, go to Settings → Financial → Tool subscription costs, pick the plan for that tool, and enter the number of seats and cost per user (or per-credit / per-ACU rate). Devin has no plan of its own: Weave prices Devin ACUs at the rate on the Windsurf Windsurf Usage-Based (ACU) plan, because Cognition bills Windsurf and Devin from one ACU pool. For tools where Weave has per-user activity (Amazon Q, Claude Code, Cursor, Firebender, Kiro, Sourcegraph, Windsurf), the cost is allocated automatically to the engineers active in that tool. For other tools, assign members to the subscription and the cost is split across them. For tools with an actual billing source, connect the provider’s admin or analytics API key on that tool’s Data page (see the tool’s integration doc for setup) — Weave then reads real billed cost and you don’t need to enter subscription details.

​

Included allowance for flat-rate tools

A flat-rate tool is a fixed monthly seat plan (for example Claude Code Max, or a Cursor Teams seat) where the fee doesn’t change with usage. For these, the value of what someone runs through the tool can far exceed the flat fee — so how Weave reports the tool’s cost depends on one optional setting. When you enter a per-seat plan under Settings → Financial, you can set an Included usage allowance, the list-price value of usage each seat is expected to cover per month:

• Leave it blank and the tool’s cost is shown as its full list-price consumption: an estimate of the value used. It doesn’t account for the plan’s usage limits, so it can exceed the flat fee you actually pay. This is the safe default when you don’t know how much usage the seat covers. Two exceptions keep the seat cost: tools with no usage cost data, such as AI code review tools, and Claude Code when the Claude Code plugin measured which requests your plan covered in the selected period (shown as seat cost plus overage).
• Set an allowance and the tool’s cost is shown as seat cost plus overage: the flat seat fee, plus only the list-price usage above the pooled allowance (allowance × seats). This is closer to what you’re billed when a plan charges for usage beyond its limits.

Either way, the per-person drill-down still shows each person’s full list-price consumption with its fidelity label — the allowance only affects the tool-level “what you pay” figure on the AI ROI report.

​

Estimated vs actual

When a tool’s cost is estimated, the figure uses published list prices and ignores any enterprise discount, committed-use pricing, or free credits you may have. Treat estimated costs as directional. For exact spend, connect the provider’s billing/analytics API where one is available (Claude Code, Claude.ai, Cursor, GitHub Copilot, Modal, and OpenRouter today).

​

Cost fidelity

Every cost row in the Cost per person drill-down carries a Fidelity label so you can tell exactly how trustworthy each dollar figure is, from vendor-confirmed spend to a list-price approximation:

​

What “Total cost” shows

The per-person drill-down footer shows a single Total cost — the sum of the usage rows above it. Each row is priced at the best available tier (actual where Weave has it, otherwise the estimated/list-price figures above), so Total cost is the value of what was used, which for flat-rate plans is not the same as what lands on your invoice: a heavy Claude Code user on a flat Max seat can show thousands of dollars of list-price Total cost even though the seat is a fixed monthly fee. The Fidelity column tells you, row by row, how much of that total is vendor-confirmed versus estimated. Contracted seat subscriptions (entered under Settings → Financial) also appear in this drill-down as separate Base cost rows, grouped under a Contracted seats subtotal in the footer. That subtotal is day-prorated to the selected date range and is not folded into Total cost, because seat cost and list-price consumption are different scopes. Seat rows are omitted when you filter the drill-down by model.

​

Evaluating ROI

Cross-reference with AI output percentage and code output to assess whether the investment is translating to productivity gains. The AI ROI report combines cost and output into a single view.

​

Common questions

​

How do I see AI cost per unit of output?

Open the AI report overview: Cost per output over time divides total AI tool cost, including prorated seat subscriptions, by AI code output for all tools and for each tool, and Cost per output by tool compares tools over the selected period. Lower is better, and review-only tools such as CodeRabbit and Greptile are left out so they don’t skew the ratio.

​

Can I match token spend to developer output?

Yes. On the AI report overview, AI output & spend plots AI-attributed code output against usage-based token spend for each period, and the Cost per person table lists each engineer’s usage cost next to their cost per output. The AI report’s Models page adds a Model comparison table with total tokens, average cost, and average AI code output per session for each model.

​

Is the cost Weave shows the same as my invoice?

It depends on the fidelity label. Actual rows are vendor-billed amounts or seat costs you entered, while rows priced from token counts at published list rates ignore discounts and credits. On flat-rate plans, the list-price value of usage can exceed the flat fee you pay (see included allowance).

​

Does token spend include seat costs?

No. Token spend and the usage cost in Cost per person cover usage-based charges only. Cost by fidelity on the AI ROI report is the only view with the full total, including seat costs.

​

Can I compare our AI spend with similar companies?

Yes, at the organization level. Benchmarks rank your AI tool costs, AI cost per AI output, and output per AI dollar against other organizations that use Weave with a similar number of engineers, or in your industry if an admin selects that comparison.