Claude Usage Analyzerv1.0.3

A solo developer running several client projects through Claude Code wants to understand where token spend is going each month. They run the analyzer to see which project folders consume the most tokens and identify oversized prompts. This helps them adjust their pricing and set client expectations for AI-assisted work.

An engineering manager at a 15-person startup notices the Claude API bill rising but has no visibility into individual usage. They deploy the analyzer to get per-session and per-developer breakdowns, then share findings in a weekly standup. The data drives guidelines on prompt hygiene and context window management.

An instructor teaching a course on AI-assisted development wants students to practice measuring and optimizing token usage. Students install the analyzer, analyze their own Claude Code logs, and produce recommendations for reducing waste. The exercise builds cost-awareness as a core engineering skill.

A maintainer of a popular open-source project uses Claude Code to triage issues and review PRs. They run the analyzer to see how many tokens each type of task consumes and whether some automated workflows are inefficient. Findings inform a blog post on sustainable AI-assisted open source maintenance.

An internal platform team at a large enterprise needs to enforce AI tooling budgets across departments. They use the analyzer's JSON output to feed a dashboard that tracks token spend by team and project. This supports chargeback reporting and policy decisions about which use cases justify AI tooling costs.

The core CLI is open source and free, providing basic reports and session listings. A paid Pro tier unlocks advanced features like cross-project trend analysis, team aggregation, and exportable executive dashboards. This model builds trust through the open-source core while monetizing deeper analytics needs.

The individual tool remains free and open source, while enterprises pay for team-level features such as seat management, SSO, centralized configuration, and compliance reporting. The open core drives adoption bottom-up, and the enterprise plan monetizes organizational governance needs.

While the CLI stays local and offline, the vendor offers a hosted service that ingests anonymized usage data to provide benchmarking, recommendations, and alerts. Teams pay for the convenience of dashboards, historical retention, and automated optimization insights without managing local infrastructure.