We envisage that this Saas can provide a set of industry solutions, which can be developed and operated at a low cost, and users can use it at a low bulk sms service cost, for mutual benefit and win-win results. But the reality is often not so good. After going deep into SaaS for several years, I also deeply feel that it is too difficult to be a standardized SaaS. Let's take a look at the voices of product managers, users, and companies. The product manager said 1. Party A's father changed from 1 to n In the past, B-end products were basically customized by large enterprises. We didn’t know much about their industries, and their needs were all brought up by them. We converted them into product bulk sms service documents and handed them over to development. At that time, I felt that Party A's father was arrogant. He didn't understand the system, and the needs were changed back and forth.
I just thought of making a product of my own one day, so I don't need to be angry with Party A's father. Wish came true, but! I started to miss the days bulk sms service when there was only one Party A dad, because now I have to face thousands of Party A dads. Although I have the decision-making power over the product, I can deny the needs of the fathers of Party A, and choose the needs that I think are important and universal, but I really can't bear to refuse their requests again and again, they say this If the function does not work, it cannot be carried out. Therefore, a big test for product managers to do standardized Saas is: how to analyze requirements? How to distinguish bulk sms service between general and individual needs? How to prioritize requirements? In this regard, I also wrote an article before - "How do B-end products balance generalization and personalization? , you can refer to.