Different Markets
Isolde’s Siiquent targets hospitals and diagnostic labs, which are institutions drowning in regulatory requirements and operating under fixed insurance reimbursements. Isolde’s razor-blade model makes perfect sense to me, as it sells razors cheaply and profits from the blades. Hospitals cannot simply purchase reagents from anyone, but Siiquent provides them for free while making customers more dependent on their consumables. It’s also smart to have the pay-per-test innovation, generating more revenue for hospitals rather than making it a cost center.
On the other hand, Emanuel’s Teomik targets research labs and universities. It’ll be customers chasing Nobel Prizes and publications, rather than worrying about regulatory frameworks. His model almost flips Siiquent’s approach, as it sets high prices for proprietary research instruments with strong profit margins, while remaining flexible about whether customers purchase consumables from them or cheaper alternatives.
So Isolde served customers who valued regulatory guidance and support, whereas Emanuel catered to customers who demanded prestigious instruments yet had the flexibility to purchase consumables from lower-cost sources.
Pros and Cons
Based on the case study, implementing a single revenue model helps eliminate customer confusion when sales forces present different offers, enables effective cost control, and prevents unintended consequences like the moral hazard from pay-per-test pricing. However, a rigid structure can risk market inflexibility, potentially missing innovations that emerge from customer feedback and preventing quick responses to competitive threats. It may also frustrate experienced managers and fail to address the distinct needs of different customer segments (hospitals vs research labs).
Conversely, continuing the flexible approach enables rapid market responsiveness and makes it more customer-focused, allowing tailored solutions that build loyalty. Both units thrived using adaptable strategies, and this flexibility empowers employees to innovate. But, without a coherent structure, the business can suffer from strategic drift and internal confusion as sales teams contradict each other. Hidden costs can pile up through reactive changes, and the missing of a clear profit logic can hinder performance evaluation.
As a star PM
I’d hope to design a process that forces Isolde, Emanuel, and Peter to collaborate toward a solution they all own. First, I’d establish a shared reality through joint customer interviews, where both Isolde and Emanuel hear directly from confused customers. Then, we would collaboratively map customer segments to identify overlaps and divergences (focus on agreed-upon facts rather than premature consensus). Second, I’d facilitate constraint mapping sessions where each leader articulates their non-negotiables and documents Scherr’s financial requirements, which can mark boundaries for acceptable solutions. Third, rather than theorizing, I believe it’s essential to conduct controlled pilots that test different revenue approaches across regions. For instance, one uses a razor-blade model, another focuses on instrument pricing, and a third employs a hybrid approach. Then we track revenue, customer satisfaction, sales force confidence, and operational complexity to let data take precedence over opinions. Finally, with pilot results in hand, I’d promote a structured decision process that incorporates collaborative criteria, such as customer impact, profitability, operational feasibility, etc. The key would be to create a process grounded in customer data rather than legacy preferences.
