The Stranded Spend Audit
Two weeks. Read-only. One number.
RidgeLine meters AI coding spend to the work it shipped. The audit is a fixed-scope look at your own estate, ending in a one-page memo and one sentence: how much of your AI coding spend in the last fortnight never reached a pull request, and the three causes behind it.
Read-only, from the first day to the memo.
Install, in about an hour
You install the read-only GitHub App on the repositories you choose and merge one short telemetry change per repository. Your engineers can read every line of it. Your code and your prompts never leave your estate.
The meter runs
Nothing for your team to do. RidgeLine meters each agent session to the commit and pull request it produced, and records the sessions that produced neither.
The memo
One page. The stranded number, where it concentrates, the three configuration causes behind it, and what recovering it would take. Yours to keep either way.
of agent spend in the last fortnight never reached a pull request
22% of metered spend · concentrated in two repositories
The three causes
- Pre-merge tests not requiredpayments-service
- Steering file stale for 90+ daysweb-checkout
- No review gate on agent branches
What recovering it would take
Two configuration fixes, an afternoon each.
Teams running agents at scale typically find double-digit percentages of their agent spend stranded on work that never shipped.
Built for the leader who will be asked about the number.
The audit is for engineering leaders (a CTO, a VP of Engineering, an engineering director) at organisations running AI coding agents across real repositories, where the agent bill has become a line item someone will ask about.
If you are a small team getting started with agents, the audit is more ceremony than you need. The free Instrument tier gives you the same ledger. Join the waitlist and start when you are ready.
Free for the founding cohort.
The path. The audit is the front door to the founding-partner programme. Six teams, chosen because a fortnightly call with the founders does not scale past six, will shape what RidgeLine becomes.
Who we are looking for. Engineering organisations in the UK or EU running AI coding agents across real repositories, typically between fifty and five hundred engineers.
The audit is free for the six founding partners we are onboarding now. Once the cohort is filled it costs £500, credited in full against your first subscription, so the audit never ends up costing anything unless it was worth nothing.
Founding partners pay half the list price for their first twelve months, locked at signature, with a direct line to the founders and a real voice in the roadmap. In exchange we ask for a fortnightly feedback call and permission to publish anonymised numbers as a case study.
Request the audit
Leave a work email and we will reply within one working day to agree scope and a start date.
Your engineers will want to read exactly what the telemetry change sends before they approve it. Send them the security page; it states what RidgeLine sees and what it never takes.
Read-only throughout. If the number is boring, you have lost nothing.