Where Garth is going

Every company is spending on AI.Almost none can say where the next dollar should go.

Today Garth tells heads of engineering what their AI spend returned, with the proof attached. In December 2026 the same record reaches the CEO and CFO: what came back, how sure you can be, and which dollar to scale, hold or stop.

Running Garth in engineering 73 Strings Automation Anywhere Capillary Zapcom KePSLA
The problem

Companies know what AI costs. They don't know what it earned.

Nearly every budget now carries an AI line, and it's usually the fastest-growing one. Ask what it returned and you get a different answer from every team, each worked out its own way.

One example, illustrative

A company pays $3M a year for AI tools. Is it getting $1M back, or $10M? Nobody in that company can say.

87%
of finance leaders say they must link AI spend to business results within a year
CloudZero, June 2026
66%
of finance leaders say their board now ties further AI funding to proven returns
CloudZero, June 2026
75%
of AI initiatives did not deliver the return that was expected
IBM CEO Study, 2025

Sources: CloudZero, Finding the ROI of AI: The Finance Perspective (June 2026), a vendor-sponsored survey of 260 finance leaders. IBM Institute for Business Value, CEO Study 2025, 2,000 CEOs: only 25% of AI initiatives delivered the return expected. The $3M example is ours, not a customer's.

What Garth does

One record of what every AI dollar returned, read from the work itself.

This isn't a survey or a self-reported estimate. Garth sits inside the systems where the work is done, the tickets, the repositories, the release records, the tool bills, and reads what was asked, what was delivered, what it cost and what came back. That's what we mean by Enterprise AI Decision Intelligence.

Without Garth

Each team's own estimate, in a spreadsheet nobody checks.

Three teams will give you three numbers, worked out three ways, and none of them ties to the accounts.
With Garth

One record for every team, worked out the same way, and a grade on how sure you can be.

The evidence behind each number is a step away, for the head of engineering and the CFO alike.
  1. 01

    Know what it cost

    What each piece of work cost, people and AI together, before AI and after, not the AI bill on its own.

  2. 02

    Prove what it returned

    Every claim is graded: seen in the work, inferred, or proven in the accounts. So you know how far to trust a number before you act on it.

  3. 03

    Decide where the next dollar goes

    For each piece of work the answer is one of four: scale it, fix it, hold it or stop it. The head of engineering and the CFO decide it from one record, together.

Everything else is an estimate. Surveys give you hopes, login counts give you usage, and a number typed into a planning tool is still somebody's guess. The record of the work is the one source nobody gets to round up.

What "proven in the accounts" means. The saving or the revenue shows up in a line your finance team can point to: a cloud bill that fell, licences that were cancelled, revenue against a feature that shipped. "Inferred" means the work points to it and the ledger doesn't yet. The grade tells you which is which.

Why engineering first

It starts in engineering because that's where the money is, and where Garth already runs.

Across enterprises, engineering is the biggest line in AI application spend and the fastest growing. It's also where Garth already runs, with five enterprise customers in the US and India. The leadership view reads that same record. We're not starting a second one.

44%
of the $77B a year enterprises now spend on AI applications went to coding tools, the biggest application line Menlo Ventures tracks
7.7x
growth in coding-tool spend in a year, the fastest of Menlo's application lines, against 5.4x for enterprise AI overall

Menlo Ventures, 2026: The State of Enterprise AI (November 2026), annualised spend measured to September 2026: $34.0B of $77.3B on coding tools, up 7.7x in a year against 5.4x for all enterprise AI; customer success is the next fastest application line at 4.3x. The agents engineering teams build and the models they call directly sit in Menlo's infrastructure line, so we read this as the floor of engineering's AI spend, not the whole.

The road

Engineering stays the core. The same question reaches the rest of the AI budget, one business function at a time.

We ask every function that spends on AI the same question, and a function joins only once Garth can read its work from the systems it already runs.

  1. Now

    Engineering

    The full picture for the head of engineering, live today. G360, GReview and GRelease keep their own roadmaps. The leadership view reads their record and doesn't replace them.

    Live · still the core
  2. The CEO and CFO view

    The same evidence, carried to the people who sign the AI budget.

    Design partner seats open
  3. Other business functions

    Which come first will be settled with the design partners. Each adds its own work, its own costs and its own measures of value to the one record.

What stays the same, whichever function it is: what was asked, what was done, what it cost in people and AI, what it was worth to the function and to the company, and how strong the proof is. That's how a CEO gets to compare one function's AI with another's on one page.

Already a Garth customer? Nothing changes in what you use today. The numbers your engineering team already reports are the record the leadership view will read, and you'll see that view before your leadership does.

Design partners

A few companies will shape the CEO and CFO view with us.

We're opening it to a small number of design partners: companies whose leaders want this answer on their own AI budget, and whose finance team will check our numbers. Tell us about your AI spend and who from engineering and finance you'd want in the room. We'll come back within one business day.

You see it firstThe view runs on your own AI budget before anyone else's, and you shape what it shows.
Engineering in the roomYour head of engineering is part of it from day one, before your CFO sees a number.
Your data stays yoursIt lives in your own Garth tenant. Nothing is pooled or published without your written yes.
Terms in writing firstWhat we give, what you give and how either side steps out, agreed before anything is connected.

How we count. Every figure on this page that isn't ours carries its source and, where it matters, its caveat. Where something is an estimate or an example, we say so. The same rule applies to the leadership view: no number without saying how it was proved. Garth is made by Darner Technology, Inc., a US company with its product team in India.