So, Cisco Jabber (now Webex)? You can't really compete against Microsoft and its bundling strategy. Even Slack is dying, unfortunately.
Webex can't be run on-prem, can it? I vaguely know about the old Cisco Jabber.
But you're right, the best competitive advantage of Teams is that it's "free"[0]. But that's about it, it's objectively bad in all other ways - anyone claiming otherwise has Stockholm syndrome and is in denial =)
Just the fact that, as a consultant, it's literally impossible to connect to multiple teams workspaces with the same client. The OFFICIAL Microsoft advice is to use Private Browsing in separate browsers...
Meanwhile on Slack I can just hit cmd-number and swap between clients. AND we can have shared channels over instances, like $vendor having a support channel on our Slack with their actual people with their own accounts.
[0] If you have M365 anyway.
Thankfully we use Slack where I work. The cross-org channels are cool.
Some use cases like business chat actually can't have E2EE, and that'd probably be Jabber's foot in the door because no other open solution has taken off in business, and businesses don't need so much network effect. This was a main Jabber use case back in the day too.
Make decent official Jabber clients, called Jabber and not something else like a bird, and server that implements the right spec with default settings. Now is the time, you can AI slopcode entire native apps if you want to. If someone really want to put extensions on a server, it's called XMPP and isn't compatible with Jabber; the X stands for excommunicated.