🧠🧩 Installable templateAdvanced
Sales Orchestrator: group-chat control tower that routes each sales ask to exactly one specialist and gates outbound sends
Traffic control for a sales team made of several bots. It replies first in the group and routes each request to exactly one specialist. It stops dogpiles and chatter, gates handoffs and outbound sends, and keeps usage down by waking only the bot that's needed.
RevOps / GTM OpsGTM Engineer
From: Prasad (@idleshubh), Sales Orchestrator template
🧠🧩 Installable templateIntermediate
GTM Chief Of Staff: enterprise-sales chief of staff for meeting prep, inbox and post-call drafts, coordinating specialist bots
A chief of staff for enterprise sellers. It owns meeting prep, the inbox, and post-call drafts, and it hands deck and other GTM work to specialist bots. It never sends anything or changes Salesforce or any CRM without the owner.
AE
From: Sultanov (@thekuchh), GTM Chief Of Staff template
10-agent outbound chain with 3 human checkpoints: ICP pattern → anti-ICP → list → fit score → trigger → opener → sequence → send → reply classifier → objection drafts
A ten-agent outbound chain where the human steps in at exactly three points. First, the ICP pattern read from your last 15 closed-won accounts, because every agent downstream reads it. Second, every opener before it gets near the send. Third, every objection reply. In between: an exclusion builder (anti-ICP from churned and ghosted deals), list builder, 0–100 fit scorer, 'why now' trigger finder, sequence builder, send layer and a reply classifier he eyeballs each morning.
SDR / BDRGTM EngineerFounder / GTM Lead
From: Upamanyu Roy, LinkedIn post (Sep 9, 2026)
🧠🧩 Installable templateIntermediate
Outbound desk team: List, Research, Draft and Stop bots in one group chat; a weekday 08:00 Stop check removes repliers before any drafting
A four-bot outbound team. List builds a fit-based target list every Monday and rejects anyone in an open opportunity. Research finds the one specific thing worth mentioning. Draft writes the message and never sends. Stop drops anyone who replied or asked to stop, every weekday before any drafting runs.
SDR / BDRRevOps / GTM Ops
From: botteams.io 'Outbound desk' team (sales-outbound), source github.com/ellelion/botteams
Coordinator + 9 specialists: 96 first-touch drafts in 3 weeks, nothing sent without approval
For three weeks a consultant ran nine specialist AI agents under one coordinator for lead research, outreach drafts, pricing research and ops. They drafted 96 personalized first-touch emails, plus research and admin work he estimates at about 115 hours. Nothing reached a prospect without his approval.
Founder / GTM Lead
From: Eddy Kawira, via AI Business Plays (Olga Pearson)
Ronin chief of staff: 7:30am revenue brief + 8am new-clinic scan with first-touch drafts
Every weekday at 7:30am the bot sends a revenue brief with 1–2 'quick wins' to act on that day. At 8:00am it scans SoCal for newly opened clinics and drafts first-touch emails (he sent 2 that week). It also built a 3-email newsletter nurture: 434 enrolled, ~20% open, 2.6% click, 1 booked call. It cut 9 X clips and 16 LinkedIn drafts from raw footage, preps calls and tracks follow-ups. His rule: everything outbound is a draft and he hits send.
Founder / GTM Lead
From: Justin French (@JustinRFrench), via AI Business Plays (Olga Pearson)
Staff meeting: account bots and specialists debate how a CSM spends their one free hour
A CSM asks her chief-of-staff bot to start a staff meeting: a group chat where each account bot and specialist argues for the CSM's one free hour. The bots are told to disagree instead of agreeing by default. In the demo, two accounts say "don't spend it on us." The follow-up bot says a pending follow-up must go out now, and the account with an SSO issue makes its case. The chief of staff returns a ranked plan: SSO first, send the next-step email already drafted in Gmail, park the rest. This also checks for bias toward one customer.
Customer Success / AM
From: Blake Schuller, Grok Bot for Post Sales session
Self-completing task list: inbox watcher → chief of staff → territory-planner bot drafts the AE territory-dispute ruling
A RevOps/MarOps lead has a receiver bot watching email, calendar, text and work chat on a schedule. It hands everything new to a chief-of-staff bot, which reads the full Slack thread to work out the real ask and splits tasks and subtasks from FYI. When a task needs a specialist, the chief of staff passes it on with context. In the demo, an AE territory dispute goes to a territory-planner bot that knows the rules of engagement, the territory setup and the CRM, and it drafts the deliverable. The human validates and finalizes.
RevOps / GTM OpsFounder / GTM Lead
From: Matthew Silberman (@matt_silberman), Grok Bot for Marketing Operations session
🧠🧩 Installable templateIntermediate
Developer Relations roster: lead + 3 bots find top-5 developer friction journeys, draft a verified tutorial + response packet
A copy-paste roster prompt: the bot renames itself Dev (Developer Relations Lead) and creates exactly three teammates: Friction (Developer Researcher: issues, questions, drop-offs), Example (Technical Writer: tutorials, sample code, verification notes) and Loop (Community Analyst: feedback themes, advocates, program ideas). With GitHub, Docs and Community connected, the first job finds the five highest-friction developer journeys from real evidence and drafts one verified tutorial plus a community response packet, publishing nothing.
Demand Gen / GrowthGTM Engineer
From: codejunkie99 (rosterroom)
Research army: one search bot splits 100–200 accounts across low-context sub-bots in a group chat
For batch signal research too big for one context, a Web Search bot (Exa) splits 100–200 accounts across a set of low-context 'soldier' bots in an 'army huddle' group chat (e.g. 200 companies, 40 each); results flow back to the search bot, which passes the merged result up to the chief of staff.
SDR / BDRGTM Engineer
From: Simon, xAI SDR (session notes by unicodef1wn; 'Grok Bot for SDRs' session)
Post-sales chief of staff (Gus): 8 routines for CSM call prep, promises, and account watches
A CSM manages one chief-of-staff bot that runs a bench of specialists: Follow-ups, one Account specialist per customer, Ink (voice), Questions (docs), Career, and Scout (internal channels). Routines: an 8:30 weekday brief; call prep written 15–35 minutes before each call; unfinished promises at 9, 1, and 4; unanswered asks every 15 minutes; a visibility watch; an exhaust (usage-cliff / escalation) watch; a Friday dashboard; and a Wednesday self-improvement scan.
Customer Success / AM
From: Blake Schuller (Grok Bot guide)
🧠🧩 Installable templateAdvanced
Founder Mode: chief of staff + 8 specialist bots for founder-led sales
A setup pack with one chief-of-staff bot and 8 specialists (Sell, Outreach, Inbox, Insights, Product, Stalk, Content, Social) in 4 folders, with 16 routines that start paused. Founder Mode merges everything into an 8am action list, a Friday pipeline + win/loss digest, a Monday revenue check, and a monthly investor update draft. Outreach stages email + LinkedIn pairs at 7am sorted KEEP / HOLD / DQ. Nothing auto-sends.
Founder / GTM Lead
From: Simon Lackowski (Grok Bot guide)
🧠🧩 Installable templateSimple
Chief of Staff daily digest for a GTM leader
Reviews approved Slack channels, your inbox, calendar, and meeting notes since yesterday and returns only the items that map to your priorities doc. Each item comes with its source, why it matters, the proposed next step, and whether you owe a decision.
Founder / GTM Lead
From: SpaceXAI Grok Bot docs (Use cases → Chief of Staff)