Miles Deutscher built a five person AI team with its own CEO, job titles, faces, and deadlines “I wanted a way to visualize all my employees and their various roles. So, I have Ethan, the CEO. I have Olivia, who’s on product. I have Mason on software. I have Ava on marketing, and I have Noah in sales. And each of these employees come with their own CRM” “When I want to step in and give them some work, I can simply drop work in and they’re trained on custom skills to be able to complete that work. … Of course, giving them real names and real faces. This is an add-on. I like it so you can start to better understand parts of your business versus just like bot one, bot two, bot three” “I click create task. I detail what needs to happen. I can even detail the skill something needs to use. I can put the owner, so is it Ethan, Olivia, Mason, Ava, or Noah? … I can set a due date, and then I can set the exact Slack channel that I want the task to be completed in, and they will cross-talk to each other depending on the roles”

Pakistani Habibi with Hijab ends up having a deep & long orgasm thanks to my Big Cock fucking her🍆Check out until the End of the teaser😈 FULL VIDEO LINK IN COMMENTS! 🔗

That's why I started building my own applications with Claude Code. Software like Zoom, which was initially just a video meeting app, is now completely bloated with features. It tries to be the all-in-one solution for teams, and yet it fails to quickly give me a transcript of my meeting. I still have to go through loops to find the recording and transcript. Clicking on many things ends in dead ends. And Zoom's AI has no clue what a meeting is or why I would need a transcript at all. Tools like Granola and Wispr Flow give me instant transcripts after the call, including a summary, and they are not even part of the meeting app in the first place. This shows that when too many people get involved, things get too complicated to use. Anyone who has tried to use Microsoft's or Google's software suites for teams knows that too. I'm not saying it's a bad thing to evolve a tool and try to make it an all-in-one solution, as long as you ensure that the original value proposition of the tool, the foundation everything else is built on, remains priority number one.