TECHNOLOGY READINESS LEVEL
A 3-step readiness check that goes beyond the TRL number.
Hi,
Last week we covered how to run a tech scan that leads to a decision.
This week, the harder half: how to tell whether a technology is actually ready.
Imagine two technologies at the same TRL. One has a dozen suppliers producing at a commercial scale. The other has two, both still building capacity, and nobody can commit to your volume for three years.
Same TRL. Different decision. A technology can be well funded, widely written about, and still years away from doing anything useful in your operation.
TRL is a useful shorthand, and like most shorthands, it hides more than it shows.
Here's the framework we use before calling anything ready, and how it played out on an actual grid-scale storage project for a multinational power company.
THE FRAMEWORK
What a readiness check should actually establish
Rather than explain these principles in the abstract, here's how three of them shaped a scouting project for a major oil and gas company evaluating green hydrogen investments.

STEP
Define what “ready” means for your decision
TRL is a scale, not a verdict. TRL 6 is ready if you're planning a pilot in 2030 and useless if you need something you can procure next year.
So set the threshold before you start scouting:
- Ready to buy and deploy now?
- Ready to pilot within 18 months?
- Ready to partner on and develop jointly?
- Ready to watch, and nothing more?
Each answer draws the line in a different place. Without it, a landscape returns everything and sorts nothing.
IN PRACTICE
The client set the floor at TRL 4 and above, which immediately removed a large volume of early-stage chemistries from consideration. That one decision made the rest of the assessment tractable, because everything that survived was at least a candidate for a real deployment conversation.
STEP
Rate the technology and the supply chain separately
A TRL number describes a technology. It says nothing about whether anyone can sell you one.
These come apart more often than teams expect. A mature technology with two capable suppliers and an 18-month lead time is a different proposition to the same technology with twenty suppliers. Both are TRL 8.
Worth establishing for each candidate:
- Who is actually producing it at commercial scale?
- What has been deployed, where, and for how long?
- Where does the supply chain concentrate?
- What's the realistic time to commercial availability?
IN PRACTICE
Alongside the technology assessment, we mapped the supplier market across each energy storage type, so every readiness rating arrived with an answer to who could supply it and when. That mattered more than the client expected. Several technologies that scored well technically had supplier bases too thin to support the deployment scale they had in mind.
STEP
Apply the same criteria to every candidate
The most common failure in readiness assessment isn't using the wrong criteria. It's using different criteria for different technologies, usually because the research on each one was uneven.
Most energy storage and process assessments will consider some version of:
- Technology readiness level
- Capital and operating cost
- Efficiency and energy density
- Performance and durability under real duty cycles
- Scalability and the specific roadblocks to it
- Sustainability and material constraints
- Time to commercialization
The output isn't a ranking. It's a comparison where the differences come from the technologies rather than from how hard someone looked.
IN PRACTICE
Every technology in the landscape was compared on that same metric set. Consistency did the work: the client narrowed a broad field to four technologies of high interest, at which point we ran a second phase on those four alone, covering scalability roadblocks, revenue streams from adoption, compatibility with other storage options, design and sizing questions, and supply chain risk.
ENERGY STORAGE CASE STUDY
From a full TRL spectrum to four technologies worth building around

A question worth asking
Readiness assessments tend to go wrong quietly. Nobody notices the criteria drifted until a pilot stalls.
Five questions worth putting to your team:
- Does everyone here mean the same thing when they say a technology is ready?
- Are we rating the technology, or the company selling it?
- What evidence would change our mind about a readiness claim?
- Which of these need to work in three years, and which can wait ten?
- Have we tested any vendor claim against someone who has actually operated the technology?
Readiness is also a moving target. A technology assessed two years ago may sit somewhere entirely different today, and the teams that revisit their own conclusions tend to move faster than the ones that don't.
If any of this is relevant to how your team evaluates readiness, we'd like to hear how you approach it.




