
Every few months, a model comes out that reasons about chemistry better than the last one.
You would think that worries a company like ours. It doesn't.
The capability curve is steep and it isn't ours to control. Any advantage built on "our model reasons better" has a shelf life measured in months.
It's also not the part doing the work. The system that decides which experiment to run next isn't a language model. It's a statistical model of the reaction: a surrogate fitted to the data you have, an explicit estimate of what it doesn't know yet, and a decision rule that trades off exploring against exploiting. That machinery doesn't improve because a new model shipped last week. What makes it perform is the data it learns from.
And public chemistry data is overwhelmingly successful reactions at their best conditions, with the failures left out. A record of what worked, not of what was tried. But failed conditions are most of the information about where a process stops working, which is exactly what you need to tell a process chemist where the operating window ends.
That gap is why we built our own HTE lab.
Not an obvious decision. Software companies don't buy fume hoods. It meant capital equipment, hiring chemists, and a class of problems we could have avoided by staying pure software. No spreadsheet justified it.
But we now generate data designed for the models we're building, rather than scraping data designed for a paper. Failed conditions included. Metadata captured because we decided in advance what mattered.
The second half is integration. A model that can't reach a customer's instruments, historical campaigns, or analytical output is a conversation, not a system. Unglamorous, slow, specific to each organization, which is exactly why it holds.
The bet: reasoning becomes broadly available, and the scarce things become proprietary data and depth of integration. Neither is quick to buy. That's deliberate.
If we're wrong, we own a lab we didn't need. We'll take that risk.