I don't know who else here has ever actually done the kind of work that we're talking about, but I have, for contract clients, over the span of most of a decade. Between G Suite and Office 365, those jobs dried up fast about a decade ago, and I wasn't sorry; the thing about selfhosted deployments of this type is that no matter how standard you try to make the platform, clients' requirements persist in varying, so each deployment ends up a somewhat different artifact whose differences, because those get less investment of effort than the common aspects, are always what cause the most problems and cost the most money in maintenance. No one was sorry to see that expense dwindle with the rise of SaaS officeware platforms; even for me, it wasn't a loss, because it freed up my time for more interesting and lucrative engagements.
Of course I'm sure that, for those of you saying this is easy, your experience is different from mine. It would be really interesting to hear more about how you've been able to make selfhosted deployments work so well for folks who aren't technical. That's a really significant achievement! Teams like Sandstorm have spent years at it and come away with nothing of import to show, and I'm sure I'm not alone in wanting to know more about how folks here have overcome the same challenges.
[Or used to, around 2006 or so - I'm not sure if they still claim managing public cloud resources is means less work.]
It would be nice if the tooling really was simple enough that wasn't so, but despite considerable effort to make it so from Sandstorm among others over quite a long time, as far as I know no one's had notable success in achieving that. Hence the rise and continued prominence of SaaS providers, who abstract all of that effort behind an SLA and a monthly fee.
I agree with the criticism of SaaS platform behavior at the head of this thread. What I think the commenters on that side of the discussion are missing or maybe ignoring, is that much of the value a SaaS offering provides is in not having to (pay someone to) administer that stuff yourself - and that, considered separately from the question of how providers behave, "all you have to think about is 'pay us and use our stuff'" is in the general case a strong value proposition.