What software services does small and medium-sized enterprises need?

the software industry is a service industry.
the software industry has gradually moved from the original spring snow to ordinary homes. Many applications of large enterprises are now common, but applications of small and medium enterprises are still not good enough.
do small and medium-sized enterprises not want software services? Or can existing software services not meet their needs? What software services do small and medium enterprises need?
several failed cases:
1: customized software
some software vendors find potential customers: "Our software can be developed based on your requirements, completely seamless connection, considerate and comfortable "
Customer:" Oh, great. When can I use it? Can it be the next week ?"
service provider: "This is impossible. You should pay first. We will research 1 month, 3 months of development, and 1 month of testing. Well, you can see it later ."
Customer: "???"
2: customer-based ready-made software
service provider: "The Boss, this software is the most mature in the market and is suitable for 109 industries with 1000 built-in functions, fully qualified for any requirement.
Customer: "I have 20 employees, but I cannot use this big deal?"
service provider: "It doesn't matter. We only charge a small amount of money to provide you with a customer."
Customer: "What is this interface? I only need three functions. How is it so complicated to use? Do you need to give us half a year of training to use ?"
3: Employee: "boss, the system has a problem and the interface cannot be opened !"
BOSS: "Ah? Go to technical support! "
BOSS:" what? Not found? Shut down, no one will touch the system, and wait for them to serve !"
BOSS: "what? Not yet? How to use such a system! What will happen in the future ?"
(after investigation, the problem was that the employee accidentally kicked off the power cord.)
...

Small and medium enterprises actually need software services. But in reality, is software services suitable for them?
From the above examples, we can see the dilemma of pushing software to small and medium-sized enterprises: Price, ease of use, and after-sales service.
Price factors:
Most small and medium enterprises are not very profitable. It is unlikely that a large amount of budget will be provided for software. In particular, it will take a few months to see the results of such a virtual investment, they will have more concerns when making decisions.
Ease of use:
I have seen a customer's original system with hundreds of features. The function menu is very long and looks "great value for money ". But what is the actual application? The vast majority of functional customers do not need it at all. A simple function requires customers

Make complex adjustments (this is also the cost of system "flexibility ). The result is that the customer no longer uses the system.
Post-service:
When the software is delivered to the customer, the customer's operators are not computer-savvy and it is difficult to judge and reflect any problems (or even mechanical faults or power outages) they encounter. They are too reluctant to respond, and will directly complain about problems with your software. The customer will not dare to use the system if necessary immediate technical support is lacking.

SOLI zookeeper said for a long time, what software services do small and medium-sized enterprises need?
1: low price
2: simple functions
3: considerate service in the future
These are from the customer's point of view. How should these requirements be met by software providers?

If the price is low, a large number of customers are required. If the function is simple, you need to customize it to the customer as much as possible. If you are considerate, you just need to invest in the service;
What should a system meet such requirements look like?
1: functions should be modular and standardized as much as possible
2: industry-oriented
3: easy to maintain
The most important part here is "service-oriented development". We should try our best to standardize functional modules. Only in this way can the system be quickly integrated, and the functions are simple, without the need to provide the customer with complex systems.
When the network conditions gradually become better, it seems very good to make the system on its own server. This makes data maintenance and detection easier.

I believe that starting thinking is progress.