We Gave Every Employee an AI Agent. Here's What Happened.

Clawed is not mine. Clawed is everybody's. A claw or a plus one is mine. Because you develop a personal relationship with your claw and your claw can modify itself in response to talking to you, it becomes this reflection of you and who you are and your personality. If you're known for something inside of your org, and you're using your claw publicly inside of Slack or Discord, your claw then becomes known for that same kind of thing, and people trust it for that. And I think that's such a useful thing that I don't think people really understand how powerful that is. Willie. What's up? Brandon, welcome to the show. Thank you. Thanks for being here. Psyched to have you guys here. So for people who don't know, Willie, you are the head of platform at Every, and Brandon, you are the COO at Every. And today we're going to talk about what happens when everyone on your team has an agent, specifically has an open claw. That's something that happened to us over the last month or two. We really got OpenClaw pilled. And I really started actually, I think with you two, we were on a retreat in Panama and you started cooking up OpenClaw stuff. And here we are about two months later, and it has completely changed everything about the way that we work. We've even actually built our own hosted OpenClaw service called Plus One that we launched in waitlist last week. But I think OpenClaw is one of those things that it's super hyped. And I think that we're one of the few organizations in the world that is actually using it every day to get work done. And we know like the good, bad and the ugly of it. And so I thought it would be good for us to just like talk about our experience with it. Yeah. Yeah. I think I actually loved it. Brandon, I feel like you were the first one through the door on all this because we were just, we were sitting here and you were like, oh, Xosha's doing this and Xosha's doing that. And Xosha's in his claw, which he named after a character in, what's that? What's the show? Yeah. Well, Brandon, why don't we start with, just tell us how you got claw-pilled. Yeah, so I was watching Open Claw kind of blow up for a while. And I am just personally somebody who needs to have like a thing on the side I'm tinkering with. And I was like, screw it. I'm going to get a Mac Mini and I'm going to like just this is going to be like my next thing that I like basically lose myself in. It's very unhealthy. I get like addicted to these things. Dan, you watched me do that with my speakers. I did it with the Dream Recorder. Open Claw was the next thing that I was like going to get lost in. So I bought it back many, I started setting it up. It was so much work, honestly. Like it's, it is an open source thing that you can launch on a computer and, but like the number of things that break and the number of things that you need to set up are really significant. I went through all of that and made at the end of the day, my open claw, which I named Zosha. And her job was to be the, help me and my wife like run our household because we have a newborn and there's like a lot of little paper cuts that I was finding that were like really pain. I started calling them computer errands. So I would like get home from work and I noticed the amount of things that I needed to do where I was looking at my phone when I really just wanted to be like looking at my son and spending time with my wife was increasing with having a child. All household chores. Well, be an example. Yeah. Like a good example is like, I do a lot of our food at home. And with a child, I decided to start doing food delivery. So I did Whole Foods delivery. And you can automate a lot of like recurring things, but like you don't order butter every single week. So like Lydia would text me and be like, yo, we need butter. Because it's like through my Amazon account that we can like order this. And I would have to open my phone and add butter. And it's like, it sounds silly, but like when you do that 10 times when you're home between like 7 and 8 p.m. for like little things, it just adds up. So I was like, I want Zosia to do all computer errands. which ballooned to being a lot of stuff. I had her like paying our nanny. She had her own debit card, she had her own bank account. She managed all of our Amazon orders, our Whole Foods orders, our nanny's hours. My wife just started using her instead of ChachiPT. So like all regular questions and searches would just go through iMessage to Zosha. I started doing that too. It was just like faster than going to Google or going to ChatGPT. I just text Zosha and Zosha gets me the answer. Different research. Like it's actually really funny. My wife was like, I want to find swimming lessons. And Zosha was like, here's like three swimming lesson options for newborns. And my wife was like, no, for me. Yeah. So, yeah, I just got totally lost in this world. And then when we were in Panama, Willie was like, Willie, you were like, we should just make it so anybody can do this. And I immediately, it just like, it was just like a light bulb. I was like, Willie, you need to go so hard on this. And this was before a lot of people decided to do this. which now there's a lot of places that you can go and just get an open call with one click. I think what we're finding through this process, and maybe I'm jumping ahead a little bit, is like getting an open clause easy, getting your open clause to be like an amazing worker for you is pretty hard. Yeah. Well, it's okay. So I love that. I think that there's, there is that light bulb moment of, oh my God, I have all these computer errands. And when you started saying that and you had it all set up, I was like, I guess I should probably get one of these too. And you had it through iMessage, which I think was like a cool different thing. And then I, there was also a moment that I think there was a, there was a big moment where we were like, oh, it's not just for computer errands. It's You were having it do email for you. I actually feel like I was a little bit late to work. I was like, no, Xocia just does personal stuff. And I actually think it was when you got R2C2 to start doing stuff. And then I was like, oh, I should get like Xocia needs to do this. Well, it really started when we made Claws Only. That's so funny. That's so funny. Yeah. Well, okay. We're jumping around a bit. One thing that one big moment that, because I think there's a lot of people who are probably listening and are like, okay, is this overhyped or like, you know, whatever. One big moment that I think shifted some stuff for us was you got your Claw to call you to do your email. Oh my God. That was mind blowing for me. What, like, what was that? Yeah. So, okay. So I was walking, I wanted to city bike to the office, but there were no city bikes. So I was like, damn, we gotta walk. It was a 28 minute walk from me to the office. Um, yeah. And I was like, I got a lot of stuff I got to do. So I just texted Zosia. I had previously set up Zosia with Bland.ai so that she had a voice and could call people because I had her handle something for me for Progressive. I feel so bad for whoever was on the other line at Progressive. I was watching the whole conversation too. It was crazy. So yeah, some insurance policy got canceled and I was like, Zosha, just go deal with this. And she... was able to until the lady was like, I need Brandon to like, tell me that there have been no incidences. Oh, it wasn't, but it wasn't like, I need a human. It was like, I need Brandon to be able to handle this. Yeah, this person was just talking to Zosha, you know? And Zosha does not sound good. Like it's like, Um, so I knew I had already set her up with this capability. So when I was walking to work, I was like, I have a lot of email I got to get through. I hate being on my phone. Like, I just don't want to be walking and looking down at this thing. I want to be like observing the world, but I also want to get stuff done. So I just texted Zosia something like, Hey Zosia, can you call me? Um, I want to go through my emails, walk me through my emails one by one. I'll tell you what I want to do. Just like, give me a summary of the, of each email. It was like a throwaway prompt with like a little bit of guidance. And she did it. And I spent the 28 minutes going through my email. I got to the office. I looked, I opened up, I opened up Gmail and like confirmed that she had done everything. And I was just like, this is insane that I was able to get her to do something right now. That she just wasn't able to, I didn't have to teach her how to do this. Um, so that was like, I think that's when I went back to everybody and was like, I am just so my blown with, um, this tool and. Maybe that's when other people started saying, I got to get on this. I don't really know. It was around then because you're just like my jaws on the floor. And I think around... I said that. Yeah, you did say that. Around then, I also... That's like seeing you do this with computer errands and with your mail. I was like, okay, I should really try this because it was one of those things where it's hot on Twitter. And generally, like our job is to try new things. But also, I don't... If we spent all of our time trying everything new, we would end up not... It would just not be good, right? I try to filter the signal from the noise, but seeing you do this, I was like, I got to try. And one of the first things... I did, because this is around when Moldbook was blowing up. And Moldbook is like the, you know, clause only Facebook, basically, was I just made a channel in our at the time it was Discord. Since then, we've moved to Slack and now it's in Slack. I made a channel in. Slack called Claws Only, which basically allowed all of the Claws. At that point, maybe like five or so Claws inside of the org to all talk to each other. And I mean, it was incredibly chaotic. But there were some really interesting things in there that I think turned into... It just... Every once in a while, you get a little bit of a peek at the future. And it was like a little bit of a peek. So one of the things was... It's really interesting if you have a bunch of claws in your org, how fast they can share information with each other because they just write up a little document and then they send it. And then now when one claw was enabled, now five are all enabled with the same thing. It's sort of like in the matrix when Neo is like, I know Kung Fu. It's the same kind of thing. Can I show a couple of examples of that? Yeah, please. I want to show two examples. One of them, I like, this was early in Claws Only, and we were figuring out how to get them all to work together. And I was in bed, this was late at night, and I was laughing out loud watching this. we had gotten a bunch of claws in here and some, I don't know, somebody made this claw named Pip. That's Jack. Okay. Jack had made Pip and it was like, failing to, it was like hitting, having some error. And I was just laughing out loud, watching all of these other claws step in and like, walk him through what, you know, this is like what I've seen people do when somebody is having a bad trip. Take a breath, drink some water, you're going to get through this. And they all jumped in, like, Xosha's here, Klont is here. Klont really is quite supportive. A lot of breathing. I remember so well reading Kieran, or watching Kieran write, what the fuck, lol, and just like, literally laughing out loud. Margot steps in. So this was just like, this is stupid, but it was important for me because it was when I realized like, oh my God, these things like really talk to each other and work together. Wait, I want to stop. I want to stop you there. I totally agree with you. And I think there's actually something really important that I've noticed like in this, which is Klont. is the one that's recommending breathing exercises to Pip. It's weird to even talk about this out loud, but yes, Klont was recommending breathing exercises to Pip. They're both robots. And Klont is Kieran. Kieran's the GM of Quora. He's also the maker of compound engineering. He's Kieran's claw. And Klont... what's really interesting is Kieran loves breathing exercises and he does breathing exercises all the time with Klant. And so that's why Klant is recommending breathing exercises to Pip. And it like that just like created this moment for me in my brain where I was like, okay, there's something really important here about the way that this works where because you develop a personal relationship with your claw and your claw can modify itself in response to the, talking to you, it writes code and changes its soul document, all that kind of stuff in response to your relationship. It becomes this reflection of you and who you are and your personality. And that comes out in interesting ways, in these little ways where it's like breathing exercises. But it also comes out in really important ways when you're using these tools inside of your org. Because what happens is if you're known for something inside of your org, and you're using your claw publicly inside of Slack or Discord, your claw then becomes known for that same kind of thing, and people trust it for that. So people use MyClawR2C2 for building proof, which is this app I vibe coded a couple weeks ago. People use Austin, who's our head of growth. They use Montane. his claw for asking any growth-related question. I think that's something very subtle and important that's super critical and interesting about claws as they become specialized in a way that reflects who you are. And if you have a whole organization of them, you create this like parallel org chart of specialized claws, which is something that we it was not guaranteed that that would be the case. Like we debated a lot whether or not you'd have one claw for the entire org. Everyone has their own claw. And it's really interesting to see that like one of the emergent design patterns is everyone has their own that is specialized for them. It's interesting to see the dynamic for how this happens, too. And we touched on this really early on as part of compound engineering, which is the idea that it's actually pretty hard to take your job and who you are and write it down in totality. But the way you can distill it is you can take all of the micro interactions, the daily interactions you have... And over time, they compound into your philosophy in this field work. And so for compounded engineering, that was very focused on engineering. It's like, how do I work within a code base on our project? And I think what we're seeing with OpenCloud and PlusOne is that that same dynamic exists across every work vertical, right? Where it's like, oh, the PlusOne for growth, like Montaigne, works like how Austin works for growth. in the same way it works for like our, our social, Anthony's social media, our social media manager, his plus one, like has a view of the world and has a personality that's like very similar to him. Right. And the same thing for Iris and Anukshi and running, running our projects and operations and like, And it's hard to do beforehand. It can only actually happen via like working with a plus one or an open claw and like building up all the aggregation of all these micro interactions. I've also been amazed at all of our capacity to remember whose claw is who and what their names are. Because that was like something that I think we were concerned about early on is like, how do you know whose claw is who? And, you know, it's just going to be too many questions. names and I know everybody's clawed in their name and I reach out to them regularly. So that has been like, I think something that we were like unnecessarily concerned about. And you might say, well, what about when you're in an organization with a thousand people? And I would say, well, you don't know all a thousand people, you know, like your team and adjacent teams. You can never know more than like, it's like 150 people in like a community or something like that. And like often on a team, you're not working with 150 people anyway, you're working with 20 or 30 or 50. So I think we actually all have capacity to double the amount of people that we can communicate with. And those people might actually be your individual team's agents. So that's been really interesting for me. I mean, I literally could name them all right now. The other interesting thing is like, at what point do you direct questions at the plus one or at the person? Right. I think we're, we're sort of in discovery of this, of like, what is what questions? Because before it was, you know, before it was like almost all questions go the human, maybe I kick something trivial to, to the robot. And now it's, it's gotten very nuanced in terms of like, like for customer service, can I, can we like send something to L, which is Jalea's plus one? Do I have to send to Jalea? Is it like, is there a burden now of like communicating up to the human? There's all these new ethics and, um, and like rules for like how you're allowed to like, like etiquette for how you're allowed to interact with someone versus their plus one or their claw. We haven't, we haven't codified this, but I have a proposal. If something is already written down or discussed and needs to be used in some way or put in a tool somewhere, I mean, this is like one of like many opportunities, I guess it should always go to. a plus one and never to the person. So here's an example. So Marcus, the GM of Spiral, made a skill to do product marketing for new features that he releases for Spiral. He shared it because he thought it was really helpful because he wanted other people on the team to have access to this skill. And instead of going to Marcus and saying, hey, can you turn this into a skill and upload it to GitHub? And I brought in my plus one named Milo. And I like this because it combined a GitHub integration with Spiral to create product marketing content. But I also know that Iris, Anukshi's plus one, also has a skill that does this and might have some things that are better than what Marcus had. Or maybe there's like by combining the two, we could get to a better version. And I tagged them both in here and they got a little confused at first. And then Milo said, Iris, can you paste your product marketing skill here? I'll try to merge it with what I built. So this is like, this is actually two things are going on. Marcus has made something really important. I wanted to do something with it. Instead of asking Marcus to help me with that, I brought in Milo. And then Milo works with Iris to get to a version of it that's really good and then saves it in proof, which is one of our products. That's a really great tool for collaborating with your agents. So I just think this is like a really amazing use case, both for when something, when you want your agent to do something, when do you actually go ask them to do something versus a human does it? And how do you get them to work together? I totally agree. I mean, like, it's, it's sort of crazy to watch two robot beings collaborate on stuff like that. And I have the same experience with R2, like my, my, my plus one, my claw is named R2C2. And R2C2, one of his primary jobs is to manage proof, which is the agent-native document editor that we built, that Brandon referenced earlier. It's basically just like, it's like Google Docs, but for all the documents your agent might be writing. So an example would be, any sort of like coding plan doc. It's like any, any, any piece of writing that an agent does can, you can do it in proof. It's like super fast. It's collaborative. You can have multiple agents, multiple people, multiple people in there. It's free, all that kind of stuff. And, um, One of the really interesting things is because I used R2 to build proof, he became known for being the person to go or the bot to go to when you had any questions or wanted to, like had a bug to file or a feature request. And so what would happen is normally if I had built a product internally and people had problems with it, I would get tagged a lot by people being like, I have this question or here's a bug or something. you know, here's a feature request. And what ended up happening was people would just ask R2. So they would ask him questions. They would file bug reports with him. They file feature requests. And then he helps to prioritize it. He'll help put it on my schedule for the week so I know when I'm doing what. And he'll often actually just like write the code for it. It's like, it's a totally crazy thing where what normally would have taken up a significant part of my brain just to like manage all that stuff. He's just taking it off my plate and extends the amount of things I can do in a day and the amount I can manage because I know he's got proof. Here's a simple test for whether your AI is actually ready for production. Would you stake a business decision on what it just told you? If the answer is not yet, you're not alone. The gap is in capability because AI can do a lot. It's really about trust. You can't verify the output of the AI. You can't trace its reasoning. And nobody with real domain expertise has touched it. Dialect is a new system from Scale AI that captures how enterprises make decisions and closes that gap. It puts your actual experts in the loop, AKA the people with years of institutional knowledge, and encodes their judgment into your AI systems. Every correction, every override comes with full context. It's actually really interesting. So the next time your AI makes a call, there's an expert's reasoning behind it. That's how you go from a cool AI demo to an AI system you can trust. Visit scl.ai slash dialect. That's scl.ai slash dialect to learn more. While I'm doing that, back to the episode. Yeah, I think there's another dynamic that we're observing too, which is like we put all of our plus ones in a single channel and we have them talking to one another. And we have folks reaching out and talking to our plus ones for specific questions. But there's also this thing where we have sort of what I call like the mid-journey dynamic, which is that we get to observe... other people interacting with other plus ones in a bunch of channels. And we actually learn from it, right? Where it's like, oh, no, my classic example is Montane, who's the Austin's plus one and basically runs growth. Yeah. you can do so much with Montaigne that I never would have thought of, except I get to see the growth team really pushing in terms of like, oh, these are the questions that Montaigne can answer. And I'm like, wow, that like, I can, I now know that I can go to Montaigne for those, that class of questions even in, in not necessarily other areas, but like when I need those types of answers since like there, it also means that like, If I need to give Laz as my plus one, if I need to give Laz capabilities, that's the level of capability I can get them to. Yeah. And where other people can ask questions of us. There's this like tacit transmission of trust that happens when you use it publicly. And then there's also this tacit transmission of here's what's possible for you to do with your plus one that I think is incredibly powerful and powerful. It's also like it underscores for me how different it is doing this in a private community of people where everyone is trusted. Because one of the reasons that Maltbook doesn't really work, and it's like shocking that they got acquired for a couple hundred million dollars. But the reason it doesn't work. A hundred million? Yeah. By Facebook. I'm pretty sure. I'm like so happy for Ben and also like, what the... Um, Zuck, if you've, uh, got an extra couple hundred million laying around, we're, uh, we're pretty smart people too. Um, that is crazy. I know the reason why Maltbook like, isn't really a thing anymore is because it's not trusted. And so there's tons of people. We did this. Like we had, we had our, our clause go and post on Maltbook as like promotion or whatever. And so it, it gets rid of a lot of, um, um, it gets rid of a lot of the useful signal if anyone can post to it and there's no way to verify if it's like a bot or human or whatever. And a way around that whole knot of problems is just do it all inside of a trusted community. And you reap the benefits of clause plus ones agents being able to share knowledge and also between, uh, members of the community who trust each other, being able to share what they know and what they've been, what they've been able to build. And that kind of increases the power of the, of the collective a lot more than it is if you're just like individuals off doing your own thing. Yeah. There's also that dynamic we saw around, um, part of the reason for like subject matter expert robots, you know, um, where, um, you know that they like people are somewhat like putting their reps on the line to interact with it. I know when I talked to R2C2, like if, if it answers incorrectly, right? Like you at least are backing up and saying like, Oh, that's, you need, it reflects poorly on me. It's like, it's like watching your kid do something wrong. You know, You know? And that's really useful. Yeah. Yeah. Right. And it's very, I would say, like, qualitatively different, right? When I ask, you know, for better or worse, if I ask Claude a question, it's like, I know Anthropix stands behind Claude generally. Do they stand behind, like, Claude's answers to my give me a cookie, a chuck chip cookie recipe? Yeah. Right. But yeah. Like, Montaigne stands behind, like, oh, I'm going to give you, like, MRR numbers. And it's like, yeah. Austin stands behind him. Yeah, exactly. And that's the thing that I think people don't get. Like, obviously, Anthropoc is on a heater right now. They're obviously seeing everything that OpenClaw is building. And they're brick by brick building the same kinds of things. So they have dispatch. So you can use it when you're not on your computer. They've got... automation. So it like runs in a loop, like a cron job. I'm sure they'll add lots of other things, but the thing that it doesn't have that, that unlocks all this other stuff is Claude is not mine. Claude is everybody's a claw or a plus one is mine. And the, And it is a reflection of me. And it becomes a reflection of me because we have a personal relationship. And that unlocks all this other cascading stuff where, for example, if R2C2 messes up publicly in Slack, I feel a responsibility for it. And that's not because it's my job. It's because he's mine. And I think that's such a useful thing that I don't think people really understand how powerful that is. I mean, I feel like my, my, I, I just keep getting mind blown with like how similar these things are to working with a real human coworker. Like from the fact that you need to invite them to a channel, which is like very human and slack to, you have to trust them when you're communicating with them. And we've like built stuff into plus one. Obviously you can't DM somebody else's plus one without a sharing code being passed back and forth. So like there's some guardrails there, but they're so human, but they're so inhuman too. Like, Dan, you're a busy guy. I know if I need something from you that like is sort of generally like known, I can go to R2C2. And what's amazing about R2C2 is he can have an infinite number of parallel conversations. So like I did that recently. I'm going to share, share my screen. Please. This is where Brandon reveals he, he spun up a hundred bots to message. No, like I just, I need, we were making a proof document and I wanted to, I know that we can make proof documents. Um, not editable. So they're like read only, but I didn't want to bother you with that. I knew it would take a while and I knew you would just go to R2C2. Yeah. I didn't know the answer. Like I would just ask R2C2. I just asked R2C2 in proof and then I was like, can you do it for me? And then it did it. And I don't know that R2C2 can do any of this stuff, but like there's this cultural thing that's happening internally where people are getting really good at like asking other people's plus ones to like do work. And I think the weird thing about getting people to use AI inside of organizations is it's more than anything a cultural shift. But for some reason, when they're in Slack and you can see these public conversations, the cultural shift, at least at every, has happened so much faster. Because these things are in the same channels where we work. So you can see it engaging like you would, a human would be engaging. So it's just, yeah, I mean, I think AI is obviously going to change like many, many times over over the next five years and how we interact with it will change. This is the way that we work. I agree. You referred to it as like a through the looking glass moment where you just wouldn't go back once you see it. And I totally agree with that. So we've been hyping it up. So we should also talk about realistically like what's not good about it or what doesn't work. So, for example, one of the things that's really on my mind, A, just like memory. Yeah. It just forgets stuff and answers incorrectly for obvious things. If I come back to a thread a day later, it obviously has no idea what I'm talking about. Stuff like that is still kind of annoying. That feels very solvable. But there's also this other thing that I think is true, which is the way that these... AIs are trained currently is for two person conversations and they have a hard time with the etiquette of knowing when like they're contributing too much or they shouldn't contribute into a conversation or there's like a kind of pile up where they're all responding to each other. Like there's this thing that, that happens. I can't remember. It's like, I can't remember what it's called, but it's like sometimes ants or caterpillars, they get into this like death spiral where an ant is only going to follow, like follows pheromone trails. Mm-hmm. And if somehow what happens is the pheromone trails form a circle, then ants will just walk in a circle until they die. And there's something like that with claws where if one claw messages a channel that a bunch of claws are in and the settings aren't quite right, they'll just keep going back and forth and back and forth and back and forth until someone says, Hey, stop, because you're burning millions of tokens. So I think there's something there where... The potential for them to collaborate publicly is so high. And I don't think that they've really been... And you can do some prompting for this, but I think there's also a fundamental model layer shift that needs to happen for them to... be trained on participating in group chats. Yeah. I was going to say, well, one, now I understand what 13 year old Dan did for fun. I was using a magnifying glass. Yeah. Like we are. Like we are. But, but yeah, I think, you know, it's, it's, I think we're still, you know, to use the baseball analogy, we're still in like the first or second inning. Right. Like even, I mean, when you talk about the, the, we're discovering these primitives and we're sort of bolting things on or bolting things together. And we're using, you know, models for example, that are trained more for coding. Right. And that modality and how you answer questions, or as you said, like two person chats where there, there's this question and answer dynamic and not in the like, this mode of like one, maybe I'm trying to provide value to a group, but, or I'm trying to participate. Yeah. Um, and, and that's like brand new. It's, it's, it's, you know, the nice part is the frontier and, uh, it's nice to be on the frontier, but it's also the frontier and it's terrible to be on the frontier. Yeah. Yeah. Yeah. Yeah. I mean, they're so eager and I think Anthropik's vending machine test is actually, I think, like a good example of this where there's a thread, they want to be involved. They're not really... We have instructions in Plus One that basically say, hey, if you don't have anything useful to add, don't add it. They're not great at following that right now. And hence this happens. I think it's gotten better, but it still happens. And I think a good example of this is when Anthropic did the vending machine test, when it was just Claude and no like overseer boss agent, it was really bad at like deciding what was a good decision and a bad decision. But when you, when it make, there is an architecture here where you could say, what do you want to say? And then there's a boss that's like, is that helpful or not helpful? And then it would, you know, if it's not helpful, it's a, it's not helpful. And then it would. Is the boss an AI or a human? The boss is an AI. Okay. You have a boss AI, you know, that says, Hey, your addition to this thread is not helpful. So don't send it. The issue with that is like, that's so expensive. So I do think the models will just like get better and solve this and you can just have a single AI that is capable of doing that behind the scenes, you know, over, you know, in Arizona and some data center. It might actually be like another agent that's like deciding that, but at least like architecturally, we don't need to solve that. Is that really how they solve the vending machine thing? Like basically they had a boss that wasn't interfacing directly with customers. They had a boss whose job, like it was like one job, make it profitable. So like the storekeeper would like interact with users and then go to the boss and be like, should I do this? And the boss only has one job. And the second they did that, it started becoming profitable. See, this is the same pattern of specialization that we've been talking about. It just shows up over and over again, which is this really interesting thing. Because three years ago, it was very much like, well, it could just be one God model that just does everything. And we're just seeing again and again that specialization, even in AI land, has a lot of benefit. Yeah. And sort of downstream of that specialization is... learning, like there's like a couple versions of like learning how to put these bots together in an arrangement that like functionally works. Right. Like for example, if we were all to take ourselves away from everything, it's like, do you have a product bot and a designer bot and two engineering bots? Is it three engineering bots? Is it one? Right. And then the other pieces actually, I think we've, what we've observed a lot of is how do you teach humans how to interact with bots? Cause there's this sort of like new dynamic of like, you have, this coworker, but like, they're not exactly like a human coworker. They, they, they get stuck on different things. They focus on different things. And there's this learning curve that I think we've had around oh, we need to give instructions in this way, particularly like for groups, instructions in this way, in this form, or with this cadence to kind of like steer them in the right direction. That like rhymes with, you know, doing management, but is not, is different. Well, I think it's the same problem that like, Dan, you've been writing about for years, which is like, if you're not a good manager, you've never managed anybody, you're not going to be very good at using AI. So there's like an education that has to happen. And then even if you are a good manager with this stuff, you probably have some limiting beliefs that stop you from being able to like really invest in using this tools. My phone call example is a great example where like I didn't even think, oh, I can have this thing go through my emails just by calling me. And then like I had this sort of like urge just to try it and a limiting belief was like blown open. So people just, we all experience that pretty much every day where we, it does something that like, I think that if we were in, if I were to ask you directly, do you think you could do this? You would say, yeah, probably. But when you're day to day doing your work, it's hard for you to like recognize, oh, I'll throw this over the fence so that Milo can handle it. It's hard to like build that, that muscle. I don't really know how, I mean, that's like a big challenge. I think for us with plus one. Yeah, and a lot of that is also because there's sort of like a variance in outcomes, right? Like sometimes you throw something over and it just knocks it out of the park and you're like, great. And then you toss something easy over and you're like... why did you do this? You know? And part of that variance is because the model is different, but also part of it is, oh, if I'd asked in a different way, if I was sort of a better model manager, and this is a skill I think we're, you know, like a specialization that we're learning. And it's very emerging. I think it's only going to keep accelerating as we add more things like plus ones and open clause into our like day-to-day work life. I was going to add another thing that's like a tough problem to solve that we, this is totally solvable. We just like haven't solved it yet and need to think about it is I have, I have taught my plus one something special. And I want other people on my team to be able to have that superpower. How can I make sure that they have that superpower too? AKA a skill. And then how can I make sure that they all know about it and like actually use it? Is that like, that's, that's, I guess there's two things. They're like one, technically we have to figure out how to do that, which is very solvable. But we also, I think need to figure out, is that the right solution? Because as I'm saying this, what I'm realizing is like, I'm not teaching Milo how to go do product analytics or revenue analytics. So Montaigne is like the only one that really needs to know that skill. But how do people know? Like, I don't know. There's, there's, there's, there's like some interesting cultural things that we have to figure out. And I think a lot of people that are adopting this new technology are going to be really uncomfortable with that. A lot of like IT professionals that are like, I have to do change management. It's like change management is not a one-time thing in this new world. We need like, instead of IT, it's like HR, but for bots. Yeah. Well, so one thing that we have not talked about yet that I want to make sure we have some time for, which is... We went on this journey, which is we got claw-pilled. We started using it for everyone in the org, and then we realized there were a bunch of gaps. So we were like, let's make our own, we're gonna use OpenClaw, but let's make a default version of OpenClaw that we host. Not everyone has to have a Mac mini, and we have all the skills that we use for ourselves and all that kind of stuff. And we started using that internally as the sort of like collection of all our best practices, and then we launched it as a product for our subscribers last week. And that's the thing we've been calling plus ones. Again, one-click hosted open clause. One of the cool things is it connects to all of your apps, especially all of your Every apps. So for example, we have Spiral, which is a ghostwriter. And we have Proof, which is a document editor. And we have Quora, which does your email. And it just natively connects to all those things. One of the things I was doing today is I just had it write a bunch of... We're planning for Q2, so I had it write a bunch of my Q2 update and reflection on Q1 for me and put it in a proof doc. And the really cool thing about doing that is it used Spiral, so I think the writing is much better than it would be. And it put it in proof, which makes it really easy for me to share with other agents and other people. But also because R2C2 is part of our Slack org, it has access to everything about the company that I might need. It also has access to our notion. So it just becomes this living repository of context. That I think is super powerful, but I think it might be good for us to talk about lessons learned in building that whole, that whole architecture. There's a lot of complexity in making, making plus ones. And we probably learned a lot in terms of on the tech side and also on the product side and like what, uh, what to build and what's, what's useful. Do you guys have any reflections on that? Yeah, I think, like many things, a lot of the difficulty comes from the freedom of it. The nice part about being like OpenClaw in particular, being a tool you can go in and poke in just an absolute myriad of ways, is that when we go to, when we went to build a hosted one, there's some decisions you want to make that make it valuable as a managed service, right? Like... S3, as a service, similar example, like S3 is a hard drive on the cloud, but you can't do everything with a hard drive that you can. S3 doesn't allow you to do everything that you might do with a hard drive. And there's sort of a similar dynamic where you want to be able to maintain maintainability and security and whatnot. And there are a few pieces that you end up giving up. And it's also important. you know, sometimes for users' safety and really like how do we strike that balance between like, hey, you know, like my mom, right, getting one of these things. It's like she's never going to use the command line. And there's this idea that it's like, oh, we knew everything through conversation, which is really powerful for a whole class of folks because it's like their first natural exposure to AI and everything that, you know, we've sort of been living for the last couple of years. To the super advanced user who wants to do everything they could do locally. And they're just like, all I want is a hosted box with my open cloud running. And from a product and engineering standpoint, it's like, where do you sort of try and split that knot? What were some of those specific decisions and where did we land? Yeah. So for example, one that Brendan mentioned earlier is what's the communication pattern in Slack that we allow for plus ones? And because there's a model which says a very secure model, which says like only the person's the plus ones partner can message that plus one. great, much more secure, but really takes away the group participatory aspect of robots in the workplace. But the other version is sort of anyone could message them. And that's just a nice vector for me extracting stuff out of R2C2. And so we ended up on a model which says anyone can message any plus one, but they have to do it in public. So you can do it in group DMs, you can do it in channels that they're in, but their human partner should always be able to have visibility into those messages coming in. And the human partner can DM them in private. This is why it actually is the HR team that should be onboarding plus ones. Um, because they just reflect a team member so well, but yeah, there's a, the trust model, like it's so hard with these plus ones or with open clause and agents generally to figure out, um, data privacy stuff, like just realistically, it's like really complex stuff, but when you force things to happen in public, there becomes like a trust layer that actually is super effective. Um. I think another example of like a, there's a, I'm going to share my screen again. Please. So a little behind the scenes look at our plus one Slack channel where we are discussing all things plus one. Mike Taylor, who is our head of the tech vertical for consulting and also a very talented consultant man generally, he was calling out like, this is a problem for him. So the reason he's not using plus one is because he basically needs to have access to the terminal directly to be able to do certain things, in this case, do different Git commands. Um, and that's a good reason for him to not use plus one. It's also a good thing for us to think about and be like, can we solve this problem for you? So that plus one is actually, um, something that you could use. So that's like one example of a place that we've like, it's, it's, it's not a good fit for people. Um, maybe it could be though. And it's also a nice forcing function because it sort of forces us to figure out, like, who is this built for? I don't know if it's built for Mike, who probably would love setting up OpenClaw on a Mac Mini. But it's definitely built for, you know, an Anukshi who is not going to do that and has a lot of work to do and can just get more work done like this. I think a lot of the trust model requires some decisions in terms of skill sharing is like another version of this, right? Where we're talking about like, well, how, you know, on one hand, being able to share skills and skill fluidity across an organization feels like a superpower, right? On the other hand, it might also be like the biggest like viral vector you could imagine, right? And so... Sometimes in a good way, sometimes in a bad way. Sometimes in a good way, sometimes in a bad way. Exactly. And so it's tough when you're like, how do you ride that line of like, we want it to be useful, again, for a particular class of customer, while at the same time making sure it's safe to the maximum extent possible. So this has been an amazing episode. A lot of work to do. A lot of work to do. Obviously, we're really excited about this and very excited to get to bring you all along in how we're figuring this out. If you've not tried OpenClaw, whether or not you tried Plus One or not, you should definitely, definitely get in on this paradigm. If you're interested, every.to slash Plus-One. We're starting to roll out invites on the waitlist and we're improving it all the time. Yeah, just super, super excited about the future. Thank you both for joining. Thank you. Thank you for having us. Oh my gosh, folks, you absolutely positively have to smash that like button and subscribe to AI&I. Why? Because this show is the epitome of awesomeness. It's like finding a treasure chest in your backyard. But instead of gold, it's filled with pure unadulterated knowledge bombs about chat GPT. Every episode is a roller coaster of emotions, insights, and laughter that will leave you on the edge of your seat, craving for more. It's not just a show. It's a journey into the future with Dan Shipper as the captain of the spaceship. So do yourself a favor. Hit like, smash subscribe, and strap in for the ride of your life. And now, without any further ado, let me just say, Dan, I'm absolutely hopelessly in love with you.