Measuring spatial biology ROI is harder than justifying the purchase, and far fewer labs do it. The platform arrives, the first projects run, and nobody defined what success looked like beforehand. Two years later the program is either quietly assumed to be working or quietly assumed not to be, and neither conclusion rests on anything measured.
Key Takeaways
|
Why Do Most Labs Never Measure Spatial ROI?
Three reasons, and none of them is laziness. The first is that the metrics were never defined, because the business case treated approval as the finish line rather than the starting line. The second is that the data is not captured automatically, so measurement means someone reconstructing scheduling logs and purchase orders retrospectively, which nobody has time for. The third is more uncomfortable: once a large capital purchase is made, nobody involved has a strong incentive to measure it rigorously.
The fix for the first two is mechanical. Define a small metric set in the business case itself, then make sure each number has an automatic source before the instrument is installed. The fix for the third is to set the review date in advance and put it in the document, so the review happens because it was scheduled rather than because someone chose to raise it. The framework for defining those metrics as part of the request is in how to build a business case for spatial biology, and metric selection by program phase is covered in building a spatial biology program: strategy, budget, and ROI.
Utilization and Throughput Metrics
These are the operational numbers, and they matter disproportionately because they are the ones that will be quoted back at you when you ask for the next thing. Keep the set small. Six metrics tracked reliably beat fifteen tracked occasionally.
Metric | How to Calculate | Data Source | Review |
Instrument utilization | Hours run divided by hours available | Scheduling or booking system | Monthly |
Sections run | Count of sections processed | LIMS or run log | Monthly |
Repeat rate | Sections repeated divided by sections run | Run log with outcome recorded | Monthly |
Turnaround time | Median days from sample receipt to data delivered | LIMS timestamps | Monthly |
Scheduling lead time | Median days from booking request to slot | Booking system | Quarterly |
Groups served | Distinct research groups with completed work | Chargeback or project records | Quarterly |
Table 1. A minimum viable metric set. Every row has an automatic data source, which is the criterion for including it at all.
Two notes on capture. Record the outcome of every run, not just that it happened, because a repeat rate is impossible to reconstruct later from a log that only counts runs. And instrument utilization needs a defined denominator agreed in advance: hours available means something different if it includes nights and weekends, and changing the definition later invalidates your own trend. On capturing this data without manual effort, the approaches in this overview of digital monitoring tools for instrument utilization apply directly, and the broader discipline of choosing metrics that drive behavior rather than just describing it is covered in using KPIs to drive improved lab performance.
Scientific Output Metrics
Scientific return is the reason the program exists and the hardest thing to measure on any useful timescale. The trap is reviewing a program on publication count before publication is possible. Papers lag instrument purchase by years, through project execution, analysis, writing, and peer review, so an eighteen-month review on publications will report near zero regardless of how well the platform is running.
Use near-term proxies that move within the first year, and reserve the lagging measures for later reviews.
- Near term: usable datasets delivered, distinct groups served, and projects that reached a decision point they could not previously reach.
- Medium term: grant applications naming the capability, conference presentations, and preprints.
- Long term: peer-reviewed publications, funded grants that cite the capability, and external collaborations initiated because it exists.
State the lag explicitly in the first review document. A program reported as having produced no publications at eighteen months looks failing; the same program reported as on track against a stated two to three year publication horizon looks managed. The difference is entirely in whether the expectation was set in advance.
How Should Cost per Sample Change Over Time?
Less than you think, and this is the most commonly misunderstood part of spatial economics. Most lab operations show real unit-cost improvement with scale. Spatial largely does not, because the dominant cost is a consumable that costs the same whether you run ten sections or a thousand.
Model it with published figures. The Yale Keck Microarray Shared Resource rate card puts reagent cost at roughly $1,674 per section, derived from its full Visium CytAssist service rate less the rate charged when users supply their own reagents. Add two operator hours at $56, $11 histology, four analysis hours per sample across two sections, and a 15% repeat rate. Assume $20,000 of annual fixed cost for a service contract.
Usable Sections per Year | Cost per Usable Section, Capital Excluded | Cost per Usable Section, $500k Capital Amortized Over 5 Years |
40 | $2,679 | $5,179 |
80 | $2,429 | $3,679 |
160 | $2,304 | $2,929 |
320 | $2,241 | $2,554 |
Table 2. Cost per usable section against annual volume. Eight times the volume buys a 16% improvement with capital excluded, but a 51% improvement once capital is being spread.
Why This Matters for How You Argue ROI Going from 40 to 320 usable sections a year, an eightfold increase, improves cost per usable section by only about 16% when capital is excluded. Roughly 93% of in-house variable cost per section run is reagent pass-through, and reagents do not get cheaper with throughput in the way labor and overhead do. Include amortized capital and the same volume increase delivers about 51%. That is the whole point. Scale does not make spatial samples cheaper. It spreads fixed cost across more of them. Which means ROI arguments built on falling unit cost will disappoint, and ROI arguments built on asset utilization, turnaround control, and capability will hold up. |
One consequence worth carrying into any review: a program with low utilization is expensive in a way that no amount of operational efficiency will fix, because the cost sits in idle capital rather than in wasted consumables. That is why utilization deserves more attention than cost per sample, despite cost per sample being the number executives ask for. Full cost category detail sits in the spatial biology cost breakdown, and the volume at which ownership overtakes outsourcing is worked through in in-house vs. outsourced spatial biology. Note that the break-even figures there use a three-year horizon with capital counted in full, so they are not directly comparable to the five-year amortization above.
Building a Simple ROI Dashboard
One page, updated monthly, three panels. Anything longer will not be maintained, and anything maintained irregularly is worse than nothing because the gaps get read as decline.
Panel | Contents | Audience and Use |
Operations | Utilization trend, sections run, repeat rate, median turnaround | You and the lab team. Drives weekly decisions |
Demand | Groups served, booking lead time, project pipeline | Line management. Evidence for expansion or a second instrument |
Financial | Cost per usable section, cost recovery against operating cost, spend against budget | Finance and executive. The annual review conversation |
Table 3. A one-page dashboard specification. Each panel serves a different reader, which is why one blended summary metric does not work.
Two design rules. Show trends rather than snapshots, because a single month tells you nothing and executives will over-read it either way. And annotate the anomalies directly on the dashboard, since an unexplained dip invites a worse interpretation than the real one. On structuring metrics so they connect to objectives rather than floating free, this treatment of KPIs and OKRs for lab managers is a useful frame, and how utilization data should feed retire, reallocate, and reinvest decisions is covered in rethinking ROI for laboratory equipment.
What Does Paying Off Actually Look Like?
Concretely: utilization climbing toward a level you defined as healthy before launch, repeat rate falling as the workflow matures, turnaround stable or improving, more than one group depending on the capability, and cost per usable section settling near the variable floor rather than being dragged upward by idle capacity. Publications and funded grants arrive later and confirm what the operational metrics already indicated.
What it does not look like is a single ROI percentage. Any number that collapses capital, consumables, staff time, scientific output, and strategic capability into one figure has hidden the thing the reader actually needs to know, which is whether the program is working operationally, scientifically, or financially, because those can diverge and each failure requires a different response. Report the three separately and let the reader draw the conclusion. For the operational picture across the full workflow, see the manager's guide to evaluating, implementing, and scaling spatial technologies.
This article was produced under Lab Manager's AI Editorial Guidelines.











