Critique the SaaS Business Model: Its Main Weaknesses and Why They Matter
Company: Amazon
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
An interviewer asks what you dislike about software as a service (SaaS) and why. Give a critical but reasoned view of the SaaS model and explain why the weaknesses you choose matter.
```hint Pick a vantage point
The model looks different to the business that pays for it, the employee who uses it every day and the company that sells it; decide whose view each criticism comes from, then explain what causes the problem.
```
### Clarifying Questions
- Should I critique SaaS as a whole, or one category such as customer relationship management, HR or team collaboration software?
- Do you want the view of the business buying the software, the people using it day to day, or the vendors building it?
- Should I compare SaaS with software installed on the customer's own servers, or assess it on its own terms?
- Do you want only the critique, or also what a product manager could do about the problems I raise?
### What a Strong Answer Covers
- A precise definition of SaaS that sets it apart from on-premises software and from other cloud models.
- Two or three well-chosen criticisms, each explained by the mechanism that causes it and the stakeholder it hurts.
- Balance: credit for what SaaS does well, so the critique reads as judgment rather than dismissal.
- A product angle: how a SaaS product team could reduce these weaknesses or turn them into an advantage.
### Follow-up Questions
- As the product manager of a SaaS product, how would you address the weakness you consider most serious?
- A large customer threatens to replace your product with an in-house build because its subscription costs keep rising. How do you respond?
- Which of your criticisms also apply to on-premises software, and which are specific to SaaS?
Overview: A product manager interview question asking for a reasoned critique of software as a service. It tests whether you can define the model precisely, identify real weaknesses for buyers, users and vendors, stay balanced, and explain how a product team could address them.