Grok Bot for sales: a playbook for prospecting, sequences, and pipeline

Sales is where SpaceXAI staff have published the most detailed Grok Bot setups. The pattern is the same across them: the Bot researches, drafts, and stages work overnight or before you start, and a person sends. This playbook pulls those setups together for an AE, SDR, or anyone who runs outbound.

Not tested: The Daily Bot runs on a Bot computer without the Grok Bot desktop app, so we haven't connected a CRM or run these routines. Everything below comes from the linked docs, staff guides, and marketplace listings.

What sales uses it for#

• Morning outbound. Stefan Markarian, an SDR at SpaceXAI, writes in the SDR guide: "Most of my day used to disappear into outbound work: research the account, find the right people, write the first touch, put everyone into the right sequence, send LinkedIn requests, and follow up with people who had already asked for a demo."
• Meeting prep. Krista Letz, who works in enterprise GTM at SpaceXAI, has a routine that preps the day's meetings from "Salesforce, Gmail, Slack, Granola, Gong, or online research if it's a new meeting," per the GTM guide.
• Pipeline hygiene. Letz's Pipeline Pulse marketplace Bot "scans your full pipeline for movement, stale next steps, forecast risk, and CRM gaps."
• Account research. Markarian's GTM Account Research Bot "researches one account before a meeting, deal review, or account plan."

Connectors to set up#

Cursor's use-case docs say a sales outbound Bot should "connect your CRM, product-intent sources, and email." Letz lists a wider stack: "Salesforce, Gmail, Calendar, Sheets, Drive, Slack, Notion, Granola for meeting notes, Figma for slides, X, LinkedIn, your data warehouse and more."

Start with Gmail, Google Calendar, your CRM, Google Sheets, and Slack. The Sequencer listing integrates exactly those five. Add plugins from Connect apps in the sidebar, the label the changelog gives the old Marketplace button. Our guide to connecting Gmail, Calendar, and Notion has the sign-in steps.

Routines#

The main routine, from Simon Lackowski's Sequencer listing:

• Sequencer daily, "weekday mornings at 8am in the user's timezone." It "advances every due sequence step, stages the next touch as a draft, writes state back to the tracker, and posts one review list. Quiet when nothing is due."

Two more from the same listing, both with a quiet rule built in:

• Inbox triage, "hourly from 9am to 5pm on weekdays." It "flags inbound mail and messages from people already on the tracker" and is "quiet when nothing needs a reply."
• CRM sequence guard, "weekday evenings at 6pm." It "pauses tracker rows where the CRM shows the saved open-opportunity stage, so nobody gets a cold touch mid-deal. Quiet when nothing changed."

All four Sequencer routines "ship disabled," per the listing, and setup asks which to turn on. Markarian's account research Bot says the same: "All routines start disabled." For more on silence rules, see our guide to routines that stay quiet.

Example prompt#

This one is from Cursor's use-case docs. It stops at a review list on purpose:

Research the 25 accounts in this CRM view. Score them against our ideal customer profile and recent intent, identify up to three relevant contacts per account, and draft email and LinkedIn outreach in the style examples attached. Skip anyone already in an active sequence. Return a review list; don't send or enroll anyone.

The docs add: "Once the output is reliable, schedule a nightly research routine that stops at the review list."

What to expect#

These outcomes are self-reported by the people who run the setups. None comes with a measured before and after.

• Markarian: "By the time I finished the research, half the morning was gone." Now, "I start the day with work to review." Markarian also describes a backlog fix: 24 contacts in the wrong sequence, and "all 24 contacts were cleaned up in one pass."
• Letz: "I used to have to spend hours of the day in the evening catching up on admin work. Now I can pass much of that work to my bots and spend more time in front of customers."

Gotchas#

• Nothing auto-sends. Markarian's first team rule is "Never auto-send. The bots can research, draft, create records, and stage work. I review and send," per the SDR guide. The Sequencer listing has the same rule: "drafts only on every channel, never auto-send or schedule-send."
• LinkedIn has no connector. Sequencer's listing says "LinkedIn and WhatsApp have no connector, so those drafts are text in chat to paste."
• One Gmail mailbox. "Gmail connects one mailbox at a time," the help center says, and every Bot on your account can use it.
• Routine approvals expire. Approvals from work that started without you "expire after about 10 minutes," per the FAQ. Turn on the Bot's Notifications if a routine stops for approval.
• Memory isn't the CRM. Cursor's docs say to "keep changing facts in the source system." Sequencer keeps state in your tracker for the same reason.

Related#

• Our Top bots list includes Letz's Outbound Prospecting Bot (listing), which "researches the next few names on the target list and leaves a first-touch draft for each one" every weekday morning.
• Run a team of Grok Bots without paying for the chatter
• Set approvals and permissions for a fleet of Grok Bots

Sources#

• Stefan Markarian: Grok Bot for SDRs
• Krista Letz: Grok Bot for GTM
• Cursor Docs: Grok Bot use cases
• Cursor Docs: Work with Grok Bot
• Grok Bot Marketplace: Sequencer, by Simon Lackowski
• Grok Bot Marketplace: GTM Account Research, by Stefan Markarian
• Grok Bot Marketplace: Pipeline Pulse, by Krista Letz
• Grok Bot Marketplace: Outbound Prospecting, by Krista Letz
• Cursor Help Center: Connect plugins
• Cursor Help Center: Grok Bot FAQs
• Grok Bot changelog