Set it once.The records do the rest.
Budgets, owners, and policies — configured once. From then on, CapHound writes the records, delivers them where your teams work, and hands you the receipt.
The operating loop
A week with CapHound
Not another tab your team has to live in. One configuration, then the work happens where it already happens.
Configure once
Budgets with owners and approval paths. Policies across every kind of control. Ten minutes, honestly.
Records flow out
Spend records to your warehouse, signals to Slack and Datadog, tickets to Jira — automatically.
Owners decide in place
Budget increases and exceptions approved with one tap in Slack or one click in email. On the record.
The receipt lands
Once a month: what was prevented, what was decided, who decided it. Forward it upward.
The dashboard? You'll barely use it. Configure, investigate when something needs a closer look, leave. That's the point.
The data contract
Five kinds of records. Every question answered.
This is what CapHound actually produces — request-grained, owner-attributed, audit-ready. Your warehouse, your BI, your auditor, and your AI agents all read from the same records.
Spend records
Who caused every dollar?
featureteamcustomerownerBilledCostFOCUS 1.0Decision records
What did each policy do to each request?
actionpolicymodelscopereasoncost_effectApproval records
Who approved what, and how fast?
decided_bychannelamountreasontime_to_decisionControl records
What changed, and did it revert on schedule?
control_typetargetspend_governedactorreverted_atThe receipt
What do I forward upward each month?
preventeddecisionsmedian_ttdrevertsaudit_refDelivered to
Warehouse push is FOCUS 1.0, nightly — Snowflake, BigQuery, S3, or any destination that accepts it. AI agents: Claude, Cursor, anything that can ask.
The controls
Every request. Every provider.
Policies are evaluated per request — not per invoice line, weeks later. Each decision is written to the record with the policy that made it, and the catalog keeps growing.
budget-limitSpending stops at the limit — hard stop or paced burn, your call per budget.downgrade-ruleNon-critical traffic moves to a lower-cost model automatically.routing-preferenceRequests stay where they belong — region, provider, data residency.model-restrictionOnly approved models run. Anything else is swapped or stopped.rate-limitBursts get absorbed before they become a bill — per scope, per environment.
gpt-4o · contract-analysis
budget-limit · legal-tech monthly
gpt-4o → 4o-mini · support
downgrade-rule · non-critical
claude-sonnet · doc-extract
routing-pref · EU residency
o1-preview · eng-sandbox
model-restriction · approved
batch-embed · growth
rate-limit · 20/min non-prod
Every request, evaluated against your policies
$2,144 never spent · MTD
NEW · FinOps AI agent
A teammate that proposes — you approve.
The agent watches your AI spend the way a FinOps analyst would: spotting waste, drafting the exact change, and bringing it to you with the dollars it holds. Strict human-in-the-loop — it never spends or changes on its own, and every proposal is on the record.
- Finds savings you'd have missed, and shows its reasoning
- Proposes the exact change with its dollar impact
- One-tap approve or reject, right where you work
Support traffic is running on gpt-4o. I can cap it to gpt-4o-mini on non-critical requests.
holds
~$1,800 / mo
quality risk
low · reversible
Nothing changes until you approve — and every proposal is recorded.
Seats
The per-seat AI spend nobody's watching.
Beyond the apps you build — the AI tools your people sign up for. CapHound consolidates Copilot, Cursor, and ChatGPT spend by employee, surfaces the paid seats sitting idle, and revokes them on your approval.
- Every employee's AI tool spend in one place
- Idle paid seats surfaced automatically
- Revoke with two-person approval — audited, reversible
j.okafor@
GitHub Copilot · idle 41d
m.patel@
Cursor · idle 33d
l.reyes@
ChatGPT Enterprise · idle 38d
One control surface, every provider.
First records in 15 minutes.
Setup is a drop-in change — your spend records start flowing the same hour. From there, onboarding is guided: we map budgets, owners, policies, and the tools your teams already use.
No public docs to dig through — because you won't be implementing this alone.