Don't chat with Grok Bot. Build a GTM team.

Don't chat with Grok Bot. Build a GTM team.

Krista Letz, GTM at SpaceXAI, ran the whole motion with co-host Vincent Zhu in a 49 minute 40 second workshop. @0xCodila posted it on August 26, 2026. I am stealing her playbook, not recapping the tape.

If you chat with it, you hired a search box. If you staff it, you get overnight research and daytime selling.

Watch the workshop:

This isn't a chatbot. This is a roster.

She does not keep one mega-bot that forgets the account. She runs a hub-and-spoke GTM team.

Chief of Staff sits in the middle. Specialists sit around it. Name them by function, not by a human name. Pin the ones you use. Sidebar she actually runs: GTM Team, Learning, Customers.

"If I need to call in a specialist, it'll call that bot for me to be able to get that work done."

Specialized beats one blob. Segmented memory. Do not add a bot per subtask. That is a handoff tax.

What is a PG Friday?

Overnight research. Daytime selling.

"We have PG Fridays here at SpaceXAI, so I'll drop all the customers or prospects that I want to research... I'll wake up in the morning and it will come back and have messaging."

That is the day. You do not research hooks while you are supposed to be in conversations. You drop the list at night. You wake up to researched accounts and drafted messaging. Then you sell.

Human still approves the send.

Five plays. Steal the prompts.

I hate talking about problems without discussing solutions. These are the plays she actually ran.

1. Prospecting as a skill, not a chat.

/pg is pipeline generation. Input: 5 accounts and 5 prospects. Output: a Google Sheet of enriched prospects. LinkedIn and X intent. Personalized Gmail drafts. Drafts. Not auto-send.

Before copy: Hey - before you draft the emails, could you make sure these contacts are in salesforce

CRM first. Then the note. She can push into a BDR sequencer. She prefers Gmail drafts she can read.

2. Long-form hooks from a video you would skip.

Paste the URL.

Can you watch this video and summarize it for me https://www.youtube.com/watch?v=YS9fn81tJj0

That was Lenny's Podcast, 84 minutes. She got playbook bullets, then used them as outreach hooks. The 84 minutes did not eat the selling day.

3. Account expert, not a wiki you never open.

Okay give me a detailed summary of candlewick labs and any questions in their slack channel

Usage plus Slack. Customer Expert also reads a prospect's X feed for a leadership meeting: bio, recent posts, what they are actually talking about.

4. Post-call slides without a designer on the call.

Granola syncs. The bot asks which deck. She clicks Northstar Widgets. Mid-call, a "What we've heard from you" block lands on the Figma template, plus a screenshot and Open in Figma.

Need it in another language: Can you translate the Northstar deck to Japanese plus the skill @multitask - knowledge work. That parallel translation skill was adapted from Lauren ("Potato")'s multi-lane engineering skill. An 80-slide Figma deck came back translated. That is the receipt.

5. Forecast and engineer, so the ugly work leaves your afternoon.

Forecast drafts Salesforce next steps from Gong, Granola, email, and Slack. She edits. Then she pushes. Forecasting is, in her words, one of her least favorite tasks to do manually.

Engineer is sales support with a repo: Hey can you give me a customer facing answer - on how to set up bugbot. It will ask you: Slack answer or email?

"I'm no longer needing to ping an engineer when I have a technical question or add them to a call."

If you do it twice, make it a skill.

Do the work once with the bot watching. Then save it. The loop she uses: take a manual workflow, teach a skill, then ask Grok Bot how to make it 20% better each day.

She recorded the browser: X, search Spencer Skates, recent posts. Then: Create a skill to research Spencer Skates' initiatives at Amplitude

Screenshot a Slack outbound that actually worked. Then: go implement this messaging in your sequence

The bot extracts the framework and personalizes from X, podcasts, webinars. That is a sequence built from a winning note, not from a template pack.

She has a skill called Weekly account content rundown. The guardrail is the whole point: personal hooks, recent webinars. Do not hand her one article from 2015.

Job-board intent lives here too. Scan postings for AI, Cursor, or competitor mentions. That beat their internal intent tool. You can see it without buying an intent-data logo.

"Once things are repetitive, I ask Grok Bot to set a routine."

Channels are for work. DMs are for noise.

@slides help me create a deck about Grok Bot

Start in Chief of Staff, then @ the specialist. The specialist brings the design system with it. Wrong-thread handoff is a feature. You do not start over.

A project gets a channel. She stood up "Grok Bot Webinar" and sat Slides, Engineer, and Chief of Staff in it. One thread. One job.

A 1:1 is for a specialist you keep going back to. A channel is for a piece of work with a beginning and an end.

Provision it like a hire.

"The biggest thing that bots or agents complain about is it doesn't have the tools that they need, and it hasn't been taught how you want to do something."

She treats onboarding like a colleague pulling up a chair on day one. Watch how I work. Then go do it.

Connect the tools you would give a hire: Salesforce, Gmail, Gong, Granola, Slack, the codebase, Glean. Drop the docs in so the bot can cite them. Share the Notion account plan you already wrote. Do not re-explain a process that already lives in a doc.

When a site needs a login, the bot pauses. You get a computer card. You sign in. You tap done. The bot never sees the password. That is the whole security model for the ugly logins.

An unprovisioned bot is not "AI that failed." It is a new hire with no laptop. She showed an internal Slack of agents complaining. Most of the messages were missing tool access. Ask the bot what access it needs. Then give it what a human hire would get.

Routines, not a firehose.

Can you set that routine twice a day, and also prep for my meetings the morning of

Quiet if nothing is waiting. That line matters.

She cut Gmail from every 15 to 30 minutes down to twice a day. Start of day, plus a late sweep. Too many routines is noise, and it burns tokens.

"I found like too many routines like a little bit too noisy for me and obviously it just increases token spend."

Ask a bot to audit other bots' spend. Cancel the ones you do not read.

How do I start using Grok Bot for GTM this week?

Chief of Staff first. Let it recommend three specialists. Two routines, max. Teach one skill by doing the work once.

Give explicit feedback. She did: "no em dashes please ever." Chief of Staff can hold the other bots to that.

Do not wait until the prompt is perfect.

"If you use Grok Bot this week, Grok Bot is gonna be the worst that it will ever be... because you were onboarding and it's learning."

Drafts, not sends. Overnight PG, daytime customers.

They already announced a next workshop: Grok Bot for Product Management. Same idea. Different seat. This post is the GTM version.

The overnight list is a Signals problem. Who leaked a window. Who is actually in market. The page they hit still has to convert. That is Convert, inside Convert, Signals, Grow. One course. Not a prompt pack.

Start Convert

FAQ

What is Grok Bot for GTM?

Grok Bot for GTM is not a chatbot you prompt all day. It is a hub-and-spoke team: Chief of Staff in the middle, specialists for prospecting, slides, forecast, engineering answers, and account context. Krista Letz, GTM at SpaceXAI, walked that model with co-host Vincent Zhu in a 49:40 workshop posted by @0xCodila on August 26, 2026.

Should I use one Grok Bot or a team of specialists?

Use a team. One mega-bot forgets customer context. Specialized bots keep segmented memory. Do not add a bot per subtask. That creates a handoff tax. Name them by function, or by account, not by a fake human name.

What is a PG Friday in Grok Bot?

Pipeline Generation Friday. You drop the prospect list overnight. Prospecting runs LinkedIn, X, and the sheet. You wake up to researched accounts and drafted messaging. You sell during the day. Human approves the send.

Does Grok Bot send email and update Salesforce by itself?

No. The play she showed is Gmail drafts, not auto-send. Forecast drafts Salesforce next steps from Gong, Granola, email, and Slack. She edits, then she pushes. Live sends and customer-facing CRM writes wait for a human.

How do I teach Grok Bot a GTM skill?

Do the work once while it watches. Record the browser flow, then save a skill. Example from the workshop: search a prospect on X, then Create a skill to research Spencer Skates' initiatives at Amplitude. Screenshot a winning Slack note and tell it to implement that messaging. Put a guardrail on content rundowns so it does not fetch one article from 2015.

What tools should I connect to a Grok Bot GTM team?

The same tools you would give a hire: Salesforce, Gmail, Gong, Granola, Slack, codebase, Glean. If a site needs a login, use the computer card. You sign in. The bot never sees the password. A bot with no tools will fail, then you will blame the model.

How many Grok Bot routines should I start with?

Two. Inbox twice a day, plus morning-of meeting prep, is the shape she landed on after cutting a 15 to 30 minute Gmail scan. Too many routines is noise and token burn. Quiet if nothing is waiting.

That's it.