This video from The Startup Project explores Jack Dorsey's new application, Buzz, presented as a potential 'Slack killer' due to its innovative integration of AI agents. It details how Buzz allows users to swap underlying AI models while preserving chat context, addressing 'model fatigue' and offering a flexible platform for solopreneurs and small teams to enhance productivity.
0:00 Jack Dorsey just launched Buzz and it's gone completely viral. Yes, it's the same Jack Dorsey who co-founded Twitter, who co-founded Block. This guy is building what people are calling a Slack killer. Now, why does this matter for you? Well, it's being called a Slack killer because it's almost like this agentic version of Slack. It's a way to have uh conversations with your teammates, except they're agents. It's a way for you to huddle agents. It's a way for you to have software being built on the fly via agents. So, in this episode, we're going to break down it so clearly for you so that you understand what it is, why you should use it, and what are the best tips and tricks to use Buzz. My take on this whole thing is it's a glimpse [music] into the future of work. I can't wait to see what you think about it. And the By the end of the episode, you'll understand if it's for you, why you should use it, how you should use it. Enjoy the episode.
0:59 >> [music] >> The Startup Project It's sipping time, baby. >> [music] >> What's up, Binnie? I saw your tweet. Uh Jack Dorsey retweeted it. By the end of this episode, what are people going to learn? >> They're going to learn how to use um Buzz. Uh mostly, I think it's like the sweet spot for um Buzz right now is I think uh solopreneurs, uh small teams. Um they're going to learn how to use it to like kind of brainstorm, keep everything in context between their agents, and just uh you know, build products, build solutions, ideate, and and like um yeah, use it to to get stuff out there quicker and be more productive.
1:44 >> Cool. Okay, so what I what I hope to get from this is basically understand what Buzz is, understand why it matters, understand some best practices on how I can use it to actually use agents to do things for me. Um and by the end of this episode, I want to understand if I should actually use this thing. Or should I just basically continue using Slack? Um and that's what I hope to get a out of this. Do you think you think you could commit to that? And also, while you're going through it, just share the best practices that haven't been shared anywhere so that, you know, we we've we've got a little edge on people. You think you can do that?
2:23 >> Yeah, I think so. Um I just want to start off by saying like uh I think the Slack killer, you know, that's a good line that it's a Slack killer. Um but I think the real like the real um selling point for me for uh with Buzz like from the beginning is just the the openness of it. So, um do we want to start there? Just like what I mean by open and and what kind of like what that allows, like the power uh how powerful the openness feature of Buzz is.
2:52 >> Yeah, I mean, sell me on Buzz. Like, why >> Okay. Okay. >> Yeah. >> Um so, first off, um it's Slack with agents inside and a lot of people like it's kind of like Slack. You got the agents inside, so Slack allows you to do that um but by adding an integration, but um in Buzz, they're like first-class citizens, right? So, they're members of your team. You don't think of them as like uh add-ons or just kind of uh um a side feature. They're an integral part of of the app. They're part of your team. Think about it that way. So, um I'm kind of uh I like to keep things simple and I just started using this not too long ago. I mean, it's only been out for a little while. Uh I just discovered it and um these are basically what you see here are the default agents you get when you start, but um under the surface, there's a really powerful thing, which is you can edit and add agents and um when you give agent instructions, uh that's just basically like a system prompt. Um the really cool thing underneath is the harness. So, we're all probably using Codex, Cloud Code, maybe something like Open Code to do our coding work, build products, um whatever, be more productive. The great thing here is that your agent harness is swappable under any agent. So, I can go under here and say, you know, I want to use Cloud Code, I want to use Codex, um I want to use Goose, and like for me already that point there was like, okay, this is very cool. Um and the reason why this is so cool is because, I mean, if any of you all your listeners probably follow this stuff at AI moves at like a breakneck pace, right? So, today it's this model, the next day it's the other model, and sometimes, I don't know about you, but personally, I'm like, I get model fatigue where I'm just like, gosh, you know, I I just switched over to this, I just got used to this model.
4:50 Like, I don't even want to hear the good things about model X cuz I'm still over here using model Y. Um but the cool thing about this is that this is a layer on top of that, and you can just switch, and the best part is is that your agent you don't lose anything in that switching process. You can change the harness under your agent, and all the context that's in your chats, so everything you've been chatting about with this agent, like all the stuff you're trying out, the apps you're building, that all that all that context comes with to that new harness, to that new model. So, first off, that's something I think is really cool about uh Buzz.
5:25 >> That's a that's such a huge deal because I feel like a lot of us are ping-ponging between different models and harnesses and stuff like that, and it's tiresome, you know, when you're when you're starting from scratch, um it does feel like and then I need to understand, okay, what is Saul good at, too, you know, like and what are the contexts for this particular model to get the most out of it. So, I think the fact that this is built natively into the product um that you can go and switch just like I like that because it's thinking about how people are working in today's day and age and they're acknowledging it and they're like, we understand that yes, there's going to be new models all the time and you might want to be switching, but you probably don't want to spend a lot of time adding context, figuring out things cuz you're busy trying to run a startup, trying to make money, trying to be productive.
6:23 >> Yep. Yep. Exactly. And you can take all your stuff with you, you know, like um if you're if you've built all these skills and skill files and folders and stuff, you know, as long as they're in like the global directory, if they're accessible to uh globally and they're they're not project-specific, like Buzz can access them. So, you that can install agent skills like normal. Um you can change then you can change hardnesses, change models, and and your your agents in the chat have access to all of them. So, I think that's really cool. Um I'm really happy about that.
6:55 >> Okay, what else do we what else do we need to know? >> We've got audio huddles with agent. So, that allows you to have like an audio chat with your agents and uh they'll be in the chat and they'll respond to you and so you can, you know, have a voice call with someone else, bring an agent in and communicate, and they also get the context of your of your whole chat in the uh audio huddle. So, that's pretty cool. Um I haven't tried that out yet though, so um I have seen there's some good videos on YouTube that run through it and show you how to do it. So,
7:25 >> What's cool about huddling and, you know, agents or an agent, I I tweeted I tweeted about this. I feel like what I'm missing from building in the AI age is I feel like I'm asking my agents to do things. Maybe I'm using WhisperFlow or even just typing it. And it feels very much like back and forth, back and forth. What's cool about huddles is live. And I I the way my brain works when I'm when I'm being creative is stuff like that is I need like live interaction in order to really like extract what's going on in my brain. I think there's probably a lot of people like me like that. So it's cool that that that's a feature. Uh my dream and I tweeted this. My dream is eventually to have like the ability to FaceTime agents. Um and that to me is like the holy grail of the future of work. But you know, cool that you can see that um Buzz is scratching the surface here. Is it good or if it's not good, we'll have to test it. Uh people in the comment section, please let us know. Um but it's interesting it's interesting that that feature exists. What what's another feature that you're excited about?
8:37 >> I mean, well, right under the surface you've got these agents and you probably want them to do work. So um they're like integrating um they have Git pretty tightly integrated um into it and your agents will actually um uh you know, what they're doing coding, they can create projects. They'll create uh feature branches and they work in parallel work trees. So they're not not actually messing with stuff that's locally on your computer. They'll make a uh work tree, a copy, and uh they can work there. So they can do things in parallel. So you could um for example, um you know, you're talking to your teammate about a UI, uh the design of your product or your webpage or something, and you can just, you know, tell the agent like spin up three different versions of landing pages based on the ideas that you guys had in the chat, right? And um they've just added this projects view. So if you go into um settings here, there are experiments. You can turn on workflows um and projects for example, and then you'll see that here. And this is basically like um you know, your your apps that you're coding on with your agents and working on with your agents. And another interesting thing is that you can integrate with GitHub, but under the surface they have their own um hosted Git hosting. So, you can push to remote repositories that are actually on your relay. So, um that's probably a more technical thing, but Buzz works on relays. So, these are like servers that you host and or that get hosted for you by by Buzz, by Block. And then they'll actually push that code to the remote repositories on your relay. So, the relay is where all your information, all your chats, everything, that's where all that stuff is is happening and where it's stored and where it's getting sent and and pushed to the other people you know, chatting with you and the agents chatting with you. So, I can see in the future that they're they're trying to take on more than just Slack here. They're trying to take on GitHub as well. So, that's pretty crazy.
10:49 >> Cool. And I think, you know, for the non-technical audience, I feel like a lot of my non-technical friends are actually starting to use GitHub now in the AI age. I don't know if you've noticed this. >> No, I don't I'm kind of in the I'm mostly mostly in the yeah, the nerd bubble. >> Yeah, it's it's interesting. It's just I feel like you know, 5 years ago if you were non-technical, 10 years ago if you were non-technical, you barely knew what GitHub was. The word repo, you're like, you know, are you repossessing my car? You know, but I think now in an AI age where we're kind of all technical in some way um something like this makes makes a lot of sense to be built natively.
11:34 >> Yeah. And the the interesting thing is you don't really have to know that much about it. Uh you don't really have to even consider it because your agents will just kind of take care of stuff for you. Like I was doing stuff here um where I was asking it, you know, pull up a simple CRM app and um uh you know, I I told it here's the chat right here. Spin up a simple CRM app using uh the Wasp full-stack framework and deploy it to Railway for me. So, you know, there's some technical knowledge there. You know, I'm asking for a specific framework, a specific hosting provider, but um it'll do that and uh even, you know, get stuff pushes it to these remote repositories um deploys it live on the web and even sends you screenshots. So, it's like, oh, here's your here's your CRM. Here's your uh that I just made. And um that's all before I even checked out what it was even doing. So, just it did it for me, uh gave me the links, gave me a little preview of it, and um yeah. Uh I thought that was pretty cool.
12:36 >> That's ins- That's insane. >> Yeah, there's a lot of I feel like they they've baked in a lot of workflows and um a lot of just like uh prompts into these agents so that these agents kind of can work end to end and really get tasks done. I think that's the idea. >> Yeah, that's that's insane. Like if you think about it. Like we're kind of like glossing over it, but like look what we built. >> [laughter] >> Yeah. And it's like it's live on the internet, right? Already. So, the nice thing is, you know, I already had a Railway account. Um I um I you know, I know a little bit about working with uh full-stack apps, but I didn't really tell it much. I just said, you can see the chat put this online. So, now I have a fully functioning CRM dashboard that I can uh share with team members and then we can The cool thing is then what you would do is you'd add them to this chat here and you start talking about what features are missing, what things you don't like, like and then you guys you know you have a conversation with your teammates and you come to a a conclusion and you just tell your agents to go ahead and start working on it and they'll do it.
13:43 >> So why this is a big deal is if you think about it, you know, you're able to create software on the fly essentially automated that's high quality that could be deployed that you can manage and a view that you know, it it is clear and I think you know, if you think about your business, let's say you work you have an agency business, proposals is you know, the lifeblood of your of your business in a lot of ways, right? And you know, imagine that you can create uh proposals based on people's data, maybe you're pitching um the NFL um and you're you know, you could put in the context of the pitch, meeting notes, let's say from granola or something else, it ingests it and then on the fly you have these agents based on that create proposals that are unique to those clients. And it's vibe coded or or it's using agents to actually you know, create them. You know, there's so many ways that you can use this interface to think about okay, I have you know, context over here, this is how it comes in and then here's how it's going to get spun up on the internet or through you know, an asset that is built within code and then here's how you're going to view it.
15:05 Is that right? >> Yep, yeah, exactly. In one of the one of the videos I made that I posted on Twitter, that was what I was going through. So I was taking a more of like a a marketing angle and I built a tweet leaderboard for for Twitter. So like my team um like how much we're tweeting, how good what are what are our top tweets, all that stuff all that information was being um uh collected in this in this app, this full-stack app, and then I was like, "Oh, well, um instead of just building it with Buzz, why don't I get Buzz to also access the app, get that information, then we can get like, you know, daily reviews here, daily digests, and um we can also like kind of um brainstorm on what's working uh in our Twitter strategy for marketing, what's not working, get it to um find like links between the the popular uh tweets, and you know, brainstorm, come up with new stuff." So, that's exactly what I did. I had it I told it, "Let's build a um publicly facing API, and then let's build a workflow." So, I just tell it daily, you know, check that API, and um give me the uh numbers back. And then the awesome thing is that's what you're seeing right here in this tweets stats for app from app. Um it's getting the stuff from that dashboard through an externally facing uh API, and um putting it here into this channel, and then I can reply to it and be like, "Okay, uh Fizz," which is one of the agents, like Fizz, "Um let me know what's the the common thread between my successful tweets this um this uh uh last 7 days." Because it also sends those over the API. So, if I understood you correctly, I think you're talking about kind of these workflows where you're like this circular stuff where you're giving information in, getting it out through apps, and it's all going into the context of your your agents and stuff like that.
16:58 >> Exactly. >> Yeah. >> Yeah, I mean, I'm interested in this because this is like the {quote} "boring stuff" that every business has that if you can figure out how to have some unfair advantage here, um it's it's what separates a good business from a bad business. >> Mhm. Yeah, and and that's the thing I really like is that this openness of Buzz like it allows this kind of these kind of integrations to to happen very easily. So, with Slack like you would have to you know to get all this kind of stuff up and running you'd have to get API tokens, create an app on their platform. Um all their stuff is uh proprietary. You have to like learn how the structure of things. I mean with agents it's easier but here because it's built on these open protocols you can get stuff like this running really easily and then you have this just like crazy context engine that just can help you do work. Like if I wanted to I could ask Fizz right now, you know, like um connect up the app uh or you know, connect yourself to the uh xAPI and um make it available so that we can start tweeting from Buzz.
18:07 Like that wouldn't be that hard. We could probably do that in in 15 minutes, you know? >> Crazies. >> One thing that I really like about this kind of uh you know, this close we were talking about this closed circle of like context um that I'm getting back from my app so that tweet dashboard app is that like here it sends me the tweets every day and the the stats like the top tweets and my stats and impressions and I can just ask uh the agent like um let's make sure I'm I'm replying there and I'll just say like uh what can like what is the common thread between my top tweets? And um sometimes like I used to do this with in a session with um uh Claude Code or Chat GPT where I'd be like literally you know exporting tweet data or copying pasting tweet data and putting it into Chat GPT on the on the um desk or on the uh brow in the browser, you know, and getting information chatting about it and and pulling it back but like this is so cool because it's pulling the the it's getting the information from the X API. It's in the context window of the agents here. I can chat about it here, and then um you know, we're we can chat with colleagues about like what you know, what are some more tweets we want to push out, what's a a different marketing angle we could take, and um uh that's what I really like about this uh here. And And you're going to see there is the um agent working. So, what's actually going on in the background? That's nice if you're um if you're used to looking at this kind of stuff in a terminal. You actually see the tool calls that it that it's uh um the tools that it's calling and uh think or here it is down here. Like what is happening? So, um it's getting information from the channels, uh checking for newer stats and things like that. Gets the result. Um and so that's all like kind of under the curtain stuff, but um we should get a response back soon.
20:12 >> And is there is there any like tips around how you is best to talk to them? Like I see here as you just wrote a short and concise question, but how do you how should how should people think about the best way to to talk to some of these agents? >> Um I mean, they're pretty good at pulling out the the intent behind your questions these days. So, just have a conversation with them like they would like a normal person. So, I don't think I don't at least don't have any special special approach there. Um I kind of just say, you know, some This is probably nicer than what I would normally type. Like usually I got typos in there and stuff. I'm like, "Give me the sauce, you know?" And uh they're usually pretty good at that is because they have all this context. So, um I'm usually pretty uh straightforward and and concise with like the the questions and the the stuff the prompts I give. Reported back. So, um it's showing like what I did. I tried Jack's Buzz. I deployed open SAS to OpenShift. My first time successfully self-hosting.
21:16 Um so, it's like um it's showing that um you know, I'm doing these things as a beginner and I'm reporting back on what I learned and those are the the things that are doing well. So, it worked. Uh my top two top two tweets got over a million impressions. Uh but this sucked theme uh got a you know, they were the bottom uh half and they got a collective uh you know, 88,000. So, um novelty gets you reach, friction gets you engagement. So, there's some actually really good advice there and um like that's kind of the power of uh using it here and having all of it in in Buzz is that makes stuff like this um uh easy and illuminating. So, that's really cool. I like that.
22:02 >> Um by the way, I saw uh one of the one of the pieces of feedback is nobody is mentioning that uh Buzz has a backdoor for Bitcoin native payments. What What does it What does that mean? >> Um so, Buzz we're talking about open protocol. So, I kind of glossed over this. It's built on Nostr and um Nostr is the name of the open protocol that Buzz is built on and I personally believe cuz you know, if you know Jack Dorsey, he's a big fan of Bitcoin. Um Nostr has tightly coupled with uh Bitcoin Lightning, which is a a very um fast and like almost uh fee-less way to um pay and transfer Bitcoin. And uh my guess here is that um because it's built on Nostr, Nostr's open, you'll be able to integrate uh Lightning Bitcoin Lightning payments into um uh Buzz and um you'll either be able to pay a agents will be able to pay for compute, this shared compute idea that we talked about, um or uh um that's in there in the settings. Um you'll be agents will be able to pay for work and compute, or people will be able to pay other people, tip other people for tasks they get done. So, like I can honestly imagine a big open community of let's say, I don't know why I keep gravitating towards graphic designers, but like I say designers and uh you know, you need a really cool logo and AI gen image gen isn't really doing it for you, and you ask some people to like, you know, spit out some ideas and and some random person in in some, you know, graphic design community uh on Buzz gives you like an awesome logo, and you just, you know, tip them. Thank you for that idea, and then you you you go ahead and and keep working. And um uh yeah. Um we'll see. It's not integrated at the moment, but I I think it will come.
23:51 >> Very cool. Awesome. So, what else do people need to know about Buzz? >> Um so, let's see. Um you mentioned that shared compute um idea, and I think that's that goes back into like the openness of Buzz, and that's uh really cool. And that was something that really surprised me, too. So, um why don't we just uh talk about that for a minute? So, we've got this uh compute uh setting here, and you can turn it on, and it will automatically um suggest some local LLM, some local um model AI models that you can download on your laptop or your computer, and you can literally share them with the other members of your team. So, um let's say that you are just starting out, you're a college student, and you want to start building a business, you got this awesome idea, you don't have a lot of time, you don't have a lot of help, and you don't have, you know, like the money to buy one of these Max Pro plans, whatever they're called, um with the like unlimited token budget.
24:57 So, um you could get together with some friends, you know, buy a decent size laptop or a Mac Studio or something or maybe even like a beefy Mac mini. You put this on, you share compute, and all of you can use this one model running from one machine even though you're chatting from different uh from different laptops, from different computers, whatever. So, um that's just like a very simple example, but um you can see how they're paving the road here for um real openness in model choice and um being able to like really harness the power of these open-source and and local models that are always getting stronger and you know, starting to compete with the frontier models from Anthropic and uh and OpenAI. So, I think that's really cool.
25:43 >> And why do you think that even this is worth playing with, you know, or you know, why is this really important? Why is local important in the grand scheme of of the future of work? >> Um I mean, model choice is important depending on what you want to do. Um and um you know, it's the same idea where Slack is the controller of your data, and that data is very valuable. You're sitting here, you know, spending I mean, this stuff makes work a lot easier, but you you still have these really cool ideas, you're iterating on these ideas, um you're putting stuff out there that you work pretty hard on and that you think a lot about. And then to have like just one company control all that data basically, um like Slack for example, have the whole all your data in that sessions, and if you're tired of Slack and want to move to something else, it's really hard or it might not even be possible to take all that data with you to some other platform. So, you just stay there and you're stuck with them. Uh it's the same thing for models, you know, you see people talking about why, you know, there there are Who knows? Um today it costs $200 a month for an unlimited plan, tomorrow it might be two 2,000. We don't know. We don't know how how what's going to happen and the future, uh, you know, having choice in the future is very important for the integrity, for the sustainability of any business because that's your data. Um, that's you what you want to be able to do with it. I don't know, some of these models have restrictions on what you're even able to ask them. So, um, governments have top-down mandates on what they're allowed to do with the models or not. So, you know, we saw models get pulled back after people started using them for a couple days.
27:27 So, like, um, you're building your businesses on top of these tools, you should be you should have flexibility and freedom and control of these tools, basically. >> Yeah, and I think the big insight of all of this is a lot of us haven't realized how much of a content uh, hub Slack and products like that have become to us. And that and we're we're learning that if you want to get the best out of any of these models, you need to have the most amount of context possible. So, what's really cool about Buzz is it's basically like, okay, we recognize that this is uh, your con- your context foundation. And we're going to go help you do a bunch like we're going to help you pivot into a bunch of directions. You want to, you know, have these projects that, you know, are integrated GitHub, we can go do that. If you want to do local stuff and do shared compute, we can help you do that. You know, etc. etc. You want to huddle an agent, we can help you do that. But it, you know, what's so cool about it is whatever you decide to do, the context is at the core of it.
28:38 >> Yep. Yep, exactly. And that's what I like about it. That's what I think is really cool is that, um, I think they really hit on something here. so you know, I think um, we'll see. It could go like I saw people commenting open claw, you know, nobody's talking about open claw anymore. Open claw was a real wow moment and like okay, we can get these agents to do a lot of productive work for us. I have the feeling that it was missing something and this shared context because we're working in teams, we're working with other people. Teams might even just mean your other agents, right? Like you just you you're going to have conversations whether it's with one agent or another, but now you have the ability to expand that the the the like your team set expand your you know, your global context window so to speak and then make it globally available to everyone in your team including the agents. So yeah, I think it's super cool.
29:39 >> All right, setting up and managing your agents or is there any sauce here? Is there anything people need to know besides what you've already shared? >> I would I wouldn't say so. I've seen it depends on how how deep in the weeds you like to go. My honest opinion would be you probably don't need to do that much. All I did the first thing I did was just I wanted one that's fable. I'm using specifically or exclusively I'm using Claude code as the harness under here, but they have adapters so you can adapt you know, you could even adapt open claw or Hermes or open claw I'm sorry open code or goose. So like any of these harnesses can be added under under the surface here under the hood. But the first thing I did was I just pinned them to models. So Fizz is a fable model and honey is sonnet because there is a certain tasks that I don't need to use the power of fable and burn through tokens so fast. So that would be like my main piece of advice. Besides that just start playing around. Um I made this chief agent officer. So, like if I do start to um create more agents with more specific um kind of uh um instructions and and system prompts, then I might delegate the delegate the delegation to Mr. Chief Agent Officer here and be like, "Okay, I have this task. Who's the best for it?"
31:03 Because, you know, you might have a copywriter, um you might have a brainstormer, you might have a code reviewer, things like that. And um you might forget who they are or I don't know. You just get an agent to kind of delegate. So, um that would be pretty much my only advice on the on that on that side there. >> Cool. Anything else you want to show? >> People were asking in uh Twitter about um skills, and I think I mentioned it already, but like all the stuff under the surface that you're used to using, if you use Claude Code or something, that's all available as long as it's um to Buzz your Buzz Buzz agents, as long as it's uh globally installed. So, skills and things like that um yeah, they can use in the and they can uh take advantage of. So, you don't lose that stuff. So, that's also very nice. And um I would say that like this is beta software. It's like I it might even be alpha. I'm not sure. It's like early preview software. So, some things don't work that great. Um I was trying to create workflows, and um you know, like set up recurring tasks and things like that. And um they weren't really landing great. Um that was one thing I noticed. Another thing I noticed was uh things can be kind of slow if you're used to it being like uh working directly in Claude Code or in um a CodeX. It seems to be a bit faster there, and I think it's because it's uh communicating with your your server, your relay, and and communicating back.
32:25 Um and um because of that, I I think it's at the point now where it's like um really good for, like I said, solopreneurs, small teams, iterating on on small software um or small ideas and um uh if you're really doing like um you know complex software engineering, this might not be the tool that you want to use. But um if you're just looking for something that can bring you value and uh like I said, bring all this stuff all your knowledge into one central uh one central tool, then this is definitely a great uh a great thing to use.
33:03 >> So, if you're a founder, um small team, maybe you know, one to 10 under 10 million dollars in revenue, zero to 10 million dollars in revenue, like should should you use this thing? Maybe you're using Slack today, should you download Buzz and actually try it out? >> So, um I'm pretty convinced that like I'm trying to convince my team uh at Wasp that uh we use this internally and exactly for that reason. So, um we are a a small company, a small startup, and um uh we're we're a a a developer tool, so we're a software company. And like you have all this stuff that you talk about in Discord, we talk about in Discord, and um we have our community there, too. So, um that's one interest like one thing I should mention is that you can create channels that are private and public, right? So, you could invite people from your community using your product to come chat with you. And then you have private channels just for your team, and then that context is shared, which is also a huge thing because if someone comes into into your chat and says, "Hey, we want to get this fixed,"
34:12 then fixing it with an agent is just a you know, an at away, right? You would just tell Fizz, "Like let's tackle this bug." Like whoever just you know, uh did a bug report or said, you know, wanted a feature, you could just have them prototype it right there. So, um yeah, I I think for um small teams, um this is definitely worth checking out. >> So, my take on my take on this is this is so cool. It's clearly you know, scratching the surface around what the future of work would look like in an age in a in a world where you have more agent employees than teammates. Um it does feel early. It does feel like they're they're just, you know, like I said, scratching the surface. But, you know, my passion is I I don't know if you know this about me, Vinnie, but I'm a co-founder of a in a company called LCA, Late Checkout Agency. And that business designs like the world's biggest AI native software.
35:17 Not Buzz, but like you know, companies like that. Um and when I see something like this, I'm I'm just like it's close. It's not there yet, um but it's close and I do believe that uh it's probably worth and I have no affiliation with Buzz or Block or or Jack Dorsey, but I do think it's like worth trying these tools just so you can you might learn a thing or two and then even if you don't end up using Buzz, like you might just end up you know, configuring Slack in a way that you know, is best for you and you learn something here. So, I think or you might realize like you love Buzz and forget about Slack and this is what the world you want to live in. Regardless, you you're going to learn. There is no losing in this situation. So, I think um the most important thing we can one of the most important things that we can do in the AI age and the agentic era is just getting our hands dirty, learning how these tools work, playing with them, and seeing how we could live in the future cuz the people that live in the future, Vinnie, those as you know, those are the people that uh could you know, look around the corner Um and who can create products that people really want and you know I think that's really important.
36:36 >> Yeah and um Yeah you bring up a really good point and and I think that's why they're they're kind of looking around the corner with this already and what I think could allow them to really be a strong player in this arena is um the fact that it's open source. Um so anybody you know that has an idea of how to so it's an open source app built on an open protocol um and so anyone who has an idea of how to improve this can and um you know that that might take it in the direction because the the you know the the hive's mind so to speak is like going to be using this thing and working on it at the same time so they'll be like okay this isn't working for me. Uh I like this about like you said trying out some from some other tool or I like this about the tool I usually use I'm going to add that in here or what not so um that might work to their advantage very well and it might become the tool that people just kind of default to um but things change so fast so who the hell knows.
37:41 >> Amen brother. Vinny thank you so much for coming on giving us a tour sharing some sauce. I'll include links in the show notes in the description where you can follow uh Vinny for more of this sort of stuff. Um I would love to have you back on the podcast Vinny the comment section on YouTube please let let me know if you enjoyed Vinny I certainly did uh if you enjoyed this topic what you want me to cover next. Um thank you so much Vinny uh any last words for the people?
38:12 >> Well if if they want me to come back I can show them some sweet stuff about how you can like uh use the open protocol that it's Buzz is built on so you can go pretty deep um and I think there's some pretty powerful stuff there that um we both alluded to in our tweets. So, um yeah, it's worth worth checking out. >> Cool. Yeah, let us know. And uh we we live to serve. So, uh if if that's what people want, we can go deeper. Thank you, Vinnie. Have a creative day, everyone, and I'll see you next time.