Spend · Costs
Costs
See where the money actually goes - vendor by vendor, before you sign the next renewal. Every vendor the project pays (Anthropic · OpenAI · Vercel · Stripe · others) with current spend band, pricing model, and the trigger that'd move us off it. Lives at .claude/brain/costs.md.
See it in motion
Where to find it
- Desktop:
http://localhost:4000/, then Reference (drawer) → Costs in the sidebar. - Hosted:
repoops.ai/team/reference(browse it from the Reference drawer) - Keyboard: ⌘ K, then type “Costs”.
- On disk:
.claude/brain/costs.md
What it does for you
A vendor table you can defend at a board meeting.Vendor · what it does · pricing model · current band · why we'd switch. One row per paid surface, refreshed when the invoice changes meaningfully.
The switch trigger is written down before you need it.Each vendor carries its pricing model, current spend band, and the scale ceiling where it starts to hurt, so the “when do we move off this?” call is already made when the bill grows, not improvised under pressure.
Lined up with Telemetry & Billing outcomes.Costs is the static “what we pay for”; Telemetry + Billing outcomes are the live “what we actually spent.” Both should converge or one is wrong.
Configure
Nothing - hand-edit the markdown when a vendor is added, removed, or repriced. The HTML twin is auto-synced by npm run sync-brain.
Use it well
Before signing any new vendor: add the row first, then sign. Forces the “what triggers us to switch?” question while it's still cheap to leave. Quarterly: re-read the bands against the last invoice - if the band's wrong, update before the next planning window so budgets price correctly.