> I'm not buying the idea that an account system is just too complicated and would eat up too much time. Then why do you think there are all of these systems t

> I'm not buying the idea that an account system is just too complicated and would eat up too much time. Then why do you think there are all of these systems that don't have it? The CEO's/PM's aren't entirely stupid. They know what business customers are asking for, and what they're prioritizing in their asks, and how they're voting with their dollars. An account system is often going to come with different roles like admin, user, viewer, and then the entire product has to be overhauled to create display-only versions of what were workspaces where changes could be made, new role authentication checks on every API call and even every data operation, and so forth. It can actually be a relatively huge undertaking that winds up touching a majority of the code, that also adds to the scope of most future feature development in a non-trivial way. It's not just a table of users and passwords per account. I'm not saying it can't or shouldn't be done. I am saying that the idea that a companies without it "by definition aren't designed for businesses" is wrong, though. Not by definition, but by the reality of actual businesses today.