No customers yet. So no case studies yet.
LevelSixLabs is in its founding-pilot stage. We could fill this page with plausible labs and invented percentages — plenty of software companies do — but you would have no way to check any of it, and neither would we. Real, anonymised studies will appear here as our first labs finish their pilots, with their permission and their actual numbers.
In the meantime, here is the thing a case study is usually a proxy for: exactly what the first 60 days involve, week by week, and the kind of lab this is built for.
What the first 60 days actually look like
Not a claimed outcome — a description of the process, and of what the product does at each step. If any of it turns out not to match your pilot, tell us and we'll change this page.
- 1
Before day 0
You send an export, we set it up
Whatever you have now — a ChemInventory or Quartzy export, a shared spreadsheet, an asset list from estates — goes in before the first call. Columns are matched automatically and shown to you before anything saves. You arrive at day 0 looking at your own chemicals, not an empty table.
The migration path this uses is the same self-serve importer described on our Switch page.
- 2
Day 0
A short call, then the structure
Rooms, the labs that hold them, who is a lab lead, and the roles: who is an admin, who is staff, who is a student and what each may change. Nothing else. The temptation is to configure everything on day one, and it is the reliable way to lose the second week.
Roles are enforced at the database, not by hiding buttons — so a student account genuinely cannot change what it shouldn't.
- 3
Week 1
Equipment in, and labelled
The instruments go in with their service history and next-service dates. You print QR labels on a standard A4 sheet, stick them on, and scan one with a phone to check it opens the right record. This is the first moment the platform stops being a database and starts being useful at the bench.
Labels print as a Word file laid out for the label sheets you already buy — chemicals and equipment on any plan, samples on Pro.
- 4
Weeks 2–3
Booking goes live, and the arguments stop
Shared kit moves onto one calendar with conflict prevention and, where it matters, a training gate. Expect one awkward week while people find out that the wall calendar is gone. Expect the double-booking emails to stop in the same week.
Overlap is refused by the database as well as checked in the browser, so two simultaneous clicks can't both win.
- 5
Weeks 3–5
The safety records catch up
COSHH assessments get built from the hazard data already sitting on your chemicals rather than retyped. SOPs are loaded and assigned to readers, so you can see who has acknowledged which version. If a near miss happens in this window — and in a real lab, one usually does — it gets filed properly, which is often the moment the value lands for a safety officer.
A filed incident report can't be edited afterwards by anyone, including an admin. The investigation that follows it can be.
- 6
Weeks 6–8
It runs without you watching it
Expiry digests, service reminders and low-stock alerts arrive on their own. The dashboard tells someone what needs them before they go looking. This is the phase that decides the answer at day 60, because it is the first time the system is doing work rather than receiving it.
Reminders run from your own records — nothing to configure, and each person chooses which emails they want.
- 7
Day 60
A decision, with your data either way
You review what changed, and you decide. If you continue, founding members get 25% off their first year. If you don't, you export everything — a full machine-readable export plus spreadsheet and PDF exports of each register — and we delete the account. No notice period, no retention hostage.
The export is a button in your own account, available any time without asking us.
What we'd tell you before you start
- Nothing here is a claimed result. We have no customers yet, so we have no outcomes to report — this is the process, not a promise about yours.
- The slow part is always the data, not the software. A lab with a decent spreadsheet is running in days; a lab starting from a paper folder should plan for the first fortnight to be data entry with help.
- Adoption is the real risk, not features. If the people at the bench don't use it, none of the rest matters — which is why the QR labels and the booking calendar come before the reporting.
- You will find things we haven't built. Our roadmap page lists what's missing on purpose, and pilot feedback is what decides the order.
Want to see the product before any of this? Open the live demo lab — no signup, real data, nothing staged.
The labs LevelSixLabs is built for
Illustrative profiles of the lab types we serve — not specific customers. Real named or anonymised studies will appear here as pilots complete.
University research lab
A PI's group running shared instruments, a growing chemical store and a rotating cast of students and postdocs.
Where it helps
- Chemical inventory with SDS and expiry visibility
- Training-gated booking on shared instruments
- Role-based access for students vs staff
Shared / core facility
A facility whose equipment is booked across multiple groups, where utilisation and fair access actually matter.
Where it helps
- Conflict-free booking across teams
- Utilisation and shared-use indicators
- QR-coded equipment records and fault reporting
University teaching lab
A teaching space with large cohorts, strict safety expectations and equipment that must be accounted for.
Where it helps
- Clear chemical hazard and COSHH-supporting records
- Visitor and access visibility
- Audit-ready records without the paperwork pile
Early feedback, on request
We won't publish quotes we don't have. As founding labs share feedback during their pilots, we can put you in touch with an early tester to hear it first-hand. Just ask.
Ask to speak to an early testerBuilding with founding labs first
We're working closely with our first labs before publishing reviews and case studies. Once those pilots are complete, we'll list verified profiles on G2, Capterra and Software Advice. We won't display badges or ratings we haven't earned — that's the same honesty you'll get from the product.
Want your lab to be one of the first stories?
Founding labs get hands-on setup, 25% off if they continue, and a say in where the product goes next. We'd love to tell your story properly — when there's a real one to tell.