Company
We build laboratory software for the labs that run regulated studies, one deployment at a time.
Every CRO we talked to was running a LIMS that fit somebody else's lab. The gap got closed by spreadsheets, share drives, and a person whose real job is knowing where things are. That work is invisible until a study is late or a data set is short.
The reason nobody fixed it is cost. Software shaped around one lab has always meant a custom build, and a custom build in a GLP setting means a validation effort that nobody can afford twice. So labs bend to the template instead.
Agents make the expensive half cheap. Agentic testers produce the validation package, so a system built for one lab can be qualified without a year of manual protocol writing.
That is the whole bet: not that AI writes your reports, but that it collapses the cost of proving software correct — and once that cost falls, software can finally fit the lab instead of the other way round.
One deployment per customer, in its own repository. Your lab's shape lives in your codebase, and you upgrade on your own schedule. Nothing we ship to another lab lands in your system without you taking it.
We replace rather than sit alongside. A LIMS that covers part of the work leaves you running two systems and reconciling between them, and we would rather do less for fewer labs than be the second place to look.
Because each customer runs its own deployment and its own repository, the code you depend on is code you hold. That is deliberate, and it is the answer to the question every small vendor gets asked.
We would rather be judged on a real deployment than on a deck. If you run studies for sponsors, we will show you the system with study data in it.
Why we started
What changed
How we build
What depending on us looks like
This page is short on the ordinary details — who we are, where we sit — because we have not settled how to say them. They will be here rather than implied.
Write to hello@vsqrd.com.
Getting in touch