Buying more machines will not make you AI-native.
An AI-native biotech is not a company where the machines do the work and the people watch. The machines are not what make it native, and buying more of them will not either. The design around them is.
AI-native
A company designed around an honest read of what people and machines each do well, and built to keep translating new capability into new ways of working.
Start with what it is not
Let me clear the fantasy first. An AI-native biotech is not a company where the machines do the work and the people watch. So the honest version is this: an AI-native biotech is built on a clear read of five things: what people do well, what machines do well, what software can now carry that it could not before, how freely information moves when moving it costs almost nothing, and where a decision can be made better than it is today. Get that read right and rebuild, and you have the start of one. Refuse to look, and you have an AI-enabled company with a bigger software bill.
What each is willing to reconsider
The difference is not the technology. Both kinds of company buy the same models. An AI-enabled biotech lays new technology over old assumptions. It keeps the inherited structure, workflow, approval chain, job description, and measure of value, and it makes each one run faster. The org chart from before is still the org chart, now with a copilot.
An AI-native biotech treats those assumptions as the actual work. It asks whether a workflow should exist in its current shape or only because it always has, how information should move now that moving it is nearly free, which decisions could happen earlier and with better evidence, which separations of duty survived only because the systems could not see each other, and where human judgment matters more rather than less. None of those are questions about a model. Each is a question about the institution.
They ask how AI can help them do their existing work at lower cost, and the tools answer that well. A year later they are quicker at the same documents, the same meetings, the same decisions in the same order.
That is efficiency, not a new institution. It is the old one with better throughput.
There is no final form
Here is the part people want and cannot have: a finish line. There isn't one. The capability keeps moving, and a company designed around last year's capability is already drifting back toward AI-enabled. So the defining trait is not any particular tool or structure. It is a capacity, the ability to turn new capability into new institutional capability, over and over, as the ground shifts. The company that can keep doing that translation is native. The one that did it once and stopped is not. Translational Intelligence is the name for that capacity; Permission, People, Programs is the system that produces it.
What this looks like in biotech
Biotech is where this matters most and where it is hardest. The work runs from discovery through development, manufacturing, quality, regulatory, and clinical, and much of that structure was built when information was expensive to move and slow to trust. Handoffs, review gates, and separations between functions were rational answers to those old limits. When the limits change, those answers should be open to review, not frozen in place because a validated process is easier to leave alone than to rethink. An AI-native biotech does not delete the judgment those gates protect. It asks whether the current shape of the gate is still the best way to protect it. The goal is not a lab that runs itself. It is a company where scientists spend their judgment on the questions that need it.
Native does not mean pulling people out of the loop.
Not every inherited boundary is a relic. Some separations exist because a human has to own a consequential decision, and cheaper intelligence does not change that. Native means being deliberate about which loops need a person, so that when something goes wrong you can still name who owned it. A company that automates faster than it can stay accountable has not become native. It has traded one kind of slowness for a new fragility. And redesign is harder than buying software, because it changes who decides and whose job was built around a constraint that no longer holds. That is why so many leaders choose efficiency and call it transformation. Efficiency threatens no one. Redesign does.
Ask the design question.
Pick a single function and ask it honestly: knowing what these systems can now do, what would we build if we designed this today, and what is actually stopping us?
The gap between those two answers is the work. For the argument this destination rests on, start with The Biotech of Tomorrow.