Every LIMS vendor demonstrates well, because the demonstration is run on a configured system by the person who configured it. What decides whether the project lands is narrower than the feature list: how much of the system you are allowed to change yourself, who does the configuration and at whose day rate, what support covers once the project team has gone, and who signs the validation. A shortlist built on those four answers is a short one.
What a lims companies list does not tell you
A directory of LIMS companies sorts on the things that are easy to publish: modules, industries served, deployment options. None of those separate two systems that both tick every box. What separates them is how each one handles the sample types and the workflows you already run, and that only appears when you put your own worklist through it. Ask every vendor to configure one real workflow of yours for the demonstration, with your own sample naming and your own result entry, then compare what each of them had to do to get there.
The lims support you are actually paying for
Support is sold as a share of the licence and described in tiers, so it is worth reading what a tier includes rather than what it is called. There is a large difference between a team that will answer a question about a configuration you built and one that accepts only defects in the shipped product. Ask what happens when something you configured stops working after an upgrade, who is responsible for fixing it, and whether upgrades are included or quoted. Then ask for the response and resolution commitments in writing.
How much lims configuration is included, and who does it
Almost every system is configurable and almost none is configurable by you on day one. The question is which parts are settings, which are scripts, and which need the vendor's own developers. Settings you can change are cheap for ever; a script is cheap once and then a maintenance liability; anything only the vendor can touch is a purchase order every time the laboratory changes. Get that split written down for the workflows you care about before the licence is signed, because the same feature can sit in any of the three.
Reading a lims implementation project plan before you sign
The implementation plan is the most useful document in a sales pack, because it says what the vendor expects of you. Look for how many of your own staff days it assumes, who writes the specifications, who builds the master data, who runs the testing, and what happens to the dates when your analysts are busy with samples. A plan that quietly puts specification and testing on the customer is the usual reason these projects run long, and it is visible before anybody signs.
Which lims modules a small lab turns on first
The module list is priced separately for a reason, and turning everything on at once is how a first phase stalls. Sample registration, result entry and reporting earn their keep immediately. Instrument integration, stability scheduling and inventory are worth having and are better added once the core is in routine use, because each of them needs master data that only exists after the laboratory has been working in the system. Licence what you will use this year and negotiate the option on the rest.
When a lims consultant earns the fee
An independent consultant is worth the money in two situations: when nobody in the laboratory has specified a system before, and when the validation has to satisfy an inspector rather than a manager. Specification is where the saving is largest, because a requirement written badly is paid for at the vendor's change rate for years afterwards. Where a consultant earns least is choosing between two shortlisted products on your behalf, because that choice turns on how your own people work.
The lims portal your clients and auditors will see
If the laboratory reports to external clients, the portal is part of the product rather than an extra. Look at what a client can do without telephoning you: submit a request, see where a sample has got to, download an authorised report, and nothing else. The same question applies to the auditor's view, which should show the trail behind a result without giving anyone the rights to change it. A portal priced per named client is a different cost shape from one priced with the system.
Questions people ask about lims providers
What is LIMS used for?
Recording samples, the tests run on them, the results and who approved them, and enforcing the order in which those things happen. That is the whole of it, which is why the questions that decide a purchase are about your own workflows rather than the feature list.
How long should a first phase take?
Long enough to build the master data and short enough that the people who specified the system are still there to accept it. The variable is rarely the software; it is how quickly the laboratory can agree its own naming, specifications and report layouts, and no vendor can do that for you.
Cloud or on premise?
Cloud unless something specific rules it out, such as an instrument network that cannot reach outside the building or a contractual requirement about where records sit. On premise means you own the upgrades and the backups, and those are the two tasks that quietly decay once the project team has gone.