Even within organizations there are critically important employees.
So, no, it doesn't make sense.
Slack contains a world of sensitive corporate information.
Oddly though I don't recall any major email company losing gazillions of emails to a hacker either, but I could be wrong.
It's an existential risk for Slack, but not unlike most other SaaS companies as well, so it's just part of the cost of doing business a per the industry.
"Funded businesses die all the time. Google cancels products all the time. companies are acquihired and products end of lifed."
So it makes perfect sense to avoid Google offerings (especially consumer side ones, which Google kills whenever it wants) and avoid "funded businesses" and newcomers that in danger of being acquihired and EOLifed.
Letting the careless early adopt those kinds of services, and using only mature ones (that have proven their longevity and aren't going anywhere even if acquired) in your company, makes sense.
Further, there is much higher trust that Slack would give a reasonable notification period of they decided to stop existing, compared with a single dev's project.