What a readiness score measures before you ask a plant for a trial

When you take the readiness score, you get a number and a short list of gaps. It is tempting to read the number as a verdict on your company. It is not. It is a snapshot of one thing: how close you are, today, to a paid trial with a named buyer.

A low score is not a rejection. It is the product doing its job, which is to tell you the truth before a buyer does.

What the score measures

The score weighs the four things a corporate buyer checks first, usually before they will even take a meeting.

Trial-ready material. Can a plant put your material into a real process in the next thirty to ninety days? This is about maturity, not perfection. A material at TRL 6 that a plant can run beats a brilliant TRL 3 idea that needs a year of bench work.

A named use-case. Do you have one specific application, on one substrate, for one buyer type, rather than a platform that could theoretically do anything? Buyers trial use-cases, not platforms. Focus scores higher than breadth.

Safety data on hand. Do you have the SDS and handling guidance a plant needs to legally and practically run your material? This is the single most common blocker, and it is entirely within your control.

A founder in the seat. Is there a founder driving commercialization, or is the science sitting in a lab with no one owning the path to a customer? Buyers work with companies, not with unattended IP.

Why we weight it this way

Notice what is not on the list: your funding, your team size, your patent portfolio, your total addressable market. Those matter for a raise. They do not determine whether a plant will run a trial next quarter. We score the things that predict a yes from a buyer, because that is the only thing the desk can actually help you get.

The score answers one question: if we made an introduction tomorrow, would the buyer say yes? Everything else is noise at this stage.

What to do with a low score

Each factor comes with its gap spelled out. Treat the gaps as a to-do list, not a report card.

• If safety data is your gap, that is often a two-week fix, not a two-year one.
• If use-case is your gap, the work is narrowing, not building. Pick the one application a plant could run and lead with it.
• If material readiness is your gap, be honest about the timeline and come back when a plant could actually run it.
• If founder in the seat is your gap, the question is bigger than this score, and worth sitting with.

Retake it

The score is meant to be retaken. Close a gap, run it again, watch the number move. When it clears the bar, submit a use-case, and the desk goes to work finding the buyer.

Scoring is free, and it is the honest first step. Take it before you spend another month guessing whether you are ready.