Subscription ROAS via ccusage to size your plan
Problem solved: Founders pay $100-$200/month for Claude/Cursor/Codex plans with no idea whether they're overpaying or undersubscribed.
What
ccusage is a local CLI that reads ~/.claude/stats-cache.json and reports your usage at API-equivalent prices. Divide that monthly number by your subscription price and you get a one-number ROAS for the plan. The 30-second decision: ROAS well above 1 means you're saving money; near or below 1 means downgrade.
Why it matters
Reported reference points from the community: 20x ROAS on a $200 Max plan for a heavy CC user; ~4x on a $100 plan (still positive); one operator confirmed Max $100 returned ~$650 of equivalent API. Same logic applies to Cursor (the "Cursor unlock" benchmark referenced $1,100/month in equivalent API spend on a $200 plan) and Codex. The number tells you when to rotate up to Max, rotate down, or open a second account.
End-to-end
- Install Node.js and pnpm if you don't have them.
- Run
pnpm dlx ccusage@latest monthly -bfrom your shell. - Read the total monthly API-equivalent cost line.
- Divide by the plan price you actually pay (Pro, Max $100, Max $200).
- Repeat at the end of each month; if ROAS < 1 for two consecutive months, downgrade or cancel.
- Optional: a menu-bar variant exists for live token-remaining display across multiple CC accounts.
Prompts
pnpm dlx ccusage@latest monthly -b
Gotchas
pnpm dlxpulls and runs arbitrary npm code each invocation — non-trivial supply-chain risk. At least one operator vetted the package source before running it. Pin a version or vendor the script if you put this in cron.
Tools
- Node.js + pnpm
- Claude Code with local stats cache