I tested 4 AI agents on 9 real tasks. Here’s who won.

0:00I told you all I have personal agent fatigue, but I am here for you. So today I am going into the personal agent minds and I am running the very first how I AI personal agent benchmark which goes across four agents in nine tasks to tell you what personal agent is actually the best. I am going to try to run this in the most unbiased equal way. I will tell you how I set up the benchmark, what is in the benchmark, how I ran the benchmark, and then we're going to look at the results and at the very end get a summary of what agent I think does best

0:40on which task. This was a really fun and also hard one to run. I spent definitely several hours today figuring out how to run this and getting it done. I hope that you all find this helpful and I am going to be along the ride with you because I really haven't looked at many of these results and so we're going to look at them live. We're going to see how it goes and I'm going to tell you which personal agent is the best for you. This episode is brought to you by work OS. [music] AI has already changed how we work. Tools are helping teams write better code, analyze customer

1:12data, and even handle support tickets automatically. [music] But there's a catch. These tools only work well when they have deep [music] access to company systems. Your co-pilot needs to see your entire codebase. Your chatbot needs to search across [music] internal docs. And for enterprise buyers, that raises serious security concerns. That's why these apps face intense IT scrutiny from day one. To pass, they need secure authentication, access controls, audit logs, the whole

1:41suite of enterprise [music] features. Building all that from scratch, it's a massive lift. That's where work OS comes in. Work OS gives you drop-in [music] APIs for enterprise features so your app can become enterprise ready and scale up market faster. Think of it like Stripe for enterprise [music] features. OpenAI, Perplexity, and Cursor are already using work OS to move faster and meet enterprise demands. [music] Join them and hundreds of other industry leaders

2:09at workos.com. Start building today. Okay, before I go into the results of the benchmark, I just want to tell you how I came up with this bench. So, the first thing I did is I went into all my agents. I went into Dot, Grockbot, Muse, and Duet, Claude's Duet, and I said, "I'm going to run a benchmark. Give me

2:30like the top tasks that you do for me." And so each of them gave me their top 10 tasks. And then I put them all on a cloud and I said, "Okay, come up with a way to run a personal benchmark against this, picking the tasks that were most common across the agents." Because to be honest, I use different agents for different things. And so I wanted to find sort of the most crosscutting use cases as well as use cases that would test different components. And then the way I was going to run this is I was going to have one operator agent which was going to use computer use to run all

3:03the other agents. um and then keep the benchmark going and and so on and so forth. The one problem with my operator agent plan was I also needed to run dot and codeex is my favorite computer use agent. So just to be very clear, I had Claude run dot and then I had codeex run claude grobbot and muse. So there's like a little bit of diff in the operator agent, but I thought this was pretty clever. The other thing that I wanted to make sure was that all of my agents had access to the same things. And this was a really good tip for you all that are

3:39suffering like me where you have all these agents and they all have access to like a couple different email addresses, a couple different connectors, like one's connected here, one isn't connected there. So, one tip I have for you all is I had Codeex use browser use to check that all my agents were connected to roughly the same stuff and had access to the same skills. So just to set the baseline, we picked a couple of tasks across the top ones for all my agents. I used codecs to make sure they

4:07all had access to the same things. Although I forgot one of my agents, Muse, and that they all had access to the same skills. So they were like as baselined as humanly possible, although of course they all benefit from memory and all the different things that are in each of those agents. So then I had this even kind of like plan. And then what I did is I had eight, actually nine use cases that I was going to test each of these agents against and created very specific lightweight prompts for each of these. I didn't want it to do that like sort of AI prompting where it does like a

4:45paragraph for you. I was like, keep it in my voice. Do exactly what I would do. And so I plan there's actually nine here. I'll I'll walk you through them. run sheet of tasks with the prompt um if an agent asks for something, what you should say, and um how you can nudge it. And so the tasks that I came up with were drafting a reply um in Slack to my friend at lovable that asked me for something this morning. Um cutting a short form video, fixing a bug from Sentry, um building a how I AI thumbnail, triaging my inbox for to-dos, building a family newspaper, explaining a physics

5:25um question answer to me because I'm going to explain it to my fourth grader. going shopping for shoes and then making a chat purity launch video. So those were the tasks and then as I said I had quad computer use run dot and then I had codeex run computer use against claw duet grobbot and muse and then I had it run and time all the things and do all the results. Before we get into the full

5:55results just a couple observations. one is man I'm now going to have computer root use run all my agents running other agents like the parallelism of this exercise was thrilling to the heart um two I did forget to hook up Muse to a bunch of business tools I just don't use Muse for business stuff and one of the things I I noticed is as I was like the bench was running I was like oh I forgot to hook up Slack Slack isn't in the connector list and so it was just kind of annoying. So it's very clear that Muse is sort of like the one off the side

6:33that's not really meant for business necessarily. It's really more of a personal agent. Um and then claude computer use is just hot garbage. Um so I was like super frustrated having clawed computer use, but I needed something other than codecs to run codecs. And so we get what we get and we don't get upset, but I did not love clawed computer use. So, let's dive into the results. I'm actually recording um my audio right now. So, as I talk through the results and tell you what I think, we're going to put that into Claude at the very end. It's going to score all these things and come up with

7:11which one I like the best. So, this sort of live human in the loop scoring, but I am going to go through all these, tell you what I think, and we can see if you agree as well. So, let's go for it. All right. So this is how IA personal benchmark. Dot, Grock, Muse, and Claude call out here. Muse and Claude could

7:28only get seven of the nine tasks done. Um, we will see if that was human error or agent error, but Dot and Grock completed all the tasks. Okay, so how we ran it again, the prompts were just one line. They were very human driven. They weren't those like big um AI prompts. The agent did not drive itself. So the agent was driven by an operator agent. I had to like babysit things. So I had to nudge things. Computer use broke. All that kind of stuff. So I was kind of in the loop. So we did a little zigzag and then actually judge blind is fake. I am

7:58judging it not blind. I'm going to judge it live on this episode and you all are going to come along with me on my judging journey. Okay. Here's the entry scoreboard and then we'll do the final score at the end. Just a couple things to see right off the bat. Muse is very fast. Muse was the fastest in four out of the nine tasks. even though it had to be steered the most. Um, Grock and Dot also had a couple tasks where they finished very fast and then Claude was overall and in incremental tasks the slowest. I called this out in my recent

8:34Claude Duet um review just super slow. So, I like forgot what it was doing. Kind of frustrating. And then you can see here, this is really funny. Claude asked for the most permissions. Like Claude was the most timid. So you can see it asked four times for permission where all the other ones only asked once. So very interesting kind of meta view on safety and and stuff like that here with claude. So let's look at minutes per task. So you can see dot and claude are generally the slowest and then muse is consistently the fastest. Um, Muse was the fastest on building a thumbnail, going through my

9:16inbox, building a family newspaper and building a launch video. Grock was fastest at drafting a reply as me and fixing a bug. Interestingly enough, it was the fastest at coding. And then Codex was the fastest at making a video and actually shopping for shoes for me, though we'll see how um good of a job that it did. Dot was also the slowest on a lot of tasks. And then Claude, for whatever reason, was very slow on replying as an email. So, you know, this impression that I had in my Muse review where I said Muse is very fast, actually held up in this experiment. And then my

9:53impression that Claude was very slow also held up in the experiment. So, while you all may think that my um reviews are not scientific, they are in fact backed up by this very um tremendously accurate data science. Okay. So, let's go through the tasks. So, the first one was replying to me. It was replying to a Slack. It was replying to a Slack to my friend at Lovable who asked me to do a talk. So, I will say all of these were fine. Um, Muse couldn't do it because it didn't have access to Slack again because I don't really hook it up to Slack. That's just

10:29not what I'm using it for. All of them were great. All of them said, "Yes, I will do this event." But I did like DOT in particular because it asked for me to be paid and it asked if it was remote. And if you don't know me, I like to be paid to do things and I like to not leave my house. So it did feel like Chad GBTC dot knew me the best and knew about the things that I cared about. My schedule is busy. I need to get paid if I'm using my time. All this kind of stuff. I promise Lovable I'll do it for

11:04you. I'm happy to do it. But it was pretty interesting to see Dot was the only one that did it. All the other ones were fine. I would call this, you know, Claude is the shortest that actually did the most inaccurate response. So, if I'm just eyeballing this, Muse didn't do it. Quad did short, but okay. I would say Grock is most in my voice and Dot did the most accurate job. So again, I think any of these tools is fine. They all did fine. This

11:37is not a very hard task. Okay. Now, here's the fun one. I had um these agents make videos for our Monday episode with Blair from Reddit. And so it actually all it did was go into my Dropbox, find the raw video, pull it down, cut it, and make the video. Claude could not do it. Duet could not do it. It would not download a video. So Claude totally faceplanted on this one. Um gets a big fat donut um on on Claude Duet for video editing. But dot Grock and Used did them. And we're just going to go ahead. Why not? Let's watch a little of them live. Not

12:20listening. What is your prompting strategy? How do you get it back on track? I don't yell at them. I know some folks do. But what I do is I take a day and then I get more vague. And we all have bots with projects and Hey, that was dot. What is your prompting strategy? How do you get it

12:33back on track? So, I don't yell at them. I know some folks do. Uh, but what I do is I take a day and then I get uh that was Grock. Grock has bad overlays, but it did the like zooming in, zooming out videos better. Let's look at Muse real quick. What's your prompting strategy? How do you get it

12:49back on track? I don't yell at them. I know some folks do, but what I do is I take a day and then I get more vague. And we all have bots with projects and context and I pop out of a project and I describe the thing large like a movie director. So here are all the facts and then here's all the intents and then I pull that back into the project and then it knows enough to apply it to what our goals

13:11are. Okay, so this is what I will say very very hot takes. Again, Claude didn't do it. These were all like kind of impressive in that I didn't touch them. the the design of the one that I like the most is Muse. So Muse is very simple. It's got the Howa AI tag in the front. The um the caption layout is ours. There's no funky stuff. The cuts are punchy. They don't do the zoom in, zoom out, but it's okay. The design of Grock is terrible. Um and it's got this like overlay on his forehead, which is very unattractive, but it did that zoom in, zoom out. And then I would say D

13:47looks very good. It looks just like the Muse one, but it again just doesn't have those punchy cuts. So, I'm going to give it to Muse. I'm giving it to Muse. I think Muse would do the best. And then I think, you know, Claude failed. Grock probably the worst. And Dot second choice. So, again, I didn't really give it much to work with. I gave it access to the transcript, a raw video. I didn't touch it and all of these cut. I think with a better skill it could have done a better job, but I was actually really surprised by Muse because I have not had

14:22Muse do this task before and it really nailed it out the gate. So, I don't know if you all know this, but I've been using Muse a lot for social, specifically posting social, but I may start to think about Muse for creating these social posts as well because it did quite a nice job. The other thing to call out is Grock did the worst and took the longest. So again, I don't think it's really optimized for this video cutting use case. And then dot was it it can't tell how long it did. I think it took about 7 minutes. Was good. Not great at this short. Okay. The next one

14:58was fixing a bug. So classic coding use case. Again, another one that had one of these agents fail. Muse did not do it. I don't have GitHub access to Muse. I don't actually have any business system access in Muse. Um, so Muse didn't nothing. I asked it to maybe assign it to Devon in linear and it thought Devon

15:17was a person. Devon is not a person. Devon is an agent. So Muse fell off the board. But let's look at the other ones. They all took about 10 minutes to get this done. And I actually had Claude Opus 55 go grade the fixes. And we'll just look at them right here. So, dotcodeex got closest to the actual fix. So, that one did um the fix that we thought was the most accurate for the bug. Claw Duet though found a second bug that we didn't find, which we really really love. Grock did the worst job, which is it loosened validation. So, it was just like we're going to solve the

15:55bug by not validating this bad issue. And then Muse didn't do it. So, I'm actually going to give Claude and Dot the wins here. I'm going to give Claude the extra thumbs up because not only did Claude find another bug and fix it, it also identified that Dot had already fixed it and said, "I don't need to ship any more code." So, I would say for coding, Codeex and Claude or Dot and Duet are truly kind of the best. I actually don't code that much with Grock, so I'm not surprised that this wasn't as good. I really only do my coding in Claude and Codeex. Um, so I'm

16:33not surprised these worked, but I was surprised at how bad the coding from Grock was. So kind of my instinct was right on these. Opening eye anthropic much better at coding than Grockbot, although Grockbot's good at a lot of stuff. This episode is brought to you by Firecrawl, which gives your AI agents data from [music] the web and beyond. Your agents can search and scrape the web while accessing Alexandra's rapidly expanding library of over 100 million index sources [music] and more than 200 data providers, all through one connection. Connect Firecrawl [music] to ChatgBT or Claude

17:10to find people in their work emails. Pick your fantasy football lineup or analyze trends for your next marketing campaign. Firecrawl is building the library for super intelligence, bringing more of the world's knowledge into the tools you already use. Go to firecrawl.dev/howi to get started. Okay, next one. Let's look at episode thumbnails. So, we did episode clips. Now, we'll do episode

17:38thumbnails. And I will say um we did the pre-work here. So our thumbnail templates are actually like quite lovely. Um so it's actually pretty easy to use um the Figma MCP and create new thumbnails. So I'm just going to do a hot judgment here. Muse did the worst job. Muse pulled our existing thumbnail and then did this really ugly one where he's like Blair is like peeking through creepy curtains. We hate this. I'm sorry Blair. I would never do this to you. Um, and so Muse is going to fail here. No good. Um, Grock though, Dot and Claude did perfectly fine jobs. Although, I will say Dot and

18:23Claude just put new content in existing templates that we had. So, didn't really get super creative. I would say Grock actually wins this one in that it gave me really good new ideas for these thumbnails and headlines, ones that we hadn't done that I also think look really nice. Actually, maybe we should test these while they're live. They have like that YouTube vibe to them. And so this is like a fun tip for you all is I have consistently tested Grock dot and claude duet on Figma. And Grock is definitely the best at Figma. Grock is like 100% the best at using Figma. I don't know if this is John at SpaceXs

19:08like Figma bro magic touch, but if you're using Figma, use Grockbot, man. It is so good. So that is my preference. I'm not surprised it's one. Gro takes the cake for Figma and maybe I will have it create the thumbnails for this episode. Okay, something that might not be obvious from the highle benchmark that I want to call out about how all these agents did things is they all have different interfaces for giving you to-dos. And so, while they all found the to-dos fine, I suppose, and they all gave me reasonable things to focus on, I am going to say that Grock did the best job because it gave

19:51me a Grock document. And these just came out, I think last week, and they're so nice. It's just this like beautiful list of things that I need to look at with little check marks, super organized, really nice to work with. And so, you know, all of them did a fine job finding the tasks. I would just say Grock gave

20:13those tasks to me in the best format. Muse only had access to my Gmail, but found all the things I need to do as a parent ahead of Halloween week, which is a busy week for parents. And then Claude wanted to put my to-dos in its little like task followup list so I could track them. Dot did the worst job here for sure. It just gave me a message with like five things I should focus on. So, Dot gets the thumb down for me on like the personal agent, personal agent. I would rank these as Grock, best interface, best job. This is what I use Grockbot for. My chief of staff is in

20:53Grockbot. I'm not surprised that it does a really good job there. Muse did a perfectly lovely job with the information it had. Claude was fine, but again, I just don't like that I have to be in the Claude app for this and dot really, really failed here. Okay, family newspaper. Um, so this was a really interesting one. This is a use case if you've used my Grockbot Tradbot that I really like where we print out a newspaper in the morning for the kids to look at about what's going on for the week, what's um what our schedule's like, what events, what news would be interesting. Claude did such a trash job

21:32that I feel like I should actually call it out. It made like a markdown file. It made me so so so sad. and Claude only had access to my work calendar and so it was just like I can't do anything. I made you an outline and I had this experience a couple times with Duet where like it couldn't do the job and then just gave me like a markdown file that was like this is how you can do the job. This is not what I want at all. So Claude definitely failed the family newspaper test. Um, but Dot, Grock, and Muse all did different jobs. And I was

22:06shocked, sadly shocked, how poorly Dot did. Like, look at this design. It is Ash Trash. And again, these are not my children's names. I just like had it swap out um different kids names. But this is so ugly. Like, what model thinks that this is a good idea? This is terrible. Grock did a really nice job. I actually run mine consistently through Grock. So, you can see here it's got big week at school. It's got a don't forget list. There's Bay Area sports. There's Halloween stuff. There's nice uh weather across the top. But Muse, per my earlier review, just absolutely crushed the family newspaper. It generated this nice

22:52little image. And I do have three boys and they're adorable like this. And so it has this beautiful image at the top, a headline. It did take two pages, but I'm okay with it if it's really cute. And it has our schedule on one page and then a cute dayby-day weather ideas, inspiration on the second page. I just think it's really cute. I think if I tuned it with a skill, it would do an excellent job. So if you're looking for

23:19family newspaper, yes, I love Tadbot. Please download it for your Grockbot. but maybe tell your muse to do it because it does a really nice job with family oriented artifacts. Okay. Um, one kind of like side task I had these agents do, which I occasionally do on the go, is take a screenshot or take a picture of my kids advanced homework, which I have forgotten how to do, and ask it, "How do I explain this to my kids?" So, I

23:49haven't done physics in a long time. like how do I explain a velocity over time graph to my kid? Now, I do know how to do this, but we just used it as a good example. I just opened up the workbook. Okay, so I picked this like exam explain this little exercise um and asked them all to complete it. They all got it right. The answer is C. They all explained it fine. Who won though? Muse won. Why did Muse win? It took approximately a half a second to get this right. And so this was one where like the information was correct across the board. Muse was so lightning fast

24:24and we didn't record it here because it was so fast. Um it was so fast and gave me the answer. And so I've actually been moving a lot of my chat GPT like googly question and answer style chats to Muse because it does such a good job and it's so fast. So, like sort of my go-to like explain how this works, what is this, look this up. I've been moving those a lot to Muse again because of this experience where it's really really fast. Okay, another personal use case I did here um shopping for some autumn shoes. Um I don't know what's going to make me cool. I'm an old lady, but I

25:06want those like Red Adidas Tokyo. Um, I hear that a slim shoe is really in right now, but I'm cheap, so I want to find a good deal. Um, so I asked Grock, do Muse, and Claude to do this. Claude totally got blocked by almost every shopping site. I don't know why. It was like consistently blocked over time. It also looked for white shoes with red stripes

25:36instead of red shoes with white stripes. Like I don't know why it did it. And it found the most expensive ones. And so like Claude really failed this personal shopping task. Um Grock found great ones. So Grock did a really really good job as did Muse. Although Muse needed a little bit of steering. So Grock was super fast and did a good job. I have Grock do a lot of this like price comparison shopping for me. And this has been my experience where it's like really good at using

26:14navigation shopping and price compare. Dot did not do a good job here either. So while Claude did like a bad job, Dot like barely tried. Dot did not do comparison. It didn't look at different colors. It didn't like say like I can't find red but I can find maroon. So I would rank this as Grock best muse almost as good. Claude not good but at least it tried and dot did not try at all. So if you're using shopping I would

26:43say Grock and Muse are your buddies. Here's the last I'm already laughing because I can tell one of these are too. So, the last one, a launch video for a chat feature called um product intelligence that I'm working on and launching. And you can just see here they just really went lots of different directions. Now, I have a skill for this and so it should be able to follow the skill and do what it's supposed to do, but we're just going to look at the differences between these. We're going

27:18to start with dot, which is not good. It's like a PowerPoint. Um, as it's No, no, no, no, no. Good. [music] I mean, this is very soothing, but this is terrible. Okay, so no fail. I hate you. Dot. Bad video. No good. Kind of like the newspaper. It's like, what are what are we even doing here? Grock

27:39crushed though. Look at this. Um, now it it it actually used my skill. So, where Oh, there's like a little error here. So, the the layout isn't perfect, but it at least used my skill and looks like our video is looking, but the layout isn't very good at all. Um, and there's a lot of overflow. So, better, but not great. Muse ate it. Um, Muse doesn't have access to my repo, so

28:07I did not set up our sweet. Every product decision has a paper trail. It is just scattered. Then, clerically, link shows what how confident together. Evance first inference saber. Hold on. I'm p I'm pausing because although it had an access to nothing, it made up a bunch of stuff. Um and gave a nice

28:29little uh British accent overview. Uncertainty out in the open. Oo. Um so I would say it's bad. Um but bad in an ambitious way. So I'm going to give Muse a couple extra points for effort. A couple of points for effort. And then Claude, I don't know. This is why I use Claw to do this. Claude did a very a very good job. And the your customers are telling you exactly what to build. It's just scattered across support chats, call notes, bug reports, issues, and pull requests. Meet

29:01product intelligence from chat PRD. Connect the tools where customers talk and your team ships. So what I will say is like Claude nailed the value prop. It used our branding. There were no layout issues. It actually went and asked and used the 11 Labs MCP to come up with a voice over. I would have loved for it to be a female voice or even my voice that I have recorded in 11 Labs, but Claude absolutely crushed [snorts] this task. Duet crushed this task. And

29:33so what I would say is Claude for video. Claude for video, Jen. It's just it's just the best. Maybe not funny Tik Tok style vertical video, but like these product walkthroughs, those sorts of things. I actually didn't think Claude Duet would do a good job and it did a really good job. Um, Muse was terrible, but like terrible because of me. Dot was

29:54terrible because of Dot and Grock tried. Like Grock followed instructions, so I can't give it a hard time. So that is the final kind of like my analysis. Let me pause. I'm going to throw this transcript into Claude and we're going to get the final ranking and scoring. All right, party people. Here we go. Here are the results of the very first how I AI personal agent benchmark and Grock one. Grockbot. Grockbot's the best and we love her. She's the best. So A+ SpaceX SI team, you cooked, the potato cooked. Grockbot is freaking awesome. So Grockbot got 93% uh done. High quality fixes. I don't actually know how these scores work, but

30:50Claude told me it's true. It won three tasks, including doing my thumbnail, doing a to-do list for my inbox, and shopping for shoes for me. So, that just shows the breadth of the Grothbot. But, as predicted, and this is why I tell people I use these two agents, Muse coming up with all the personal use cases. We gave Muse a break on the tasks that it couldn't do because I didn't give it GitHub and I don't give it access to work stuff, so it can't do those tasks. But on the tasks that it had access for, it crushed, especially creative ones. The short form content, it did the best. Family newspaper did

31:28the best. It's super fast at explaining homework. It is my personal agent. I am not surprised to see it up here. Dot coming right up behind. I think Dot got kind of like a little sandbagged. So, I would actually say that Dot scored closer to Claw Duet than it did to Muse because Dot really like got scored for writing a Slack like me. Like that's not amazing. And it did a good job of code and it did a good job of orchestrating all the other agents. So, Codeex does orchestrate all the other agents, but Dot's not Codeex. Um, but it totally failed on anything creative. It wasn't

32:08great to work with. So, I would say like Dot is a little bit more towards the Clawude end of this ranking than the Muse Gro end of the ranking. And then poor Claude Duet. Um, pulling up the rear 79% super slow. Um, it did fix the bug the most completely and it did my launch video the best, but otherwise either did not complete or lost against

32:33all these other models, unfortunately. So, Duets's got some work to do. Okay, so what are my takeaways? Pick your agent for your job. But if you're picking work jobs, probably give it to Grockbot. And if you're picking life jobs, probably get it to Muse and OpenAI, Anthropic, get your act together. You're losing to to these other agents. Access really matters. So make sure that you have consistent tool access across your agents if you're

32:58trying to benchmark them. I like speed. So fast, uh, I used to say all the time, fast speeds, right? But fast is a very good part of an agent experience. um using artifacts, using different ways to communicate between human and agent. Those like quality of life affordances that I call them really do matter. Gro's documents are very nice. Um and so the way the the agent is actually designed and presents you information as a human is really important. Number five, safety

33:28styles differ. Claude's still a nerd. It's still asking for permission. And so like when you have a personal agent, striking that right balance between permission giving and um proactivity is really important. I really like Muse's sidebar with all the permission asked so I can don't forget them. Um but Claude was just way too conservative. And then at the end of the day, there are still two agents racing for my coding workflows. Dot and duet. Um which means

33:56OpenAI and Anthropic Codeex and Claude. I think this race will continue because this is where a lot of the tokens are being spent, bought, and used. Um, but I would still go to those tools, but I actually wouldn't go to those agents. So, what's interesting about this is while those two agents did the best job on coding, I would not use those agents to code. I would just use the underlying tools and models to code. So, that is it. That is the how I AI agent benchmark. I am so happy um to have done this. We now have a framework when new agents come out. I can definitely run

34:30them. And now I'm gonna go back to hanging out with my Grockbot, hanging out with my muse, and ignoring Dot and Duet. Thanks for joining How I AI. Thanks so much for watching. If you enjoyed this show, please like and subscribe here on YouTube or even better, leave us a comment with your thoughts. You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app. Please consider leaving us a rating and review which will help others find the show. You can see all our episodes and learn more

35:03about the show at howiaipod.com. See you [music] next time.