Serious NGS vendor evaluation means interrogating the parts of the deal that are not on the quote. The instrument price is the number everyone focuses on, negotiates hardest, and remembers. It is also, over the life of the platform, one of the smaller numbers involved. A sequencer is not a purchase; it is the entry point to a multi-year relationship in which consumables, service, software, and support will cost far more than the instrument did, and in which switching vendors later ranges from expensive to impractical. The questions that reveal what that relationship will actually cost are the ones a good evaluation puts in writing before anyone signs.
This is a question set, not a ranking. It names no winners and quotes no prices, because the right vendor depends on your applications, volume, and constraints, and because the answers you need are answers about your specific situation that only the vendors can give you. What follows is organized around the risks that a purchase price alone never reveals, and it ends with the discipline that makes the whole exercise work: getting the answers in writing.
Key Takeaways
|
Consumable Lock-In and Reagent Pricing
Most sequencing platforms run on proprietary consumables: flow cells, reagent kits, and library preparation chemistry sold by the instrument vendor and not readily substitutable. This is the single most important commercial fact about owning a sequencer, because it means the vendor sets the price of every run for the life of the instrument, and you have very limited leverage once the instrument is on the bench. The purchase locks in the supplier, and the supplier sets the recurring cost.
The arithmetic makes the point starkly. On representative figures, a program running 1,000 whole genomes a year spends on the order of $3.4 million on reagents over a five-year instrument life, roughly three and a half times a typical production-instrument purchase price near $985,000. The full cost model behind those figures is worked through in the breakdown of what NGS actually costs. The consequence for vendor evaluation is direct: a 10% difference in locked-in reagent pricing over that period is about $340,000, which is almost certainly more than you can move by negotiating the instrument price. The number everyone negotiates hardest is not the number that matters most.
Negotiate the Recurring Cost, Not Just the Sticker Because reagents are proprietary and consumed continuously, the reagent price is where the real money is, and it is where buyers have the least leverage after purchase and the most before it. Ask, in writing, for the current reagent and consumable pricing, the historical rate of price increases over the past several years, and any contractual cap on future increases. A vendor unwilling to discuss reagent price trajectory before the sale is showing you exactly how that conversation will go after it, when you have no alternative supplier and a bench full of samples waiting. |
Platform Roadmap and End-of-Life Risk
Sequencing platforms turn over. The major vendors, spanning the established short-read leaders, the high-fidelity and single-molecule long-read providers, and the newer entrants competing on cost, all release new instruments and retire old ones on cycles that rarely match a buyer’s five-year amortization. An instrument bought near the end of its product cycle can be superseded within a year or two, which affects resale value, long-term reagent availability, and how much of the vendor’s development attention its software and chemistry continue to receive.
You cannot get a guarantee about the roadmap, and a vendor cannot honestly give you one. What you can ask for is the relevant history and the current commitments: how long the vendor has supported previous-generation instruments after releasing a successor, whether reagents for older platforms remain available and at what pricing, and what the stated support horizon is for the specific instrument you are considering. A vendor with a track record of supporting older instruments for years is a different risk from one that discontinues support quickly, and that history is knowable before you buy.
Support, Response Times, and Parts
An instrument that is down is not producing data, and for a program with turnaround commitments, downtime is the risk that turns a good year into a bad one. The headline specifications say nothing about how quickly a broken instrument gets fixed, and that is the number that determines your real, delivered throughput. Support quality is where the difference between two similarly specified platforms most often actually lies.
The questions worth asking in writing are specific: what is the guaranteed response time for a service call, and is it business hours or around the clock; are field service engineers located within reasonable reach of your site or flown in; what is the typical time to resolution for a major fault, not just the time to first response; are critical spare parts held regionally or centrally; and is a loaner or backup arrangement available for extended outages. Vague assurances of excellent support are worth nothing. Specific, contractual response and resolution commitments are worth a great deal, and the full treatment of service agreements and their true cost is covered in Service Contracts, Uptime, and Total Cost of Ownership for Sequencers.
Training and Applications Support
A platform your team cannot run confidently is a liability regardless of its specifications, and the gap between a successful installation and a productive one is usually training. Ask what training is included with the purchase and what costs extra, whether it covers both the bench workflow and the analysis pipeline, whether it is delivered on your instruments and your samples or in a generic setting, and what ongoing applications support is available when a new assay or a difficult sample type comes up months later.
Applications support deserves particular attention because it is where the vendor relationship either earns its cost or does not. The first time a run fails for reasons the team cannot diagnose, responsive applications support is the difference between a day’s delay and a week’s. Ask how applications support is delivered, what it costs, and, when you call reference customers, ask them specifically how good it actually is, because this is the area where the gap between the sales promise and the delivered reality tends to be widest.
Reference Customers Worth Calling
Every vendor will offer reference customers, and every offered reference will be happy. That does not make them useless; it makes the selection and the questions matter. Ask for references running your applications at a similar scale, not just any satisfied customer, and ideally find one or two the vendor did not hand you, through your own professional network, since an unmanaged reference speaks more freely than a curated one.
The questions to ask a reference are the ones the vendor will not answer straight: how the instrument’s real-world uptime compares to what was promised, how quickly service actually responded to a serious fault, whether reagent pricing has risen since purchase and by how much, how good applications support really is when something goes wrong, and the single most useful question of all, whether they would buy the same platform again knowing what they now know. A reference who hesitates on that last question has told you something the specification sheet never would.
Questions to Put in Writing
The discipline that makes this entire exercise worth doing is simple and constantly neglected: get the material answers in writing, in the contract or an appendix to it, not in a sales presentation. A commitment that lives only in a meeting or an email from a sales representative who may have moved on by the time you need it is not enforceable and, in practice, not reliable. The table below maps the questions to the risk each one addresses, as a starting checklist to adapt to your situation.
Question Area | What to Get in Writing | The Risk It Addresses |
Reagent pricing | Current pricing, recent increase history, and any cap on future increases | Runaway recurring cost after lock-in |
Roadmap and support horizon | Stated support duration for this instrument; older-platform support history | Being stranded on a discontinued platform |
Service response | Guaranteed response and resolution times; parts and engineer location | Downtime that destroys delivered throughput |
Training | What is included, what costs extra, bench and analysis coverage | A platform the team cannot run confidently |
Applications support | How it is delivered, what it costs, response expectations | Prolonged delays when a run fails |
Total commitment | All verbal commitments captured in the contract or an appendix | Promises that evaporate after signing |
Table 1. A risk-mapped vendor question set. Each row pairs what to secure in writing with the specific risk it addresses. Adapt to your applications and constraints, and treat "in writing, in the contract" as the standard for anything material.
These questions feed directly into the weighted evaluation and the business case that justify the purchase. The structured selection process they support is covered in the Guide to Choosing an NGS Platform, and the way these cost commitments belong in the capital request is covered in How to Build a Business Case for an NGS Instrument. The broader operational context, once the vendor is chosen and the instrument is running, is in the Manager’s Guide to Next-Generation Sequencing in the Lab.
This article was produced under Lab Manager's AI Editorial Guidelines.















