En
← All articles

How long can AI infrastructure earn its cost back?

Depreciation schedules explain part of AI investment; utilization, operating costs and credible reuse determine much more.

AuthorOpen Market NotesTypeArticle
Server racks stand on a timeline beside a utilization dial, with a red return arrow below.

Reading guide and original analysis | October 22, 2026

An AI infrastructure purchase makes several promises that mature at different times. The supplier expects payment. The operator expects useful computing service. The finance team must allocate the asset's cost over an estimated service life. A reader trying to assess the investment needs to know which promise a reported number actually addresses.

This matters when evaluating a new investment announcement or a quarterly earnings release. A larger capital budget describes a commitment, while a lower depreciation charge can improve reported profit without proving that a machine has become more productive. Neither number, considered alone, tells us how much commercially useful service remains. This article develops a way to examine that missing link rather than forecasting any company's return.

An estimate with consequences, not a hardware expiration date

Meta extended most server and network-asset lives to 5.5 years from January 1, 2025. Meta 2025 annual report

These are company accounting disclosures, not independent tests of how long a particular accelerator can run a commercially relevant workload. The difference is consequential. Equipment might still function physically while the cost of using it makes an available alternative preferable. Conversely, being slower than a new generation does not necessarily remove all profitable uses. A service with flexible completion times could have different requirements from a latency-sensitive product.

Our analytical inference is therefore to ask what work an older machine can still perform economically, rather than ask only whether it is technically obsolete. The answer depends on the actual task, the price or internal benefit attached to successful completion, and the resources consumed to obtain it. A useful-life estimate provides an assumption to examine; it does not supply those operating observations.

A deliberately simple example

Consider an entirely hypothetical operator paying 100 monetary units for equipment, with no residual value. Assume straight-line depreciation, a full year of service, and no financing, tax or other accounting complications. A four-year estimated life allocates 25 units of expense per year. A six-year estimate allocates about 16.7. The annual difference is about 8.3 units, but the original cash payment remains 100.

This is a comparison of two initial assumptions, not a calculation of the effect of changing an estimate midway through an asset's life. It also says nothing about the actual policies or earnings of the companies cited above. Its purpose is to isolate a mechanism: spreading a given cost over more years lowers the annual allocation, without manufacturing another customer or reducing a power bill.

Now suppose that the hypothetical equipment produces the same volume of paid work under both assumptions. The change in accounting life cannot improve its underlying economics. If instead software improvements allow the equipment to perform useful work longer, there may be a genuine economic reason to revisit the original estimate. The evidence needed is the extension of useful service, not merely the resulting improvement in reported margin.

The distinction also works in reverse. A prudent short life can make current accounting profit look weaker even when the equipment continues to provide valuable service afterwards. Comparing margins without considering these assumptions can therefore misread both optimistic and conservative choices. It is reasonable to test an estimate; it is not reasonable to infer misconduct from its direction alone.

Utilization needs a denominator and a purpose

For a reader, “busy” is an incomplete operating description. A machine can be occupied by useful customer work, internal experimentation, repeated failed jobs or work that could have been completed more cheaply elsewhere. These are analytical possibilities, not assertions about a particular operator. Their economic implications differ even if an aggregate activity measure looks similar.

The relevant denominator also matters. Installed equipment, powered equipment and equipment available to a particular workload are not interchangeable concepts. A system waiting for another component to become available may be physically present without delivering the intended service. A mixed fleet can look well utilized in aggregate while one costly generation remains underused. None of this can be resolved from a total spending figure.

A more informative evaluation would follow a cohort of equipment from purchase into service and then through changing assignments. What share of its time produces accepted work? What does that work earn or save after electricity, maintenance and the people required to operate it? Does the operator have a demonstrated use for the later years, or only a general intention to find one? These questions connect the depreciation assumption to observable operations without demanding that public reporting disclose every customer's activity.

Reuse has costs of its own

Redeploying equipment to a different task is a plausible way to preserve value, but it needs an implementation case. Imagine moving older hardware from an urgent workload to a batch-processing service. The lower urgency may create room for slower equipment. Yet adapting software, moving data and maintaining a second configuration could consume the expected benefit.

The proper comparison is the incremental cost and benefit of continuing to use that equipment against the available alternative. Original purchase cost is relevant when assessing whether the investment paid off, but it should not by itself force continued operation. If running an old system consumes more resources than the service is worth, having already paid for it does not make that usage economical.

There is also a legitimate case for spare capacity. Reliability requirements or uncertain demand could justify equipment that is not constantly busy. The evidence should explain the service being protected and the cost of a shortage. Treating every idle hour as waste would be as simplistic as treating every occupied hour as value creation.

Why a write-down cannot settle the investment question

Amazon’s 2025 filing describes an undiscounted-cash-flow recoverability screen for operating long-lived assets, with impairment measured against fair value. Amazon annual filing

That accounting policy should not be confused with a commercial hurdle rate chosen by an investor or operator. A project can remain useful while producing a disappointing return relative to alternatives. Equally, uncertainty about future demand is not sufficient evidence that a specific company must record an impairment. Applying an accounting conclusion requires the relevant asset grouping, forecasts and other facts, much of which a public reader may not possess.

For our analysis, the useful question is what would change the expected remaining service: a durable reduction in paying demand, a more expensive operating environment, or an inability to adapt equipment to work customers still need. Those are scenarios to investigate, not predictions. A write-down would recognize a loss in carrying value; it would not itself repair the operating problem or recover the original payment.

The most helpful future disclosures would connect equipment cohorts, their deployment and credible later uses with the financial estimates. Until that connection is visible, the responsible conclusion may be a range of possibilities rather than a confident payback date. Evaluating AI investment requires patience about long-lived benefits, but also a clear account of what evidence would make that patience unwarranted.

Information only. No investment, legal, tax, or financial advice.