16 Free AI Workflows & Prompts for RevOps
Every RevOps leader wants to implement AI. This cheat sheet gives you 16 ready-to-run AI workflows (+ prompts) across 4 areas:
- Revenue Intelligence AI Workflows
- Deal Intelligence AI Workflows
- Pipeline and Forecast AI Workflows
- AI Productivity Workflows
.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
AI foundations for RevOps
- What AI should replace, augment, or leave to humans across the RevOps motion
- The anatomy of a good RevOps prompt: role, context, task, output format, constraints
- Why workflow-mode AI (structured input to structured output) beats search-mode AI for revenue ROI
Revenue intelligence workflows
- Win/loss analysis across closed deals to surface real reasons by segment and competitor
- Live competitive intelligence built from what buyers actually say in deals, not stale battlecards
- Churn signal detection from CS notes, NPS, support data, and usage patterns
Pipeline, forecasting, and coaching workflows
- Deal scoring and MEDDIC compliance checks against call transcripts and CRM data
- Pipeline hygiene scans that flag stale stages, missing fields, and at-risk opportunities
- Forecast scenario planning, rep call coaching, and structured CRM write-back
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
16 AI Workflows for RevOps: Deal Scoring, Forecasting & CRM Hygiene
#114 Running RevOps on AI Workflows & Agents
Free Claude for RevOps Cheat Sheet
Frequently asked questions
What is an AI workflow and how is it different from just asking AI a question?
A one-off question gives you a single answer. An AI workflow is a repeatable structured process: defined trigger, defined input, defined output format, and a defined action that follows. The 16 workflows in this cheat sheet all follow that pattern, which is what makes them production-ready instead of one-time experiments.
Do I need Weflow or any specific tool to run these workflows?
No. The prompts work in any LLM (Claude, ChatGPT, Gemini) and use data you already have in Salesforce, your CI tool, and your CS platform. Weflow makes the data layer cleaner (activity capture, conversation intelligence, AI field updates), which makes the workflows more accurate, but the prompts themselves are tool-agnostic.
Which RevOps tasks should AI replace, augment, or stay human?
Replace repetitive, data-heavy tasks with clear inputs and outputs (pipeline hygiene checks, call summaries, MEDDIC scoring). Augment tasks where AI does the heavy lifting but a human makes the final call (forecast prediction, deal risk flagging, win/loss patterns). Keep human judgment for relationships, accountability, and final forecast commits.
What data do I need to feed these workflows?
It depends on the workflow. Most need a combination of CRM data (deal records, stages, closed-lost reasons), call transcripts, sales notes, and sometimes CS engagement data. Each workflow lists its inputs explicitly so you know exactly what to gather before running it.
How do I know if a prompt is producing good output?
Run each workflow on a small batch first (10 to 20 deals or calls), review the output with sales leadership, and check whether the insights match what your team already knows. If the AI surfaces patterns your reps recognize, the workflow is calibrated. If output feels generic or contradicts ground truth, refine the role, context, or constraints in the prompt.
How often should I run these workflows?
Each workflow lists its recommended trigger. Win/loss runs monthly or quarterly. Competitive intelligence runs monthly, or immediately when a competitor shows up more often in lost deals. Pipeline hygiene runs weekly. Churn signal detection runs monthly. The point is to make them part of an operating cadence, not ad hoc.