RevOps Lab

Welcome to the RevOps Lab - a podcast exploring the art & science of Revenue Operations. Every week, Philipp & Janis host RevOps professionals to discuss best practices and lessons learnt building scalable revenue engines. This show is for everyone interested in processes, tooling, enablement, and strategies to supercharge your GTM play. To find more episodes and resources on scaling your revenue engine, visit getweflow.com/revops

#129 How to build scalable AI agents – with Tiffany Jones, Co-Founder at The Revenue Insiders

Tiffany Jones spent almost nine years scaling sales operations at DocuSign and nearly four years running RevOps, enablement and marketing ops at HackerOne, and now co-founds The Revenue Insiders. She joins Janis to explain why agents on top of messy data just burn budget, and why an AI-first go-to-market engine needs three separate AI layers: inputs, data structure and outputs. Together they dig into forecasting agents, governance and what the shift means for RevOps jobs. Tiffany closes with her unpopular opinion that RevOps is underselling itself and should recommend its own agentic replacement.We cover:Why agents on top of messy data are still garbage in, garbage outHow to align executives on the problem before you deploy an agentWhy forecast agents fail when deal signals live in notes apps, texts, emails and SlackWhy you don't need perfect data, just consistent patternsThe three layers of AI: input capture, data structure and outputsCapturing seller activity in the moment while keeping humans in the loopWhy context matters: the BCC-to-CRM emails that landed nowhereGovernance: keeping sensitive customer data from crossing accountsWhy go-to-market productivity hasn't had its engineering moment yetOutput-layer use cases: conversational deal rooms, loss analysis, board and QBR decksIs RevOps at risk? Why the role gains value but feels more stressful than everRevOps leaders as future CROs, or "chief revenue architects", and centralized AI operationsWhy RevOps should recommend the agentic solutions that replace its own repeatable workLinks:Tiffany Jones: https://www.linkedin.com/in/tiffanyelizabethjones/The Revenue Insiders: https://www.therevenueinsiders.comJanis Zech: https://www.linkedin.com/in/janiszech/Philipp Stelzer: https://www.linkedin.com/in/philippstelzer/WeFlow: https://www.weflow.ai/Community: https://www.weflow.ai/communityRevOps Letter: https://www.weflow.ai/revops-letterChapters:(00:00:00) Intro(00:02:18) Tiffany Jones's path through RevOps(00:04:49) Garbage in, garbage out(00:06:24) Managing the AI-first mandate(00:09:57) Why forecast agents fail(00:12:57) Three layers of AI(00:15:35) Structure and context(00:17:58) Governance and the system of truth(00:20:29) Data leaks and compliance(00:23:41) Why GTM hasn't 2x'd yet(00:25:50) What agents can do on top(00:30:11) Is RevOps at risk?(00:33:31) RevOps and the future CRO(00:36:09) Unpopular opinion: RevOps is underselling

11-16
38:35

#128 How RevOps can use AI to enable 3x AEs – with Jacco van der Kooij, Founder at Winning by Design

Jacco van der Kooij, founder of Winning by Design and author of Revenue Architecture, returns to RevOps Lab to lay out his "10X engineer to 3X seller" model. He joins Janis and Philipp to explain why AI should turn AEs from order takers into full-cycle sellers who prospect, close and expand their own accounts, and why the gap will be decided in the next six months. Together they dig into rollout guardrails, why agents work half-blind without unified data, and a trade-show playbook that books a full agenda before the event starts. Jacco closes with the unpopular opinion that a customer who won't meet you probably won't buy from you.We cover:The 1X, 2X and 3X seller: from AI call summaries to full-cycle ownershipWhich roles shrink: CS absorbed into the product, SDRs splitting into inbound and outboundWhy SDR/AE/CSM specialization was the anomaly and full-cycle selling is a return to normal"You sell it, you own it": why sellers should take on expansionSetting up Claude, ChatGPT or Grok to work 16 more hours a day for each sellerWhy a 250K–300K seller needs to bring in $1–2M when customer retention can't be counted onWhy AI-native companies already run at 3X while SaaS companies will pass through 2X firstWhy inbound is falling at AI-native companies and outbound is backWho owns the 3X rollout: guardrails, controlled rollouts and use-case championsWhy fragmented sales data leaves agents operating half-blindTesting in parallel: A/B/C/D tests across sellers as engineering thinking for salesA trade-show playbook: speakers, LinkedIn likes and ICP mapping to book meetings before the event2X vs. 3X: Uber vs. Waymo, aided vs. autonomousJacco van der Kooij: https://www.linkedin.com/in/jaccovanderkooij/Winning by Design: https://winningbydesign.com/Janis Zech: https://www.linkedin.com/in/janiszech/Philipp Stelzer: https://www.linkedin.com/in/philippstelzer/WeFlow: https://www.weflow.ai/Community: https://www.weflow.ai/communityRevOps Letter: https://www.weflow.ai/revops-letterChapters:(00:00:00) Jacco's return and Winning by Design(00:02:45) The research behind the model(00:05:39) Roles that disappear(00:09:15) The 1X, 2X and 3X seller(00:11:54) Full-cycle selling returns(00:15:48) Why specialization broke(00:18:00) Rolling out 3X safely(00:19:41) Falling inbound, rising outbound(00:24:13) GTM as the moat(00:28:55) Data gaps and parallel testing(00:34:01) The trade-show playbook(00:38:47) RevOps, centralization and urgency(00:42:20) Unpopular opinion: meet your customer

11-09
45:30

#127 How to build an AI-ready GTM org for 2027 – with Lonny Sternberg, VP of RevOps at Veriforce

Lonny Sternberg has spent 13+ years building scalable revenue engines, from zero-to-one startups and a NASDAQ listing to VC- and PE-backed companies at $350M+ scale, and now leads RevOps at Veriforce. He joins Janis to lay out his operating thesis: in the age of AI, clarity beats speed, and clarity comes from a loop of governance, context, systems and rhythm. Together they dig into shared definitions, context capture that doesn't depend on reps updating the CRM, and why change management still decides whether any of it sticks. Lonny closes with his unpopular opinion on why RevOps must be in the room before the decision, not after the cleanup.We cover:Why clarity, not focus or time, is the new bottleneck for RevOpsThe loop system: governance, context, systems and rhythmGovernance as shared definitions, not rules: ARR, ACV, SQL-to-SQO conversion and who owns which numberWhy agents and MCP layers either accelerate a thoughtful process or accelerate a disasterWhen everyone becomes a data analyst with Claude and brings their own metrics to the meetingBuilding the context layer: CRM, first- and third-party data and governance combinedAutomating context capture, because reps shouldn't have to update the CRMSurfacing the right context for the right person: call prep, live calls and objection handlingMeeting ICs where they already work: Slack, Teams, Zoom and emailWhy MEDDIC-style methodologies fail when they feel like extra data entry for repsChange management and enablement that empowers instead of disciplinesRhythm and cadence: backing into the end state instead of ticking weekly checkboxesUnpopular opinion: RevOps belongs in the decision early, not in the cleanup afterwardsLonny Sternberg: https://www.linkedin.com/in/lonnysternberg/Veriforce: https://veriforce.com/Janis Zech: https://www.linkedin.com/in/janiszech/Philipp Stelzer: https://www.linkedin.com/in/philippstelzer/WeFlow: https://www.weflow.ai/Community: https://www.weflow.ai/communityRevOps Letter: https://www.weflow.ai/revops-letterChapters:(00:00:00) Intro(00:01:41) Lonny Sternberg's path through RevOps(00:04:54) Clarity and the loop system(00:06:01) Governance, context, systems, rhythm(00:09:39) Shared definitions and metrics(00:11:30) Agents accelerate clarity or chaos(00:14:48) Building the context layer(00:18:00) Surfacing context by role(00:21:38) Meeting reps where they work(00:23:10) The MEDDIC data-entry trap(00:24:30) Change management and enablement(00:26:03) Rhythm and cadence(00:29:56) Unpopular opinion: RevOps seat at the table(00:31:53) Is the function shifting?

11-02
33:30

#126 Stop Building Agents, Design Workflows Instead – with Ravi Parimi, GTM & RevOps Leader

Ravi Parimi has spent 20+ years in revenue operations and GTM strategy, from AWS, VMware and Cisco to Zendesk and ServiceTitan, plus a stint as executive in residence advising a16z portfolio companies. He joins Janis and Philipp to explain why the agent-first mindset breaks in production and why workflows, not agents, are the unit of design. Together they dig into human-agent handoffs, permission scopes and guardrails, and why RevOps has to run agents like a product after launch. Ravi closes with the unpopular opinion that most teams badly underestimate the operating model change ahead.We cover:- Why an agent-first mindset works for experimenting but fails in production- Workflow as the unit of design: inputs, outputs, people and systems- Lead routing as the test case: account disputes, strategic accounts and other edge cases- Why deterministic rules matter if you want agents without hallucinations- Treating agents as digital workers in the talent mix: what agents do best vs. humans- Autonomy with a scope, like a driver's license- How agent speed changes your org design and the humans in the loop- Running agents like a product: roadmap, workflow v1/v2/v3, benchmarks and release cycles- Agent ops: owning speed, quality, cost and latency after launch- Why agents need sandboxes, testing and security layers before production- Why modern revenue organizations will run as systems of agents and humans- Why solution and field engineering leaders could be tomorrow's CROs- Why judgment and taste become the premium skill when agents give the answersRavi Parimi: https://www.linkedin.com/in/rparimi/ Janis Zech: https://www.linkedin.com/in/janiszech/ Philipp Stelzer: https://www.linkedin.com/in/philippstelzer/ WeFlow: https://www.weflow.ai/ Community: https://www.weflow.ai/community RevOps Letter: https://www.weflow.ai/revops-letter Chapters:(00:03) Ravi Parimi's path through RevOps(02:59) What's wrong with agent-first(06:54) Jobs to be done and lead routing(09:56) Why the workflow mindset is missing(13:54) Agents as digital workers(15:44) Autonomy, scope and permissions(17:13) Rethinking workflows and org design(18:58) Running agents like a product(21:11) Testing, sandboxes and guardrails(24:13) The future of RevOps and the CRO(28:48) Field engineers as future CROs(32:01) Judgment, taste and revenue architecture(34:26) Unpopular opinion: operating model

10-26
39:45

#125 Why Most GTM AI Strategies Fail (and How to Fix It) – with Kelly Lewis & Tiffany Jones, Hosts of The Revenue Insiders

Janis Zech, CEO and founder of WeFlow, joins Kelly Lewis and Tiffany Jones on The Revenue Insiders to explain why AI in go-to-market fails without a clean data foundation. He walks through automated activity capture, AI meeting prep and coaching scorecards on MEDDIC/MEDDPICC, and why accurate forecasts depend on deal intelligence. The hosts push back on critical thinking, business context and vibe coding. Janis leaves listeners with one question for annual planning: are you AI-first or problem-first?We cover:- The three problems behind weak AI results in go-to-market: siloed data, non-selling time and unpredictable quota attainment- Why manual data entry doesn't work and what to automate instead- Design principles for data capture: integrate the signal systems, map everything back to the CRM, stay headless- Why activity has to be mapped to opportunities, not just accounts- AI meeting prep that cuts 15 minutes to 5 and lives in the calendar, Slack or email- Coaching scorecards that auto-populate MEDDIC/MEDDPICC from every email, call and deal room- Automation vs. human in the loop: why reps still need to understand the framework- Why enablement and critical thinking matter more once AI does the data entry- From system of record to system of intelligence to engagement orchestration- Why AI forecasting failed without data pipelines, and how to give CROs multiple forecast numbers- Feeding AI your business context: personas, industries, buying cycles- Mining transcripts and emails for the real close-lost reasons- Why vibe-coding your own GTM stack is slower and costlier than it looksOriginal episode: https://www.therevenueinsiders.com/podcast/episode/39359e05/ai-first-or-problem-first-the-revops-question-for-2027 Kelly Lewis: https://www.linkedin.com/in/kellylewis418 Tiffany Jones: https://www.linkedin.com/in/tiffanyelizabethjonesThe Revenue Insiders: https://www.therevenueinsiders.com Janis Zech: https://www.linkedin.com/in/janiszech Philipp Stelzer: https://www.linkedin.com/in/philippstelzer WeFlow: https://www.weflow.ai Community: https://www.weflow.ai/community RevOps Letter: https://www.weflow.ai/revops-letter Chapters:(00:01) Janis's path to WeFlow(03:43) Three problems in go-to-market(05:48) What's different from Gong and Clari(07:08) Design principles for data capture(12:55) AI coaching on MEDDPICC(15:40) Automation vs. human in the loop(19:45) Enablement in an AI world(23:34) System of intelligence(24:52) Forecasting needs deal intelligence(26:48) Feeding AI your business context(30:58) Mining transcripts for real answers(32:14) Vibe coding vs. long-term partnership(35:07) AI-first or problem-first?

10-12
40:05

Recommend Channels