A Chemist, a Lawyer, and an Engineer Walk Into a Bar

A chemist, a lawyer, and an engineer walk into a bar. It sounds like the setup to a joke. For me it was a summer evening, in my own backyard, under a canopy, with a drink in hand.

The chemist is a friend of many years, a medicinal chemist by training. He has lived the whole arc of a drug: basic bench chemistry, the clinic, and lately process development, the quiet craft of turning a molecule into something you can actually manufacture. The engineer is his wife. She works at Palo Alto Networks, mid-career and deep in it, on the team that keeps data secure in the cloud. The lawyer is me.

We were not solving anything that night. We were talking about the thing everyone is talking about: what happens when artificial intelligence meets life sciences. And somewhere in the conversation I realized the three of us were the whole story. The science, the machine, and the law. Take any one away and the future we were describing does not get built.

Let me walk you through it.

Start with the machine, because that is where the noise is.

The AI we grew up with was narrow. Think of the old Google search box. One model, one job. Rank the pages, flag the spam, recommend the video. It did not understand anything. It matched patterns. Today's models are different in kind. Train a system on a huge slice of human knowledge to predict the next word, over and over, and something surprising happens. It can write, reason, and code across almost any subject. That knowledge lives in the weights, the billions of numbers set during training. The weights are the asset.

Underneath it all sits a stack. Chips and data centers at the bottom. Foundation models above them. Tools and applications on top. Most companies that call themselves "AI companies" are that top layer, a clever front end built on someone else's model. Easy to build. Easy to replace. Because the value lives one layer down, in the model and the data, and those belong to someone else.

A company that runs on someone else's model, with data that blends into everyone else's, owns almost nothing durable. It is renting its advantage. The winners will own theirs.

That is the whole game, and it is not really a technology question. It is a question of what you own.

Which is where the lawyer earns his seat at the table.

Strip AI of the hype and it runs on old, durable law. Where did the training data come from, and did anyone have the right to use it? That is provenance, and provenance is contracts. Who owns what the model produces? Property and intellectual property. What can cross a border, and what gets you sued when it does? Privacy, licensing, jurisdiction. When people build these systems inside companies, what do they owe, and to whom? The plain old duties of loyalty and care.

None of this is new. The subject is new. The law is not. My foundation has always been transactional law, and transactional law is exactly the right tool for a world where value moves from one bucket to another and someone has to make sure it arrives clean and stays owned. The technology will change every six months. The law underneath it has held for a century. Build on the part that lasts.

Here is what most people miss. In life sciences, data is an asset only if you can legally own it and assign it. Most AI-biotech data is licensed access, not owned. It does not survive a merger or an exit.

Whoever holds the pooled-data rights, and a clean method for proving where the data came from, owns the real thing.

Everything else is packaging.

So what do you actually build?

Not a holding company. Not a handful of startups holding hands. A federation: separate companies sharing one data-and-model layer, with the legal right to pool and cross-use what each of them generates. The structure is the product.

But be honest about the hard part. Two good datasets do not automatically make one better dataset. If they come from different labs, instruments, or patients, pooling them can simply teach a model which company produced the sample, not the biology. The question is never "does everyone have data." It is "does the combined data compose into one loop that compounds." Almost no one asks that before they combine. A lawyer who does is worth his weight.

Then put the three people in the same room. Literally. Palantir did not sell its software over the wall. It sent its own engineers inside the customer to build next to the people who owned the problem. Do that in life sciences: engineers at the bench, next to the biologists, building against real experiments and real data. Then do it again in the conference room, because that is where these ideas actually mature, and where they get monetized. The scientist, the engineer, and the lawyer, at the bench and at the table.

Point all of it at one place first. My choice is metabolic disease.

It is the largest and still-widening market in medicine. And the gaps that matter most, who responds, who keeps the weight off, whose liver actually improves, all turn on long-run human data that no single company legally controls. That is precisely the data a federation is built to assemble and own. The gap in the science and the moat in the law turn out to be the same argument, seen from two sides.

And the frontier keeps going. The hardest question is not what a molecule looks like on paper. It is how it behaves inside a living cell. That is physics and biology at once, and it is where quantum computing eventually earns its place. The least-solved layer is always the most defensible one.

A chemist, a lawyer, and an engineer walk into a bar.

The joke works because we assume they have nothing to say to one another. The truth is the opposite. The next generation of life-sciences companies will be built by exactly these three, at one table, owning their stack, owning their data, and structuring the whole thing so it holds up years later when a buyer's counsel finally comes to look.

Same three people. Same problem. One table.

If that is a table you are trying to build, I would like to hear from you.