The difference in Siiquent’s and Teomik’s business model reminded me a case study we read for my BUSGEN105 class, where we analyized two existing companies’ strategy, one was focusing on quantity with low-margin over quality, the other was targeting affluent individuals to get high-margin and sells quality goods instead of producing a lot. Similarly, Isolde’s Siiquent targets hospitals and laboratories with essential testing materials and reagents—products that need constant replenishment, operating with a classic razor-blade model. For them, even it offers low margin, this creates stable, recurring revenue and fosters long-term customer relationships, which I personally find appealing because it aligns with their target market’s requirement for reliable, consistent supplies that are critical for daily operations. In contrast, Emanuel’s Teomik’s business model, driven by high-margin machine sales, targets larger buyers, such as government labs and large hospitals, willing to make significant capital investments upfront. Their model also well aligns with their target market as Teomik’s customers are focused on quality, performance, and reliability, and are willing to pay a premium for advanced technology.
Imposing a single revenue model would simplify operations, allowing for cost savings through a streamlined sales force and integrated distribution channels. The company could present a unified front to its customers, reducing confusion and ensuring a more consistent customer experience. A single model could also create economies of scale, as merging the two sales teams could reduce overlap and inefficiencies. However, I have also read news where the higher-ups wanted to unify the revenue models of two distinct divisions. The idea was to streamline operations and cut costs, which sounds great in theory. Applying it to Siiquent-Teomik could simplify things like the sales force and customer experience. But in my opinion, forcing a single revenue model can backfire. In that merger I read, they actually saw customer satisfaction drop because the unified model didn’t meet the specific needs of different customer segments. For Scherr, making Siiquent adopt Teomik’s capital-intensive model could alienate customers who appreciate the affordability and convenience of consumables. Conversely, applying Siiquent’s consumables model to Teomik might dilute the value of their high-end equipment. I believe flexibility is key. Companies that allow different models to coexist often do better because they can effectively serve diverse market needs. They can even use this hybrid business model to their competitive advantage. I’ve seen organizations thrive by maintaining distinct strategies under one corporate umbrella, as long as there’s clear communication and shared goals. For example, the large companies we know, specifically Microsoft also has hybrid model that combines one-time sales like software licenses with recurring revenue from cloud services and subscriptions.
If I were to be PM assigned to navigate merging process, I would follow very data-driven and customer centric process and ensure that both merging sides are heard and that a viable, mutually agreeable solution is reached. Firstly, I would focus on defining our objectives clearly: are we trying to reduce costs, improve efficiency, or unite sales forces. Also, I would make sure to set boundaries on what we can be flexible or not, because from what I learned in my BUSGEN105 class, preserving company values and culture is important. For our specific Siiquent-Teomik case, I’d facilitate a meeting with Isolde and Emanuel to define what success looks like. We’d set clear objectives that respect both divisions’ strengths, like expanding market share or boosting profitability, without sacrificing what makes each division successful. Secondly, I’d organize sessions where both leaders present their business models in detail. Understanding each other’s operations can build mutual respect and open doors to innovative solutions. Drawing from my past work experiences in different companies, I’d encourage brainstorming sessions focused on synergy. For instance, could we bundle Teomik’s machines with Siiquent’s consumables in a way that adds value for customers? However, thirdly, before we decide on a strategy, I would do tests like piloting the proposed changes. This lets us test our assumptions and tweak things based on real-world feedback. In any of my past projects, even if it was school project, piloting helped us avoid mistakes in case it doesn’t resonate with customers as expected. Lastly, I would always collect customer feedback to understand their needs and with team, we would do regular updates and feedback loops to catch issues early and keep everyone on the same page. In my experience, this kind of transparency always built trust and made any process smoother.
