# The yield on a GPU is an approved workflow

Jensen Huang and six of the largest asset managers on Wall Street signed six memorandums of understanding targeting more than half a trillion dollars for AI factories as revenue-generating assets. The revenue arrives inside enterprises, one approved decision at a time, and almost none of them can trace it.

> By Saad Bin Shafiq, Founder of Nodes · Aug 11, 2026
> Canonical: https://www.nodes.inc/blog/gpu-yield-approved-workflow


---
Wall Street has agreed to underwrite the supply side of AI. Nobody has underwritten the demand side.

On Monday, Jensen Huang sat across from six of the largest asset managers and private-credit firms in the world on CNBC and announced six memorandums of understanding targeting more than half a trillion dollars of third-party capital for AI factories: the land, the power, the shells, and the compute inside them. His argument that chips are now an investable asset class came down to one sentence: "These are revenue-generating assets now."

He is right. And the revenue he is pointing at arrives somewhere his financing partners cannot see: inside an enterprise, one approved decision at a time.

## What six term sheets can price

One executive at the table compared the structure to underwriting a house. The bank looks at the borrower, and the bank looks at the asset. For an AI factory, the asset side of that ledger is legible: power contracts, construction cost (the table put a single gigawatt at fifty to sixty billion dollars), tenant credit, utilization, the resale value of the silicon.

This is third-party capital, structured as separate financing platforms, and the half trillion is a target rather than a committed fund. Huang was explicit that Nvidia's own balance sheet stays out of it, and equally explicit about who the platforms exist to finance when asked directly: the AI labs, plus the clouds and enterprises building alongside them. Terms, rates, and borrowers come later. What was announced on Monday is a thesis with a number on it: silicon is productive, long-lived, and fungible enough that lenders can treat it the way they treat power plants.

The borrower side is where the chain gets long. The tenants are AI labs, clouds, and the enterprises building capacity alongside them. Labs and clouds resell what they build as tokens and instances, and the buyers of those, further down the same chain, are the same enterprises approving AI budgets. Every dollar of yield the financing depends on eventually has to be a dollar some CFO decided the compute earned.

To their credit, the people at the table said the uncomfortable parts out loud. Spreads could widen if the scale gets very big. Some of these bets will lose. Enterprises are never early adopters, and the value of what AI does inside them is hard to quantify. That last concession is where the chain thins out: the tenant's credit is priced. What the tenant's own customers get back from the compute is not. The trade is collateralized at the factory and unquantified at the point where the return is generated.

## The demand side files no yield statement

A financed office tower produces a rent roll. A financed AI factory produces invoices, and the enterprise paying them produces, in most cases, a usage dashboard: queries run, tokens consumed. Consumption is a cost report. It is not a yield statement.

Ask an enterprise what its AI spend returned last quarter and the common answers are a pilot narrative, an adoption curve, or a survey. The [CHRO version of this problem](/blog/chro-ai-strategy-2026) is a budget that ranks AI first and funds a list of tools that each report their own activity. The CFO version is the same list at the capital-allocation level: the spend is itemized, the return is folklore.

Markets have seen this shape before. Another executive at the table reached back to the birth of the mortgage-backed market in the 1970s for his analogy, and the analogy teaches something he did not linger on: housing did not become an investable asset class when capital showed up. It became one when standardized paper existed, when title, appraisal, and amortization schedules made a house's economics portable. The standardized paper of AI yield, the record that ties a unit of compute to a unit of business outcome, does not exist inside most enterprises.

## The unit of yield is a named workflow

Here is what that instrument looks like when it exists.

An intelligence layer sits above every system of record a company runs. Its agents ingest and process what those systems hold, reason across them, and propose workflows that cut across the silos: a retention intervention, a pipeline rerank, a renewal play. Every proposal arrives priced, with the cost of action and the cost of inaction attached. A human approves, edits, or declines it. On approval, the system acts across the underlying systems and signs a Decision Trace: what happened, where, why, what the reasoning was, and what input the human gave.

Concretely: an agent reading across the CRM, the HRIS, and the ATS notices that three producers in one region crossed a flight-risk threshold in the same week the region's open requisitions stalled. It drafts a retention play for the manager and a pipeline rerank for the recruiter, prices what walking talent costs against what the interventions cost, and puts both in front of the humans who own those calls. One gets approved as drafted. One gets edited. When they execute, each carries its trace. Next quarter, the question of what the compute behind those two workflows returned has a line-item answer.

That loop turns compute spend into an auditable unit of return. The workflow has a name. The trigger is recorded. The decision is attributed. The action is logged where it landed. The delta against the baseline is measurable, because the baseline was stated when the proposal was priced.

This is also why the commercial unit at Nodes is a named workflow, from trigger through approved action and evidence, rather than a meter on seats, tokens, or model calls. A meter measures what a system consumed. A workflow measures what a decision returned. Only one of those is something a CFO can underwrite.

## What the ledger looks like when it exists

At a Fortune 500 insurance carrier, this loop has run against four years of production data covering 10,765 agents, with the methodology published in [Decision Traces](https://arxiv.org/abs/2604.19819). Every proposal in that record carries the same form: a named workflow, a stated baseline, the priced gap between acting and waiting, and the human decision that closed it. A workflow, a baseline, a delta, a sign-off. That is a yield statement for AI spend, and a quarter's worth of them is the demand-side paper the supply-side financing quietly assumes exists.

The same form is why the architecture survives the buying process at all. The questions a credit committee asks of a financed factory's tenant are the questions a procurement review asks of an AI system: where the data goes, who signs off, what evidence survives. An architecture that answers them in writing is underwritable twice over.

Insurance capital sits on the funding side of Monday's announcement, underwriting the factories. An insurance carrier is where this loop has run longest on the demand side: the end of the trade where financed compute has to show what it returned.

## The asset that appreciates

The question the coverage keeps circling is residual value: what financed silicon is worth when the next generation ships. Nobody at the table quantified it. Silicon depreciates on the model cycle, regardless of what any future term sheet assumes.

The demand side holds an asset with the opposite curve. Every approved workflow leaves evidence behind: the context graph connecting the company's systems gets denser, the record of what was proposed, decided, and returned gets longer, and the next proposal gets sharper because the last hundred are on file. The data stays. The intelligence layer reads across it. That record compounds while the silicon it runs on depreciates.

Who holds that compounding asset depends entirely on architecture. An enterprise that rents its intelligence through someone else's API is [accumulating that record for its vendor](/blog/you-re-building-your-competitor-s-moat-the-hidden-cost-of-renting-ai-models). An enterprise running the model inside its own VPC, with customer-owned weights and no data egress, accumulates it for itself, and keeps it if the vendor relationship ends. On a decade horizon, that ownership line will matter more than the price per token.

If chips are the first investable asset class AI has produced, the governed decision record is the second. It will take longer to price. It is the asset the capital is betting on whether it knows it or not.

Huang's announcement finances the factories. What makes the factories good collateral, in the end, is an enterprise that can show what came back. The supply side named its half trillion on Monday. The demand side gets underwritten one approved workflow at a time.

## Sources

- [CNBC transcript, Becky Quick with Jensen Huang and Wall Street leaders on the AI infrastructure push](https://www.cnbc.com/2026/08/10/cnbc-exclusive-transcript-cnbcs-becky-quick-speaks-with-nvidias-jensen-huang-wall-street-leaders-on-500b-ai-infrastructure-push-on-closing-bell-overtime-today.html)
- [Benzinga, Huang says chips have become an investable asset class](https://www.benzinga.com/markets/tech/26/08/61098798/nvidia-jensen-huang-chips-investable-asset-class-500-billion-ai)

*Saad Bin Shafiq is the founder of Nodes, serving data-sensitive enterprises. Methodology: [Decision Traces](https://arxiv.org/abs/2604.19819).*