Here’s your crash course in prompt engineering for RevOps - no coding required (just vibes).
Prompting isn't just a technical skill - it’s a business lever. Garbage in, garbage out applies just as much to prompts as it does to CRM data. A well-structured prompt can lower costs, increase consistency and drastically improve the accuracy of AI outputs - even on leaner models.
But the #1 challenge? Getting meaningful results, consistently.
“AI is like a very intelligent third grader - it’s brilliant, but needs a lot of direction,” said Jake Obremski.
This messaging aligns closely with our guide on Prompting Best Practices for RevOps Teams, which emphasizes that most teams don’t have a prompting problem - they have a context problem.
“RevOps” means different things in different organizations - and the same goes for prompts. A vague prompt like “analyze this call” won’t cut it.
Instead, add layers of context:
If you’re using tools like Swyft AI, feed in metadata like user roles, team type, close dates and historical patterns to enrich results even further.
💡 Tip: Use job-specific phrasing (“As a RevOps Analyst…”) instead of generic language (“You are a business analyst”) to shape AI behavior.
NoFraud had to train their AI to interpret acronyms and jargon like “CVV” and “chargeback rate” differently across teams. Otherwise, the model would flag normal fraud ops chatter as red flags in customer conversations.\
Start by:
“Most hallucinations are our fault,” said Hannah. “Somewhere in the prompt, we probably contradicted ourselves.”
Don’t just ask AI to “summarize.” Explain what you’ll do with the output:
Jake recommends including output format and business goal directly in the prompt. For example: “Summarize in JSON format for ingestion into Salesforce; goal is to auto-create an opportunity."
Our blog post Can ChatGPT Increase Efficiency for RevOps? shares examples of using prompts to structure executive summaries with target audience and tone specificity.
Here’s your go-to checklist:
“Prompt your AI to review your prompt,” joked Matt. “It’s prompts on prompts on prompts.
AI hallucinations aren’t always a dead-end. They’re often cues that:
Best way to spot them? Ask reps. “My reps are the first to say: ‘WTF is this?’ when something’s off,” said Hannah. “That’s our fastest QA loop.”
Jake recommends tools like Swift that store prompts by use case and allow teams to test them in sandbox environments. You can also:
“Don’t be afraid to start over,” added Hannah. “Sometimes your prompt needs a full reset.”
This session wasn’t just about writing better prompts - it was about using AI more responsibly and effectively in revenue workflows.
Here’s what to remember:
Looking to take your prompting skills from good to great? Start with clarity, context and continuous iteration.
Check out our blog and join the RevOps Co-op community for more tactical deep-dives, expert webinars and AI-powered playbooks for RevOps.