The Great Business Model Debate: Why Software Companies Are Doomed If They Can't Reconcile Product Strategy, Revenue Logic, and Customer Value
This is a review blog based on three studies/articles I was introduced by Professor Gladys Mercier. My intention in writing this was to first summarize my learnings, find similarities and also find critical arguments that might create an argument between different aspects of these studies.
References
"A Framework for Analyzing Software Business Models" by Risto Rajala, Matti Rossi, and Virpi Kristiina Tuunainen (source)
"What Is a Business Model?" by Andrea Ovans (Harvard Business Review) (source)
"The Product Strategy Defined" by Roman Pichler (source)
Abstracts
A Framework for Analyzing Software Business Models
(Risto Rajala, Matti Rossi, and Virpi Kristiina Tuunainen)
This study explores the concept of business models in the context of software businesses, aiming to develop a framework for analysis. The authors employ a case study methodology with a grounded theory approach, conducting interviews with experts and management from selected case companies. The research identifies four key elements of software business models:
Product Strategy
Revenue Logic
Distribution Model
Services and Implementation
The framework provides a holistic view of the essential aspects of software businesses, considering factors such as the competing environment, customers, resource environment, and financing. The authors argue that this framework can help both researchers and practitioners understand and analyze the bounded variations between different software businesses.
The paper concludes by positioning the business model as a manifestation of business strategy and emphasizes the need for further research into analyzing specific software companies, products, and business networks. This framework contributes to the understanding of how software companies create and capture value in the dynamic and networked software industry.
What Is a Business Model?
(Andrea Ovans, Harvard Business Review)
In this article, we discuss a comprehensive overview of the concept of business models, synthesizing various definitions and perspectives from business literature. Ovans explores how the term has been used and defined by different scholars and practitioners, from Michael Lewis's simple "how you planned to make money" to more complex frameworks like Alex Osterwalder's Business Model Canvas.
The author discusses key components of business models, including:
Value proposition
Customer relationships
Revenue streams
Cost structures
Ovans also examines the relationship between business models and strategy, highlighting Joan Magretta's distinction that a business model describes how a business runs, while strategy explains how to do better than rivals.
Throughout the article, Ovans presents different approaches to business model innovation, signs of failing business models, and methods for creating new ones. By providing this broad perspective, the article serves as a valuable resource for understanding the evolution and importance of business models in modern business thinking.
The Product Strategy Defined
(Roman Pichler)
This article focuses on defining and explaining the concept of product strategy within the broader context of business models and product management. Pichler argues that an effective product strategy is crucial for realizing a product vision and achieving business goals. He identifies three key elements of a product strategy:
The target market and user needs
The product's key features and differentiators
The business goals
Pichler introduces the Product Vision Board as a tool for capturing and communicating product strategy. He emphasizes the dynamic nature of product strategy, discussing how it should evolve through different stages of the product lifecycle, from launch to product-market fit and beyond. The author places product strategy in relation to the product vision and roadmap, illustrating how these elements work together in product development and management.
The article concludes by highlighting the importance of regularly reviewing and adjusting the product strategy to ensure continued product success and alignment with business objectives. Pichler's practical approach provides valuable insights for product managers and businesses seeking to develop and maintain effective product strategies.
Key Concepts in Product Management and Business Models
Product Strategy: The overarching plan that guides the development and lifecycle of a product. It encompasses the product's vision, goals, target market, and competitive positioning. A well-defined product strategy helps teams make informed decisions about feature development, resource allocation, and market approach. It aligns the product's direction with the company's overall business objectives and ensures that all product-related activities contribute to achieving these goals.
Revenue Logic: The framework that describes how a product or service generates income for the company. This includes pricing models (e.g., subscription, one-time purchase, freemium), revenue sources (direct sales, licensing, advertising), and strategies for maximizing revenue (upselling, cross-selling). Understanding revenue logic is crucial for product managers to ensure the product's financial viability and contribute to the company's profitability.
Distribution Model: The method by which a product or service reaches its end users. This can include direct sales, partner networks, online platforms, or physical retail channels. The choice of distribution model significantly impacts a product's market reach, customer acquisition costs, and overall success. Product managers need to consider factors such as target market, product complexity, and support requirements when determining the most effective distribution strategy.
Services and Implementation: The additional offerings that complement the core product, including customer support, training, customization, and integration services. These elements are critical for ensuring customer success, particularly for complex or B2B products. Product managers must consider the full spectrum of services required to deliver value to customers and factor these into the overall product strategy and resource planning.
Value Proposition: The unique benefit or solution that a product offers to its target customers. It articulates why customers should choose this product over competitors' offerings. A strong value proposition is essential for product differentiation and marketing effectiveness. Product managers must continually refine the value proposition based on customer feedback, market trends, and competitive landscape.
Customer Segments: Distinct groups of customers with similar needs, behaviors, or characteristics that a product targets. Identifying and understanding customer segments helps in tailoring product features, marketing messages, and support strategies. Product managers use customer segmentation to prioritize development efforts and ensure the product meets the specific needs of its target users.
Channels: The various touchpoints and methods through which a company interacts with its customers, including marketing, sales, and support channels. These can be direct (company website, sales team) or indirect (partners, resellers). Effective channel management is crucial for reaching target customers, delivering the product, and providing ongoing support. Product managers need to ensure that the product strategy aligns with and supports the chosen channels.
Key Resources: The critical assets, both tangible and intangible, required to develop, deliver, and support the product. These may include technology infrastructure, intellectual property, human resources, or partnerships. Identifying and securing key resources is essential for product success. Product managers must work closely with other departments to ensure these resources are available and effectively utilized throughout the product lifecycle.
Market: The total addressable group of potential customers for a product. Understanding the market involves analyzing its size, growth potential, competitive landscape, and trends. Product managers use market analysis to inform product strategy, identify opportunities, and assess the product's potential for success.
Needs: The specific problems, desires, or requirements of customers that a product aims to address. Identifying and prioritizing customer needs is fundamental to product management. It drives feature development, informs the product roadmap, and ensures that the product delivers real value to its users. Product managers must continuously gather and analyze customer feedback to stay aligned with evolving needs.
Key Features and Differentiators: The core functionalities and unique aspects of a product that set it apart from competitors and deliver value to customers. Identifying and developing key features is a critical task for product managers. They must balance customer needs, technical feasibility, and business objectives to create a product that stands out in the market and meets user expectations.
Business Goals: The specific objectives that a product aims to achieve for the company, such as revenue targets, market share, customer acquisition, or strategic positioning. Aligning product development with business goals ensures that the product contributes to the company's overall success. Product managers must translate these high-level goals into actionable product strategies and measurable outcomes.
Dynamic Nature of Business Models and Their Relationship to Business Strategy
Dynamic Nature of Business Models
Business models are not static constructs but dynamic entities that evolve over time. This dynamic nature is crucial for businesses to remain competitive and relevant in changing market conditions.
Evolution with Product Lifecycle: Rajala, Rossi, and Tuunainen highlight that business models change as products grow and mature. They identify key events in the product lifecycle that often trigger business model adjustments:
Launch
Product-market fit
Sustained growth
Rejuvenation or decline
Regular Review and Adjustment: Pichler recommends reviewing and adjusting the product strategy (a key component of the business model) on a regular basis, suggesting quarterly reviews as a rule of thumb. This regular reassessment ensures the business model remains aligned with market realities and company goals.
Signs of Business Model Obsolescence: Ovans, citing Rita McGrath, points out several indicators that a business model may be losing its effectiveness:
Innovations to current offerings create smaller and smaller improvements
Difficulty in conceiving new improvements
Customers are increasingly finding new alternatives
Adaptation to Market Changes: All three sources implicitly or explicitly acknowledge that business models must adapt to changes in the market environment, including shifts in customer preferences, technological advancements, and competitive pressures.
Innovation in Business Models: Ovans discusses the concept of business model innovation, suggesting that introducing a better business model into an existing market can be a form of disruptive innovation. This highlights the potential for companies to gain a competitive advantage through business model changes.
Flexibility in Software Business Models: Rajala, Rossi, and Tuunainen's focus on software businesses underscores the particular need for flexibility in this rapidly evolving industry. The networked nature of software businesses requires adaptable business models that can respond to changes in the ecosystem.
Relationship to Business Strategy
Business models and strategy are closely connected, with each one influencing and shaping the other. Together, they guide how companies create, deliver, and capture value.
Business Model as Strategy Implementation: Rajala, Rossi, and Tuunainen position the business model as a manifestation or implementation of business strategy. They suggest that the business model is derived from and should align with the broader business strategy.
Distinction between Model and Strategy: Ovans, citing Joan Magretta, makes a clear distinction:
Business Model: Describes how a business runs
Competitive Strategy: Explains how to do better than rivals
Business Model as a Component of Strategy: Pichler's approach suggests that product strategy (which can be seen as part of the business model) is a component of the overall business strategy. He places product strategy in the context of a broader vision and business goals.
Strategy Informing Business Model Choices: All three sources imply that strategic decisions inform the choice and design of business models. For example, a strategy focused on cost leadership would lead to different business model choices than one focused on differentiation.
Business Models Enabling Strategy: The documents suggest that innovative business models can enable new strategic possibilities. For instance, a novel business model might allow a company to enter new markets or compete in ways previously not possible.
Alignment of Model and Strategy: There's a consensus across the documents that for a business to be successful, its business model must be aligned with its overall strategy. Misalignment can lead to inefficiencies and missed opportunities.
Iterative Relationship: The dynamic nature of business models implies an iterative relationship with strategy. As business models evolve in response to market changes, they may inform adjustments to the overall strategy, creating a feedback loop.
Strategy as a Guide for Model Evolution: Pichler's emphasis on product vision guiding product strategy suggests that higher-level strategic goals should guide the evolution of business models over time.
In the end, what have we learned from all this business model talk? Well, it's clear that running a successful software company isn't just about having a great product. It's about finding the right mix of product strategy, money-making plans, and customer value. These big-shot researchers and experts (they really are big shots) might use fancy words, but they're all saying pretty much the same thing: you've got to stay on your toes. The tech world moves fast, and your business model needs to keep up. There's no ‘one size fits all’ solution. Every company's got to figure out its own special sauce, mixing and matching different pieces to create something that works for them and their customers. So, if you're in the software game, keep your eyes open, listen to your customers, and don't be afraid to shake things up when you need to. That's how you will stay in the game and maybe even come out on top.
Disclaimer: The content of the blog is just my summarization of the original knowledge provided by a few notable people mentioned below I am a non-native English speaker, and hence, I have used multiple GenAI tools to correct the Grammar and sentence framing of the blog to make the reading experience smooth and error-free.
Notable people mentioned in these studies and papers:
Risto Rajala
Co-author of "A Framework for Analyzing Software Business Models"
Affiliation: Department of Information Systems Science, Helsinki School of Economics
Matti Rossi
Co-author of "A Framework for Analyzing Software Business Models"
Affiliation: Department of Information Systems Science, Helsinki School of Economics
Virpi Kristiina Tuunainen
Co-author of "A Framework for Analyzing Software Business Models"
Affiliation: Department of Information Systems Science, Helsinki School of Economics
Michael Lewis
- Author of "The New, New Thing"
Peter Drucker
Management consultant and author
Introduced the concept of "theory of the business"
Joan Magretta
- Author of "Why Business Models Matter"
Alex Osterwalder
- Developer of the Business Model Canvas
Clay Christensen
- Author of "Reinventing Your Business Model"
Rita McGrath
- Author of "When Your Business Model is In Trouble"
Karan Giotra
- Co-author of "Four Paths to Business Model Innovation"
Serguei Netessine
- Co-author of "Four Paths to Business Model Innovation"
Ramon Cassadesus-Masanell
- Co-author of "How to Design a Winning Business Model"
Joan Ricart
- Co-author of "How to Design a Winning Business Model"
Mark Johnson
- Author of "Seizing the White Space"
Roman Pichler
- Author of "The Product Strategy Defined"
Henri Fayol
- Early management theorist
R. Edward Freeman
- Author of "Strategic Management: A Stakeholder Approach"
Carl Shapiro
- Co-author of "Information Rules"
Hal R. Varian
- Co-author of "Information Rules"
Philip Kotler
- Marketing author, mentioned in relation to the "whole product concept"
Paul McHugh
- Author mentioned in relation to sales and marketing activities in software
Mustafa Saifee
https://www.linkedin.com/in/saifeemustafa/
https://bento.me/msaifee