This reading made me think a lot about how the “fit” between a market and a revenue model is less about theory and more about matching how customers actually behave. Isolde’s and Emanuel’s approaches each made complete sense for their own contexts: hospitals under regulation and reimbursement limits versus research institutions driven by prestige, grants, and discovery. The first needed predictability and compliance; the second valued performance and credibility. In product terms, they were building for two different user archetypes, and each shaped their business model around those users’ incentives.
What struck me was that both sides were right, but the merger created confusion across overlapping customers and internal teams. Siiquent’s razor-blade model depends on recurring reliability and service, while Teomik’s thrives on high-margin instruments and flexibility. When merged, it became unclear who was selling what and why. I understand Peter’s instinct to unify the revenue model for clarity, but I also get why Isolde and Emanuel pushed back. Their adaptability was their edge. It reflects a familiar tradeoff in product work: standardizing for efficiency versus staying flexible for market fit.
If I were the PM mediating this merger, I would start by creating a shared view of the customer landscape before debating any structure. I would map each market segment’s journey and identify where each model adds value or friction. Then I would facilitate a workshop that surfaces overlaps, gaps, and tradeoffs across the two models. The conversation should center on customer outcomes and measurable metrics like retention or satisfaction, not on defending legacy processes. After that, I would guide the group through scenario planning to explore what happens under different degrees of integration (unified model, hybrid model, or continued separation) so decisions are grounded in data and empathy, not hierarchy.
What I appreciated most about the case is that it challenges the instinct to equate strategy with uniformity. In practice, different markets often require different pricing, packaging, or delivery methods, and trying to flatten them into one “system” usually creates new problems. I have seen this tension before in product teams that expand across regions or user types. It always comes down to balancing coherence with adaptability.
I am not entirely sure flexibility like this can scale easily, and part of me wonders if it might hide deeper inefficiencies over time. But I like that the case reframes success as building understanding first and structure second. The more aligned people are on who the customer is and what value looks like, the easier it becomes to make the right tradeoffs later.
