Custom software for laboratories

Software for the parts of your laboratory your LIMS doesn't solve. We build and integrate what sits between customer requests, samples, test workflows, results and reports, without forcing you to replace the systems that already work.

For European testing, calibration and diagnostic laboratories. Whether that is a veterinary diagnostic lab removing duplicate sample registration, a calibration lab under ISO 17025 accreditation, or a group bringing a second laboratory into one digital landscape: we have done it before.

Integrate

Connect the systems you already use. LIMS, ERP, CRM, instruments, customer portals, reporting and invoicing, so information moves between them instead of being entered twice.

Modernize

Replace the manual bridges, not everything around them. PDF order forms, spreadsheets, email handoffs, duplicate sample registration and ageing internal applications, one workflow at a time.

Extend

Build the functionality standard software cannot provide. Customer-specific request and sample workflows, quote-to-job handovers, dashboards, automation and the reports your customers actually ask for.

Why laboratories work with us

The labs we work best with are rarely the ones that never digitized. They are the ones whose operations have become too specific for their software landscape to cover cleanly: a LIMS doing its job, a portal covering part of the intake, and people holding the rest together. Here is how we work on what is left.

Compliance is not an afterthought

We've built software for ISO 17025 accredited labs, IVD manufacturers under EU IVDR, and clinical laboratories following ISO 15189. Compliance requirements are part of our development process from day one, not a checklist at the end.

We speak your language

Sample registration, test routing, turnaround time, result validation, traceability, audit trails, certificates and accreditation documentation. We understand the domain because we've worked in it. Our team works in English, German, and Dutch.

Your LIMS is usually not the problem

Most of the friction in a laboratory sits between systems rather than inside them: the request that arrives as an email with drawings and acceptance criteria attached, the sample details typed again on receipt, the report assembled by hand before release. We close those gaps and leave the systems that already work in place. Read our decision guide on when a lab needs a new LIMS versus a better workflow around the current one.

European, long-term partner

Based in the Netherlands, working across Europe. We're not a project shop that disappears after delivery. Our lab clients work with us for years, because regulated software needs ongoing maintenance and evolution.

My first engineering role was at TNO, the Netherlands' largest applied research organization. That's where I learned what labs actually need from software: reliability, traceability, and zero tolerance for data integrity issues.

Sander van Hooft

Sander van Hooft

Founder, Sandorian

Free assessment

State of lab digitization 2026

Where does your lab stand? Benchmark your operations against European testing and calibration labs in 5 minutes. Get a personalized report with actionable recommendations.

Personalized scoreSection breakdownPDF report

Start here

New LIMS or better workflow?

A decision guide for labs that feel friction everywhere but are not yet sure whether the real problem is the core system or the workflow around it.

Read the guide

Labs knowledge base

Practical guides on lab digitization, LIMS implementation, regulatory compliance, and laboratory IT infrastructure.

Does your lab need a new LIMS, or a better workflow around the one you already have?

Many labs assume they need a new LIMS. Often the bigger problem is the workflow around it. Here is how to tell the difference before making an expensive decision.

May 15, 2026

Method version control for laboratories: managing SOP changes without losing traceability

How laboratories can manage method and SOP version changes without losing traceability, reviewability, or training control.

Apr 17, 2026

Instrument calibration and maintenance tracking in ISO 17025 labs

What good calibration and maintenance tracking looks like in ISO 17025 labs, from schedules and evidence to traceability and audit readiness.

Apr 17, 2026

CAPA workflows in laboratory software: from deviation to verified closure

How laboratory software should support CAPA workflows, from deviation logging and investigation through corrective action and verified closure.

Apr 17, 2026

Audit-Ready Lab Software: What It Actually Needs

The practical capabilities audit-ready lab software needs, from permissions and audit trails to validation support, traceability, and review workflows.

Apr 16, 2026

View all articles

IVDR, ISO 17025, ISO 15189, and more

Frequently asked questions

Common questions from lab directors and IT managers exploring software partnerships.

We already have a LIMS. Does that rule us out?

The opposite. An existing LIMS usually means the workflows around it have grown specific enough to be worth building for. Most of our work sits between systems rather than inside them: the customer request that arrives as an email with drawings and standards attached, the sample data entered once in a portal and again on receipt, the reports and certificates going back out, the invoice at the end. This guide on new LIMS vs better workflow explains how we think about that decision.

Do you build LIMS systems from scratch?

Not typically. Most labs already have a LIMS or are evaluating one. We help with LIMS selection, integration with your existing systems and workflows, and custom modules that your off-the-shelf LIMS doesn't cover. When a lab needs something truly custom, like a specialized sample tracking system for veterinary diagnostics, we build that too.

Where do these projects usually start?

Usually at the point where a process still runs on people. A request that has to be turned into a fully specified test job by hand. Sample details typed a second time when the material arrives. A spreadsheet that decides test routing. A report assembled manually before it can be released. We map that stretch of the workflow first, build the smallest piece that removes a manual step, and grow from there.

Which compliance standards do you work with?

We build software that meets ISO 17025 (testing and calibration labs), ISO 15189 (medical labs), IVDR (in-vitro diagnostics regulation), IEC 62304 (medical device software), and GLP/GMP requirements. Our development process includes validation documentation, audit trails, and change control from the start.

Can you work with our existing lab systems?

Yes. We integrate with existing LIMS platforms, ERP and invoicing systems, customer portals, and legacy databases. Instrument connectivity is a different problem: what is possible depends on what the manufacturer exposes, so we scope it honestly up front instead of promising it. In many cases, improving the workflow around the current system creates more value than forcing a full replacement.

How long does a typical project take?

It depends on scope. An integration between two systems that already exist typically takes 3 to 6 months. Connecting a full workflow, from customer request to certificate and invoice, can take 6 to 12 months. We always start with a short assessment phase (2 to 4 weeks) to map your current workflows and define the roadmap.

Do you work with labs outside of Europe?

Our focus is on European laboratories, particularly in Germany, the Netherlands, Belgium, and Austria. We understand the regulatory landscape (EU IVDR, DAkkS accreditation, RvA) and work in English, German, and Dutch.

Let's talk about your lab

An integration between systems that will not talk to each other, a workflow that still runs on email and spreadsheets, or functionality your current software was never going to cover. We can help.

Book a 30-min call