Skip to content
AI Spend Insights

Know exactly where your AI budget is going

Total AI spend
£0
4,218 sessions this month
CapEx projects
£0
66.3%
OpEx projects
£0
27.1%
Unattributed
£0
312 sessions
Spend by provider
Anthropic£98K
GitHub£52K
Cursor£42K
Windsurf£23K
Live session feed
Streaming
Engineer
Project
Provider
Category
Confidence
Cost
WH
Will H.
Analysis Agent
Anthropic
Claude Opus
Feature
94%
£284
1 of 4,218 sessionsAuto-classified by Flowstate AI

AI-powered session classification

Every AI coding session is automatically analysed and classified. The Flowstate classifier examines prompts, file paths, git context, and tool usage to categorise the work and match it to the right project — so spend flows through to the correct cost center.

AI classifier categorises the work

Feature development Category
Architecture & design Category
Bug fix & debugging Category
Refactor, testing, docs… Category

The classifier figures out what work was done and matches it to a project via ticket IDs, branch names, and file paths.

Project cost center determines CapEx / OpEx

Payments v2 CapEx
Analysis Agent CapEx
Platform Maintenance OpEx
Infrastructure & SRE OpEx

Once a session is attributed to a project, spend flows through to the project's cost center. You set CapEx or OpEx on the project — Flowstate handles the rest.

AI spend is growing — but nobody knows where it's going

Finance sees a growing "AI tools" line item with no way to attribute it to teams or projects. Engineering leaders can't answer basic questions: Which teams are driving the Copilot bill? Is our Claude API spend producing anything? Should we invest more in agents or more in people?

Without attribution, AI spend is a black box — and black boxes get cut first when budgets tighten.

Full visibility into AI spend

Provider-level breakdown

See spend by provider — GitHub Copilot, Anthropic, OpenAI, custom agents. Know exactly where each dollar goes.

Project attribution

AI spend is attributed to projects using ticket IDs, branch names, and file paths. Drill into any project to see per-session cost, category, and confidence.

Trend analysis

Track AI spend over time with date range selectors. Spot runaway costs before they become quarterly surprises.

Token-level detail

See input and output token usage per agent, per project. Understand not just what you're spending, but why.

Full picture from both ends

Flowstate pulls cost and usage metrics directly from AI providers, and captures session-level telemetry from developer machines — giving you a complete view of what's being spent and where it's going.

Provider API integrations

We pull billing and usage data directly from your AI providers, giving you the cost side of the equation without any agent installation.

Supported providers
Claude Code
ChatGPT
Gemini
Cursor
Windsurf

Session telemetry CLI

Our open-source CLI identifies and configures telemetry on developer machines, regardless of the AI tooling they use. It captures session-level data for classification.

Supported tools
Claude Code
Copilot Chat
Gemini CLI
Cursor
Windsurf
Qwen Code
Aider
OpenCode
macOS & Linux supported
Enterprise

MDM-ready rollout

The Flowstate CLI identifies and configures telemetry on developer machines, regardless of the AI tooling they choose to use. Roll it out across your org with your existing MDM tooling — Jamf, Intune, Kandji, or plain shell scripts.

  • Silent install via Homebrew or direct binary
  • Auto-detects installed AI tools and configures telemetry hooks
  • Zero-config for developers — no manual setup required
  • Open source — audit the code, contribute, or fork it
Works with your MDM
Jamf Microsoft Intune Kandji
Terminal
$ brew tap meetflowstate/tap
$ brew install flowstate-telemetry
✓ Flowstate telemetry installed
$ flowstate init
Detecting AI tools...
Found: Claude Code, Cursor, Copilot
Configuring telemetry hooks...
✓ Connected. Tracking AI sessions.

Stop flying blind on AI spend

Book a demo and see exactly where your AI budget is going — and whether it's worth it.