This case reminds me of the Daimler-Chrysler merger, where two successful companies struggled to merge their distinct business models and strategies. Daimler focused on premium, high-cost vehicles, while Chrysler thrived on mass production. The failure to reconcile these differences eventually led to the collapse of their merger. Similarly, in the case of Siiquent and Teomik, we see two business units with distinct revenue models that cater to different markets, and the challenge is how to align them effectively.
Isolde’s Siiquent targets hospitals and diagnostic labs, utilizing a “razor-blade” model—selling diagnostic machines at low margins but generating recurring revenue from the consumables needed for testing. This model works well in a price-sensitive market, where initial capital investments are a hurdle, but continuous consumable purchases are necessary. On the other hand, Emanuel’s Teomik serves research institutions, selling high-margin scientific equipment, with less dependence on consumables.
The debate between imposing a single revenue model and maintaining flexibility is crucial. A single model could streamline operations and create consistency across the company, improving internal efficiency and customer understanding. However, it risks alienating one of the target markets, limiting flexibility, and potentially reducing the company’s overall competitiveness and market reach. Maintaining flexibility, on the other hand, allows each unit to respond to its market’s specific needs but could lead to internal confusion, inefficiencies, and misaligned strategies.
If the CEO mandated the merger, my role as a product manager would be to facilitate a process that fosters collaboration rather than force a premature solution. The first step would be aligning the department heads on shared business goals. Rather than focusing on revenue models, I would ask Isolde and Emanuel to identify their common objectives, such as customer satisfaction and operational efficiency. This would help create a collaborative environment and shift the conversation away from a binary choice between two models.
Next, I’d gather data to objectively assess the performance of each model in their respective markets, including metrics such as LTV. By analyzing customer needs, buying patterns, and profitability, we could identify where each model works best and where they overlap. This data-driven approach would help ensure that the decision is grounded in market realities rather than personal preferences.
I would also encourage them to explore hybrid revenue models. For example, could Siiquent’s consumable-based model be applied to certain research markets? Or could Teomik’s machine-focused approach work in larger hospital labs? By testing these ideas in different customer segments, we could experiment with a tailored approach rather than forcing a rigid structure.
Lastly, I’d streamline the process with a roadmap for integration, establishing clear roles, timelines, and accountability for both teams. This ensures the merger progresses smoothly and both units remain aligned on their shared goals.
