Show notes
What happens when an AI system moves beyond recommending the next sales action and begins running a connected revenue workflow? In this episode of Tech Talks Daily, I speak with Abhijit Mitra, CEO of Outreach, about the operational work required to turn agentic AI into measurable revenue outcomes. Abhijit argues that adding another AI tool can create extra complexity when customer data remains fragmented and applications cannot share context. The starting point is the business process: what problem is being solved, which data supports it, what agents may do, and where human judgment remains necessary. We discuss the difference between a recommendation and an autonomous action. Revenue teams may begin with supervised spot checks while an agent researches accounts, identifies prospects, drafts messages, and runs targeted campaigns. Once the data and results earn confidence, parts of that process can operate continuously. Multi-step work adds another requirement because the output of one agent must become useful input for the next. Research, outreach, coaching, forecasting, and expansion cannot deliver their full value as isolated tasks. Context runs through the entire conversation. Abhijit describes the customer history, product usage, prior interactions, industry signals, buyer priorities, and organizational memory that can turn a generic model response into a commercially useful action. He says access to a frontier model alone does not create a revenue platform because each business still needs its own context layer and controls. We also discuss Outreach's MCP Server and Client, which allow agents to receive information from surrounding systems and return their work to platforms such as Salesforce Agentforce, OpenAI, Anthropic, and Microsoft. That interoperability creates a governance question. Abhijit's advice is to give an agent the same roles, permissions, and data access as the person or team it supports. If the platform cannot control access at that level, he advises companies to wait. The conversation then turns to the changing software model. Abhijit describes a move from assigning SaaS licenses to employees toward deploying agents with particular skills and a defined capacity. That makes workflow design and measurement increasingly important. He recommends establishing a baseline before rollout and tracking revenue against cost through indicators such as win rate, deal size, quota attainment, pipeline movement, forecast accuracy, and seller productivity. Can revenue teams use agents to remove administrative work while protecting customer trust and keeping relationship building human? Listen to the episode and share your thoughts with me.