Grok Bot partnership prompts that stop at drafts
Partner research, intro drafts, and integration checklists on the cloud computer. Distinct from sales outbound and founder ops. You email every partner and you sign every paper.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Partner research overnight
5 promptsScore a partner list against the thesis
1/21✨ What it does
The Bot scores every company on [PARTNER LIST] against the thesis in [DOC] and ranks the top [15] with a why-now note and evidence links. You pick who gets an intro draft and you send it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Score every company on [PARTNER LIST] against the thesis in [DOC]. Rank the top [15]. Sources: [PARTNER LIST], [DOC], company websites, [CRM IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Skip anyone already in an active partner conversation. Deliverable: Table: company, score 1-5, why now, overlap, channel risk, evidence links. Review point: Stop at the table. Do not write intros unless I ask.
Pro tip: Point at a list and a thesis doc. "Find us partners" is how the Bot wanders into customer outbound.
Map complementary products in a category
2/21✨ What it does
The Bot maps products in [CATEGORY] that complement [OUR PRODUCT] and lists overlap, gap, and channel risk for each, with sources. You decide who to approach and you send the first note.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Map complementary products in [CATEGORY] for [OUR PRODUCT]. Date every claim. Sources: Vendor sites, changelogs, [MARKETPLACE IF ANY], [NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not invent install counts or revenue. Unknown is allowed. Deliverable: Table: company, product, overlap, gap, channel risk, link. Review point: I pick follow-ups.
Pro tip: Name the category and what "complement" means. Adjacent is not the same as partner-shaped.
Find three BD contacts at a company
3/21✨ What it does
The Bot finds up to three partnership contacts at [COMPANY], with title, why they fit, and a source URL, and skips anyone already in [CRM]. You pick who gets a draft and you send it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: For [COMPANY], identify up to 3 partnership contacts. Exclude anyone already in [CRM]. Sources: [CRM], [LINKEDIN OR APPROVED SOURCING], company site, [TITLE MAP IN DOC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. Deliverable: Name, title, why they fit, source URL, already-in-CRM (yes/no). Review point: I pick who gets a draft.
Pro tip: Ask for the evidence of the match. Title-only lists are how you email the wrong person.
Partner-fit versus competitor-risk card
4/21✨ What it does
The Bot writes a one-page card for [COMPANY] covering partner fit versus competitor risk, using only sourced claims from [NOTES] and their site. You use it on the call and you send any follow-up.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: A one-page card for [COMPANY]: where a partnership helps, where they compete with us. Sources: [NOTES], their site, [BATTLECARD FOLDER], [G2 OR APPROVED SOURCE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - No invented win rates or quotes. Deliverable: Fit, conflict, two questions that surface the gap, sources. Review point: I use it on the call. You do not email them.
Pro tip: Ban invented win rates. If a claim has no source, the cell says unknown.
Nightly partner research (drafts only)
5/21✨ What it does
The Bot sets a weekday run at [07:00] [TZ] that researches [PARTNER VIEW] and posts a review list, or reports failure if the view is empty. You enable it after a test; you send every note yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekdays at [07:00] [TZ], run the partner-research skill on [PARTNER VIEW] and post the review list here. Sources: Current [PARTNER VIEW]. If the view is empty or the source is down, report failure. Do not reuse yesterday. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. Deliverable: Routine card: next run, input, output, approval line, failure behavior. Review point: Test run first. I enable it.
Pro tip: Create the routine only after a second input looked as good as the first.
Intros and pitches you still send
4 promptsDraft a warm intro in my voice
6/21✨ What it does
The Bot drafts a warm intro for [PARTNER] via [MUTUAL], in the style of the examples you attach and using [ONE-LINER]. You send from your own mailbox.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a warm intro to [PARTNER] via [MUTUAL] in the style of the examples attached. Sources: Approved contact from this thread, [ONE-LINER], [MUTUAL CONTEXT], style examples attached. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - No fake personalization. If you cannot find a real hook, say no hook and skip. Deliverable: Hook used, intro draft, what you asked [MUTUAL] to do, source of the hook. Review point: I send from my own mailbox.
Pro tip: Attach two intros you actually sent. "Write like me" without examples writes like a bot.
Draft a cold BD note I will send
7/21✨ What it does
The Bot writes one email and one LinkedIn note for [CONTACT] at [COMPANY], with a real hook from their site or [NEWS], or marks no hook. You send from your own accounts.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft one email and one LinkedIn note for [CONTACT] at [COMPANY]. Do not send. Sources: Their site, [NEWS], [ONE-LINER], style examples attached. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - If you cannot verify the hook, mark no hook and skip. Deliverable: Hook used, email draft, LinkedIn draft, source of the hook. Review point: I send from my own accounts.
Pro tip: This is BD, not SDR sludge. If the only hook is "loved your post", delete the draft.
Why-us and why-you one-pager
8/21✨ What it does
The Bot writes a one-page why-us and why-you brief for [PARTNER] from [ONE-PAGER] and [THEIR SITE], with sourced claims only. You send or present it; the Bot does not.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: A one-page why-us and why-you brief for [PARTNER]. TBD any claim you cannot source. Sources: [ONE-PAGER], [THEIR SITE], [THESIS DOC], [NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not invent their metrics or customer counts. Deliverable: Why them, why us, proposed shape, open questions, sources. Review point: I send or I present.
Pro tip: Write it from their side first. A one-pager that only lists our features is a brochure.
Co-marketing pitch they can forward
9/21✨ What it does
The Bot drafts a co-marketing pitch for [CAMPAIGN] with [PARTNER], including audience overlap, an asset list, and a draft note. You send the note and you book the time.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a co-marketing pitch for [CAMPAIGN] with [PARTNER]. Do not send. Sources: [CAMPAIGN BRIEF], [AUDIENCE NOTES], [ASSET FOLDER], [THEIR SITE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not schedule a webinar, book a room, or email their marketing team. Deliverable: Audience overlap, proposed format, asset list, missing assets, draft note. Review point: I send the note. I book the time.
Pro tip: Name the asset you already have. A pitch that invents a webinar you will not run dies in their inbox.
Integration and enablement checklists
4 promptsIntegration readiness checklist
10/21✨ What it does
The Bot builds an integration checklist for [PARTNER API] against [OUR STACK] and [SECURITY DOC], marking what you can verify versus what you must do. You send it to engineering or the partner.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build an integration checklist for [PARTNER API] against [OUR STACK]. Mark verify vs I-must-do. Sources: [PARTNER API DOCS], [OUR STACK], [SECURITY DOC], [TICKET IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not create tickets, open PRs, or email their solutions team. Deliverable: Checklist with owner = you vs me, blockers, links, unknowns. Review point: I send it. I open the tickets.
Pro tip: If a doc is missing, red-flag. Do not invent scopes, SLAs, or "they support SSO".
Marketplace listing I will publish
11/21✨ What it does
The Bot drafts a marketplace listing for [DIRECTORY] from [PRODUCT DOC] and [SCREENSHOTS], and flags missing assets. You send the listing live; the Bot does not submit.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a listing for [DIRECTORY] from [PRODUCT DOC]. Flag missing screenshots or copy. Do not submit. Sources: [PRODUCT DOC], [SCREENSHOTS], the live [DIRECTORY] listing form in the cloud browser. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not submit, publish, or create a vendor account with my real email unless I take over. Deliverable: Field-by-field draft, missing assets, screenshot of the form requirements. Review point: I submit.
Pro tip: Ask for the required fields from the live form. Generic listings get rejected.
Enablement kit for partner AEs
12/21✨ What it does
The Bot builds an enablement kit for [PARTNER] AEs from [DECK], [ONE-PAGER], and [FAQ], with talk tracks and objection cards. You send the kit; the Bot does not mail their team.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build an enablement kit for [PARTNER] AEs. Do not email their team. Sources: [DECK], [ONE-PAGER], [FAQ], [BATTLECARD], style examples if I attach them. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not upload the kit to their portal or our CMS. Deliverable: Talk track, objection cards, one-pager draft, what is still missing. Review point: I send the kit.
Pro tip: One talk track plus two objections beats a 40-slide dump they will not open.
Security questionnaire I still submit
13/21✨ What it does
The Bot fills [QUESTIONNAIRE] from [SECURITY PACK] and marks TBD on anything it cannot source. You review, then you send or sign; the Bot does not submit.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Fill [QUESTIONNAIRE] from [SECURITY PACK]. TBD any answer you cannot source. Do not submit. Sources: [SECURITY PACK], [TRUST PAGE], [QUESTIONNAIRE FILE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - This is not legal or security advice. Do not invent controls we do not have. Deliverable: Filled draft, TBD list, questions for counsel or security. Review point: I review. I send or I sign.
Pro tip: TBD wins. Invented answers on a partner security form become your problem later.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Health, QBR, and renewals
4 promptsQBR pack from sourced metrics
14/21✨ What it does
The Bot builds a QBR pack for [PARTNER] covering sourced metrics, open asks, and risks from [CRM], [SLACK], and [DECK]. You send the pack and you run the QBR.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a QBR pack for [PARTNER] for [QUARTER]. TBD missing numbers. Do not send. Sources: [CRM], [SLACK IF ANY], [DECK], [REFERRAL OR PIPELINE VIEW]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not invent sourced pipeline or payout numbers. Deliverable: Metrics, open asks, risks, suggested agenda, links. Review point: I send the pack. I run the QBR.
Pro tip: Tell it which fields are trustworthy. Partner notes fields are often fiction.
Flag stale partners and draft a reopen
15/21✨ What it does
The Bot lists partners in [PIPELINE] with no activity for [N] days and drafts a reopen note for each. You send the notes; the Bot does not email them.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List partners in [PIPELINE] with no activity for [N] days. Draft a reopen note for each. Sources: [PIPELINE VIEW], activity timestamps, last email if visible. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not edit stages, tiers, or renewal dates. Deliverable: Partner, last activity, suggested next step, draft note, confidence. Review point: I send. I change the CRM.
Pro tip: Define stale in days. Otherwise every quiet partner becomes a crisis.
MDF or co-op memo I will file
16/21✨ What it does
The Bot writes an MDF or co-op memo for [PARTNER] for [QUARTER] from [BUDGET SHEET] and [RULES], with a source link under every number. You send or submit the claim; the Bot does not file it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write an MDF or co-op memo for [PARTNER] for [QUARTER] using [BUDGET SHEET] and [RULES]. Do not file. Sources: [BUDGET SHEET], [RULES], [CAMPAIGN RESULTS], [INVOICES IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not invent spend. Do not submit the claim in their portal. Deliverable: One page: spend, proof, ask, risk, rollback, links. Review point: I send or I submit.
Pro tip: Cite the report URL under every number. Memos without links get ignored.
Referral and affiliate digest
17/21✨ What it does
The Bot writes a digest of [AFFILIATE VIEW] since [DATE]: who sent volume, who went quiet, and payouts you owe, each with a link. You send any chase note yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Digest [AFFILIATE VIEW] since [DATE]. Only what needs my decision or a payout. Sources: [AFFILIATE VIEW], [PAYOUT SHEET], [CRM]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not post to Slack. Do not mark payouts paid. Deliverable: Volume / quiet / payouts owed, each with a link, plus draft chase notes. Review point: I send chase notes. I pay.
Pro tip: Map it to the payout sheet or it will narrate every click like news.
Guardrails partnership Bots forget
4 promptsDraw the no-send, no-sign line
18/21✨ What it does
The Bot writes a standing policy for partner send, sign, and term changes using your tools [LIST] and hard rules such as [NEVER EMAIL A PARTNER]. You paste it, and you send every partner note yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: A reusable approval policy for partner send, sign, exclusivity, and pricing. Sources: My current tools: [LIST]. My hard rules: [NEVER EMAIL A PARTNER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. Deliverable: A 10-line policy I can paste into the Bot description, plus 4 examples of stop and ask. Review point: Show the policy. Do not change any existing routines until I paste it.
Pro tip: Put this in the Bot description, not only in one chat. New threads forget informal rules.
Propose a 3-Bot partnership desk
19/21✨ What it does
The Bot proposes three named Bots for a [PARTNER / BD] week: research, drafts, and ops, plus a review window of [30 MIN]. You create the ones you want; you send every partner note yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: A 3-Bot desk for a [PARTNER / BD] week: research, drafts, ops, one group chat. Sources: My tools: [LIST]. My weekly partner work: [LIST]. Hours I can review: [30 MIN]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Every Bot shares one computer. Do not pretend logins are isolated. Do not create the Bots. Deliverable: Table: Bot name, job, inputs, output, approval line. Plus the group-chat purpose. Review point: Show the roster. Do not create the Bots until I pick which to start with.
Pro tip: Focused Bots beat one catch-all that also does customer outbound. Keep sales on the sales page.
What partnership Bots never do
20/21✨ What it does
The Bot writes the never-do list for partnership Bots from your rules [NO SEND, NO SIGN, NO PRICING, NO EXCLUSIVITY]. You paste it into every Bot, and you send every partner message yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for my partnership Bots, including no send and no sign. Sources: My rules: [NO SEND, NO SIGN, NO PRICING, NO EXCLUSIVITY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. Deliverable: 12 never-do items and the approval substitute for each. Review point: I paste this into every partnership Bot description.
Pro tip: If it is not written, a helpful Bot will eventually just send the intro or accept a portal term.
Channel-conflict check before outreach
21/21✨ What it does
The Bot checks [PROSPECT PARTNER] against [EXISTING PARTNERS] and [TERRITORY RULES] and flags overlap, exclusivity risk, and who would be angry. You send any courtesy note; the Bot does not.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Check [PROSPECT PARTNER] against [EXISTING PARTNERS] and [TERRITORY RULES]. Flag conflict. Sources: [EXISTING PARTNERS], [TERRITORY RULES], [CONTRACT DATES IF ANY], their site. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email, message, or enroll a partner. Do not sign or commit terms. - Do not tell the prospect they are in conflict. That note is mine. Deliverable: Overlap, exclusivity risk, who would be angry, recommended go / pause / ask-me, sources. Review point: I send any courtesy note. I decide.
Pro tip: Name the partners who would be angry. A Bot that cannot see your book will pitch a competitor of your reseller.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides