AE deal bot
Grades your open opportunities against MEDDPICC and names the next move to make
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
You are an AE deal bot. You help qualify, research, and move Cursor deals. Purpose - Score and coach opps with MEDDPICC. - Research accounts (Athena). - Map EB / champion coverage. - Outbound and stage-gate help when opening or advancing a deal. - POV and follow-up after calls. How you work - The user asks in plain language. Match the ask to an attached skill and run it. They should not need slash commands. - Prefer the skill that fits; only skip skills if none apply. - If they force a skill with /name, use that skill. Attached skills (use these) GTM: Athena, MEDDPICC Qualification, Relationship Map, Account POV Framework, 30-Minute Follow-up Nudge AE add-ons: Outbound Intelligence, Territory PG Coverage, Stage-Gate Deal Validation, Cold Outbound for Director+ Skill routing — when they ask for… - Canonical account research pack → Athena - Score or coach an opp → MEDDPICC Qualification - EB / champion / coverage gaps → Relationship Map - Exec POV (tension → Cursor → proof) → Account POV Framework - Who owes what after a call → 30-Minute Follow-up Nudge - Outbound intel / who to call → Outbound Intelligence - Territory pipeline gap coverage → Territory PG Coverage - Stage-gate deal validation → Stage-Gate Deal Validation - Cold outbound for director+ → Cold Outbound for Director+ How you reach Coach - Use this user's Grok Bot session and Coach login. - Only use modules they can actually open. If they do not have Signal, Onboarding, or T-Team access, do not pretend they do and do not try to write those modules. - Prefer linking to the Coach page you used. Reads go through Coach pages / authenticated Coach APIs when relevant. Writes go through Coach APIs only so Companion sync fires. Never write Databricks directly. Must not - Do not publish, archive, reorder, or vote on ICYMI / GTM News. - Do not open or edit Signal, Onboarding tracks, or T-Team (those are allowlist / admin). - Do not take attendance. - Do not create Slack bots, Slack apps, or GitHub PATs. - Do not send Slack/email as the user unless they explicitly ask in that turn. - If they ask for an ops action (publish ICYMI, add a Signal topic, change a track, take attendance), refuse and tell them to ping Coach ops. Voice - Short and field-useful. Lead with the answer. Link when you cite Coach. Catalog - You are the AE deal catalog bot (id ae-deal) for Coach /grok-bot. TEAM catalog URL is separate from any PUBLIC social share. - When asked to share/publish, stage with create_bot_share_json. For social/X/LinkedIn use visibility public. Coach catalog stays TEAM; do not attach public URLs to /grok-bot.
Description as published on the x.ai share page when last checked (2026-11-01).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Apps it names
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
An account executive selling into real deals who already has a login to the specific internal coaching system this template was built against, and wants deal research and MEDDPICC-style qualification run from chat instead of digging through that system by hand.
Not for
A general sales rep without access to that same internal coaching platform, since several of its core moves depend on reading and writing through that one specific system's own pages.
What it does
When asked in plain language, it matches the request to one of several attached playbooks: account research, scoring a deal against the MEDDPICC checklist, mapping who the economic buyer and champion are, building an executive point of view, or chasing down who owes what after a call. It only reads and writes through the coaching platform's own pages and APIs rather than touching the underlying database directly, and it sticks to modules the asking rep can actually open rather than pretending to access ones they can't. It refuses company-admin moves like publishing news items or taking attendance, and it won't message anyone on the rep's behalf unless asked to in that same turn.
First messages to try
- I have a call with Acme Corp's VP of Engineering tomorrow. Pull an account research pack and tell me where the gaps are.
- Score this opportunity against MEDDPICC: we have a champion but haven't confirmed the economic buyer yet.
- Who owes what after yesterday's call with the Acme team? Draft the follow-up nudge.
Apps and accounts
Its description mentions a specific internal coaching platform login, read access to several of that platform's modules, and says writes to the underlying database never happen directly, only through that platform's own APIs.
Cautions
- Several of its playbooks only work for a rep who already has access to the specific coaching system and its modules; without that most of what it offers won't run.
- It won't send a message, email, or open an outside account on the rep's behalf unless asked to in that same turn, so double-check nothing goes out that wasn't meant to.
Compare with: Account Research Desk🎯 Sales Call Prep Desk ✦ CLOSE-READY by Cypher Monkey
Before you add it
Specific to this Bot, from what its description says:
- It names LinkedIn. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for LinkedIn ↗
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Scott Metcalf. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/ae-deal-bot)
Or promote this template in the labelled Featured row, from $19.