Sometimes. It depends on what the cycle costs you in life, and almost nobody prices that. A cycle count in a warranty is a blunt instrument standing in for a number the industry does not currently measure: the degradation cost of this cycle, on this pack, at this temperature.
A warranty cycle limit is not a physical limit. It is the manufacturer pricing their own uncertainty about your operating profile, and it is deliberately conservative. The operator question underneath it — could we just cycle as hard as possible and buy new cells? — is a real economic question with a real answer, and the answer changes cycle by cycle. What decides it is the marginal degradation cost of the next cycle against the spread that cycle captures. Get that number and the warranty limit stops being the binding constraint on revenue.
This is a live and public argument in the storage industry, not a hypothetical.
“The cycle limit is one of the biggest caps on revenues.”
That is a European BESS operator speaking to Energy-Storage.News in March 2025, in an article that also reports typical warranty limits of 1.8 to 2.0 cycles per day averaged annually, and notes that most OEMs and power plant controllers clip capacity to manage warranty conditions — which limits the megawatt-hours actually used.
The same operator asked the question directly: does it make sense to have cycle limits at all, or could you cycle as hard as possible and buy new cells? It is a good question and it has not been well answered in public.
Meanwhile the degradation itself is expensive. Energy-Storage.News reported in April 2026 that a typical grid-scale battery is projected to lose 20 to 30% of its capacity in its first decade, and that capacity loss can cost tens of millions of dollars of a project’s valuation.
And the instrument you would use to manage it is not precise enough.
Analysis published by 3E in September 2025 found battery management system state-of-health readings can differ from actual battery condition by as much as 8%, that manufacturers commonly write plus-or-minus 10% accuracy disclaimers into warranty terms, and that there are documented cases of BMS health values jumping up to 10 percentage points after a software update.
An 8% error on the number you are using to decide whether to cycle is not a rounding problem. On a large system it is the difference between capturing a warranty claim and missing it.
The failure mode operators actually report is not dramatic. As FlexGen put it in April 2026: systems that cannot hit nameplate discharge because a handful of cells are out of sync.
A cycle is worth taking when the revenue it captures exceeds the life it spends. That is the entire decision, and it is computable.
Spending life is a physics question before it is a finance question. The same megawatt-hour dispatched at a high cell temperature costs materially more life than one dispatched cool, because the degradation rate is governed by temperature, depth of discharge and rate — not by the number of cycles on a counter. Two packs at the same cycle count, worked differently, are not the same asset.
So the useful output is not “cycles remaining.” It is a cost, in dollars, attached to each dispatch decision before you make it — which is what turns a warranty limit from a hard ceiling into a priced trade-off. That is the job GridPowr™ does, and the number SENTRIX Runway™ reports.
On real ERCOT market data covering January 2026, including a winter scarcity event, our own modelling found that price-only dispatch ran a fleet materially hotter than degradation-aware dispatch, and that once asset damage was costed, the degradation-aware strategy was the only one that stayed value-positive. We state the direction and not the magnitudes: that study is in a corrective pass and the dollar figures are held until it closes.
A read-only assessment runs on data you already have, before any hardware conversation. You see the record; you decide what it is worth.
Choir™ Corp