The Challenge: Complex Assay Workflows
A single assay can involve pipetting sequences, liquid transfers, reagent distribution, sample preparation, disposable tip handling, mixing, incubation, washing, measurement, and the controlled progression of multiple assay phases. Laboratory automation products must coordinate all of it: scientific knowledge, physical laboratory actions, instrument behavior, and human decisions.
When those parts are not connected through one product experience, the business pays for the gaps: slower change, higher training effort, operational variation, and late discovery of defects.
The Market: Automated Assays in Diagnostics and Life Science Labs
Laboratory automation and liquid handling workstations are used by clinical diagnostics labs, pharma and biotech R&D, contract research organizations (CROs), and academic research centers. Their customers run assays: standardized lab procedures such as ELISA-type immunoassays, nucleic-acid sample preparation, or cell-based tests. Samples and reagents are pipetted into microplates, then incubated, washed, shaken, separated with magnetic beads, and finally measured on a plate reader.
What matters in this market is throughput, reproducibility, walk-away time, reagent cost, and compliance with GxP and IVD regulations. Every failed run means lost patient samples, wasted reagents and disposable tips, and instrument time that cannot be recovered.
Why the Laboratory Automation Product Needed to Evolve
Turning a lab's assay into an automated method traditionally needed specialized application scientists who know both the biology and the instrument scripting in depth. That created four business problems:
- Slow time-to-assay. Setting up a new assay or changing an existing one could take weeks.
- High dependency on scarce experts, which made customer onboarding and scaling expensive.
- Errors found too late. A wrong volume, labware type, or tip choice often showed up only during a run, after reagents and samples were already used.
- Poor portability. Methods were hard to standardize, review, and transfer between labs and sites.
The goal was to let lab scientists describe the assay in their own language (which liquids, which plates, which steps, what timing) and have the system take care of how the instrument executes it. Across the product, the work also aimed to connect the people who define an assay, those who run it, and the teams who maintain and improve the product, and to find workflow and usability problems before they reach customers.
Our Solution: Assay Workflow Design, Instrument Runtime, and Quality Assurance
Assay design. The assay workflow design product gives procedure owners a structured environment to define, organize, review, and export laboratory workflows. It captures the relationships between pipetting actions, labware, reagents, samples, tip handling, assay phases, and the logical conditions that govern a run. Procedures involving transfers, pooling, dilution, incubation, washing, and measurement can be reasoned about as one coherent workflow, so tacit laboratory knowledge becomes explicit and maintainable.
Laboratory execution. The instrument runtime product is where a workflow becomes real activity. It connects assay selection, sample and consumable handling, instrument states, pipetting and liquid transfers, user prompts, maintenance, and reporting into an orchestrated sequence operators can follow with confidence. A well-designed procedure only creates value when it is executed consistently, and that consistency directly drives customer confidence and cost to serve.
Quality assurance. The product is tested through realistic user workflows, not isolated checks alone: creating and editing procedures, configuring assay phases, preparing labware and materials, pipetting and transfer actions, importing and exporting assay files, and recovering from interrupted work. That produces evidence that a change works in the context where customers actually use it.
Inside the Assay Editor: No-Code Assay Authoring for Lab Scientists
The heart of the assay design product is the Assay Editor, a guided, no-code authoring application. It runs in the browser, while the lab's instrument configuration and assay data never leave the customer's premises. It covers the full assay definition:
- Process definition. The assay is modeled as phases made up of drag-and-drop actions: add reagent, transfer liquid, distribute, incubate, shake, wash, capture (magnetic bead separation), measurement, and delay.
- Liquid definition. Input materials such as patient or research samples, reagents, controls, standards, and tagged liquids, including reagents prepared on the deck and before-use actions such as mixing.
- Layout and labware. Microplate layouts with rows, columns, and wells, replicates, blanks, control positions, and the maximum samples per plate, plus multi-cavity labware such as reagent troughs and cartridges.
- Pipetting know-how. Liquid classes, aspirate and dispense cycles, mix definitions, liquid level detection, and disposable versus fixed tips, with settings checked against each tip type's volume limits.
- Parameterized assays. Logical values and lookup tables decide volumes, reagents, and tip usage at run time, so one assay definition serves many test variants.
- Time constraints. Time-critical steps, such as the maximum time between reagent preparation and use, are defined explicitly to protect assay validity and reagent stability.
- Data evaluation. Measurement labels, replicate evaluation (average or median), and blank correction per row or column.
- Built-in validation. Invalid references, missing input materials, wrong step order, or out-of-range volumes are flagged while the assay is authored, before anything reaches the instrument.
- Instrument-aware defaults. The customer's own instrument configuration is imported, so only valid options are offered.
- Ready for global use. The user interface is multilingual.
What Changed Across the Product Lifecycle
- 1 connected product lifecycle: assay definition, operational use, and product verification are treated as one continuous journey.
- 3 connected capability areas: assay design, instrument runtime, and quality assurance support the customer from design through execution.
- More realistic validation: important workflows are exercised the way users experience them, including complex procedure setup and file exchange.
- Greater change confidence: repeatable coverage for important behavior as workflows and capabilities evolve.
- A stronger platform for growth: reusable product knowledge and validation patterns make expansion more manageable.
Efficiency Gains Across Assay Development, Validation, and Support
The business case is strongest across the full lifecycle, not in one isolated activity. Small reductions in authoring effort, handoff time, rework, validation effort, training demand, and operational support add up across every procedure, release, instrument, and customer environment.
- Shorter time to usable product. Clearer authoring means less time clarifying handoffs, so changes reach review and validation sooner.
- Less rework. Procedure owners, product teams, and quality teams work from one coherent representation, so fewer issues surface late.
- Lower validation effort per change. Reusable end-to-end patterns prove established behavior still works, freeing quality time for the highest-value risks.
- Lower cost to serve. Consistent procedures and clearer runtime guidance reduce operator questions, support interactions, retraining, and manual recovery.
Business Value for Laboratory Automation Product Teams
- Shorter assay development and change cycles. Lab scientists configure assays themselves instead of waiting for scripting specialists.
- Lower cost of customer onboarding, and less dependence on scarce application scientists.
- Fewer failed runs. Errors caught at design time save samples, reagents, and disposable tips, and protect instrument uptime.
- Standardized, reproducible protocols that are easier to review, version, and transfer between sites, laying the groundwork for GxP and IVD-regulated workflows.
- One assay definition, many variants, which reduces the number of methods to maintain.
Faster Product Development
Better decisions earlier, faster movement from requirement to usable capability, and less rework from misunderstood workflows.
Consistent Laboratory Work
Less variation between users and sites, the repeatability laboratories expect from automation products.
Lower Release Risk
Workflow, usability, and integration problems are found before customers see them, so change does not weaken trusted behavior.
The approach also strengthens existing product capabilities instead of treating every improvement as a replacement exercise. That protects prior investment and lets the portfolio support more assays, instruments, teams, and customer environments without a proportional increase in delivery complexity.
Where This Experience Applies: IVD, Pharma, CROs, and Lab Software
Our team does not need a ramp-up period to learn the domain. On this engagement, a team of 4 senior software developers works embedded with the client's product owners and application scientists in laboratory automation and life sciences, and we speak their language. This experience applies directly to:
- Laboratory automation and liquid handling manufacturers (OEMs)
- In-vitro diagnostics (IVD) and clinical lab companies
- Pharma and biotech R&D, drug discovery, and screening labs
- Contract research organizations (CROs) and contract testing labs
- Lab software vendors: LIMS, ELN, scheduling, and instrument control software
- Genomics and molecular diagnostics sample-prep providers
The Outcome: A Scalable Foundation for Life Science Products
What began as an effort to improve complex assay workflows became a stronger business foundation for laboratory automation products. By bringing assay authoring, laboratory operation, and quality evidence into one product story, we helped the organization reduce the time and effort needed to create, change, verify, and support complex laboratory workflows.
It shows how our teams help medical device and life science organizations turn complex domain knowledge into dependable, commercially scalable products that create value for customers, operators, and the business.
Prefer a document to share with your team? Download this case study as a PDF ↓