Krista Letz @kristaletz ·
Grok Bot for GTM
Grok Bot for GTM
What you need
- Connected apps
- Salesforce, Gmail, Calendar, Sheets, Drive, Slack, Notion, Granola, Gong, Figma, X, LinkedIn and the data warehouse.
- Routines
- Daily meeting prep, inbox scans with auto-drafted replies, follow-up drafts from Granola or Gong notes, overnight prospecting and a weekly media rundown per account.
- Skills
- Skills recorded by demonstrating a task, an anti-slop skill the author keeps editing, a skill for spinning up parallel cloud agents, and live slide updates from a call transcript.
What prompted it
The author spends most of the day on customer calls, which used to leave hours of admin for the evening.
What Grok Bot did
- Connected Grok Bot to the tools the author uses daily, and had it scan Gmail and Slack to learn the author’s writing style.
- Set up a pinned Chief of Staff that owns meeting prep, the inbox and post-call drafts, and calls on the other bots.
- Added a prospecting bot that researches accounts overnight and drafts outreach in Gmail in the author’s voice.
- Gave each strategic account its own customer-expert bot, which watches Slack, calls and email and flags feature requests.
- Added a product-expert bot connected to the codebase, a forecasting bot that updates Salesforce notes, a 1:1 bot, a slides bot in Figma and a sales coach that reviews Gong calls.
- Onboarded the bots like teammates: demonstrated each task once, turned the recording into a skill, and added a rule every time the author corrected a bot.
Evidence and limits
- Original post checked on X (Oct 17, 2026)
- Outcome reported by the author
- Not reproduced by anyone else yet
- Stop the Granola recording 5 to 10 minutes before a call ends so the slides bot can build a slide from the discovery before you wrap up.
- Give the slides bot your design guidelines up front.
- Without repo access, an internal knowledge tool like Glean can serve as the product expert’s source.
