Disrupting the space now doesn't seem any less hard now than it was 10 years ago when slack and zoom did it.
But yes, if your point is that it's hard, then indeed. It is hard. Should that stop someone? No!
And something being harder stopping your from doing it is ubiquitous in life. It's a good skill to know how much effort something will take and weighing the risks and rewards.
What is it about enterprise IT that is preventing us from building a better alternative?
How can we get around those hurdles?
The hurdle is producing a full suite covering everything Microsoft sells in one package, which seems impractical without their funding to start with.
Enterprise chat might not be a commodity quite yet - SSO, DLP/data classification, auditing, retention, compliance checkboxes - but these seem insurmountable at first glance to get a FOSS solution to reach a viable enterprise feature matrix.
Killer features as a moat might help, but while almost everyone uses chat, everyone probably uses chat differently, so that means discovering killer features for a niche and trying to own that segment before expanding. Unfortunately this is the "Draw the rest of the owl" part, because while I have quibbles with chat apps, I struggle to envision a chat app that does something radically different than any other chat app.
Your comment is just fake empathy noise.
There are already open source alternatives built for both Teams and Zoom. The issue is that open source projects don’t have salespeople that will promise compliance and integration (whether or not they can actually deliver).
Hard disagree on the "only" modifier. Surely integration helped, but I've used Zoom, and I hate it every time I have to use it. Teams is comparatively a godsend.