This is where I believe you are probably mis-reading your potential customer base.
If you target the business with only 2 to 3 total workers, then you MAY be safe with your assumption.
However, my experience differs greatly as soon as the number of employees/workers in a business exceeds approximately 12 users. At this point the current Frappe Business Model becomes a burden to the potential customer.
They already spend a great deal in just trying to keep their employees focused and on task so their business thrives. So, why does the Frappe Cloud Business Model fail at this size business???
It is because the Frappe servers are updated far to frequently with changes in the core ERPNext system. The client business owner cannot possibly keep up with retraining their users with the new features or the changes to the old features.
In 6 of my last 8 implementations of ERPNext, when offered the choice of Frappe Hosting or of my more expensive version of hosting it for them, they choose my more expensive hosting option. In every case of the 6 that chose my hosting is was because they could NOT tolerate the disruption to their businesses that the constant changes in ERPNext core system would impose on them.
Frappe Cloud hosting does not give the cusotmer a choice to stay at their originally installed version level. All versions changes (even if they include bugs) are forced onto the cloud customer and they must begin again learning what is different in their system.
All of this relearning takes up valuable time from a small business.
So, to help you understand this a little better, let me share some of the statistics of the 8 businesses I used here as the example.
the 6 that could not tolerate the constant changes were all in the range of 12 to 27 employees that would be users of the system.
all 6 businesses were between $4 million and $11 million in gross revenues per year.
4 of the 6 businesses required that I support them at their installed version for a minimum of 3 years. The other 2 of the 6 required only 2 years of the same version.
The 2 businesses that were relaxed enough to only require 2 years of the same version level were also the 2 at the bottom of the revenue numbers in that group of 6 and had the fewest people to train each time.
The 2 businesses out of 8 that did NOT make the requirement of me to keep them at their originally installed version level, did “request” no changes in version for the first 6 months. They were both also less than $500k in revenues per year and 5 employees or less.
These 2 smaller businesses ultimately chose my hosting for themselves because it also came with my real time assistance if they have problems. They would not have to wait for a “service ticket” to bubble up to a technician for resolution. They can call me direct and get me or one of my implementation techs on the phone 24/7. We are local to them and can even provide on-site training or assistance if needed.
Getting back to the 4 businesses that required a stable version holding for at least 3 years. All but one of them required me to provide at minimum 90 days of testing server access with any new version prior to making the change. The one other in this group required 6 months of test server access.
This last requirement is probably the most difficult to meet. It means that I must find a way to create my own repository at the version point of making the 90 day (or 6 month) test server for the client. If they decide to move forward with the version change, I would not be able to pull whatever the most recent version was after the 90 day time frame because ERPNext core changes faster than that and the fresh updates would be different from what the client tested for 90 days.
In conclusion, the customers that I have been servicing are already familiar with the offerings of other ERP systems and are at least a little educated about the things that can go right and wrong with a system implementation. This has changed how they look at such a major software integration into their business.
So, I know this probably offends some of you. However, this is my actual experience. Your mileage may vary, but do not delude yourself into thinking that you can convince your customers to allow you to be constantly changing their system as ERPNext grows each week. In fact it would not surprise me to find that some of your customers that experience those changes for a while will grow tired of your service and seek an alternate solution. Probably not because of the quality of the software, but because of the quality of their user experience.
I found that STABILITY is more important than features to almost ALL of them, and PRICE did not have very much influence here. They ALL paid more for my stability offering.
Hope this helps someone.