Chapter 3: Become a SAAS - how to make it easy to use and sell

Author:neo yang Time:2022/06/01 Read: 5412
Outline of this article: 1. SAAS architecture 2. Differences between SAAS and self-used backend management systems 1. Why is it difficult to use? 2. What’s the difference? three, […]

Outline of this article

1. SAAS architecture

2. The difference between SAAS and self-used backend management systems

1. Why is it not easy to use?

2. What’s the difference?

3. The secret to making a good SAAS - perspective

1. What is God’s perspective?

2. What is the user perspective?

SAAS can be heavy or light. It can be heavy enough to support a world-class enterprise like Adobe, Microsoft, Google, and ZOHO. It can also be as light as a small tool that a small team of a few people or even a programmer can make, spread on the Internet and make money.

No matter what kind of SAAS you do, there are a few things you should pay attention to.

1. SAAS architecture

SAAS is re-architected.

The purpose of architecture is to reduce the marginal cost of development.

In any case, SAAS must first be a software. And it is at least a somewhat complex software, whether it is based on WEB or has various clients.

This software also needs to be continuously iterated as the business develops. If the marginal cost of iteration is high, it will be difficult to continue playing.

In addition, for companies with multiple SAAS products, architecture becomes even more important. Because these SAAS products can be developed based on the same underlying layer, a large number of components can be reused in various products. This significantly reduces R&D costs and R&D cycles.

This is why many SAAS companies pay attention to the underlying architecture and low-code platform. No matter how many SAAS products these companies have, they are often based on the underlying architecture and low-code platform of a high-availability architecture. Most of the development is actually just through parameters. Configuration can be achieved.

Generally speaking, no matter what kind of architecture is adopted, there are a few basic things that many SAAS products will have. For example: form engine, Views engine, process engine, permission management system, etc.

In the following articles, we will discuss the above commonly used modules in detail.

2. The difference between SAAS and backend management system

In recent years, many people have told me about this situation: the SAAS (management SAAS) they made, users said that it was difficult to use, incompetent, too complicated, and did not have many functions (but in fact, it did ).

1. Why is it not easy to use?

If you look carefully at their SAAS, you will find that these SAAS often have the following things in common:

The following content can only be viewed by VIP users.

Subscribe to VIP

Subscribe to my VIP membership and you can read all paid VIP content.

If you are already a VIP member, please log in.


copyright © www.lyustu.com all rights reserved.
Theme: TheMoon V3.0. Author:neo yang