Sound NGS instrument selection is a process problem before it is a product problem, and the labs that get it wrong almost always get it wrong in the same way: they start by comparing instruments. They collect specification sheets, line up the numbers, and let the comparison define the decision. By the time anyone asks what the lab actually needs the data to do, the shortlist has already been shaped by which vendors had the most impressive numbers to put forward, which is not the same question as which instrument fits the work.
This guide lays out a selection process that produces a defensible choice: one you can explain to a finance committee, defend against a vendor’s objection, and live with for the five or more years the instrument will sit on the bench. It stays deliberately on process rather than product. It does not name instruments, rank vendors, or quote prices, because the right instrument depends entirely on your specific requirements, and a generic ranking would only recreate the specification-sheet mistake at a larger scale. For product-level and price-level comparison of specific platforms, follow the cross-links where noted. This article is about how to decide, not what to buy.
Key Takeaways
|
Start From the Application, Not the Instrument
The first document in a selection process is not a specification sheet. It is a written statement of what the lab needs the data to do, in enough detail that it constrains the instrument choice rather than following from it. That statement has to answer a specific set of questions: which applications the instrument will serve, what read length and depth each of those applications requires, how many samples per year and how they arrive across the year, and what turnaround the work demands. None of these are properties of any instrument. They are properties of the science, and they are what a good selection is measured against.
This is also where the coverage and cost work pays off. Knowing the reads and data volume each application actually requires, which you can size with the sequencing coverage and cost calculator, turns a vague sense of "we need a sequencer" into a concrete output requirement an instrument either meets or does not. A selection built on that requirement is defensible. One built on a general impression of capability is not, because a general impression is exactly what vendor marketing is designed to shape.
Platform Classes and Where They Fit
Sequencing instruments fall into broad classes by output, and the class decision is a bigger lever on both cost and fit than any choice within a class. The right class follows directly from the volume and turnaround requirements written down in the previous step. The table below maps classes to the situations they suit, as a process input rather than a product recommendation; specific instruments within each class are compared at the product level in the resources cross-linked below.
Platform Class | Where It Fits | The Trap to Avoid |
Benchtop, low output | Small panels, amplicons, QC runs, low or irregular volume | Outgrowing it fast if real demand was underestimated |
Mid-throughput | Exomes, targeted panels, mid-size cohorts, mixed workloads | Paying for flexibility you do not use if the workload is narrow |
Production-scale | Whole-genome cohorts, high sustained volume, population work | Chronic under-filling if volume does not materialize, which is the most expensive error of all |
Table 1. Platform classes as a process input, mapped to where each fits and the characteristic error of each. The class follows from the volume and turnaround requirements, not from the specification sheet.
The single most common and most expensive class error is buying up: choosing a production-scale instrument sized for hoped-for volume that never arrives, then running it chronically under-filled at a high cost per sample. The economics of why an under-filled large instrument is so costly, and how flow cell size drives cost per sample, are worked through with real figures in the breakdown of what NGS actually costs. Match the class to committed volume, and plan the upgrade path deliberately rather than buying ahead of demand.
Building an Evaluation Matrix
A weighted evaluation matrix is the tool that turns a selection from an argument into a decision. It has two parts: a set of weighted criteria, and a score for each candidate against each criterion. The discipline that makes it work, and the discipline most labs skip, is fixing the weights before any vendor scores are entered. Weights set after the scores are visible are not weights; they are rationalizations, adjusted consciously or not until the preferred instrument wins.
Start with criteria drawn from the application requirements, weighted to sum to 100. A representative set:
Criterion | Weight | Source |
Application fit (read length, depth, output) | 25 | The written requirement |
Cost per sample at our real volume | 20 | Volume and cost modeling |
Turnaround and run flexibility | 15 | The turnaround requirement |
Service, uptime, and support quality | 15 | Vendor evaluation |
Data and informatics ecosystem fit | 10 | Existing infrastructure |
Site and footprint feasibility | 8 | Facility assessment |
Upgrade path and vendor roadmap | 7 | Strategic plan |
Table 2. A representative weighted-criteria set for an NGS platform selection, weights summing to 100. Adjust the weights to your own priorities, but fix them before scoring any candidate.
Now score each candidate 1 to 5 against each criterion, multiply by the weight, and sum. Consider two illustrative platforms: Platform A, strong on application fit and service but more expensive; Platform B, cheaper but weaker on service and ecosystem fit. Under the weighting above, the result is close.
Weighting Scenario | Platform A | Platform B | Winner |
Application-first (Table 2 weights) | 4.13 | 3.88 | Platform A |
Cost-first (cost weighted to 30) | 3.96 | 4.03 | Platform B |
Table 3. The same two platforms, the same scores, two weightings. The winner flips. Illustrative scores; the point is the sensitivity, not the specific numbers.
The Weights Are the Decision Nothing about either platform changed between the two rows above. The only thing that changed was how much the lab decided cost mattered relative to application fit, and that single choice flipped the winner. This is why the weighting cannot be an afterthought and cannot be set after the scores are in. If you weight the criteria first, honestly, based on what the lab actually needs, the matrix makes the decision for you and you can defend it. If you weight them after seeing the scores, the matrix simply launders a decision you had already made, and everyone in the room can tell. |
The criteria that require the most careful scoring are the ones vendors are least forthcoming about: real cost per sample at your actual volume rather than at maximum utilization, and genuine service quality rather than the contract’s stated terms. Both have dedicated treatment ahead. The questions that surface a vendor’s real answers are covered in Evaluating NGS Vendors: The Questions to Ask Before You Sign, and the true cost of ownership behind a service contract is covered in Service Contracts, Uptime, and Total Cost of Ownership for Sequencers.
Running a Demo or Benchmark
For a significant purchase, a specification sheet is a claim, not evidence. A demonstration run on your own samples is how the claim gets tested, and where the stakes justify the effort, it is worth insisting on. The value is not in confirming the instrument produces data; it will. The value is in seeing how it performs on your sample types, at your typical input quality and quantity, with your applications, and how the run fits into a realistic version of your workflow rather than an idealized one staged by the vendor.
Design the benchmark to answer the questions your evaluation matrix scored lowest-confidence on. If real-world cost per sample is uncertain, run a realistic batch and measure the true consumable cost, including any failed or repeated runs. If turnaround is the deciding variable, time the whole process from sample to result, not just the sequencing step. And use the same samples across every candidate instrument, so the comparison is genuine rather than a set of separate best-case demonstrations. A benchmark that only confirms what the specification sheet already claimed was not worth running. One that surfaces a real difference in how two instruments handle your actual work is worth a great deal.
The choice between fundamentally different sequencing approaches, particularly short-read against long-read, is often best resolved this way, because the tradeoffs are specific to the application and the sample. That decision has dedicated treatment in Short-Read vs. Long-Read Sequencing: Which Belongs in Your Lab?.
Contract and Qualification
The instrument decision is not finished when the matrix produces a winner. Two steps remain, and both are where a good selection can still go wrong. The first is the contract, where the service agreement, uptime commitments, response times, and total cost of ownership are negotiated, and where the true multi-year cost of owning the instrument becomes clear in a way the purchase price alone never shows. The second is qualification: the documented installation, operational, and performance checks that confirm the instrument arrived working and establish the baseline you will measure it against for the rest of its life.
Qualification is worth insisting on even outside a regulated setting. Without a documented record of how the instrument performed when it was new and correct, every future disagreement with a vendor about drift or degradation becomes an argument about impressions. With it, the conversation is about data. The full qualification sequence and what each stage should verify are covered in Installation and Instrument Qualification: IQ, OQ, and PQ for Sequencers, and the site and environmental requirements that have to be confirmed before an instrument can even be installed are covered in Footprint, Power, and Environment: Site Requirements for a Sequencer.
Once a platform is selected, contracted, and qualified, the decision rejoins the broader operational picture of running a sequencing program, covered in the manager’s guide to next-generation sequencing in the lab, and the strategic and budget context that should have preceded the whole selection is in the guide to building an NGS program. For product-level and price-level comparison of specific platforms, once your process has defined what you are comparing them against, see NGS Platform Comparison: Which Sequencer Fits Your Lab?.
This article was produced under Lab Manager's AI Editorial Guidelines.
















