We're building the clinical study operating system.
Clinical research runs on a Frankenstein of EDCs, CTMSs, patient apps, and CSV exports stitched together by humans who could be doing more interesting work. We started Clinstead because we think that's solvable — and because we've been measuring how much time the duct tape actually costs.
Three vendors, one study,
two years of reconciling.
Before Clinstead, we worked across sponsor ops, CRO project management, and platform engineering. The pattern was always the same: one team modelled the protocol, another team collected the data, a third team shipped a participant app, and a fourth team spent the next two years reconciling them.
The reconciliation was the product, not a side effect. Every amendment meant tracing a field change across four schemas and three audit trails. Every inspection meant exporting data from systems that disagreed about the time zone.
We started Clinstead in late 2025 with one bet: if a study has one canonical model — and every surface (design, runtime, participant) reads and writes from that one model — the reconciliation work disappears. Forms become trustworthy by construction. Amendments propagate. Inspectors get exactly what they ask for, the first time.
That bet is the product. SteadFlow, SteadOS, and SteadReach are three best-in-class surfaces on top of one canonical spine. We're early — but the studies running on Clinstead today are already shipping protocols in days that used to take weeks.
Six principles that shape every decision.
Canonical-first, always
Every form, event, signature, and amendment lives in one canonical model. If you find a place where two systems disagree, that's a bug — not a feature of clinical software we accept.
Designed for the regulated world
Auditability, controlled change, reason-for-change capture and role-aware access aren't checkboxes — they're the design constraints we start from. We don't claim certifications we haven't earned.
Built with researchers, not for them
Our team includes people who have run trials and people who have built operating systems. Both kinds of expertise show up in the product.
Agents augment, humans approve
Our agentic operators draft, suggest, and triage at the speed of data. Every action lands with a rationale, and a qualified human approves before anything binds.
Participants are people, not records
If SteadReach feels like a consumer app, that's intentional. Adherence isn't a UX problem you solve once — it's a discipline.
Where the data lives, stays where the data lives
Data residency is a study-level setting from day one. EU stays in EU. UK stays in UK. No tortured workarounds to host a single site outside the chosen region.
Small team. High craft.
We're a deliberately small, multi-disciplinary team: engineers who have shipped regulated software at scale, clinical-ops leads who have run multi-country trials, and a design practice that takes UX in the regulated world seriously. We hire slowly and pay competitively.
Our advisors include people who built EDCs in the early 2000s and who learned, the hard way, what canonical actually means.
Registered in England and Wales. Remote-first across the UK and EU, with regular in-person time in London and Birmingham.
- Founded
- 2025
- HQ
- London, UK
- Working hours
- UK / EU primarily
- Hiring
- Yes — see roles
Want to see what we've built?
Book 45 minutes with the team. We'll wire up a slice of your protocol and show you exactly what changes.