19:04Austin Marchese · Tutorial
Boris Cherny's 4 Step Playbook to 10x Your AI Productivity
A YouTuber translates Claude Code creator Boris Cherny's engineer-written adoption ladder, chat window to AI-native, into plain English.
August 17thThe argument in one line.
Grok Bot and Claude aren't competing models, they're two different categories of tool, an AI team member you hand work to versus an AI workbench you build inside, and picking between them case by case matters more than picking a favorite.
Read if. Skip if.
READ IF YOU ARE…
- You already pay for Claude, Grok Bot, or both and want a task-by-task answer instead of a general opinion.
- You're a founder or operator deciding which AI subscription is actually worth the money for daily work.
- You want a repeatable framework (team member vs. workbench) for deciding which AI tool to reach for on any new task.
- You're curious about newer AI-agent interfaces (group chats of bots, routines, artifacts) and how they fit into real workflows.
SKIP IF…
- You're looking for a technical model benchmark or coding-capability comparison, this is a workflow comparison, not a model eval.
- You don't use either Claude or Grok Bot and aren't in the market for an AI subscription.
The full version, fast.
Grok Bot and Claude fall into two different categories: Grok Bot is an AI team member you hand work off to, Claude is an AI workbench you build inside of. Testing both across twelve professional use cases split into operations, growth, and innovation, Claude wins the tasks worth getting right the first time (meeting notes, reports, sales copy, proposals, building tools), while Grok Bot wins the fast, low-stakes, low-friction tasks (inbox triage, online errands, competitor research). Automating repetitive work is a tie. The final score lands 6-4 in Claude's favor, but the video's real argument is that neither tool is the limiting factor anymore, most people just aren't creative enough yet with what they hand these tools to do.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 00:18
01 · Cold open: which one should you use?
Sets up the premise: Grok Bot and Claude are fundamentally different categories of tool, not competing models.
00:18 – 02:21
02 · AI team member vs. AI workbench
Defines the core framework: Grok Bot as an AI team member you hand work to, Claude as an AI workbench you build inside of, with a feature-by-feature comparison chart.
02:21 – 02:49
03 · Part 2: which tool wins each use case
Introduces the 12-use-case format, split into operations, growth, and innovation buckets.
02:49 – 04:19
04 · Use Case 1: inbox and messages
Grok Bot wins as an executive assistant for triaging Slack and email and estimating deal flow, because the task is low-stakes and worth abstracting away.
04:19 – 05:15
05 · Use Case 2: meeting notes and action items
Claude wins because meeting context needs to live on the creator's own machine so it compounds over time, not disappear into Grok Bot's closed system.
05:15 – 06:57
06 · Sponsor: Granola
Sponsor break for Granola, an AI meeting notepad that transcribes calls locally and pushes recaps into Slack and Claude Code via MCP.
06:57 – 08:42
07 · Use Case 3: completing online tasks
Grok Bot edges the win for errands like renegotiating bills, saving a friend $500 on an insurance call, thanks to lower friction and bot-to-bot group chats.
08:42 – 10:00
08 · Use Case 4: reports and solutions
Claude wins clearly: reports worth doing are worth collaborating on with an AI that already has business context, not just aggregating raw data.
10:00 – 11:21
09 · Use Case 5: finding new customers
A slight nod to Grok Bot for cheap, fast audience experiments, with Claude brought in afterward to harden whatever direction actually works.
11:21 – 12:39
10 · Use Case 6: creating marketing content
Claude wins clearly on content quality and includes the creator's own YouTube-growth lessons: break each step apart, aim for middle-to-middle not end-to-end.
12:39 – 14:14
11 · Use Case 7: writing sales copy
Claude wins because sales copy has to be actively pushed away from the AI's statistical-middle default, which needs a workbench, not a handoff.
14:14 – 15:49
12 · Use Case 8: client proposals
Claude Design wins for proposals because of inline feedback and one-click rebranding, versus Grok Bot's lack of an iterative workspace. Includes the recurring Claude Max giveaway break.
15:49 – 16:48
13 · Use Case 9: researching ideas and competitors
Grok Bot wins on web-browsing feel and lighter-weight competitor teardown, feeding a proposal doc the creator then builds inside Claude.
16:48 – 18:41
14 · Use Case 10: building an app or internal tool
Claude wins clearly via Artifacts, single-use vs. long-running shareable tools built from a prompt, including a real estate portfolio dashboard and a restaurant's drink-recipe tool.
18:41 – 19:34
15 · Use Case 11: automating repetitive work
Called a tie: Grok Bot's built-in routines lower the bar to try automating something, but anything meant to last long-term still gets rebuilt as deterministic code or a Claude skill.
19:34 – 21:03
16 · Use Case 12: things you've never thought of
Not a head-to-head. Grok Bot's group-chat-of-bots interface changes how the creator thinks about problems, surfacing objections he hadn't considered.
21:03 – 21:28
17 · Recap: which tool per bucket
Quick recap: Grok Bot for fast/messy work in each bucket, Claude for anything meant to be built right and last.
21:28 – 22:51
18 · Part 3: the elephant in the room
The real closing argument: the limiting factor was never the tool, it's whether the person using it is being creative enough with what they ask it to do.
Lines worth screenshotting.
- Grok Bot and Claude aren't rival models, they're two different categories: an AI team member you hand work to, versus an AI workbench you build inside.
- The deciding question for any task isn't which tool is smarter, it's whether you want to do the work yourself or hand it off entirely.
- Across 12 head-to-head business use cases, Claude won 6, Grok Bot won 4, one was a tie, and one wasn't a real contest.
- Claude wins every task where the output needs to be right the first time: meeting notes, reports, sales copy, client proposals, and building internal tools.
- Grok Bot wins every task that's fast, low-stakes, and disposable: inbox triage, online errands like renegotiating a bill, and messy competitor research.
- A friend used Grok Bot to renegotiate his insurance and saved $500 in 22 minutes just by having the AI go back and forth with the customer service rep.
- AI models bias toward the statistical middle of a response, which is exactly why AI-written sales copy that isn't pushed away from that average fails to stand out.
- Grok Bot's group chat feature lets separate bots (a grocery bot, a trainer bot) talk directly to each other, so updating one automatically updates the other.
- Claude's most underused feature, according to the creator, is Artifacts: a shareable, auto-hosted mini website built from a single prompt with zero technical skill required.
- Artifacts split into two types: single-use (a client proposal, sent once and done) and long-running (a live team dashboard used every day, like a 200-unit real estate portfolio tracker).
- Automating repetitive work is the one true tie: Grok Bot's built-in routines lower the friction to try automating something, but anything meant to run long-term still gets rebuilt in Claude as deterministic code.
- The lesson from growing a YouTube channel with AI: break every content task into distinct steps (research, outline, script, revise) instead of asking for the finished product in one shot.
- Aim for 'middle-to-middle' AI use, not 'end-to-end': the goal is compressing the time each step of a process takes, not removing the human from the process entirely.
- The video's closing argument: the tool stopped being the limiting factor a while ago, the limiting factor is whether the person using it is creative enough with what they ask it to do.
Claude wins the work that has to be right the first time.
WHAT TO LEARN
Across twelve business use cases, Claude beat Grok Bot 6-4 with one tie, and the pattern is simple: hand off the fast, disposable stuff, but build anything worth getting right.
02AI team member vs. AI workbench
- Decide per-task whether you want to hand work off with low visibility, or stay in the loop and build the final product yourself, that single question predicts which tool wins.
04Use Case 1: inbox and messages
- Fast, low-stakes, disposable tasks (inbox triage, online errands) favor an AI team member you don't have to babysit.
- Grok Bot handled inbox and Slack triage well enough to act as a standing executive assistant, without needing to be watched.
05Use Case 2: meeting notes and action items
- Meeting context needs to live on your own machine so it compounds over time, a tool that stores everything in its own closed system can't build that history with you.
07Use Case 3: completing online tasks
- A real-world test: negotiating an insurance bill through an AI agent saved $500 in 22 minutes, proof that low-stakes online tasks are worth automating.
08Use Case 4: reports and solutions
- Reports worth doing are worth collaborating on, not just generating from aggregated data, because the value is in shaping the analysis, not producing a first draft.
09Use Case 5: finding new customers
- Experiment cheaply first, then harden what works, run fast low-friction tests in one tool, then rebuild the direction that actually works in a tool built for iteration.
10Use Case 6: creating marketing content
- Break any AI-assisted process into distinct steps (research, outline, draft, revise) instead of asking for the finished product in one prompt.
- Aim for AI compressing the time each step takes, not removing the step entirely, that's the difference between a process you can trust and one you can't.
11Use Case 7: writing sales copy
- AI defaults to the statistical middle of a response, so copy meant to convert has to be deliberately pushed toward specificity, not generality.
12Use Case 8: client proposals
- An iterative workspace with inline feedback beats a regenerate-and-pray cycle for anything that gets revised repeatedly, like client proposals.
14Use Case 10: building an app or internal tool
- A single prompt can produce a shareable, auto-hosted mini tool with zero technical skill, useful both as a one-off deliverable and as a long-running team resource.
15Use Case 11: automating repetitive work
- Automations meant to run once are fine as quick low-friction routines, automations meant to last need to be rebuilt as something deterministic you actually own.
17Part 3: the elephant in the room
- The tool isn't the bottleneck anymore, most people aren't being creative enough yet with what they ask these tools to do, and that's the harder skill to build.
Terms worth knowing.
- AI team member
- A category of AI tool you hand a task to and it goes and does it, with limited visibility into how, similar to delegating to a person. Grok Bot is framed this way in this video.
- AI workbench
- A category of AI tool designed to be worked inside of, step by step, with full visibility into the process. Claude is framed this way in this video.
- Artifact
- A shareable, auto-hosted mini website or interactive tool that Claude generates from a single prompt, usable by non-technical teammates without any setup.
- Group chat effect
- The creative shift that happens when multiple named AI bots are dropped into one chat and made to interact like teammates, which can surface ideas a single chat interface wouldn't.
- Statistical middle
- The average, most-probable response an AI model tends to produce by default, which content and sales copy have to be deliberately pushed away from to stand out.
Things they pointed at.
Lines you could clip.
00:00
“There's a battle going on right now between Grokbot and Claude, and they're both competing to get you to use their tool.”
07:11
“A friend of mine had Grokbot negotiate his insurance. It got him three months free and then lowered his monthly rate, which saved him $500 in 22 minutes.”
12:48
“Sales copy that lands in the statistical middle does not stand out by definition.”
21:39
“You just sat through 12 use cases and you're thinking about which tool to use. But the tool isn't the limiting factor anymore. It's you.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphor
There's a battle going on right now between Grokbot and Claude, and they're both competing to get you to use their tool. So which tool should you actually use? Well, today I'm going to break down why these two tools are fundamentally different, tell you which tool to use for the 12 most important professional use cases, and then I'll address an elephant in the room that I guarantee you're ignoring.
So part one, you're not picking a model, you're picking who does the work. Grokbot and Claude actually fall into two completely different categories of tools, an and an AI workbench. So what is the difference?
Well, an AI team member is something you hand work to. You ask it to go do something and it goes and does it. Whereas an , this is something that you work inside of.
You sit down and you build the final product in real time. So Grokbot is an AI team member. And from a product standpoint, this category of tools makes everything feel as close to texting a real person as possible.
So with Grokbot specifically, you can name your bots and even drop them. in group chats together. It literally feels like you're texting your team.
And this is great. But just like when you're collaborating with team members, you don't have visibility into what and how they're doing things, which limits the flexibility. Claude, on the other hand, is an AI workbench.
This category is designed to feel like a tool in your hands, not a person that you're speaking with. So you're in control on every step. And so with Claude specifically, it runs on your local machine, works directly with your files, and lets you see the entire process step by step.
And the thing to consider with these workbenches is to get the most out of them, it asks for more upfront. Because you're not handing something off like to a team member, you're actively building something.
And if the distinction isn't clear yet, here's a chart with specific features and how these two categories are different. Starting with what computer are they working on? So CloudCore, CloudCode, right?
This can run on your local machine, whereas Grokbot runs on a shared virtual computer across every bot that you spin up. Do you have visibility into its actions? With Cloud, you see more of a step -by -step process.
And whereas with Grokbot, you get minimum visibility where most of it is abstracted away from you. Then who owns the file? and conversation history.
For this, let's talk about Cloud Code. So Cloud Code works directly on your machine with your own files, whereas Grokbot lives entirely in their ecosystem. That simplifies the experience, but it also locks you into their account.
So the next time that you're deciding which of these to use, ask yourself, do I want to work on this myself or hand it off entirely? And that's a framework I use to decide which tool fits which task. And it's a mental framework that's stuck when I've taught it to other people.
And throughout these use cases, I want you to start more thinking about this AI team member versus AI workbench concept. because that's important going forward no matter what tool you use so part two which tool wins each use case we're gonna go through 12 important professional use cases today and they fall into three buckets the first operations which is your day -to -day then growth which is how you expand your role and business and then the third is innovation which is how you experiment with new things that might eventually become something bigger and the use cases that we cover get more interesting as we go but if you can't solve the operational tasks you'll never actually have time to grow or innovate so starting with operations use case number one is reviewing your inbox and messages the question that i asked myself for this use case is do i actually want to work through this myself or is this something that i would hand off to a team member and for most inboxes and messages i don't want to do this myself so handing it off to an ai executive assistant just makes sense so in this case here i'd create a new grokbot name it executive assistant and then i tell it analyze my inboxes and for me that's my slack and my email and then i'll say flag anything i need to respond to by the
end of the day it then walks through connecting your accounts and sets up a routine to run on its own and for tests like this i bias towards whatever is the easiest least friction to set up because i like tweaking it over time and i like constantly iterating on this honestly i've yet to find something that i truly truly love so i just like iterating and going by feel and what grokbot does is it handles this pretty seamlessly for smaller tasks like this and that's when it starts feeling like magic at times claude can feel a bit overwhelming for something like this and because grokbot's connections carry across chats.
I can then actually create a second bot. I call it Video Sales Manager, and it uses the same Slack connection and email history. I'll then just ask what outstanding deals are currently in the air, and based on how past history, estimate how much of that will close.
That then helps me budget going forward, and then I can make hiring decisions for my team. And this is important, but it's the kind of tasks an executive assistant would handle. It's a nice to have, not necessarily business critical, but it saves me a ton of time in my day.
So for this use case, Grokbot is a winner because I actually prefer the abstraction for more straightforward use cases. Use case number two is creating action items and pulling insights from meeting notes.
This is a similar question to use case number one. Am I working on this or handing it off? So I personally love recording calls and it has nothing to do with just creating action items and follow up messages after the call.
But instead, it's because I want the context of that call sitting in my system so I can work with AI to improve how I run calls, build products and solve problems for my customers, as well as improve my team's experience. And this process of iterating on the context is something i want to do myself and so part of the problem for this specific use case for grokbot is that it doesn't store or save anything on my machine by design out of the box everything lives in their virtual system now claude on the other hand lets me pull meeting notes in through my connections store that context directly on my machine so it can learn over time and then i can work through it to pull out the action items that provide value to my business so for this use case claude wins because this is a task i want to stay in the loop on not hand off but in order to actually do this you do need to record the calls themselves.
Which brings us to today's video sponsor, Granola. And if you've been around this channel, you know that I love this tool, which is why I'm so pumped to be working with them. So Granola is an AI notepad that transcribes your meeting straight off of your computer's audio.
So what that means is that no bot has to join the call. It's just you and the other person, and it still records the meeting. This feature alone is what made me first start using Granola.
But what keeps me using it every day is what happens after the call. Because the reality is that the meeting is never... all that much work.
It's the follow -up. It's making sure you don't forget anything and things fall through the cracks. And Granola helps me solve these problems through three different ways.
The first that I stopped writing action items for my team. So after a call, I just share the Granola link and every person asks their own questions in the meeting. They'll ask, what are the action items?
What did Austin say about the deadline? It has honestly changed how I run meetings and how I structure them. The second is that the integrations do the follow -up for you.
So Granola connects with Slag, Zapier, and Claude Code directly through their MCP. So for example, you can finish a meeting open your laptop and the recap is already sitting in your team slack without you having to do anything and the third is that every meeting becomes something you can search and act on so how this works is literally during calls if a person says something that i'm not sure what it means i'll ask granola a question about it while i'm still on the call so for example i'll be like what does msp stand for and it'll give me a brief overview instantly so i can feel educated while i'm having the conversation or after the call if i totally forget what was the discussed I click into the call on granola and I ask questions directly there to refresh my brain about what we discussed so I'm excited to officially partner with granola and offer my community 100 off their first month click the link in the description and try it on your next call you are going to be happy that you used it okay getting to use case number three completing online tasks for you so yesterday a friend of mine had grokbot negotiate his insurance it got him three months free and then lowered his monthly rate which saved him 500 in 22 minutes I then tried the same thing
my internet bill it went back and forth with the customer service rep and i didn't actually end up saving anything but at least now i know i'm not getting ripped off on prompt is a screen to help you renegotiate any prices which is pretty powerful so whether you're using cloud or grokbot you should just go and do this and both the tasks that i mentioned fall squarely into the completing online tasks for you going back to the executive assistant question would i have my assistant sit down and argue with a cable company for me absolutely would i do it myself on a busy day no in that case it makes it a perfect task for an AI teammate.
And now I have used Grokbot for other online tasks and I was impressed. It found me restaurants in Florence and then it booked a wine tour for me and my now fiance after we got engaged. Don't tell her that I had Grokbot do that, but I did.
And so you can also do this with Claude. So I wouldn't say this alone is necessary to switch to Grokbot, but I found that Grokbot's just a little faster and the interface, the reduced friction, just I find myself doing more things like this. But the reality is that you can do it on Claude.
The one thing that Grokbot is unique here is the group chat component of it so let's say you have a grocery shopping bot and then you have a personal assistant trainer bot as the user you can have the shopping bot talk directly to the trainer bot before ordering anything and that way you'll never actually have to manually update the grocery bot you could just talk to the trainer and it'll automatically fill in the grocery shopper this type of cross collaboration is where grokbot has an edge for this task primarily because it's more flexible and the optionality that it comes from and i'll touch on the ability to invent new use cases more later in the video because i I think this is so powerful about the interface.
Use case number four is creating reports and identifying solutions. So Grokbot is a winner of use case three by a slight edge, not a massive game changer, but use case number four, creating reports and identifying solutions. This has a clear winner.
One thing I foundationally believe is that the best users of AI don't just use it to move faster. They use it to make the final product better. And so sure, you could tell Grokbot, create a monthly report based on customer feedback, and that's a great start, but there's really no great collaboration.
happening here crockpot is genuinely strong at aggregating and capturing data but to actually take that raw data analyze it and then shape it into something that you're confident in claude is the obvious choice here back to our core question in this video are you working on it or are you handing it off if a report is worth doing it's worth doing right and if you're watching this you've probably already set up your cloud system to have an extensive llm knowledge base so it already has a key context about your day -to -day your business and how you like reports structured and on top of that you're going to actually want to work through the report with the AI as a collaborator, which is exactly what Claude paired with Obsidian gives you.
So a clear preference here for Claude, but Grokbot is great for those quick analysis, but anything that deep dive or requires collaboration, you're gonna need Claude, and that's likely any report that's worth doing. And so that wraps up operations. And as an operator myself, I genuinely do love that stuff, but it's not where the fun starts.
That's in the growth and innovation part of your professional life. So bucket two is growth, and use case number five is finding new customers. This one comes down to two strengths.
One, Grokbot's a - to let you experiment quickly with low friction and two, Claude's ability to help you iterate, collaborate, and think deeper. Here's how I think about it.
You want to experiment and then harden the flow. And so what I do is I'll run a bunch of low effort experiments to see if there's any real signal through Grokbot. Then when there is, I come into Claude and actually build out a real workflow around it or investigate the situation more.
So for example, at one point, I had no idea who was actually reading my newsletter. So I spun up a product growth engineer bot and I had to talk to an audience. expert bot to figure out what kind of audience I had and how to speak to them directly through our products.
That was the experiment phase, cheap, fast, and pretty low stakes. Once we actually had a direction worth committing to, I moved the whole thing into Claude to build out and harden the real process and final product. So getting customers can be a whole other video, a whole other deep dive, but high level, here's how you can put it to work in two steps.
The first is if you don't already have a target audience file, use either tool to interview you and just build it out. Very simple. You can just say, interview me.
to identify my exact target audience. And then once you get that, use a follow -up prompt to figure out where you can actually find those customers and how to reach them. And so for getting customers, I give a slight nod to Grokbot just because of how fast you can iterate.
There's no clear winner here, so you can do it all end -to -end through Claude if you have to. Use case number six is creating marketing content. This is where quality matters more than quantity.
It is trivial for any AI tool to pump out infinite content. The real question is, which tool actually gets you something that's good? And there's a clear nod to Claude here for several reasons the first is you can build far more elaborate context around your voice your writing style and password then you get better iteration experience inside tools you're already collaborating with frankly the underlying model does matter in this case one problem with grokbot is grok The model is just not that good.
And in this video, I'm focused on the bigger product differences that won't change much over time. But today, this is still a real factor to consider the model behind these actions. So if you're creating content and marketing content, Claude is a clear winner here.
And the best way to do this with Claude, there are a couple of lessons that I've learned while growing my YouTube. The first is clearly break down each step in the process. It's not write me five short form scripts.
It's research, outline, scripting, revisions. Treat each step in the process as it's own distinct problem the second is aim for middle to middle not end to end you want ai compressing the time each step takes not removing the step entirely now for what it's worth content systems are hard so if you are a founder or operator who wants to work directly with me to help you with this there is a link below if you are interested in working together but for this use case the clear winner is clawed use case number seven is writing sales copy to understand who wins here you have to understand how ai works ai will bias towards the of what the output should be and And I've talked about why in length in another video, which is linked below, but sales copy that lands in the statistical middle does not stand out by definition.
So you have to actively push AI away from that instinct and away from that average response. And giving the stakes here, which is closing new business, this is another clear AI workbench use case. And so once you're using these workbenches like Claude, my favorite move here is bringing in actual experts, meaning their books, their podcasts, their videos, all of that, and combining it to create training data steer AI towards sharper, more specific answers instead of generic ones.
My go -to here is using Claude code with Obsidian and iterating back and forth until I get a product that I like. And if you don't want to go through pulling all this information, training your system with experts, my free buildpartner .ai plugin can help you do that with our slash expert advice skill, which will call these experts and give you direct feedback as if you're talking to them.
And so this is with your workbench, Claude. If this is with Grokbot, working with that kind of dense contextual material just isn't as smooth now once you do start tackling this use case one thing that i like to use is an abstraction analysis prompt in sales abstraction kills conversions so the goal is to speak clearly and directly enough to move people to buy and this prompt on screen will analyze your sales copy like a curious 12 year old asking questions at every vague point again abstraction is the enemy of conversion and so the more questions you can answer with the copy itself the better it's going to perform a clear nod here is claude specifically using claude code for non -technical tasks use case number eight is create client proposals.
Claude design is my go -to for this one. So a client and I were recently talking about the best ways to build proposals and he was going back and forth with Claude trying to design them, but the iteration cycle just wasn't working. Every small change meant generating the whole thing again and hoping it got it right.
And the solution here, which is what I use for all my proposals is using Claude design. And there are two specific reasons why this is so helpful. The first is you can give inline feedback.
So you click directly on what's wrong and either fix it yourself or tell Claude to fix it. And it knows exactly what you're talking about. because you already pointed it to it.
The second is it makes it super easy to make general changes. So you can take an old proposal and build an entirely new one using a client's branding. Same structure, same content, but it reformats it around their colors, their fonts, their logo in minutes.
And so this is a much more effective AI native way to edit proposals than regenerate and pray cycles. You're not waiting on full rebuilding every time you want to make one simple change. And so the reason that Grokbot loses here is it just lacks that iterative workspace.
so the clear winner is Claude. And so now before we get to the last four use cases, you know the drill. This is our anti -slap agreement.
Everything in this video is built by humans for humans. So as part of this agreement, subscribe to this content so it can keep reaching more people. I appreciate all of you and all of your support.
And as a thank you, I give away a Claude Max subscription every single video. This video's winner is Karen Hewler EC, who is building a workforce ecosystem for professionals. To enter this video's Clawed Max giveaway, comment below with the one task you'd hand to a team member or something that you're building.
I'll take real and fake answers. Let's have some fun. The next bucket, we've gone through operations, we've gone through growth.
Now it's innovation. Use case number nine is researching ideas and competitors. This is where Grokbot's web browsing ability genuinely feels like magic.
It's just lighter weight for Claude for this specific job. And I just use it more for whatever reason. So what I do is if I see a product I like, I'll drop the link and I'll say, analyze this.
And I've given Grokbot access to our buildpartner .ai GitHub repo and asked based on their funnel and their offering, what features could we add? Then it'll go through and turn that into a proposal doc that I can build off of. And I do this a bunch and I've created a product growth bot that's dedicated to this kind of investigation.
I never actually found myself doing this inside Claude. It's functionally there. I can very easily do it, but it's not something I have time to iterate on manually, which makes it a perfect task to hand off to a teammate.
The winner here for me is Grokbot. And on screen, if you want to try this yourself, drop in a competitor's link and ask it to break down their landing page, their funnel, and what you should be doing that you're not based on this information. And going to why I use Grokbot for this, it's where interfaces genuinely matter to me.
Use case number 10 is building an app or internal tool. At this point, the answer should be pretty obvious. Claude wins here.
This is your workbench. This is where you're iterating. you're collaborating, and you're actually building the thing.
Now, this doesn't mean that Grogbot has zero value here, and we'll get to that. But first, my favorite and honestly most underused cloud feature is artifacts. I was on a run today with an engineer at one of the biggest fintech companies, and he didn't even know what this was.
And so I was like, bro, you have to use this. So an artifact is essentially a simple website cloud builds and hosts automatically, which is shareable with a single prompt. And it can pull live real -time information, so it actually stays up to date.
over time. Like I actually tell everyone about this. So another buddy of mine who I run a small real estate investment group with built a landing page artifact showing our entire portfolio and its performance.
And we have ownership across about 200 units in seven different locations. So this was quite overdue. We just never got time to do it.
Now, this is a real tool that our team will use. And it took legitimately zero technical skills because Claude abstracts all of the website complexities away from it. So when you're thinking about artifacts, break it up into two types, single use and long running.
Single use is something like a proposal. I'll use claw design for this and I'll turn it into an artifact, send it to the prospect and then it's done. A long running one is different.
You build it once and then it's used consistently. So the real estate portfolio one that I mentioned, that's a long running one. And then another example is a founder I work with.
He did this with his restaurant's drink menu. So now any bartender can pull up a recipe on the spot and he didn't have to use anything technical. It's just a useful, persistent link that his whole team can access.
And so that's how you can use artifacts, which is just another way to build things. within the Claude code ecosystem, but what about in Grokbot? Personally, I've used it to curate and analyze customer feedback, reading everything and handing me a single summarized doc, which I'll then bring into Claude to build with.
I just like how Grok handles pulling and connecting data, but the execution for me always happens in Claude. And so the winner here is Claude. Use case number 11 is automating repetitive work.
Grok is built to move fast and take more risks. Claude is built to be more careful. Inside Grokbot itself, you'll actually see routines that sits right next to the conversation history.
And this is great for building lightweight automations. For anything that I need to run long -term, I either have Claude build the automation deterministically, which means it creates code so that it can repeatedly run, or I turn it into a Claude skill that I can wire into a routine, something that I actually own and I can share with my team as needed.
So generally Grok, again, low friction, Claude is a little more work, but a little more thorough. In this case, the reduced friction of Grok creating automation is something that makes a big impact. I'm just running more automations now.
than I ever used to because the bar for should I even bother automate this has dropped so low. So with all that, I'd say this one's a tie. Start in Grokbot, graduate to Claude, but you can just do everything in either tool.
Use case number 12 is doing things you've genuinely never thought about. So this last one isn't really a head to head. It's more about how Grokbot impacted how I think.
What Grokbot provides is an interface where you treat agents like teammates. And I don't think that's a small design choice. Grokbot has taken off and people are genuinely like you.
it that way and we're already seeing it show up elsewhere meta's new muse feature has a very similar interface and it's to mimic this team -based collaboration and the vibe that you get when you use it is what i call the seeing agents interact like teammates can stimulate ideas a plain chat interface never would so an example is i recently put two bots in a group chat and had them review a business offer and ask them to argue with each other about whether the business idea was actually good one was instructed to find flaws and the other to find the upside.
I wouldn't necessarily have thought to do something like this, but the group chat interface made me think about it. And after reading the back and forth, it surfaced a couple of objections that I hadn't considered. And I ended up throwing that into my product's landing page.
I equate this much like the first time ChatGPT came out in 2023. Using Grokbot has genuinely shifted my mental model for what use cases can even look like. And so in this video, I talked a ton about Grokbot and there's Meta's new product Muse.
This genre of tools you're AI teammates are worth experimenting with in my eyes. And depending on when you watch this, Grokbot may cost money.
I know Muse right now is entirely free. So just get the creative juices flowing, spend 30, 45 minutes on it. You don't have to go crazy.
But before we get to the elephant in the room, here's a recap of the different buckets and how you should think about it. Operations, Grokbot for the quick, low -stakes stuff, while Claude for anything you want to actually collaborate on and get right. For growth, Grokbot for the fast experiments, Claude for building the real things once you know it works.
And then for innovation, Chalkbot for wide, messy discovery. Claude for actually building what comes out of it.
But if you walk away from this video just thinking about the 12 use cases, you're going to miss what I think is the most important, which is part three, the . I guarantee you're ignoring. You just sat through 12 use cases and you're thinking about which tool to use.
But the tool isn't the limiting factor anymore. It's you. Yes, you.
The last use case I talked about was the importance of stimulating your creativity as you use these tools. The process of becoming more productive with these tools is as much creative as it is technical. The creator of Cloud Code, Boris Cherny, has a great quote, give the model a task that feels harder than you think it can do.
And reading between the lines here, he's saying you need to be more creative with how you use these tools and what you use them for. That's the part I think a lot of you watching haven't actually sat with. Grokbot specifically is built to stretch that creative muscle because the friction of trying something weird is basically zero.
Naming a bot. dropping it in a group chat with another one seeing what happens that's a creative act not a technical one and the people watching this i know you guys are using claude like 95 of you and there's no reason you can't flex this creativity with claude you just have to be aware of this and start flexing the muscle so for either tool here's a prompt to get you thinking differently about how and where to use ai based on your past conversation history the problem isn't necessarily about which tool to reach for it's about knowing what to do with either one and if you want a full playbook on that, go check out this video where I walk through exactly how to build 10 times faster with cloud.
I'll see you in the next video. Peace.
The Hook
The bait, then the rug-pull.
Two AI tools, twelve real business tasks, one running scoreboard. Before picking a side, the video makes the case that Grok Bot and Claude aren't even playing the same game.
Named ideas worth stealing.
00:22model
AI Team Member vs. AI Workbench
- AI Team Member: hand it work, it goes and does it (Grok Bot)
- AI Workbench: sit down and build the final product inside it (Claude)
The organizing lens for the entire video: decide per-task whether you want to hand work off with limited visibility, or stay in the loop and build the thing yourself.
Steal forAny framework for deciding which AI tool or agent to reach for on a new task
12:25list
Lessons Learned While Growing on YouTube
- Clearly break down each step in the process, treat each as its own distinct problem
- Aim for middle-to-middle, not end-to-end, compress the time each step takes rather than removing the step
Two rules the creator uses for getting good AI-assisted output on content and marketing tasks.
Steal forAny AI-assisted content or copywriting workflow
How they asked for the click.
VERBAL ASK
05:15product
“Click the link in the description and try Granola on your next call, 100% off your first month.”
Mid-video sponsor read woven into the Use Case 2 discussion (meeting notes), tied directly to the surrounding content instead of a generic interruption.
MENTIONED ON CAMERA
FROM THE DESCRIPTION
AFFILIATECommission earned if you click.
OTHER LINKSAlso linked in the description.
- Paste This Into Claude, Never Get Stupid AI Responses Again ↗
- The Ultimate Guide to Building 10x Faster with Claude ↗
- Build 10x faster with Claude ↗
- 17 things Claude Design can do ↗
- The 5 biggest Claude lies ↗
- Free 5-day AI playbook (what I used to build a $25M+ startup) ↗
- Use BuildPartner to build 10x faster with Claude Code (try free) ↗
- Want to build a Custom AI App that saves you 10+ Hours a week ↗
- Want a Custom AI App that runs your content and saves you 10+ Hours a week ↗
- Obsidian ↗
- Claude Design ↗
- Grok Bot ↗
Visual structure at a glance.
