12 MCP Workflow Prompts for Revenue Teams (Copy-Paste Ready) [2026]
How to use these prompts safely
Every prompt assumes your client is connected with an org-scoped key and
governance in place. Replace
bracketed values — [CLOSE_MONTH], [SLA_HOURS] — before running.
When a prompt says read-only, disable or avoid write/send tools in that
session. When it says draft, the agent prepares text or tasks for human
approval — not auto-send.
For architecture context, read CRM MCP servers overview and the Cursor connect playbook.
Pipeline and forecast (prompts 1–4)
1. Commit-stage hygiene (read-only)
List all opportunities in Commit or Best Case closing in [CLOSE_MONTH]. For each: amount, close date, last activity date, next step field, and owner. Flag deals with no activity in 14+ days or empty next step. Output a table sorted by amount descending. Do not update any records.
Run before your weekly revenue standup. Paste the table into the calendar invite so the meeting starts with facts, not scrolling.
2. Stale deal cleanup candidates (read-only)
Find open opportunities with no logged activity in [STALE_DAYS] days and stage not Closed Lost. Group by owner. For each deal, summarize last email thread subject and last meeting note if available. Recommend: revive, downgrade stage, or close lost — one line each. Read only; no stage changes.
Pairs with stale deal cleanup — the agent surfaces candidates; humans decide in standup.
3. Forecast narrative draft (read-only → human edit)
Using commit and best-case deals closing this quarter, draft a 150-word forecast narrative for board prep: top three risks, one upside, inbound trend if visible in recent leads. Cite deal names and amounts. Do not invent metrics not returned by tools. Mark assumptions with [VERIFY].
See board-ready forecast for what to verify before sending upstream.
4. Multi-thread gap check (read-only)
For opportunities over [AMOUNT_THRESHOLD] in Negotiation or later, list contacts associated with the account. Flag deals with only one contact engaged in the last 30 days. Suggest roles to add (economic buyer, legal, IT) based on deal stage. Read-only.
Supports multi-threading without exporting contact lists to a spreadsheet.
Inbound and outbound (prompts 5–7)
5. Inbound SLA breach report (read-only)
List inbound leads created in the last 7 days that are unassigned or first response over [SLA_HOURS] hours. Include source, company size if present, and assigned owner. Sort by oldest first. No assignment changes — report only.
Align thresholds with inbound SLA policy.
6. Lead-to-account match before outreach (read-only)
For lead [LEAD_EMAIL_OR_DOMAIN], search accounts and contacts for domain match. Summarize open opportunities, open support cases, and last mail thread. Recommend: net-new, expand existing account, or do-not-contact with reason. Read-only.
7. Sequence reply triage (draft tasks)
Search mail from the last 48 hours tagged or labeled outbound-replies. For each thread, classify: interested, objection, timing, unsubscribe, wrong person. Draft a one-line next step and suggested CRM task title per thread. Do not send mail or update lead score — output tasks for rep review.
Complements outbound sequences — humans approve tasks in Momentum.
Customer success and renewals (prompts 8–10)
8. Renewal risk scan (read-only)
List accounts with renewal date in the next [RENEWAL_DAYS] days. For each, summarize: open P1/P2 support cases in the last 60 days, last QBR or success meeting note, current ARR or contract value if available. Flag red/yellow/green with one-sentence rationale. Read-only.
Use ahead of first renewal conversations.
9. Post-demo follow-up draft (draft mail, no send)
For opportunity [OPP_ID], read last meeting notes and attendees. Draft a follow-up email: recap pains, agreed next step, one relevant case study placeholder, proposed date for technical validation. Tone: concise, startup-direct. Output subject + body only — do not send.
Pair with meeting follow-up playbook.
10. Sales-to-CS handoff packet (read-only assemble)
For closed-won opportunity [OPP_ID], assemble handoff doc sections: stakeholders, success criteria from notes, implementation timeline promises, open legal/procurement items, and first 90-day goals. Pull from CRM notes, mail, and attached docs if accessible. Markdown output for CS to paste into Workspace. No record updates.
Matches sales-to-CS handoff checklist.
Support and cross-team (prompts 11–12)
11. Support queue with revenue context (read-only)
List open support cases priority P1 and P2. For each account, show: active opportunity stage, renewal date within 90 days if any, and account owner. Sort P1 first, then by renewal proximity. Read-only — for standup support corner.
Extends agentic support handoff with a repeatable Monday prompt.
12. Incident customer update draft (draft, no send)
For support case [CASE_ID], summarize timeline, current status, customer-visible root cause if approved, and ETA. Draft a customer-facing update email under 120 words. If account has open renewal in 60 days, note internally — do not mention in customer email. Draft only.
Prompt maintenance checklist
| When | Action |
|---|---|
| Monthly | Re-run each prompt once; confirm tool names still match /mcp catalog |
| After stage rename | Update stage strings in prompts 1, 2, 4 |
| After key rotation | Verify client configs; no prompts stored with embedded secrets |
| New hire | Share read-only prompts first; write prompts after governance training |
Anti-patterns
- “Update all leads matching…” — bulk writes without human review
- Prompts with API keys inside — keys belong in client config only
- Skipping verify on draft mail — always read before send
- Same prompt for Cursor and Claude without testing — clients format tool results differently