These amazing sponsors make my research possible

ComputerComputer ↗
One AI teammate, built for your whole team. Prep calls, build presentations, and draft follow-ups in minutes. Try Computer free.
beehiivbeehiiv ↗
Newsletter, website, podcast, and community hosting. Use ADAM30 for 30% off.
ZoomInfoZoomInfo ↗
GTM context built on the world's best b2b data, now available headless (CLI, API, MCP).

Paid placements. Sponsors have no say in coverage. Sponsor an issue →

Grok Bot is too easy. I’m not technical, but I want to see my AI’s machinery.

I spent a couple days really trying to find a use case. I was impressed by the product, but didn’t fall in love as a user. It’s a leap forward if you want a packaged solution. If you’ve built any kind of personal OS in Claude Code, Codex, or an open source harness, it’s a step back in control and ownership.

The AI x GTM space is a series of hype cycles. The hard part is figuring out which ones to jump on and which ones to watch from the sidelines. Grok Bot is the latest mania, and the biggest mover on my Trends tab over the last 30 days.

Is it worth it? For me, not yet.

Today I’ll cover four things: the Grok Bot trending data, what GTM operators are doing with it, what I tested, and the bet I’m making that keeps me from going all in.

Grok Bot. So hot right now.

Grok Bot is one of the hottest AI x GTM topics I’ve seen out of the gate. Hansel levels.

Here’s what I’m seeing in the data from my Trends tab and GTM panel:

Grok Bot is the fastest riser in GTM share of conversation

Grok Bot launched August 11. Two days later it passed OpenClaw and Hermes in share of conversation across my GTM panel.

It sits at #23 of 809 tracked names on share of conversation since August 4. That is the biggest gain of any brand I track. Claude Code still has three and a half times Grok Bot’s share.

The GTM crowd is engaged. People are running real experiments and legitimate operators are betting on Grok Bot quickly.

Krista Letz runs enterprise GTM at SpaceXAI. On August 16 she published how she actually uses Grok Bot at work. 2.9 million views. Her setup is a team of bots. A Chief of Staff owns meeting prep, inbox, and post-call drafts, and spins up the others. A prospecting bot runs overnight, watches the prospect’s webinars and podcasts, and drafts outreach in her voice. A customer expert per strategic account watches Slack, calls, and email. A forecasting bot writes Salesforce opp notes. A slides bot builds customer decks in Figma from the brand system. She had a great framing: It’s a “doing partner,” not a “thought partner.” (LinkedIn · X)

Krista Letz on how she uses Grok Bot at work

My friend Brendan Short put Krista on The Signal’s live show on September 3 with Eric Nowoslawski. Eric is one of the most serious outbound builders that I follow. His open source projects are amazing and he has great takes. 521 people registered. Brendan’s eight takeaways are the best condenses read on Grok Bot for GTM I’ve seen. Definitely follow Brendan and Eric. Three things that stood out for me:

– “The computer is the product.” Each bot has its own machine, so the work keeps going after you shut the laptop. Eric kept a second MacBook plugged in because Hermes broke constantly. He migrated off Hermes by asking Grok Bot to do it.

– Eric’s four-point outbound check runs on a cron. One customer, 100 leads a day. Every day the bot checks lead volume, noon send volume, and deliverability, and on Fridays it retires any domain under 0.7% reply and buys replacements. Grok Bot shipped on a Tuesday. He had this live Wednesday. Reply rate doubled.

– “Turns out, you can just build things.”

Brendan Short's eight takeaways from the Grok Bot live show

There are skeptics as well:

Maja Voje rated 22 GTM tools. Claude Code got S tier: “The best chance at building a GTM Brain for non-technies.” Grok Bot got C: “The lowest-friction way to get a working agent. Fine for simple tasks, thin once the workflow gets real.”

Tom Wentworth says we’ve reached the performative era of AI in GTM, with Grok Bot demos as exhibit A. I respect Tom on fitness and GTM.

Beyond GTM, lots of big-names are drinking the Kool-Aid and calling it a moment.

Lenny Rachitsky: “I got early access to Grok Bot and I’m hooked. I haven’t been this excited about a new AI product in a while. It’s like OpenClaw, but super easy, reliable, and less scary to use.” He’s since partnered with SpaceXAI to give his annual subscribers a free month.

Gavin Baker: “I think @bot is another ‘Claude Code’ moment for AI. I would estimate my personal AI usage is up something like 100x.”

Greg Isenberg: “Grok Bot might be the first tool that lets one non-technical person run an entire business with a team of AI agents.”

Michael Truell, Cursor CEO, now inside SpaceXAI: “It’s grown faster than any product we’ve seen.”

What I tested in Grok Bot

Seeing the mania, I jumped into Grok Bot for a couple days in search of a killer use case.

My first bot

Check my new beehiiv subscribers each morning, enrich them with ZoomInfo, tell me the senior people at companies I want to talk to, and draft the email. It seemed doable, but was kinda annoying because I didn’t have anything connected.

My first Grok Bot prompt

Then I gave the same idea to Codex inside my personal OS. It built me an incredible system in about an hour with very little steering. It watches new subscribers, enriches them under a spend cap, matches them against my GTM Index, picks the five people a day I should talk to, and drops the drafts into my Gmail. Today I sent five emails. The system is humming.

That isn’t a commentary on the products. Codex had an unfair advantage. It already had API access to beehiiv and ZoomInfo, my entire GTM Brain, and the scripts Claude Code wrote to run operations across my stack. But that’s the point. I want a system, not a personal agent.

My repo and a roster

My next move was to give Grok Bot my local context system. It read my CLAUDE.md, my strategy docs, and my wiki, and correctly summarized what the company is and how my nightly runs. Then I stood up a Chief of Staff with four specialists under it. Nightly Ops read last night’s run and came back yellow, the same yellow my own morning summary already gives me. It proved the handoff. It didn’t tell me anything new. A capable guest in the repo is still not Claude Code sitting there with 66 skills loaded and a stack of APIs.

My Grok Bot roster: a Chief of Staff and four specialists

What I learned

My existing machine still wins. The nightly, the skills, the wiki, the morning emails and Telegram pings. A Grok Bot reading the folder is a capable guest, not a replacement OS.

Connectors decide everything. Eric’s cron fires because his tools were wired. My best use case died because mine weren’t. Same product, opposite experience.

The whole package is magical. The product is very smart and the experience is slick. But I didn’t find a job worth moving my daily work. Grok Bot would handle the work for me. I want to learn how my AI works.

I want to be a BUILDER, not a bot user

Grok Bot is playing to the bigger TAM. My mom doesn’t want 66 markdown skill files, a GitHub, or a Karpathy wiki.

But I don’t want to be a “normal” AI consumer. 11 months ago I crossed into a different phase of working with AI. I decided that I wanted to be a system builder, not just a chat prompter.

This is aspirational for me because I’m not an engineer. I never touched a terminal until October. I didn’t have a GitHub account until January. But I’ve found that building with AI is very accessible. And I’ve fallen in love with this way of working:

  1. Coding harness for all work. Claude Code and Codex, running in parallel on the same project. Easy to swap.

  2. Context system (the brain). Local files, a Karpathy-style LLM wiki with 500+ pages that gets better every night, GitHub.

  3. Capabilities. Lots of APIs and CLIs, some MCPs. Beehiiv, Apify, ZoomInfo, Clay, Exa, OpenRouter, Airtable, Netlify. 66 skills and 400+ scripts my agents wrote to run operations across the stack.

I own my context. I craft the system with agents. I’m not tied to any single app, model, or harness. This ownership is important because I believe that my professional future is tied to working with AI.

Things move so fast in this domain. Models, harnesses, connectors, the whole stack turns over every few months. If you’re locked into one packaged stack, you might not be as flexible, and your learnings might not compound as much. This chart shows how fast new theory comes online:

AI x GTM theory arrives in waves

I wrote in August that marketing orgs would barbell: system builders on one side, brand and community builders on the other. I want to be a single human that can work on both ends of that barbell.

That’s my personal bet. But it’s not for everyone. There are many smart and successful people who will do great on the other side of this bet.

And I’m not quitting Grok Bot. I’m treating it as a secondary tool, not a primary system. I’m going to keep tinkering when new ideas come up. It’s worth staying close.

I’m curious how deeply you’ve engaged in this one (or not).

What job has Grok Bot taken over for you?

I read all replies