Skip to main content

Understand your bill

Your AI bill doubled.Can you saywhy? We can.

Every month the invoice says your coding agents worked hard. It cannot say on what, for whom, or whether any of it was worth it.

Quesma turns Claude Code, Codex, and Cursor sessions into a clear view of what the agents did, what it cost, and what you got back.

CLAUDE CODE / SAVINGS REVIEWCHECKING COST…
checkout-service / session 4F2A
  1. Fix the flaky checkout retry without changing the API$0.000
  2. Read(payments/retry.ts)$3.72
  3. Bash(pnpm test checkout --filter retry)$8.40
  4. Read(tmp/checkout-ci.log)$22.10
  5. Read(tmp/checkout-ci.log) ↻ repeated context$34.76
  6. Edit(payments/retry.ts)$45.18
  7. Bash(pnpm test checkout --filter retry)$58.92
  8. 42 passed · checkout retry fixed$64.28
Illustrative session and savings estimate.

Behind the bill

When the bill doubles,this is where theanswer lives.

Quesma reads the sessions themselves and sorts thousands of them into one picture of the work: by team, by repository, by kind of work.

Illustrative AI coding usage bill showing token usage and amount due
  • Marketing started using Claude Code

    A team you didn’t expect found a use for the tools.

  • Heavy work with Fable 5

    The default model got smarter, and pricier.

  • Security fixes before the audit

    The work ran hot for three weeks because you asked it to.

The patterns

Fix the problems. Find good practices.

The patterns only appear when sessions are analyzed together.

Cost tools only find things to cut. Quesma also finds problems recurring across teams, and the skills, tools, and routines used in one part of the company but nowhere else.

A failure worth fixing once.

Three teams hit the same broken integration environment. 47 sessions worked around it one at a time, each burning time and tokens on the same dead end.

Integration environment did not start47 SESSIONS

docker compose up exited before tests began

checkout-apiPayments
18
billing-servicePayments
16
data-pipelinePlatform
13

A skill worth sharing.

Custom skill deploy-preview lived on one team for months. Quesma shows where it is used, and which teams have not met it yet.

deploy-previewWEEKLY USE · LAST 12 WEEKS
Platform
Payments
Web
Datahas not met it yet

Instructions agents misread.

One repository’s rules send every session down the same wrong turn. Rewriting one file fixes all the future ones.

web-app/CLAUDE.md · line 14
“Always run the full e2e suite before committing”
  • #4821 fix typo in tooltip → full e2e suite38 min
  • #4837 rename a variable → full e2e suite41 min
  • #4859 update README → full e2e suite44 min

31 sessions took the same wrong turn

Dependencies nobody decided on.

An MCP server spread session by session until half the company relied on it. Better to know.

mcp-server-postgres11 OF 20 TEAMS

first seen Feb 12 · no decision on record

DESIGN PARTNERS

Bring clarity to your AI coding budget.

Early access opens soon. The collector deploys in your environment, the record accumulates in your cloud, and early teams get every analysis first. Contact us to get in early.