AMA: Payscale VP, GTM Operations & Business Intelligence, Kayvan Dastgheib-Beheshti on Revenue Ops KPIs

TL;DR: An LLM wired into my actual data. In 2026, that is the differentiator. Two years ago I would have said Salesforce, because nothing runs without it. That answer is now table stakes. The tool I cannot operate without today is Claude (or equivalent) connected to the warehouse, Gong, and SFDC, with prompts and workflows built specifically for revenue diagnostics. What it replaces: The week-long deal-review prep cycle. Five minutes against call transcripts and CRM data instead. The "build me a ...Read More

TL;DR: Demand Gen owns generation. RevOps owns the system. When the KPIs overlap, both teams lose accountability. The reason this question keeps coming up is that most companies have built attribution models where marketing and sales can both claim credit for the same pipeline, and neither team owns the underlying definitions. That is a design problem, not a personality problem. What Demand Gen owns: Top-of-funnel volume and channel mix MQL volume and quality Campaign-attributed and influenced p ...Read More

TL;DR: Start from the AOP, work backward to the operational levers RevOps actually controls, and commit only to what the function owns. The mistake I see most often is RevOps committing to revenue outcomes (bookings, NRR, GRR) that the function influences but does not own. That looks accountable on a slide and falls apart at performance review time, because the underlying levers belong to Sales, CS, and Marketing. The process I use: Start with the AOP. Bookings, NRR, GRR, CAC payback. These are ...Read More

TL;DR: The worst KPIs share one trait. You can hit the number and hurt the business. Most RevOps teams inherit a scorecard built by people who confused "we can measure it" with "we should commit to it." Activity and adoption metrics dominate that list because they are easy to count. They are also the metrics most likely to create gaming behavior inside a quarter. The repeat offenders: Activity counts as primary measures. Calls dialed, emails sent, meetings booked without a quality screen. Reward ...Read More

TL;DR: A successful RevOps function ships decisions, not dashboards. AI is changing what "shipping a decision" actually means. The traditional benchmarks for a RevOps leader were forecast accuracy, clean comp plans, healthy pipeline coverage, ARR the CFO trusts, and a CRO who comes to you for diagnosis instead of just reports. Those still matter. What changed in the last 18 months is that hitting those benchmarks no longer differentiates you. It just keeps you employed. The new bar: Self-service ...Read More

TL;DR: There is no comprehensive solution, and the leaders looking for one are usually trying to buy their way out of a process problem. Every two years a new vendor pitches the "RevOps platform" that will replace four other tools. It never works, because the problems RevOps owns are not problems a single suite can solve. The stack is modular by necessity, and the leaders who try to consolidate it into one vendor usually end up paying more for less flexibility. The categories that actually matte ...Read More