If you run RevOps, your job description and your actual job are not always aligned. On paper, you're a strategic partner to the revenue org. In practice, you're fielding Slack messages from five different teams, debugging a validation rule that broke overnight, and triaging a request queue that grows faster than you can clear it.
The headcount to fix this almost never gets approved. You've made the case. Finance said no. So you absorb more, automate what you can, and live with a backlog that would make a project manager cry.
Von connects to your CRM, call recordings, emails, and data warehouse, then spends a few days learning how your business actually works: your field mappings, pipeline definitions, territory logic, fiscal calendar. From there, it handles Salesforce admin work, builds reports, cleans data, documents processes, and answers questions from across the org so they stop landing in your queue. Think of it as the headcount that finally got approved.
Here are the use cases where RevOps leaders are getting the most value today.
1. Salesforce Admin on Demand
A rep can't move a deal to closed-won. A flow is firing when it shouldn't. Someone needs a new field on a page layout. These requests are constant, and they pull you off whatever strategic work you were trying to do.
Von handles Salesforce administration through natural language. It can build flows, create and modify validation rules, spin up custom objects, edit fields, and troubleshoot errors. When a rep hits a wall in Salesforce, Von can diagnose the issue by tracing the validation rule or automation that's blocking the action and explain what needs to change. At SeekNow, Von diagnosed a "closed-won" flow error by identifying the specific validation rule causing the problem. It also reassigned 600 accounts to a new owner with a single command.
Before any changes go live, you review and approve them. Von does the work. You stay in control.
Try: "Why can't my rep move this deal to closed-won? Check which validation rules or automations are blocking the stage change and tell me what's causing the error."
2. Workflow Audit and Consolidation
If you've inherited a Salesforce org, you've inherited someone else's logic. Dozens of flows, process builders, and validation rules built over years by people who are no longer at the company. Most of them are undocumented.
Von audits your entire automation landscape and maps the dependencies between workflows, validation rules, and fields. It identifies which automations overlap, which ones conflict, and which ones can be consolidated. Jesse Meller, Global Head of Enablement and Operations at Canary Technologies, used Von to audit 71 Salesforce workflows and build a consolidation plan that brought them down to 9. Taylor Kelly, Head of RevOps at Tapcart, described using Von to dig through years of history, workflows, and fields to identify the right references and run real-time audits. She put it simply: if you've ever spent time digging through undocumented customizations or trying to figure out which workflow is actually breaking a process, Von handles that.
Try: "Audit all active flows and process builders in our Salesforce org. Map the dependencies between them, flag any that overlap or conflict, and recommend a consolidation plan."
3. The Semantics Layer That Stops Inconsistent Reporting
The CRO asks marketing for a pipeline number. Sales pulls the same number from a different report. The numbers don't match. Someone pings RevOps to figure out which one is right. The answer is usually that both teams defined "open pipeline" differently.
Von solves this with organizational memory. You define your business logic once: what "open pipeline" means, which field represents revenue, how your fiscal calendar works, what "churn" means at your company, how territory assignments map. Von stores those definitions, and everyone who uses Von inherits the same logic. The CRO and a sales manager ask the same pipeline question, they get the same answer.
Try: "Here's how we define open pipeline: stage is Discovery through Negotiation, close date is within the current fiscal quarter, and amount is greater than zero. Store this so everyone gets the same answer when they ask about pipeline."
4. Reports and Dashboards Without the BI Team
The BI team has a six-week queue and Salesforce native reporting can't handle anything complex. So you end up exporting to Excel, building pivot tables, and emailing a spreadsheet that's outdated by the time it arrives.
Von builds live, interactive dashboards from natural language. Describe what you want to see, and Von creates it. These aren't static exports. They're dashboards that pull from your connected data sources, and they cover what one RevOps leader described as the "bottom 80%" of BI use cases. The analyses that don't need a data engineering team but do need more than a Salesforce report. At Bloomreach, the team built a marketing attribution model in Von in a single day that outperformed their dedicated attribution tool, and they subsequently removed it from their stack.
Try: "Build me a dashboard showing pipeline by stage, region, and rep for the current quarter. Include week-over-week movement and flag any deals that changed stage in the last 7 days."
5. Data Hygiene at Scale
Dirty data is a tax on everything RevOps does. Duplicate accounts, contacts without owners, opportunities with blank fields, stale records clogging up reports.
Von scans your CRM and identifies data quality issues: duplicates, records missing critical fields like website or owner, contacts that haven't been touched in a defined window, accounts with conflicting information. Then it prepares the fixes. It can batch-update fields, merge duplicates, and correct integrity errors, all with a human-in-the-loop approval step before any changes hit Salesforce. Steven Turrisi, a GTM and RevOps leader, described cleaning up years of tech debt in a weekend using Von. Tasks that used to take 30 minutes each in Data Loader were batch-corrected in seconds.
Try: "Find all accounts in our Salesforce org that are missing a website, have no owner, or haven't had any activity in the last 180 days. Group them by issue type and prepare a cleanup plan I can review before applying."
6. Territory Planning and Account Assignment
Territory planning is one of those projects that everyone agrees is important and nobody has time to do well. Most teams do it once a year and hope for the best.
Von compresses that process. It pulls historical performance data by territory, models different assignment scenarios against real revenue outcomes, and once you've made a decision, it executes the reassignments in Salesforce. Natalie Love, VP of GTM Strategy and Operations at 15Five, compressed territory planning from weeks into days using Von.
When territories need mid-year adjustments because of rep turnover, market changes, or account growth, Von handles those too without requiring a full replanning cycle.
Try: "Pull revenue by territory for the last four quarters. Show me which territories are overperforming and underperforming relative to the team average, and model what happens if I redistribute the bottom 20% of accounts from Territory A into Territories B and C."
7. Clearing the Request Queue by Enabling Self-Service
A huge portion of the RevOps request queue is questions that people could answer themselves if they had access to the data. "What's my pipeline coverage?" "How many deals closed last month?" "What's our win rate by segment?" These are lookups that happen to require RevOps because nobody else can navigate the data.
When Von is deployed across the revenue org, those questions stop landing in your queue. Sales leaders, AEs, marketing, and CS can ask Von directly and get consistent, auditable answers. Kieran Snaith from Qualified described this dynamic clearly: his team used to be inundated with questions, going from request to request to request. With Von, other departments get those answers on their own, and his team redirects their time to higher-value work.
Every person who starts self-serving through Von is one less ticket in your queue, permanently.
Try: "Set up Von access for our sales leadership team with the following context: our pipeline stages, our fiscal calendar, and our standard definitions for win rate, pipeline coverage, and average deal size. I want them to be able to pull their own numbers without coming to my team."
8. Process Documentation That Doesn't Live in One Person's Head
If you got hit by a bus tomorrow, how much of your Salesforce org's logic would be lost? Most RevOps teams carry critical institutional knowledge in the heads of one or two people. None of it is documented because documenting it is a project that never reaches the top of the priority list.
Von documents your existing Salesforce setup: automations, field dependencies, business rules, permission sets, and the logic behind them. It builds a living reference that anyone on the team can query. When a new RevOps hire joins, they don't have to reverse-engineer the org from scratch. They ask Von. At Qualified, Kieran's team compiled all of the knowledge required for Von to take over recurring tasks, including the cadence, structure, and format of executive readouts. That knowledge now lives in the system instead of in someone's notebook.
Try: "Document all active automation in our Salesforce org. For each flow and validation rule, list what it does, which objects and fields it touches, and any dependencies on other automations."
9. Recurring Reports on Autopilot
Monday morning pipeline reports. Weekly forecast summaries. Monthly board decks. These recurring deliverables eat hours every week, and the format barely changes. The only thing that changes is the numbers.
Von's scheduled commands automate recurring reports and analyses on whatever cadence you set. Define the report once, set the schedule, and Von generates and delivers it automatically. Eric Choronzy, CRO at DemandScience, runs a single prompt every Monday that generates weekly tear sheets for each rep based on individual sales math, account data, and year-over-year comparisons.
The time you used to spend assembling these reports is now time you spend acting on them.
Try: "Every Monday at 8 AM, generate a pipeline summary for each sales team. Include total pipeline by stage, deals that moved forward or backward last week, and any deals with close dates in the current month that have had no activity in the last 7 days. Deliver to Slack."
10. Competitive Pricing Analysis from Call Data
Pricing conversations happen on sales calls every day. Reps hear competitor pricing, packaging objections, and budget constraints in real time. That intelligence almost never makes it back to the people who set pricing strategy because there's no reliable way to extract it from hundreds of call recordings.
Von cross-references structured CRM data with unstructured call recordings to surface pricing intelligence at scale. It can identify which competitors come up most in deals at specific stages, what pricing objections are most common, and where your packaging is creating friction. At Qualified, Kieran's team built an entire competitive intelligence program using Von that their CEO described as delivering what a dedicated competitive analyst had never been able to produce.
Von makes it a recurring output instead of a backlog item.
Try: "Analyze all call recordings from the last quarter where a competitor was mentioned. Group by competitor, show the most common pricing objections and packaging concerns, and compare our win rate in competitive deals versus non-competitive deals."
These use cases all connect to the same reality. RevOps teams are doing critical work with insufficient resources. Von gives RevOps the capacity to do the work that's been sitting in the queue, the work that makes the entire revenue org run better. The time you get back goes straight into the strategic work you were hired to do.
