You have done the validation work. You have run the customer conversations, built the bottom-up model, and navigated the internal review cycle twice. Your VP of R&D still believes in the product. And the honest answer, the one you have not said out loud yet, is that you are not sure whether this is a business case that needs one more iteration or one that was never going to survive this market window.
The Romans had a god for this problem.
Saturn's lesson on premature harvests
Saturn was the god the Romans credited with teaching humanity to farm. Not abundance itself, that was Ceres. Saturn governed the discipline underneath abundance: the reading of seasons, the timing of the sow, the knowledge that effort applied at the wrong point in the cycle produces nothing regardless of its quality. His festival, the Saturnalia, was a reminder of that discipline. The seed planted in the wrong season never germinates, and it costs you the next planting window too.
Product managers (PMs) building business cases for innovative RUO tools are in a Saturnalian position more often than they admit. The question is rarely whether the idea is good. The question is whether you are before the growing season, inside it, or past it, and whether you have the discipline to tell the difference before the organisation makes that call for you.
The case you cannot stop rebuilding
In my experience across RUO innovation pipelines, this is among the most persistent failure modes, and the one least likely to be named directly in a gate review. Teams talk about insufficient data, conservative sales forecasts, or finance people who do not understand the technology. What they do not say is: we rebuilt this case three times, and each time the numbers got a little more convenient.
The planning fallacy is well-documented. Kahneman and Tversky identified it decades ago, and Kahneman's Thinking, Fast and Slow (2011) remains the clearest account: people systematically underestimate costs and timelines and overestimate the probability of success for their own projects, independent of how intelligent or experienced they are. In life sciences product management, this bias gets an institutional accelerator. Robert Cooper, who developed the Stage-Gate framework, noted in Winning at New Products (5th ed., 2017) that kill rates at gates are consistently lower than the data on project outcomes would justify. The process was designed as a go/kill mechanism. In practice, it rewards persistence. Teams that push through uncertainty get funded. Teams that kill early look like quitters.
The result is a business case that has crossed a threshold it cannot come back from. Every assumption has been adjusted at least once. The model reflects what the organisation needs the answer to be. However, the market is telling you something else. What looks like analysis at that point is performance.
The real question is whether you are walking away permanently or stepping back until the season changes. Those are different decisions and they require different moves.
Three tests before you rebuild
There is no single kill trigger for a business case, instead, there is a diagnostic sequence. Running it before you rebuild the case for the third time is the discipline the uncertainty map framework calls for, and the one most PMs skip.
A useful way to read these open questions is to sort them into three types of uncertainty: objective uncertainty (data that cannot exist yet at this stage), epistemic uncertainty (questions the team has not asked), and subjective uncertainty (the PM's own attachment to the outcome). The kill decision almost always involves all three types at once. The trap is treating them as one problem, because each type requires a different response, and applying the wrong one wastes time the case does not have. Subjective uncertainty does not get a dedicated test. It is the reason the other two tests exist. If you were not attached to the outcome, you would have run the diagnostic already.
Test 1: Is the gap objective or epistemic?
Objective gaps are appropriate at every stage. At Milestone 2 (MS2) for a new automated western blot platform, you do not have long-term instrument reliability data under real-world lab conditions, and you are not supposed to. That gap belongs in an assumption log with a resolution timeline. A revenue model is the wrong place for it.
Epistemic gaps are different. They mean the team has not yet asked the right question. A team developing a qPCR reagent optimisation kit for pharma R&D may have solid VOC on assay sensitivity and throughput, and no data at all on how method transfer works between their development labs and GMP manufacturing. That gap is unasked. The team has not yet raised the question, which means it is not staged anywhere in the plan. Those two types of gap require completely different responses.
The case is ready for a structured diagnostic before any kill or fund decision, and that is exactly what Test 2 is for.
Test 2: What does your most resistant buyer object to?
This is where the synthetic buyer panel earns its place as a kill-decision instrument.
A synthetic buyer panel is an AI-powered simulation built from your existing VOC data, persona frameworks, competitive intelligence, and other market inputs. It constructs the strongest possible objection your most resistant buyer would make and pressure-tests your commercial case before anyone else does.
Run the business case against your most resistant synthetic buyer persona. Not your most enthusiastic synthetic early adopter persona. Not your most supportive KOL archetype. Your most resistant synthetic buyer: the QC lab director at a mid-size pharma who has a validated workflow, a risk-averse procurement process, and exactly zero appetite for method revalidation costs.
Either the synthetic buyer panel surfaces an objection you can reframe, meaning the commercial case has a presentation problem, or it surfaces an objection that defeats the value proposition entirely regardless of how it is framed, meaning the case has a structural problem. Those are different situations. They require different responses.
A concrete example: a team building a novel automated sample preparation platform for genomics workflows posed this question to their synthetic buyer panel: 'What would prevent you from adopting this platform in the next budget cycle, even if the throughput data is compelling?'
The core facility director synthetic persona, built from VOC with directors managing 8 to 15 researchers and $300K to $500K annual reagent budgets, responded with a concern the team had not modelled: concordance data requirements. Core facilities adopting new sample prep workflows need to demonstrate concordance with their existing validated methods before they can publish or deliver results to PIs. Generating that data takes 3 to 6 months and requires headcount the facility does not have. The business case had priced the instrument and the reagent consumables, but had not accounted for the adoption cost. That single panel response forced a fork: either reframe the value proposition around concordance support as a bundled service, or identify a first-entry segment where method validation is not a barrier to first purchase. Neither outcome is a failure. Both are better than a gate committee finding it first.
Test 3: Is this a product problem or a timing problem?
Some business cases are sound ideas arriving at the wrong moment. The pain is real, the product is differentiated, and the market is not ready to absorb the switching costs at this point in the adoption curve.
Timing problems look like product problems until you separate them. The signals are specific:
- VOC confirms the pain but not the urgency.
- Early adopters cannot generate mainstream reference customers.
- Competitive pressure exists but has not yet forced incumbent response.
- Required scale is 18 to 24 months away.
A timing problem justifies tabling the case, with a dated re-entry trigger and documented evidence. Tabling is not the same as deferring indefinitely. It means: here is the market condition that changes this case, here is how we will monitor for it, and here is the date when we revisit.
If the synthetic buyer panel surfaces an objection that cannot be reframed, and the timing analysis shows the market is not converging toward resolution, the case has a structural commercial problem. That is a different situation from a timing problem, and the response is a kill decision.
The kill decision framework
The table below maps the five most common signals to their actual diagnosis and the correct response. Use it before rebuilding the financial model.
| Signal | What it actually means | What to do |
|---|---|---|
| You have rebuilt the case more than twice | Inputs are drifting to fit the conclusion, not the market | Stop. Run the synthetic buyer panel before touching the model again. |
| The market signal is real but the timing is off | This is a timing problem, not a product problem | Notify the portfolio management team and table it with a dated re-entry trigger. Document the evidence now. |
| The synthetic buyer panel surfaces an objection you cannot reframe | The commercial case has a structural flaw, not a presentation flaw | Kill it. The synthetic buyer panel just saved you 18 months. |
| Sales will not commit to any revenue number | Two distinct risks are bundled into one unanswerable question: whether the product performs well enough to justify switching, and whether customers will switch even if it does | Break down the risks. The case may still be viable for one of them. |
| You keep changing the strategic rationale | The case is drifting between frames because none of them hold | Pause. The product may be real. The business case is not ready. |
The discipline a kill requires
Saturn's discipline was reading the season correctly and acting on that reading before the window closed. The Romans understood this as a form of courage: the courage to recognise when the cycle has turned and to respond accordingly.
A clean business case kill is a result. Rebuilding the case a fourth time to avoid that conversation is the failure.
The PMs who get this right built the diagnostic discipline to know which question they are actually answering before they open the spreadsheet. The uncertainty map gives you the vocabulary. The synthetic buyer panel gives you the stress test. The kill decision gives you back the next planting window.
The organisation that funds cases it should have tabled is borrowing from the next innovation cycle to dodge an uncomfortable conversation in this one.
Table it with precision or kill it with courage.
Frequently asked questions
Q: How do I run a synthetic buyer panel if I do not have a formal persona framework in place?
Start with what you have. If you have VOC from field application scientists (FASes), sales, or beta users, that is your raw material. The synthetic buyer panel does not require a polished persona document. It requires you to construct the strongest version of the objection your least enthusiastic buyer would make. Write that objection in first person, from their perspective, with the specific context that makes it defensible. Then try to answer it honestly. If you can answer it, you have a presentation problem. If you cannot, you have a structural problem. The panel discipline is the exercise of building the objection seriously, not the formality of the persona document.
If you want to explore building a synthetic buyer panel tailored to your specific product and market, Strivenn offers a free 30-minute PersonaAI consultation. It is a practical conversation, no obligation, and you will leave with concrete next steps. Book your session here.
