How LEX Scientific Went Live With QBench in 29 Days

“QBench is in the Goldilocks zone - the right amount of rigidity so that it's predictable and compliant, and the right amount of flexibility to handle all kinds of use cases your developers probably didn't even anticipate.”

Tom Keeling, Lab Manager, LEX Scientific

Overview

When LEX Scientific's long-tenured lab manager retired on short notice, he left behind more than an open position. The laboratory's data management infrastructure - a custom LIMS built in Microsoft Access over 20 years - effectively left with him. This departure resulted in significant difficulties with system maintenance and operation. With an ISO 17025 accreditation audit approaching, the lab needed a qualified replacement on a compressed timeline.

Tom Keeling, LEX Scientific's incoming Lab Manager, had implemented QBench across four prior organizations. After evaluating five LIMS platforms, he selected QBench and led the implementation himself. The lab was fully operational on the new system in 29 days.

This case study documents the conditions, decision criteria, implementation approach, and operational outcomes that made that timeline possible, and what other labs can reasonably draw from it.

The Problem: A Single Point of Failure

LEX Scientific performs environmental testing across a broad range of sample types and client configurations, including radon analysis, polarized light microscopy, and multi-matrix environmental sampling. The lab serves commercial clients, retail channel partners, and facility managers, with some customers generating thousands of individual test submissions annually.

For two decades, all laboratory data flowed through a custom LIMS developed by a single individual in Microsoft Access. When that individual retired earlier than expected, the system became effectively inoperable for any administrative purpose. Report signatures could not be updated. Configuration changes could not be made. Bug fixes required contacting a retired employee.

The operational risk was compounded by a documented compliance exposure. Prior audits had identified deficiencies in three areas central to ISO 17025 accreditation: data traceability, user authentication, and audit trail integrity. ISO 17025, the internationally recognized standard for testing and calibration laboratory competence, requires that labs demonstrate tamper-evident records, documented procedures, and attributable user activity. The existing system configuration did not meet these requirements. The accreditation audit was scheduled and updates to the existing system were not considered viable. The lab could not delay its timeline to accommodate a standard implementation cycle.

The Evaluation: Five Platforms, One Selection Criterion

Tom evaluated approximately five LIMS platforms before making a recommendation to LEX Scientific's ownership. His evaluation framework was shaped by one non-negotiable constraint: the implementation had to be self-directed, complete within weeks, and under the lab's control from start to finish.

Enterprise-tier platforms were assessed and set aside. While technically capable, these systems are architected for vendor-led implementations, typically requiring dedicated IT resources and multi-month deployment timelines. Transferring implementation ownership to a third party was not compatible with the lab's audit schedule.

An open-source LIMS was evaluated on cost grounds. The absence of licensing fees was attractive, but self-hosted deployment introduces sustained infrastructure obligations, including server provisioning, security compliance, portal hosting, and ongoing maintenance, that fall outside the operational scope of a mid-sized environmental testing lab on a compressed timeline.

A startup-stage platform was identified but not selected. The key disqualifying factor: single-vendor dependency. The laboratory was actively replacing a system that had failed precisely because its continuity depended on one person. Selecting a platform with equivalent organizational fragility would not resolve the underlying risk.

One additional competitor presented a competitive case on pricing and entry-level features. Its base tier included capabilities that QBench reserves for higher subscription tiers. However, it did not demonstrate the same combination of structure and flexibility that would be necessary to configure the LIMS to match the lab's prior system as closely as possible. Tom was unwilling to commit to a platform when he could not determine where the boundaries of customization would fall, a decisive risk when replicating an established system on a compressed timeline.

QBench was selected on the basis of demonstrated prior performance. Tom had completed four QBench implementations across different laboratory environments over the preceding decade. He understood the platform's configuration logic, support responsiveness, and behavioral limits under production conditions. That institutional familiarity, not feature comparison, was the determinative factor.

“With QBench, the implementation was entirely in my hands. I knew what to expect from support: I'd hear back within 24 hours, and it would either be solved or I'd have clarity on the issue. That's the kind of predictability you can build a timeline around.”

Tom Keeling, Lab Manager, LEX Scientific

The Implementation: Conditions That Enabled 29 Days

Three factors converged to make LEX Scientific's timeline possible. Each is worth understanding independently, because the absence of any one of them would have extended the project materially.

Factor 1: Prior Platform Experience

Tom had implemented QBench four times across different laboratory environments over the preceding decade. He did not require onboarding, platform orientation, or a learning curve. Configuration work began from a position of established competency, not discovery.

Factor 2: A Constrained, Well-Defined Scope

Rather than designing a new system, Tom made a deliberate decision to replicate the existing one - field labels, report formatting, workflow logic, and output structure - precisely enough that neither staff nor clients would notice the transition. This decision eliminated the most common source of implementation delays: ongoing scope definition and stakeholder alignment. The question of what the system should do was answered on day one.

Factor 3: AI-assisted report building

The legacy system's report templates contained conditional logic, embedded calculations, result-dependent text strings, and date derivations that could not be fully replicated through QBench's visual editor alone. Tom's method: build the structural layout in QBench's visual editor, export the underlying source code, and use an AI assistant to generate the required logic based on plain-language specifications. The AI-generated code was pasted back into QBench and validated against legacy output. This process was repeated across multiple report types without requiring formal programming expertise.

The active build phase required approximately two weeks. Total elapsed time from project initiation to go-live was 29 days, which includes an initial planning period during which Tom assessed configuration architecture before building began.

“I came into the site and looked at their tests and I was kind of blown away. I don't think I've ever seen that many tests created that quickly that are real data in the site.”

Aaron Baer, Implementation Team Manager, QBench

Within weeks of go-live, LEX Scientific had processed more than 2,000 tests in QBench. That volume within that timeframe represented a high-confidence, full-production rollout rather than a cautious or partial adoption.

QBench also delivered capabilities the legacy system had never provided:

• Staff productivity reporting: The laboratory owner had identified productivity visibility as an explicit operational requirement. QBench's reporting infrastructure made this available immediately - workload by staff member, volume over time, order status at any point in the workflow.

• Order management: Follow-up on overdue and near-due orders now runs through automated, system-driven workflows rather than the manual tracking the legacy system required.

• Customer portal deployment: LEX Scientific is preparing to activate the QBench Customer Portal for high-volume clients who currently contact the lab by phone to check on result status. Portal access will give those clients direct, real-time visibility into their submissions and reduce inbound call volume.

• API integration: For channel partners who distribute the lab's testing products through retail and online outlets, LEX Scientific is developing a custom-branded results portal built on QBench's API infrastructure - a separate client-facing experience that operates on top of the QBench platform.

Compliance Outcomes

ISO 17025 requires that laboratories maintain complete, attributable, tamper-evident records of all testing activity. QBench's audit trail functionality satisfies these requirements as a default platform capability.

Every user action is logged, every data modification is attributed, and every result carries a complete chain of custody from sample receipt through final report delivery.

LEX Scientific had no trouble meeting these requirements during implementation, even on short notice. QBench's compliance architecture was not configured specifically for this lab; it reflects design decisions built into the platform for all customers operating in regulated environments.

Tom entered the ISO 17025 audit with confidence in the system's evidentiary integrity. Compliance readiness was a known property of the platform he had selected, not a variable he had to manage.

Ready to See QBench in Action?

LEX Scientific's implementation is one example of what becomes possible when a lab has the right platform, a clear scope, and ownership of its own timeline. Every implementation is different. QBench works with each lab to define an approach that fits their workflows, their team, and their deadlines.