Enterprise DNA

Instead of QBench

Stop renting QBench. Own your laboratory system.

We build your version around sample intake, bench work and technical review. We map your QBench exports, bring the agreed records across and run the system with you.

QBench starts at US$16,500 a year for Foundation, US$19,500 for Growth and US$25,500 for Advanced. Each starting plan includes five users.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the annual bill covers

QBench bundles laboratory work into paid tiers

Its published plans charge for workflow, connections and quality management at different levels. Compare those tiers with the work your lab actually needs.

paid

Foundation from US$16,500 a year

The starting five-user plan covers orders, samples, tests, worksheets and reporting.

extension

Growth from US$19,500 a year

The starting five-user plan adds instrument file parsing, a customer portal and inventory management.

verified

Advanced from US$25,500 a year

The starting five-user plan adds quality management, equipment records and billing.

groups

Seats as the team grows

QBench lists volume discounts from ten users and custom Enterprise pricing for fifty or more.

cable

Connections priced separately

Managed third-party and instrument integrations start at US$1,500 a year.

school

Training and migration services

Training is billed upfront. Professional services vary with scope, including migration and custom connections.

Your version

Follow a sample from receipt to review

Intake

Keep the sample and its history together

See what arrived, where it was received and which tests still need assigning.

  • check Sample identifiers, customer and material recorded together
  • check Collection and receipt times remain separate
  • check Custody movements retain the handler and note
  • check Samples without assigned tests appear in the attention list

Bench work

Know what holds up each customer

Compare the work waiting for a measurement with the work waiting for review.

  • check Tests ordered by due date and assigned analyst
  • check Customer totals for overdue and reviewed tests
  • check Failed quality control shown beside recorded limits
  • check Open sample issues carry an owner and due date

Evidence

Keep corrections visible

A corrected value becomes a new result revision. Earlier evidence and reviews remain in the history.

  • check Each result retains its method revision and calibration evidence
  • check A changed result returns to the review queue
  • check Review checks quality control, validation references and calibration dates
  • check Missing collection times and custody records are flagged

Paperwork

Prepare the documents your reviewer needs

Create branded drafts from the same records used in the weekly review.

  • check Draft certificates with values, uncertainty and reviewer details
  • check Sample custody records with recorded movements
  • check Nonconformance records with actions and owners
  • check A read-only weekly view of work, exceptions and customer turnaround

Make it yours

Design your own QBench replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from QBench. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your QBench replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your QBench data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Lab for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Lab for Claude Code

Connected to your own database

Which tests are overdue or waiting for review?

T001

Sample
S001
Customer
Harbour Water Lab Client
Method
PH
Analyst
Aroha
Due_date
2026-10-02
Status
reviewed

T002

Sample
S001
Customer
Harbour Water Lab Client
Method
TURB
Analyst
Aroha
Due_date
2026-10-02
Status
awaiting review

T003

Sample
S002
Customer
Harbour Water Lab Client
Method
PH
Analyst
Ben
Due_date
2026-10-03
Status
awaiting review

T004

Sample
S003
Customer
Southern Materials
Method
SOLIDS
Analyst
Ben
Due_date
2026-10-06
Status
awaiting result

Ask it anything

Ten questions your version answers today

QBench offers configurable reports and analytics. Here these questions are built into the free version and can be changed around your own records.

chat_bubble Which overdue tests still await review rather than a measurement?
chat_bubble Which customers have the most overdue tests in our loaded history?
chat_bubble Which results combine failed quality control and values outside our recorded limits?
chat_bubble Which instruments have expired calibration or missing evidence?
chat_bubble Which sample receipts have no collection time or custody entry?
chat_bubble Which methods have no validation reference?
chat_bubble Which test results were measured outside the recorded calibration period?
chat_bubble Which samples have arrived without any assigned tests?
chat_bubble Who owns each open sample issue and when is it due?
chat_bubble What changed between every recorded revision of a result?

Switching

How to switch from QBench

A move usually involves exporting sample records, mapping your fields and customer names, testing the import, then reconciling records before you switch.

  1. 1

    Export your records

    Use QBench’s documented sample spreadsheet export, and check with QBench what your account allows, usually CSV or Excel. Export the sample records you want to bring across. If you also need tests, worksheets, attachments, signatures, custody records or review history, list those separately. The sample import does not bring all of them across automatically, so they need separate mapping or handling.

  2. 2

    Map and test the import

    Match your QBench customer names and sample headings to the fields in Lab for Claude Code before loading records. Start with a test run of the sample import, using a small set of exported records if that suits your needs. Check that the mapped information lands in the expected fields before importing the full set. Include only the records and history you have agreed to bring.

  3. 3

    Check what the import flags

    Review the test run and note every item the import flags, along with any record you cannot match confidently. Resolve the field or customer mapping where you can, then run the test again. After loading the agreed records, compare them with QBench and investigate warnings or mismatches. Reconcile the records before you rely on Lab for Claude Code for live work.

  4. 4

    Run both side by side

    Keep QBench in use while you check the new setup against your normal laboratory work. For a short period, compare incoming samples, assigned tests, result records and review checks in both systems. Confirm that your team can follow the intended process and that the records you need are available. Agree what counts as a successful comparison before you stop using QBench.

  5. 5

    Switch off QBench

    Once the records are reconciled and the side by side check is complete, make Lab for Claude Code your working system. Tell your team when the change takes effect and keep the exported QBench records you have decided to retain. Do not assume that tests, attachments, signatures or audit history came across with the sample import. Confirm their handling before ending your QBench use.

construction

Where the real effort goes

The main work is usually mapping your own sample fields, customer names and laboratory rules, then deciding which history matters enough to bring and how to handle records the sample import does not cover. You will need time to test and reconcile the chosen records. If Enterprise DNA installs and runs it for you, they handle this mapping and test run as part of the agreed scope.

Not ready for a call?

Get your QBench switch plan by email

We will send you the step-by-step plan for moving your business off QBench, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free version or have your lab’s version built

Open source

Do it yourself

Free code; hosting and agent costs are yours

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Review the sample export guide and test your field mapping
  4. 4 Import your QBench sample export, reconcile it and validate your intended use
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your sample fields, methods, review rules and certificate wording
  • check Your QBench exports mapped and the agreed history brought across
  • check A web front end, barcode capture and instrument connections scoped for your bench
  • check A different technology stack if your laboratory needs one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed, connected and operated through Omni by Enterprise DNA
  • check Access controls, backups and monitoring agreed for your team
  • check Your lab’s validation and rollout supported with evidence
  • check Ongoing changes as methods, customers and workflows change
Book a call

Questions

Instead of QBench, answered

Does the free version replace every QBench module? expand_more

It covers sample records, assigned tests, result revisions, review checks and draft paperwork. We scope instrument connections, customer access, billing and the rest of your workflow around what your lab actually uses.

Can we bring our QBench records across? expand_more

QBench documents sample spreadsheet exports. The free version imports samples from a spreadsheet or CSV after customer and field mapping. Test worksheets, attachments, custody and review history need separate mapping. We agree that scope, do a test run and reconcile the records before switching.

Does this make our lab accredited? expand_more

No. The checks flag missing records and evidence. Your laboratory remains responsible for method validation, competence, accreditation scope and approved report release. Certificates stay marked as drafts, even when a result has a recorded review.

What changes when someone corrects a result? expand_more

The corrected result gets a new revision with its reason and evidence. The earlier value remains visible. A review of the old value does not approve the new one; the latest revision returns to the review queue.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer for the agreed customisation and operation. We review your sample volumes, methods, history and connections with you before setting the scope. The free code has no licence fee; hosting and your chosen assistant have their own costs.

Build around the way your laboratory works

Spend 30 minutes with Sam. Bring your QBench bill, a sample export and the bench workflow you want to change. We will map the version you need and the records to bring across.

Book a call with Sam Get the free version

Lab for Claude Code is free and open source, published by Enterprise DNA.

Done paying for QBench?

Get your version built