Choosing a lims system for small laboratories: where a web based lims removes the infrastructure problem, what is lims used for at this size, why simple lims software beats a configuration project when picking lims for small labs, and the lims configuration and lims implementation effort that decides whether it is used

Buying at the size you actually are

1. Prefer a hosted, web based system unless there is a reason not to. A web based lims removes the server, the operating system patching, the database administration and the backup regime, none of which a small laboratory has staff for. The trade is dependence on the provider's availability and a subscription rather than a capital purchase.
2. Count the configuration effort, not the feature list. Ask how long implementation takes for a laboratory your size, who does it, and what it costs. A product configured by a consultant over three months is a different purchase from one a laboratory manager sets up in a fortnight.
3. Decline the regulatory tier you do not need. Electronic signature workflows, full audit trail review and validation packages are necessary for regulated work and pure cost for a research laboratory. Buy the tier your obligations require and no more.
4. Check the instrument interfaces you will actually use. One or two integrations usually cover most of a small laboratory's volume. Ask whether those specific instruments are supported out of the box, because a bespoke interface is a disproportionate cost at this scale.
5. Make adoption the deciding test. Have two of your own staff enter a day's real work during the trial. A system nobody uses is worse than a spreadsheet, and at this size one reluctant user is a large fraction of the laboratory.

Getting your data out again

Ask what an export looks like, in what format, and whether it includes the audit trail. A hosted system whose export is a set of screen reports is a system you cannot leave, and that changes the negotiation at every renewal.

Test the export during the trial rather than trusting the answer. This is the single most useful hour of a hosted software evaluation.

Pricing models and how they bite later

Per user pricing is predictable and penalises occasional users; per sample pricing scales with success and can surprise a growing laboratory. Model both against your realistic growth over three years.

Ask what a support renewal increase has looked like historically. The subscription you sign is not the subscription you will be paying in year four.

Starting small deliberately

Implement sample registration and result entry first, and add inventory, scheduling and reporting once the core is in daily use. Laboratories that configure everything before going live usually go live late and with a system shaped by nobody's real workflow.

Keep the first configuration simple enough that it can be changed. The workflow you think you have is rarely the workflow the system will reveal in the first month.

Common questions

What should a small laboratory look for in a LIMS?

Fast implementation, a hosted option, sensible pricing per user, the instrument interfaces you actually use, and an interface your staff will adopt. Feature breadth matters far less than whether it is configured and used.

Is a web based lims a good idea for a small laboratory?

Usually yes, because it removes the server, the backups and the patching, which a small laboratory has nobody to do. Check the availability commitment, where the data is held and how you would get it out.

Could a spreadsheet do the job?

For a very small operation, sometimes, until two people edit it at once or somebody asks what a result was six months ago. The moment traceability or concurrency matters, a spreadsheet stops being cheaper.

How long should implementation take?

Weeks rather than months at this size. If a vendor's answer is a multi-month project with a consultant, they are quoting their enterprise product and you are being sold the wrong thing.

Browse by service class

• Compare Gene synthesis on advertised prices