Grok Bot procurement prompts that stop before you sign
Vendor renewals, PO drafts, and spend against contract. This is not finance P&L or ops office-manager work. The Bot never pays, never approves a PO, and never emails a vendor.
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.
Vendor renewals
5 promptsRenewals due in 90 days
1/21✨ What it does
The Bot lists contracts in [CONTRACT FOLDER] that renew or expire in [90] days, with notice windows and a draft decision note each. You approve which renewals to start; the Bot does not email vendors.
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 vendor contracts in [CONTRACT FOLDER] that renew or expire in [90] days, with notice windows and a draft stay-or-cut note each. Do not email vendors. Sources: [CONTRACT FOLDER], [AP SHEET], [CALENDAR]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - If a notice window is missing, mark unknown. Do not invent a date. Deliverable: Vendor, end date, notice window or unknown, spend, draft decision, link. Review point: I approve which renewals to start.
Pro tip: If the notice clause is missing, the row is unknown. Do not invent a date to be helpful.
One-vendor renewal pack
2/21✨ What it does
The Bot builds a renewal pack for [VENDOR] from [CONTRACT], [USAGE], and [LAST INVOICE], with price vs last year and a stay-or-cut note. You approve the decision; the Bot does not 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: Build a renewal pack for [VENDOR] from [CONTRACT], [USAGE], and [LAST INVOICE]. Show price vs last year. Do not send. Sources: [CONTRACT], [USAGE], [LAST INVOICE], [TICKET VOLUME 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - If two sources disagree on price or seats, show both. Deliverable: Pack path, price vs last year, usage vs seats, draft stay-or-cut, conflicts. Review point: I approve the decision.
Pro tip: Show last year and this year as two numbers. Do not blend them into a helpful average.
Auto-renew trap list
3/21✨ What it does
The Bot flags contracts in [FOLDER] that auto-renew with a notice window inside [60] days, and marks the clause unknown when it is missing. You approve which ones to cancel or renegotiate; the Bot does not contact the vendor.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Flag contracts in [FOLDER] with auto-renew and a notice window inside [60] days. Unknown if the clause is missing. Do not contact vendors. Sources: [FOLDER], [CALENDAR]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not cancel a subscription or chat with the vendor. Deliverable: Vendor, auto-renew yes/no/unknown, last notice day or unknown, draft next step. Review point: I approve which ones to cancel or renegotiate.
Pro tip: Auto-renew plus a short notice window is the trap. Silence in the PDF is unknown, not "probably 30 days".
Price-increase letter pack
4/21✨ What it does
The Bot matches each price-increase letter in [INBOX] for [PERIOD] to [CONTRACT] and drafts a pushback with the cite. You approve what goes out; the Bot does not email the vendor.
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 each increase letter in [INBOX] for [PERIOD], compare to [CONTRACT] and draft a pushback with the cite. Do not send. Sources: [INBOX], [CONTRACT], [PRICE BOOK 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - If the contract is silent, say silent. Do not invent a cap. Deliverable: Vendor, old price, new price, cite or silent, draft pushback. Review point: I approve what goes out.
Pro tip: Cite the clause or say the contract is silent. A vibe-based "that seems high" draft is not a pack.
Multi-year vs annual note
5/21✨ What it does
The Bot compares a [N]-year lock to annual for [VENDOR] using [USAGE] and [PRICE], and writes a stay-flexible vs lock-in note. You approve the term; the Bot does not sign.
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 [VENDOR], compare a [N]-year lock to annual using [USAGE] and [PRICE]. Do not sign. Sources: [CONTRACT], [USAGE], [PRICE], [BUDGET LINE]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not accept an online "renew now" click. Deliverable: Annual vs multi-year table, unused-seat risk, draft pick, what you assumed. Review point: I approve the term.
Pro tip: Name the break cost and the unused-seat risk. A cheaper year-one rate is not a win if seats go idle.
Purchase orders
4 promptsPO draft from a request
6/21✨ What it does
The Bot drafts a purchase order for [REQUEST] using [VENDOR], [SKU OR SCOPE], [BUDGET CODE], and [TERMS], and flags anything over [THRESHOLD]. You approve the PO; the Bot does not submit 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: Draft a PO for [REQUEST] using [VENDOR], [SKU OR SCOPE], [BUDGET CODE], and [TERMS]. Flag anything over [THRESHOLD]. Do not submit or approve. Sources: [INTAKE FORM OR THREAD], [PREFERRED VENDOR LIST], [PRICE BOOK]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. Deliverable: Draft PO fields, over-threshold flag, missing fields, file path. Review point: I approve the PO.
Pro tip: A PO without a budget code is a draft with a hole, not a PO. Leave the hole visible.
Intake to PO fields
7/21✨ What it does
The Bot turns [INTAKE] into PO fields against [TEMPLATE] and lists every required field that is still missing. You approve the completed form; the Bot does not create the PO in the system.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Turn [INTAKE] into PO fields against [TEMPLATE]. List missing required fields. Do not create the PO in the system. Sources: [INTAKE], [TEMPLATE], [CHART OF ACCOUNTS]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not invent a budget code or a ship-to. Deliverable: Mapped fields, missing list, draft ask back to the requester. Review point: I approve the completed form.
Pro tip: Do not fill a required field with a guess. Missing stays missing so you can ask the requester.
Duplicate-PO check
8/21✨ What it does
The Bot checks [DRAFT PO] against open POs in [PO SYSTEM] for the same vendor, SKU, or amount in [30] days, and marks likely duplicates. You approve whether to proceed; the Bot does not void or submit a PO.
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 [DRAFT PO] against open POs in [PO SYSTEM] for the same vendor, SKU, or amount in [30] days. Do not void or submit. Sources: [DRAFT PO], [PO SYSTEM]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not void, close, or submit a PO. Deliverable: Match / no match / ask-me, open PO links, draft proceed-or-stop note. Review point: I approve whether to proceed.
Pro tip: Same vendor plus the same amount in the same month is the usual double-buy. Ask for the open-PO link.
Blanket PO remaining
9/21✨ What it does
The Bot shows released vs remaining on blanket PO [PO NUMBER] against [END DATE], with receiving notes if they exist. You approve any new draw; the Bot does not release 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 blanket PO [PO NUMBER], show released vs remaining vs [END DATE]. Do not release a new draw. Sources: [PO SYSTEM], [RECEIVING], [CONTRACT]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not release a draw or raise the blanket. Deliverable: Released, remaining, end date, receiving gap, draft draw note for me. Review point: I approve any new draw.
Pro tip: If receiving and the PO tool disagree, show both. A blended remaining balance is how you overdraw.
Spend watch
4 promptsWeekly spend vs contract
10/21✨ What it does
The Bot shows spend by vendor for [PERIOD] versus [CONTRACT OR BUDGET LINE], flags overages, and ties totals to [AP OR CARD]. You approve what to cut or renegotiate; the Bot does not pay anyone.
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 [PERIOD], show spend by vendor vs [CONTRACT OR BUDGET LINE]. Flag overages. Totals must tie to [AP OR CARD]. Do not pay. Sources: [AP OR CARD], [CONTRACT OR BUDGET LINE], [CONTRACT REGISTER]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - If totals do not tie, show the gap. Do not invent a blended number. Deliverable: Vendor, spend, contract or budget, over/under, source, gap if any. Review point: I approve what to cut or renegotiate.
Pro tip: This is spend against a buying contract, not a P&L. If the total does not tie to the source, say so.
Maverick spend list
11/21✨ What it does
The Bot lists charges in [PERIOD] with no matching PO or contract in [REGISTER], grouped by owner, and drafts one internal note each. You approve who to ask; the Bot does not email the vendor.
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 charges in [PERIOD] that have no matching PO or contract in [REGISTER]. Group by owner. Draft one internal note each. Do not email vendors. Sources: [CARD FEED], [PO SYSTEM], [REGISTER]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not email employees either. Drafts stay here. Deliverable: Owner, charges, age, matching PO (none), draft internal note. Review point: I approve who to ask.
Pro tip: Off-contract is a people problem first. One internal draft per owner, not a vendor complaint.
Card vs PO mismatch
12/21✨ What it does
The Bot matches [CARD FEED] to open POs for [PERIOD] and flags charges with no PO plus POs with no receipt. You approve the cleanup; the Bot does not close or pay POs.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Match [CARD FEED] to open POs for [PERIOD]. Flag charges with no PO and POs with no receipt. Do not close or pay. Sources: [CARD FEED], [PO SYSTEM], [RECEIVING]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not close, receive, or pay a PO. Deliverable: Unmatched charges, unmatched POs, links, draft cleanup note. Review point: I approve the cleanup.
Pro tip: A charge without a PO and a PO without a receipt are two lists. Do not net them into one "variance".
New-vendor spend spike
13/21✨ What it does
The Bot flags vendors first paid in [90] days or up more than [X]% versus [PRIOR PERIOD], against [PREFERRED VENDOR LIST]. You approve who needs a contract; the Bot does not add them to preferred.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Flag vendors first paid in [90] days or with spend up more than [X]% vs [PRIOR PERIOD], against [PREFERRED VENDOR LIST]. Do not add them to preferred. Sources: [AP], [PREFERRED VENDOR LIST], [CONTRACT REGISTER]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not change the preferred list. Deliverable: Vendor, first-paid or spike %, preferred yes/no, contract yes/no, draft next step. Review point: I approve who needs a contract.
Pro tip: A new vendor at real spend is a contract hole, not a preferred-list add. You decide who is a one-off.
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.
Quotes and contracts
4 promptsQuote comparison table
14/21✨ What it does
The Bot compares quotes for [JOB] against [MUST-HAVES] and [BUDGET], and recommends one with gaps called out. You approve the pick; the Bot does not accept a quote.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare quotes for [JOB] against [MUST-HAVES] and [BUDGET]. Recommend one. Do not accept. Sources: [INBOX QUOTES], [RFP], [MUST-HAVES], [BUDGET]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not accept a quote or pay a deposit. Deliverable: Table, gaps vs must-haves, draft pick, what you assumed. Review point: I approve the pick.
Pro tip: Must-haves in the brief or it picks the pretty PDF. This is a buy, not an ops contractor hunt.
Notice-window calendar
15/21✨ What it does
The Bot extracts end date, notice days, and last-notice day from each contract in [FOLDER], and marks unknown if a date is missing. You approve what to put on the calendar; the Bot does not email vendors.
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 each contract in [FOLDER], extract end date, notice days, and the last day to give notice. Unknown if missing. Do not email vendors. Sources: [FOLDER], [CALENDAR]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not create calendar events unless I ask after review. Deliverable: Vendor, end date or unknown, notice days or unknown, last-notice day, draft reminder to me. Review point: I approve what to put on the calendar.
Pro tip: Last-notice day is the useful date. An end date without notice days is only half a reminder.
MSA vs SOW gap list
16/21✨ What it does
The Bot compares [SOW DRAFT] to [MSA] for [VENDOR] and lists conflicts plus missing clauses, without inventing legal language. You approve the redlines; the Bot does not send 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: Compare [SOW DRAFT] to [MSA] for [VENDOR]. List conflicts and missing clauses. Do not send redlines. Sources: [MSA], [SOW DRAFT], [PLAYBOOK 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not invent legal language. Do not send redlines. Deliverable: Conflict list, missing clauses, cite on each, draft redline notes for me. Review point: I approve the redlines.
Pro tip: Conflicts stay visible. Do not "helpfully" rewrite a liability cap you did not find.
Preferred vs one-off
17/21✨ What it does
The Bot marks each vendor in [PERIOD] as preferred, contracted, or one-off against [PREFERRED LIST], and drafts a one-off justification. You approve exceptions; the Bot does not change the preferred list.
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 spend in [PERIOD], mark each vendor preferred, contracted, or one-off against [PREFERRED LIST]. Draft a one-off justification template. Do not change the list. Sources: [AP], [PREFERRED LIST], [POLICY]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not add or remove preferred vendors. Deliverable: Vendor, tag, spend, draft justification, keep-or-ask. Review point: I approve exceptions.
Pro tip: A one-off that repeats is a preferred-list candidate. You still add the name.
Make the procurement Bot durable
4 promptsProcurement Bot description
18/21✨ What it does
The Bot writes a description named [NAME] for renewals, PO drafts, and spend watch, with a never-pay, never-approve, never-email-vendor footer. You approve the text and you create the Bot.
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 a procurement Bot description named [NAME] covering renewals, PO drafts, and spend watch. Never pay, never approve a PO, never email a vendor. Sources: [SYSTEMS], [POLICY], [REVIEW DAY]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. Deliverable: Description, weekly jobs, never-do footer. Review point: I approve the text. I create the Bot.
Pro tip: Write "if two sources disagree, show both" in the description. Buying is not a place to blend numbers.
Monday spend-watch routine
19/21✨ What it does
The Bot prepares a Monday routine that runs spend watch for [LAST 7 DAYS] against [REGISTER] and posts the pack here, failing if a source is down. You approve enabling it; the Bot does not pay or email during the run.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Mondays, run spend watch for [LAST 7 DAYS] against [REGISTER] and post the pack here. If a source is down, report failure. Do not pay or email. Sources: [AP OR CARD], [PO SYSTEM], [REGISTER]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not reuse last week if a source is down. Deliverable: Routine card, pack format, failure policy. Review point: I approve enabling it after a clean test.
Pro tip: Test on last week before this week. If AP or the card feed is down, the run fails; it does not reuse last Monday.
What procurement Bots never do
20/21✨ What it does
The Bot writes a never-do list for procurement Bots from [NO PAY / NO PO APPROVE / NO VENDOR EMAIL], with the human substitute for each. You approve the list and paste it into every procurement Bot.
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 procurement Bots on this computer from [NO PAY / NO PO APPROVE / NO VENDOR EMAIL]. Include the human substitute for each. Sources: My rules: [NO PAY / NO PO APPROVE / NO VENDOR EMAIL]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not change live Bot descriptions. This is a list for me to paste. Deliverable: 12 never-do items and the human substitute. Review point: I approve the list. I paste it.
Pro tip: If it can click the PO tool, the never-do list is the product. Pay, approve, and vendor email stay on you.
Vendor scorecard from sources
21/21✨ What it does
The Bot scores [VENDOR] on price, delivery, tickets, and contract fit using [USAGE], [TICKETS], and [INVOICES], with cites and a stay-or-cut note. You approve the score; the Bot does not send it to the vendor.
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 [VENDOR] on price, delivery, tickets, and contract fit using [USAGE], [TICKETS], and [INVOICES]. Cite each score. Do not share with the vendor. Sources: [USAGE], [TICKETS], [INVOICES], [SLA]. 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 pay, approve a PO, submit a PO, or email a vendor. New bank details are a stop. - Do not email the scorecard to the vendor or to the team. Deliverable: Score table with cites, unknowns, draft stay-or-cut, pack path. Review point: I approve the score.
Pro tip: A score without a cite is a vibe. If tickets or usage are missing, the category is unknown.
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