PROVANTIS 13

Provantis is the software thousands of scientists run their preclinical studies on — and it had spent years as a legacy desktop product. I led the design of Provantis 13: taking it from an ageing desktop application to a modern web app, and building the component library, the system, and everything in between that made it possible.

Provantis 13 spans more than a dozen modules, from General Toxicology and Pathology through to Report Assembly and Audit, each with its own dense, regulated workflows.

Designing them screen by screen would never hold together. So the work started in the middle: InstemUX, a single component library that every module is built from. The key considerations on the right shaped how that system was made, built once, consistent everywhere, and ready to scale as Provantis grows.

You don't replatform software like this lightly.

Provantis isn't a side project people open now and then. It's the daily workbench for regulated science, dense, high-stakes, used for hours at a time by people who know exactly how it should behave.

Move that to the web and you can't just make it prettier. Every screen carries years of muscle memory and regulatory weight. Get it wrong and you slow down the people who can least afford to be slowed down.

So the job wasn't a reskin. It was a rebuild, done without breaking the trust the old product had earned.

You can't design an application this big screen by screen. It falls apart.

So before the pages came the system: InstemUX, a full Figma component library built from the ground up, the buttons, tables, forms, patterns, and rules that every screen would be made of. One source of truth, so the product stays consistent as it grows and engineering builds from the same parts the design does.

Design the kit first. Then the product designs itself.

Enterprise science software lives or dies on dense screens, long tables, deep forms, a lot of data on view at once. The easy thing is to design for the showcase. The right thing is to design for the scientist on hour six.

So the components were built for the hard cases first: heavy data, edge states, the screens nobody screenshots but everyone uses.

If it held up there, it held up everywhere.

WHY IT MATTERS

Provantis sits underneath research that has to be right. The science it carries doesn't get a second draft.

A tool like that earns its keep quietly, by being fast, clear, and trusted by the people leaning on it all day. That's the bar a rebuild like this has to clear.