Free Claude for RevOps Cheat Sheet
RevOps - if you feel the Claude FOMO, this cheat sheet helps you get over it. It covers:
- 60+ Claude use cases for RevOps
- Copy & paste prompt templates
- How to set up each Claude mode
- How to give Claude the right context
- When to use Claude vs. dedicated GTM AI tools
.webp)
"With Weflow, we’re now capturing all relevant activities and have full transparency into the performance of each sales rep. It’s a game changer."
%201.svg)
"Weflow gives us better visibility and predictability of our business."
"Weflow eliminated the need for our VP to ask, ‘Did you follow up with that deal?’. It tracks customer interactions automatically, creating a framework that drives accountability across the team."
"None of the other tools gave us a solution like Weflow. From the beginning, we had a really smooth process."
.webp)
"I had a first introductory call with Weflow. I think I was sold after 15 minutes. There’s no question that the people at Weflow understood the problems that we were trying to solve."
"I’ve worked with Gong before, but Weflow’s simplicity and real-time sync are game-changing."
.webp)
"We use Weflow to auto-capture activity data, run deal reviews, and analyze our pipeline to inform our forecast. Being able to spot deal risks early has improved win rates and pipeline health."
.svg){kind=icon}
.svg){kind=icon}
.svg){kind=icon}
.svg){kind=icon}
.svg){kind=icon}
What's Inside
60+ RevOps use cases mapped to Claude
- Concrete plays across pipeline, forecasting, CRM hygiene, MEDDIC reviews, QBRs, territory planning, deal desk, and comp
- Weekly-grade examples like stale-opportunity audits, week-over-week pipeline narratives, and forecast variance explanations from actuals versus plan
- Every use case tagged to Chat, Projects, Cowork, Code, or API so you know how to actually run it
Picking the right model and mode
- When to default to Sonnet for fast high-volume work and when Opus is worth it for exec-ready synthesis
- The operational role of each mode: Chat for ad hoc, Projects for context, Cowork for delegation, Code for SOQL and Apex, API for always-on
- Role-based starting points for analysts, managers, and RevOps leaders so adoption matches how you actually work
Prompt templates, context, and guardrails
- Copy-ready prompts for pipeline reviews, MEDDIC scoring, QBR summaries, SOQL generation, pre-meeting briefs, and deal-risk Slack messages
- The exact context Claude needs: ICP, stages, forecast categories, metric formulas, quotas, handoffs, fiscal calendar, plus a reusable system prompt
- Operational rules on PII handling, sandbox testing for code, and where human judgment still owns the final call
Janis Zech
Janis Zech is the co-founder and CEO of Weflow, the modular Revenue AI Orchestration platform. He co-hosts the RevOps Lab podcast, where he sits down with RevOps leaders and sales operators to unpack how they run revenue teams, forecast pipeline, and use AI to get more out of Salesforce. At Weflow, Janis focuses on helping revenue leaders turn messy CRM data into reliable forecasts and better sales execution. His angle on the podcast and blog is always practical: what's actually working inside high-performing revenue orgs, and what's just noise.
Go Deeper
Claude Prompts RevOps Teams Run to Automate Forecasting and CRM Hygiene [With Template]
#83 Becoming strategic in RevOps with our cheat sheet - with Janis and Philipp
Free Strategic RevOps Cheat Sheet
Frequently asked questions
What's the difference between using Claude in Chat versus Projects, and when does it actually matter?
Chat is for one-off tasks where you paste your data, get your output, and move on — no setup, no persistence. Projects matter when you're running the same workflows repeatedly, because you set your company context once (stage definitions, segments, fiscal calendar, metric glossary) and every conversation inside that project inherits it automatically. If you're doing weekly pipeline reviews, QBR prep, or recurring MEDDIC scoring, Projects will save you significant time versus re-pasting context every single session.
Do I need to set up an API or MCP integration before this cheat sheet is useful to me?
No — the fastest path to value is exporting a Salesforce report as CSV and pasting it directly into Claude Chat. The API and MCP setup is covered in the cheat sheet, but it's for teams that want live data access and always-on automation, not a prerequisite for getting started. Most RevOps managers and analysts will get real, immediate output from Chat and Projects before they ever touch the API.
Which RevOps tasks should stay human-led even if Claude can technically do them?
Deal judgment in live reviews, comp decisions, and anything with legal or compliance implications should stay human-led. Claude can score a deal against MEDDIC from call notes and flag qualification gaps, but it can't replace a manager who's been in the room with the rep and the prospect. Use Claude output as a structured starting point for deal reviews — not the final word you bring to your CRO.
What context do I actually need to prepare before Claude's output is reliable enough to use in a forecast call or exec deck?
At minimum, Claude needs your stage definitions and exit criteria, segment thresholds, forecast category definitions, key metric calculations (ARR, pipeline coverage target), and quota by segment. The cheat sheet includes a full system prompt template in Section 5 that covers all of this — fill it in once, paste it into your Project instructions or API system prompt, and your outputs will be grounded in your actual operating model rather than Claude's assumptions.
How do I know if a Claude-generated pipeline summary or MEDDIC score is actually accurate enough to act on?
Cross-reference at least one specific data point against your Salesforce source of truth before trusting the full output — if one number is off, check them all. For MEDDIC scoring specifically, the output is only as good as the call notes or activity log you pasted in; if the input is thin, the score will be thin. Treat Claude's deal risk assessments as a structured first pass that your managers pressure-test, not a replacement for the review itself.
How often should I be running Claude-assisted pipeline reviews versus setting up automated recurring workflows?
Start with manual Chat or Projects workflows on your existing cadence — weekly pipeline review, bi-weekly forecast call prep — and run them that way until the prompts are dialed in and the output is consistently useful. Once you're getting reliable output from a repeatable prompt, that's the right time to move it into Cowork for scheduled delivery or into the API via n8n or Zapier for full automation. Automating a workflow before you've validated the output quality just means bad analysis runs on a schedule.