Writing a spatial biology business case means translating something your researchers find self-evidently valuable into terms a finance reviewer can test. Leadership is not skeptical about the science. They are skeptical about a number nobody can source, a benefit nobody can measure, and a recurring cost nobody has funded. A good business case removes all three objections before they are raised.
Key Takeaways
|
What Belongs in a Spatial Biology Business Case
Deliver it as two documents. A narrative of two to four pages explains why, what, and how. A separate spreadsheet carries every figure, so a finance reviewer can interrogate the arithmetic without arguing with your prose. Splitting them also means the narrative can be read in five minutes by someone who will never open the spreadsheet, which describes most of the people who will decide.
Section | What It Contains | Primary Reader |
Capability statement | What the lab will be able to do that it cannot do now, in terms of research questions | Everyone. This is the paragraph that gets quoted |
Demand evidence | Named projects, sample counts, grants in preparation, current outsourced spend | Line management |
Options considered | Outsourcing, shared access, and in-house, with why the recommendation wins | Finance and procurement |
Full cost model | Capital, consumables, sequencing, histology, storage, compute, staff, service, across three to five years | Finance |
Value and return | Monetized benefits, directional benefits, and the payback period | Finance and executive |
Risks and dependencies | Analyst availability, storage capacity, facility work, vendor support | Line management and facilities |
Ask | The specific decision requested, and what happens if it is deferred | Approver |
Table 1. Business case structure. The options section is the one most often omitted and the one reviewers most reliably ask for.
The options section matters more than its length suggests. A proposal that recommends purchase without showing that outsourcing and shared access were evaluated reads as a preference rather than a decision. Include the comparison even when the conclusion is obvious, and take the figures from the spatial biology cost breakdown so the numbers in the narrative and the spreadsheet agree. On document construction generally, the guidance in setting up a CapEx business case applies directly.
How Do You Quantify Scientific and Throughput Value?
Not every benefit converts into currency, and pretending otherwise is how business cases lose credibility. Sort the claims into three categories before you write anything, and be explicit in the document about which category each one sits in. Reviewers trust a proposal that admits what it cannot measure far more than one that assigns a dollar value to everything.
Avoided outsourcing spend | Monetize | Already recorded in purchase orders and directly comparable |
Turnaround time reduction | Monetize if it protects a deadline | Convertible when a grant milestone or study timeline depends on it |
Staff time released | Monetize cautiously | Real only if the time is redeployed to funded work, not simply freed |
Grant competitiveness | Directional | Genuine but probabilistic. State it, do not assign a figure |
New collaborations enabled | Directional | Plausible and unprovable in advance. Name specific interested groups instead |
Publication output | Directional, with a lag warning | Lags purchase by years, so a monetized figure invites a bad comparison |
Scientific insight and novelty | Do not claim numerically | Assigning value to this is what makes finance discount the whole document |
Table 2. Sorting value claims by whether they can be defended in currency. The third column is what to say when challenged.
For throughput, resist the temptation to model theoretical instrument capacity. Reviewers who have approved instruments before know that nameplate throughput and realized throughput differ substantially, and a proposal built on the former signals inexperience. Model realized volume instead: the sample counts you gathered as demand evidence, plus a repeat rate. Where the readiness assessment identified gaps, those become costed line items in this document rather than problems to discover after approval.
Grant and Collaboration Revenue
Two revenue arguments are available, and they carry different weight. The stronger one is that the capability is required by work already funded or in preparation. If a submitted or pending grant names a spatial method in its aims, that is a documented commitment, and it converts the request from speculative to necessary. Pull the specific aims language and quote it.
The weaker argument is recharge revenue from serving other groups. It is legitimate, particularly in a core facility setting, but treat it conservatively for three reasons. Recharge rates rarely recover full cost, demand from other groups is a forecast rather than a commitment, and any figure you project becomes a target you will be measured against. Model it at a fraction of optimistic volume, and say in the document that you have done so.
What Cost Avoidance Can You Actually Claim?
Cost avoidance is the most defensible number in the document because it compares a real current expense against a modeled future one. The published rates that make spatial pricing benchmarkable also make this calculation straightforward. Work an example on the figures the Yale Keck Microarray Shared Resource publishes for 10x Visium CytAssist, as of July 2025.
Worked Example: Annual Cost Avoidance A lab currently sends out 80 sections a year. At the Yale internal rate of $2,141 per 6.5 mm section, adjusted by the external academic multiplier of 1.63 derived from published Boston University rates, the effective rate is about $3,490 per section. Annual outsourced spend is therefore roughly $279,000. Running the same 80 sections in-house consumes reagents at roughly $1,674 per section, the figure derived by subtracting Yale’s user-supplies-reagents rate from its full service rate. That is about $134,000 a year in consumables. Gross annual avoidance is approximately $145,000, or about $1,820 per section. That figure is not the return. Capital, facility work, operator time, analyst time, storage, and service contracts all have to come out of it, and at this volume they may well exceed it. What the number does is establish the size of the pool the investment is competing for, which is exactly what a reviewer wants to see first. |
The cost estimator embedded in the cost breakdown linked above will run this same arithmetic on your own volume, rate category, and quoted capital figure, and it reports the annual section volume at which in-house and outsourced costs cross over.
Two cautions. First, use the rate category you would actually be charged, not an internal rate a colleague quoted informally, because the multiplier between them is substantial. Second, do not claim avoidance on samples you were never going to send out. Unmet demand is a real argument for capability, but it is not avoided spend, and a reviewer who spots that conflation will discount everything else in the document.
Presenting to Decision-Makers
The presentation is a different artifact from the document. Four things determine how it goes.
- Lead with the decision, not the background. State what you are asking for and what it costs in the first thirty seconds. Executives who want context will ask for it.
- Translate, do not educate. Approvers are rarely spatial biologists and do not need to become them. One sentence on what the technology does, then straight to demand, cost, and return.
- Show the phasing. A request for a first phase with a decision gate is far easier to approve than a request for a whole program. It also demonstrates that you have thought about being wrong.
- Name your own risks. Raising the analyst gap yourself is disarming. Having it raised for you is not.
The tactics in winning capital budget approval for laboratory equipment investments are worth reading before you present, particularly on engaging stakeholders early enough that the approver has heard about the proposal before it reaches them formally.
Where Do Business Cases Get Rejected?
Rejections cluster into a small number of recurring patterns. Each has a pre-emptive fix that costs nothing but a paragraph.
Objection | What Triggers It | Pre-emptive Fix |
"Who is going to run this?" | No named operator or analyst with allocated time | Name both, with the percentage of their time committed |
"What happens in year two?" | Capital funded, consumables not | Show the three-year model and request the recurring line explicitly |
"Can we not just send it out?" | No options comparison included | Show the outsourced comparison and the volume at which it stops being cheaper |
"Where does this number come from?" | A figure with no source | Cite published rates or your own purchase orders for every number |
"How will we know if it worked?" | No metrics or review point | Define metrics by phase and set the review date in the document |
"Is this the right time?" | Platform generation uncertainty | Address it directly with vendor roadmap conversations, not silence |
Table 3. Common rejections and what prevents them. Most are failures of the document rather than of the proposal.
The pattern across all six is that reviewers reject uncertainty they cannot size, not costs they consider high. A proposal that states its risks, sources its figures, and asks for a bounded first step gets approved at higher rates than a stronger proposal that leaves the reviewer guessing. For how the request fits into overall program sequencing, see Building a Spatial Biology Program: Strategy, Budget, and ROI, and for the operational picture across the whole workflow, the Manager's Guide to Evaluating, Implementing, and Scaling Spatial Technologies. Once the program is running, the measurement framework is covered in Measuring ROI on Spatial Biology Investments: Metrics That Matter.
This article was produced under Lab Manager's AI Editorial Guidelines.









