Hey, well done on getting this shipped! It would be cool if I could walkie-talkie this response over to you! I watched two of the videos. The first video was

Hey, well done on getting this shipped! It would be cool if I could walkie-talkie this response over to you! I watched two of the videos. The first video was about the problems that you typically have in a team and I think he hit the nail on the head there. It is frustrating with all the github emails and jira emails and slack notifications from 100 channels. I was really hoping you had solved this or at least partially. When I watched the second Jira I saw the product. I would describe it as potentially better than Slack but hard to be sure without using it. But I didn’t see how it solves the problems? Don’t I still have many channels, conversations etc. to track. And all the emails are still there! Async voice chat may be great but I feel it is a leap of faith for me. You see the problem is where you have a company that is already on teams and slack, that product is embedded deeply across the org so at best if I try yours I will still need to keep slack going because the sales guys won’t switch (vice versa the sales guys use some cool communication tools but still need to run slack). It might be different in small startups that could drop and switch in a decision made when chatting at the bar after work or whatever. I guess in short I didn’t see the killer feature. But… I am not an “early adopter” persona. I might get it once you are wildly successful. What would be interesting and compelling would be say a YC startup that switched to it write a case study. The motivating problems you mentioned are good ones to solve and I am keen to see them solved. I think the solution is a mix of software and management culture change and business skills training (efficient meetings etc.) and probably for 2023, some AI!