Good morning. Thank you all for joining us. I'm Valerie Mack. This session marks the fourth in our series of quarterly post-earnings webinars aimed at providing you all with a deep dive on our latest product innovations and strategy. Today, we will deep dive on our agentic enterprise architecture, evolution, and innovation. As you heard earlier this week on our earnings call, our four-system architecture of engagement, agency, work, and context is foundational to how we are helping customers become agentic enterprises. Starting with some housekeeping, some of our comments today may contain forward-looking statements that are subject to risks, uncertainties, and assumptions which could change. Should any of these risks materialize or should our assumptions prove to be incorrect, actual company results or outcomes could differ materially from these forward-looking statements. A description of these risks, uncertainties, and assumptions, and other factors that could affect our financial results or outcomes is included in our SEC filings, including our most recent report on Forms Form 10-K, Form 10-Q, and any other SEC filings. Except as required by law, we do not undertake any responsibility to update these forward-looking statements. Today, I'm really excited to host Muralidhar Krishnaprasad, or MK, our President and Chief CTO of Product Engineering, and Madhav Thattai, our Executive Vice President and GM of Agentforce. We're going to start with a brief presentation and a demo, and then we're going to jump straight into your questions. And I know this is not a shy group, but please do submit your questions in the chat. With that, I'll hand it over to you, MK. All right. Thank you, Val Mack. As you all know, first of all, good morning, and thank you for joining us. As you all know, every company wants to become an agentic enterprise, for us, the definition of an agentic enterprise is where humans and agents drive customer success together that you can get better productivity, higher revenue, and of course, more efficiency in your operations. Next slide. I think the biggest mistake people do is that they just think simply all it is is you just need an LLM to do the work, because raw intelligence is not enterprise work. On the left side, you see the frontier models all ready to go tackle the complex intelligent task, on the right side, you have the enterprise outcomes. Unfortunately, 95% of all these enterprise AI pilots fail because they are not crossing the chasm. These LLMs can't act their own, they are non-deterministic. You can't rely on their outcomes all the time, and they lack business context. Next slide. This is really why the agentic enterprise needs more than models. This is not just us just pontificating, but really through our experience over the last several years, making so many of our customers successful becoming an agentic enterprise. The four things that we really need, starting from the bottom, is a system of context, which can tell you exactly what your data is, what your customers are, what are they doing, so that you have the business context around the operations you want to do. The next is the system of work, where the work actually gets done, whether you're servicing a customer, you're selling to a customer, you're marketing, and so on. You have a system of agency, which is actually doing that, taking that raw intelligence and being able to orchestrate across the system of work, using the context appropriately. Finally, the system of engagement, where you're actually talking to that customer on that right channel, whether it's for employees or for customers. We believe these four is really what takes crosses the chasm from intelligence to business outcomes through an AI-driven model. Next slide. Here in Salesforce, our four layers of context, work, agency, and engagement, we believe we have the industry's only unified stack that can make this possible. Starting from the bottom, of course, we can run on any models, whether it's OpenAI, Anthropic, Gemini, Llama, et cetera. Starting from the bottom, our Data 360 provides that foundational system of context. You can bring all your structured data, unstructured data, in many cases, just zero copy. You can leave the data in their warehouses, but pull them together and really create that singular customer profile, product profile, and others, which can help you give that context of what the users or accounts is doing across your business. We have at, above that is a system of work. We have the most industry's comprehensive, thing related everywhere from marketing, sales, service, operations, analytics, and so on. This is where work gets done. This is where all your business workflows are created as well. As you know, we recently launched our CCaaS and ideas and product line as well to join this. You have the system of agency. This is where the Agentforce customer and employee agents are built. This is the one that is taking the context and then bringing all of the business workflows that are there in Customer 360 together using the power of the LLM models. Finally, the system of engagement is where we have both our channels, with all the channels that we support from WhatsApp, SMS, text, email, and others. More premium channel is with Slack for our employee experiences, particularly with Slackbot and our ability to do enterprise search, and really bringing in all of the power of the visualizations also into the system of engagement. This is how comprehensive our stack is, and they all work together in unison. Next slide. Now, I'll just briefly deep dive at two slides on the context itself and hand over to Madhav. To do that context, you really need data, and this is really where Data 360 comes into play. You can connect to hundreds and hundreds of different sources that's in your enterprise very easily. You can turn any unstructured data, your call transcripts, your notes, your design documents, whatever they may be into both structured data as well as vectorize them so that agents can actually understand and reason over them. Y ou also get memory. All these agents get both short-term and long-term memory, so that when you come back after three months to talk to your business, it can actually quickly pull back what you have done. You also want to bring that quality and clarity, because data quality becomes important. You're putting the reputation of your business on the line by putting the agents in the front, and this is where the data quality and cleansing comes into play. Next slide. Putting this together, the way context works is you see on the left side, you have all of this data and all of these applications sitting there with the power of the Data 360, the MuleSoft, Informatica, and Tableau. You can actually create those MDM records, the unified profiles, create the context engineering around it, where you tie all of this data with the raw data, with the context about what they're doing with the agents, and be able to go analyze it, and then link it back into the system of work. This is how the context layer at the bottom ties in with all your data stores in an enterprise with the system of work that we have across, and then feed it to the agentic layer. Madhav, over to you. Thank you so much, MK, and glad to be with all of you today. MK talked about the system of context. I want to now touch on the system of agency and what we've built with Agentforce. I think you all saw this in our earnings. We talked about the performance of Agentforce in the last 15 months. We're now at an $800 million run rate, up pretty significantly year-over-year. We went from about 3,000 customers to now over 23,000 customers across those 29,000 deals that you see. It's been incredibly encouraging to see customers from all over the world in different industries using Agentforce for many different use cases, some of which we're going to talk to you about today. A couple of things that are really, really important as we think about this. First of all, we see Agentforce uplifting our licensed products, where customers are now using them for premium experiences for employees with our Agentforce for Sales, Agentforce for Service, Agentforce One Edition products. The customer is getting a lot of value on those employee use cases. Of course, there's the consumption business, where these are fully autonomous agents that are facing customers. You've obviously seen the great examples with Williams-Sonoma and others, where we have these agents that are doing kind of end-to-end life cycle work for our customers. Also really encouraging to see that some of those customers now are really at a deep stage of maturity. They are coming back for more credits and more expansive use cases as they start to drive this across their life cycle. Incredibly, incredibly, you know, exciting performance for the product, and, you know, we're really just getting started. Let's go to the next slide. Now, I want to spend a minute on this. We introduced this new metric this week, I know I've talked to some of you already about what it means, but MK made what I think is the most profound and important statement, which is: It is not sufficient to just measure intelligence. We've been talking about intelligence as measured by tokens for a couple of years now, ever since this capability launched. It's really important to understand what's happening at the infrastructure layer. Just like when we, you know, when we talk about the cloud, we want to understand what's happening at the compute layer, at the storage layer, at the networking layer, and we really see tokens as a part of that infrastructure layer. What we care about and what our customers care about is turning that intelligence into work. We introduced this new metric, Agentic Work Unit, which is really comprising all of the work that is being done on our platform with these agentic systems. That could be a decision made by an agent to respond or make a decision and reason through a particular task. It could be the task of actually performing a record update or triggering a workflow, or maybe an API in a third-party system, maybe running a piece of code. We now systematically measure everything that's happening in Agentforce, in Slack, in MuleSoft, and we say, "Okay, let's really understand how are customers getting real work done?" Because that real work is what really tells us that the utility of the product is valuable to the customer. The more they use the product, the more we know it's having an impact on their business. It's early. We're trying to understand, you know, a lot about this metric. We can now look at this metric by product line, we can look at it by customer, we can understand which use case they're using it for, so really, really exciting. We think that the moment has come to move from a simple measure of intelligence, which is an input, into what is the output and the actual work getting done. If you go to the next slide. And here are some examples. These are some of our incredible customers, we talked about some of these at earnings as well, that are really doing a lot of work at scale. And you can see the variety of different use cases, and that's really what jumps out on this slide. We have customers like Agibank, recently went public in Latin America. They are using this agent externally, facing their customers. Every time a customer comes back to ask about loan status, to understand what their next steps are, they are directly interacting with this agent. A great customer, like Bouygues, in Europe, they have their agent that they call Iris, which is helping their employees, and it's helping their employees with fairly complex tasks across all of the things that their employees need to do to really drive that internal productivity. ADP is a great customer. They're actually using an agent internal to their company that's helping them with HR workflows. This isn't even in just sales and marketing and so on, this is actually expanding what they think Agentforce can be used for. Of course, General Motors is using task-based agentic automation. This is, I have very specific tasks that I need to go accomplish. These tasks are in the flow of work. They are where my employees are working, in Salesforce, in Slack, and that automation is driving a lot of productivity. That's really been encouraging because we see customers that are experimenting with a variety of use cases: pure employee productivity, employee assistance with more complex agents, and then, of course, really the important use cases, which is we now feel confident enough in this agentic technology that we're gonna have our customers interact with this agent. That's been really, really encouraging to see, and a lot more to come with all of these customers that are really starting to add more use cases. Let's go to the next slide. This is really the bottom line here. There has been a tremendous amount of energy around building. We can vibe code, we can accelerate the deployment of software, we are significant users on MK's team and across all of our engineering teams, where we believe that this technology is accelerating our ability to build, and that is remarkable. However, there isn't an enterprise in the world that wants to vibe operate. The build is the first part of this journey, and we have really worked over the last couple of decades with our customers to help them run their business. Now, to run your business, after you build, you need to understand: how do you wanna test the capability? Is it working? How do you evaluate it? How do you observe it? Is it driving your KPIs? Is it driving your outcomes? How do we continuously optimize? That is where the fact that we are so deeply embedded with our customers, the fact that their most valuable work, which is how they interact with their own customers, happens on Salesforce, really gives us a deep understanding of how we take the best of this intelligence technology, turn it into remarkable experiences, but then importantly, help businesses operate and manage that capability. I'm gonna stop there. Let's go to the next slide, because rather than just talk theory, we actually wanna just take a few minutes and just show you how the product works end to end, and for that, we're gonna bring in, the incredible Gabe Sumner to walk us through a quick demo of what this experience actually looks like. Thank you so much, Madhav. What are we looking at here? What we're looking at is the type of agent that we are helping our customers create, which is essentially an agent that represents the brand. As Madhav and MK just talked about, for it to do that reliably, it's gotta be grounded in those four systems: engagement, agency, work, and context. Let's just start with context. If I just give this agent an instruction, "I need to reschedule my flight," we know that to do this job reliably, to answer that question, the agent has gotta be grounded in that enterprise context that Madhav or that MK talked about. It's gotta know who the customer is. It's gotta know what their flight was. It has to know what an appropriate replacement flight might be. Customers also wanna take these agents a step further. We want the agents to take action on the brand's behalf, and that means you need to give the agent some level of agency to respond flexibly across a whole spectrum of requests that the agent might get, while always adhering to your business rules. If we're going to transform all those customer experiences with agents, we need these agents to engage across all the different channels where customers are, which is going to include mobile, but extends all the way out to voice and your 800 number with those CCaaS systems that MK talked about earlier. If the agent needs to escalate to a human, it means the agents have to work where your employees work, which means supporting seamless handoffs between the agent to employees inside the work systems where they are using to work and collaborate. As MK and Madhav just talked about, we are the only agentic platform that brings together these four systems. Let's take a little bit of a deeper dive to explore exactly how that happens. This is Agentforce Builder. This is where our customers define their agents. Agents are defined with topics. You can think of these as essentially the jobs the agent is allowed to do. Behind each of these topics is essentially a little sub-agent that is comprised of both instructions and actions. If we were to go into instructions, like, these are the guardrails that you create that guide the agent's behavior. Because we've introduced this new scripting language, Agentforce Script, we are able to blend this kind of like deterministic logic, your business rules, with natural language kind of instructions, and that is what gives Agentforce this kind of the agency to adapt while always kind of adhering to your business rules. Now, there's also, these agents are comprised of actions, and you can kind of think of these as the tools that we've equipped Agentforce with to actually do all of this work. What would that work be? Well, it can be things like, retrieving data from Salesforce or outside Salesforce with Data Cloud. It can also be executing your business workflows. It could also be even using those MCP tools from kind of the open ecosystem that we participate in. Gabe, let Yeah. Let's pause here for a second. Yeah, sure. This is really important. What Gabe is showing you is how the agent gets built. When you think about how the agent gets built, he said some really, really critical things. These are kind of the core and most important innovations that we brought in. Number one, tying in that context directly so that the agent is leveraging all of that enterprise data that is connected into Salesforce. You don't have to build extra data connections. You don't have to move data around. It is seamlessly integrated into that data. That was one point that he made that is really, really critical. The second thing that's really important is, one of our biggest learnings in the agentic enterprise has been this need for deterministic control. These aren't just agents that are answering simple questions. These are agents that are executing on work. How do you make sure you are tying that deterministic ability into the Agent build is really critical. Really importantly, those business workflows sit in Salesforce today. MK brought this up before when he called it the system of work. Tying it back into the work and the process that is happening is what allows customers to not have to recreate process in order to roll out these agents. That's a really important way in which these agentic deployments can go a lot faster and a lot easier. Go ahead, Gabe. Yeah, absolutely correct. Then as we move forward, we've talked about all the different engagement channels, so this would be where you extend Agentforce to all those channels where your employees and customers are. Then if we go down here to the very bottom, and I'm sorry, Zoom is in my way here, but you have data, which allows it to be grounded in that unstructured data, like those knowledge articles. Honestly, the way to kinda like see all of this come together, I find, is just, like, go test the agent and see how Agentforce actually goes and does a job. This is the simulator inside of Agentforce Builder that we can use to kinda see how the agents work or how Agentforce works. I'm just gonna ask it to find a flight from Seattle to JFK. Like, what is happening right now is Agentforce is kinda using that agency that we granted it to flexibly understand the intent, to make a plan, to ground itself in all that right enterprise context, to execute the actions in adherence with our business rules, until finally it surfaces the right answer. Not just, like, surfaces the right answer, but explains the reasoning that it used to produce that answer. We've given our customers the tools to really dig deep into all of this and just really look at all the individual details that were used to create this reasoning. You know, Madhav talked a little bit about the vibe coding experience. Like, we're trying to bring that vibe coding experience into the enterprise. If you notice problems with any of this execution, you can just ask Agentforce to fix it, and instead of, like, it generating a bunch of ad hoc code that you have to then maintain yourself, it's generating kind of metadata that sits on top of an enterprise-grade platform. That's how we help our customers get their agents ready for deployment. Of course, one test never enough for these non-deterministic solutions, which is why we also have Testing Center, which uses AI to generate hundreds, if not thousands, of AI-generated test scenarios, so that we can just test a whole spectrum of things that different ways that customers might ask the agent to do different things, to make sure that the agent is performing as you expect across all of those different simulations. Long after deployment, we're giving our customers the tools to understand how their agents are doing against the backdrop of all their business KPIs, so they understand the value that agents are bringing to their business. We're also not only helping them understand how agents are doing, but also what the agents are doing. You can drill down into this, get visibility across different topics, and even highlight things that the agent could be doing better, and zoom all the way down into individual interactions to really see how an agent is doing an individual job, look at everything that's being done to do that job, interrogate it, troubleshoot it, and that becomes that kind of flywheel that just makes the agent better and better and better. This is how we're bringing together those four systems that MK and Madhav just talked about, to convert that raw intelligence of these frontier models into trusted enterprise work. Madhav, I'll give it back to you. Thank you so much, Gabe. Really appreciate it. Let's go back to the slides, 'cause we wanna show you a little bit of how we think about the stack. We know this question is gonna come up, we thought we would just address this head-on. You've probably seen here in the last couple of weeks a lot of announcements from the frontier model companies about their enterprise agentic stack. Let me start with saying this, these are companies that we deeply partner with, both OpenAI, Anthropic, the other model companies, the hyperscalers. We are very close partners in really building this technology and bringing it to customers. Secondly, these companies are also customers of ours. We also work really, really closely together to make sure that they are being successful as they're building these remarkable companies with this remarkable technology that is genuinely, you know, changing the world and changing the enterprise. There's some important takeaways here when you think about what the frontier companies are saying about the enterprise business. If you go to the next slide, we kind of broke this down a little bit to map it to how we think about our stack. Let's just start with frontier. We are in deep agreement with OpenAI that context really matters. As Gabe showed you, the workflows really matter. Where your employees are working and how they are working is really, really critical. You need a system of agents across all of these important surfaces in order to go deliver this, deliver this capability out to the enterprise. That is really good validation of the things that we have said for a couple of years, the bottom line being the model layer alone, which by the way, isn't really represented anywhere on the stack, but the model layer alone is insufficient to make sure that that intelligence is being turned into work. In fact, we also were encouraged to see, you know, that OpenAI is partnering with many of the big system integrators that we work very closely with as well, Accenture, Deloitte, and McKinsey, and others, because that implementation is really critical. Turning this into operation is really critical. This is a deep and important validation of our understanding of how these things actually get turned into real work. Anthropic, of course, has also been talking about their enterprise strategy. They had an event, you know, earlier this week, where they talked about their strategy. You kind of see how these experiences that Gabe talked about, the employee experience that we think of in Slack- these prompt and automation workflows that we've now been doing for a couple of years with our customers, and then, of course, these agents that are gonna be building truly autonomous capabilities are really critical. It's interesting, in one of the main demonstrations that they showed, the experience began in Slack. A group of people were talking about how do they improve a decision that they needed to make, but the immediate next step was someone needed to leave Slack and move to a different UX in order to go execute a task. They had to take that task, bring it back to Slack in order for the decision to get made. Now, we don't believe that's the right experience for users. We think all of those things have to happen in one place, and of course, we're deeply partnering with Anthropic to make sure that customers do not have to leave their flow of work in order to bring all of that intelligence and that capability. A deep validation of the things that I think we've been saying for a while as we have built this comprehensive stack, that MK talked to you about before. Let's go to the next slide. This is now a view of our system of agency. We touched on each of these things, so I'm not gonna really get into, repeat the detail that we just talked about, but a lot of deep innovation at every layer. This innovation is not limited to Agentforce. Gabe showed you the operating layer today, where we optimize, we analyze. Well, that layer is built with Tableau. When we think about the orchestration layer, an agentic system where agents are talking to each other, we are very closely tied with our MuleSoft technology to extend that across the enterprise. Of course, at the context layer, we're making sure that we're tying in with Data Cloud, with Informatica, for all of the reasons that MK said, to really surface up all of those capabilities. When you think about the experience layer, this is the work with our applications teams to really make sure this intelligence is surfaced for employees. It's working with Slack, so you're in the system of engagement. It's working with all our channels, like voice and chat and WhatsApp, to make sure these agents are surfaced in those channels. It's a really critical strategy for us to bring these unified capabilities to our customers, but really importantly, we are unified, but not locked in. We know we live in a heterogeneous environment, that customers in the enterprise will wanna connect a lot of technologies at every single layer. The open side of this equation really, really matters. Openness at the data layer, the ability to orchestrate across all of these systems, the ability to share telemetry and data so that customers can do the analysis that they need. The ability to really connect across all the interfaces. It could be Microsoft, it could be Apple, it could be whatever interface a customer really wants to use, and make sure that our agents are able to surface up in those interfaces. That's really the strategy and what we've done. If you go to the next slide. Really importantly, a strategy and a set of slides and a set of demos and blog posts are really not the business that we are in. The business that we are in is to be really deep in the trenches with our customers, really making sure this technology is making them successful. It's been a real privilege to work with some of the biggest companies in the world, as I said, across industries and across use cases, so we can really understand how this technology can create value in a number of different scenarios. I won't drain the slide. I'm happy to, you know, talk about some customer examples in Q&A, but each of these customers has helped us drive a critical innovation in the product. Working with Williams-Sonoma really helped us understand, how do we tie that context layer together to create an incredibly rich experience? If you haven't played with it, you should go to Williams-Sonoma's website. This is an agent that's helping you not just discover Williams-Sonoma's products, but really create experiences in your life. It starts from that in order to go in and then make product recommendations and actually think about what products customers want, and then customer service. Well, tying all that together requires a tremendous amount of context. Adecco is an incredible customer of ours. In fact, they just yesterday launched a brand-new voice experience for their candidates. Adecco uses us to do what is, you know, their most important business process, which is qualifying candidates in order to match them to jobs. That process is a perfect example of why LLMs and determinism have to come together. You want to use LLMs to create this rich experience for the candidates. It's flexible, it can ask them questions, it's empathetic to where these humans are. A qualification process has 30 steps. You wanna make sure every single step is followed. If you just handed that off to an LLM, it is not gonna execute consistently and accurately across all of those things. Equinox. Equinox really helped push the boundary on, how do you create rich experiences with this technology? This isn't just a bot that you put on a website. You wanna have rich information, you wanna have rich content, you wanna have interactability, you wanna have flexibility in how the agent actually plays out. It's really been incredible to partner with these customers as they're pushing the boundaries of how this agentic technology is gonna be used. What I wanna do next is hand it back to MK. He's gonna give us a little bit of view of where is this technology going? What does the future really look like? MK, over to you. Thanks. Thanks, Madhav. I think what you saw in even Gabe's demo is a hint of where agents are gonna be calling other agents, the super agent, as we call it, right? Every customer of ours wants a single brand agent that coordinates work across everything else. Because when you go to Salesforce.com, you're not going there just with an intent of just asking a service question. You might wanna go to sales, you might wanna go to marketing, and so on. The Williams-Sonoma is a good example, where you may be asking about the sous chef agent about some recipes, and then move on to going purchasing things. Super agent becomes an important thing. We believe 2026 is the year that every company and brand will choose a super agent and be ready for it. On the consumer side, with Agentforce, we have the super agents that can go talking to other agents or let other agents talk, call into us. Next slide. Even more interesting on the employee side, is where we believe Slack is gonna play a huge role in the system of engagement and super agents for employees. Next slide. That comes with Slackbot. If you have not tried Slackbot, you must try it today. Slackbot is a perfect example of how the context that's in Slack, where all our work gets done uses the power then of our AI tools to be able to go bring that right thing at your fingertips, and it's able to go orchestrate, not just across all your data in your enterprise, but across all your agents as well to get your task done. As you can see here, we've already seen huge success with Slackbot. In fact, we heard from many, many customers where if their Slackbot was turned off, they literally said, "We can't work anymore." It's become such an important ingredient in just a few months since it's been released. That is how we believe, both at the consumer side with our Agentforce super agents, on the employee side with our Slackbot and Slack super agents, we're gonna really bring the power of agents talking to agents to your fingertips. I think that's the end, correct? I think. Yep. With that, thank you all, and we're ready for your questions. Awesome. Thank you so much, Madhav and MK. We are going to jump into Q&A now. As a reminder, please do submit your questions via the Q&A feature in the Zoom channel. To start here, we have a question that we've been getting pretty regularly from investors this week. You know, people are really excited to see the Agentforce momentum, the $800 million ARR, the strong growth, but people really wanna understand what the long-term ARR ceiling or long-term growth rate assumptions are when we think about our path to our fiscal year 2030 revenue target. Maybe I could start and then pass it over to Madhav. I think first just what we're really excited about with that $63 billion, you know, we have incorporated Informatica, of course, but it also takes into account the net new AOV performance we've had over the last few quarters. And when we gave you the update at Investor Day on how we see the slope of the curve into the back half of this coming fiscal year, that's what really gave us a lot of conviction, is we're seeing this broader adoption motion that's Agentforce, but also let me go deeper on my core apps. Let me go deeper with my products with Salesforce and really driving a broader set of adoption than just, you know, Agentforce over here and the rest of the business over here. Maybe, Madhav, you can help bring that to life in the conversations you're having. Yeah, I think it's important for us for everyone to get an understanding of how we go to market and what the monetization strategy looks like. When you think about Agentforce, you can think of three key ways in which we bring this capability to market. Number one, as Val mentioned, we sell products that create premium experiences for employees. This is a licensed business. This is an upsell, uplift business, and we have products that are add-ons to our cloud, so we call them Agentforce for Sales, Agentforce for Service. We have all of these products for the industries as well. We've got the most premium Agentforce One Edition, and those are, you know, 50%-70% uplift on a per-seat basis. These products are really ensuring that in employee scenarios, we're driving that productivity. We're driving the agency that customers really have, for all of those kind of employee use cases. That's a really significant part of the business. Half of the ARR really comes from that license uplift business, and we're continuing to see expansion and growth, a remarkable trajectory. We just launched that product in the middle of last year, and remarkable momentum there. That's one type. The second type that's really critical is the consumption business, what Gabe showed you is an example of an external-facing agent that is doing a lot of complex tasks. In many cases, those tasks cut across marketing and commerce and service. These are agents that are truly autonomous, creating new types of experiences. We sell that as a consumption business. That business also has grown really significantly, significant ARR on that business. That gives customers the ability to really build these flexible multi-use case agents. There's also a lot of value. You imagine an agent that is now acting as the front door, as MK said, as we build towards these, you know, super agents in the future. That is a remarkably valuable experience from a customer perspective and something that we expect, you know, we will also be able to generate a lot of value from. That's the second model. The third model for some of our customers that really go end-to-end with us is this new Agentforce enterprise-level agreement, those agreements are really looking holistically across a customer. They're thinking about the licenses and the seats. They're thinking about what are the consumption agentic use cases. How is this customer gonna use Data Cloud? How do we integrate across their enterprise with MuleSoft? How do we bring the power of our analytics with Tableau? A comprehensive really at the transformation level, and that we introduced, you know, not that long ago, and we have a lot of customers and great momentum on that front as well. That's really how you should think about, you know, the three monetization models. As Val said, we expect uplift in all of those things. Today we report Agentforce as kind of a sum of those things, and we will continue to do that. We expect Agentforce to really penetrate and uplift all of those businesses, and so far, we're really seeing a lot of expansion in each of those buying models. Yes, the next question here is one that I think kinda ties very closely to this question, when we think about the longer term, you know, obviously we had a record quarter with RPO $72.4 billion in Q4 of FY 2026, but how do we think about the trade-off, as you mentioned, between seat licenses, agentic enterprise license agreements, and the flexible consumption credits, especially in the context of potentially reducing seats, right? I think everyone saw some of the news that came out yesterday. How do you think about that? How do you think about the growth in Agentic Work Units with that as the backdrop? Yeah, maybe Val, you could start with some of what we shared at Investor Day. Absolutely. on how we think about the expansion on a per customer basis, 'cause I think that'll be useful. Yeah, I think just to remind everyone, when we think about the overall wallet share expansion opportunity that we have with our customer base, if we are able to address the agentic enterprise opportunity with these customers, it's not just a, you know, incremental add-on type agreement, right? When we're going live with products like Agentforce Data 360, we're not only getting this motion of customers more willing to go deeper on their current applications, whether it's in Service Cloud, they want to add on field service because they want the plug-in, the tie-in, the agentic experience to be able to plug in across that use case, or they're willing to go from just a Sales Cloud, Service Cloud experience to add on Tableau, Slack, because now they have confidence in the ability for these agentic capabilities to lift all of those products and the underlying context to get a lot of value from all these different touch points. That, for us, when we've seen customers who have gone live early, we've actually seen a significant uplift that goes beyond 20%-30% growth. It goes two to three to 4X of an overall spend expansion. When we're trying to address this opportunity, we're really trying to address three things. First, of course, we want consumption. We want to ensure that we get high-value consumption. Agentic Work Units is a really good measure of that, and Madhav, you can touch on that. The second is, we want to have a lot of value in the seats that they have today. We still see seats expanding, right? Across Sales Service, Slack, there's still growth that we're seeing today. Longer term, that might change, but I think a motion that's been really exciting for us is these bundled SKUs, Einstein 1 Edition, the more premium seats, where they're actually increasing their ARPU. To translate to that, to customer terms, they're getting more value out of that existing seat and are willing to pay more for that seat base. The third piece is really around that data and context, right? We just brought Informatica into the fold. It's been a great first quarter for us with that asset, but now with Informatica, MuleSoft, Data 360, Tableau, all these assets together really give us a broad scope to be able to address the context data needs that our customers have. That gives us a lot of confidence in that 3-4x kind of expansion opportunity that we shared at. Let's build on what Val Mack just said. I mean, seven of our top 10 deals saw this kind of motion. This isn't the same as, you know, "I have one more app I'm gonna add, and that's gonna give me 10%, 20% uplift." This is now, "I'm gonna reimagine what my enterprise experience is gonna be," that is a 2x and a 3x, and so on. When we really think about that, the right question that we've been really thinking about and that we talked about a little bit at earnings as well, is every one of our customers is gonna be on this journey of becoming an agentic enterprise. The really key question for us is: how do we make sure that Salesforce is clearly and obviously the partner for our customers as they think about completely changing their customer experience? We've had very encouraging growth on that front. We started with, you know, 3,000 Agentforce customers. We're now up to 23,000 Agentforce customers, the rate at which we are penetrating our customer base is really significant. We've added a lot of new customers along the way as well. That penetration of, "Let's go help our customers transform into these agentic enterprises," is really the key. That's on the employee side, that's on the data side, and that's on these very, you know, significant, orchestrated super agents as well, those types of use cases that we're driving. To measure the work of those agents is really where we think about Agentic Work Units. MK, maybe this is something that you could, you could, help talk about a little bit as well. We really want to move from just measuring pure input consumption, like tokens, into output. MK, would love your thoughts on the Agentic Work Units and how you think about that for our customers. Yeah, sounds good. First, let me add one more thing to what you guys said. It kind of dives into the Agentic Work Unit. If you take that sales engagement SDR Agent, what it's able to do today is really go bring in more customers that we would probably never have even looked at before, leads and opportunities. Like, for example, even within Salesforce, like, almost 90% of the folks who come to our website and others is too small for anyone to actually go have a meaningful conversation with them. With our sales agent, it actually starts engaging with them, knows what they're doing, and then it brings them up either to schedule a meeting with a salesperson or to actually close the deal. That is an example where it's actually gonna cost more seats to like, more humans to be used to kind of create more sales, grow the top of the top line. Coming back, one of the challenges we saw was just looking at raw token usage doesn't give you the full picture. That's just, "Okay, we are gonna have 1 billion, somebody else is gonna have 1 billion. So on." With this new Agentic Work Unit, what we're able to say is, it's not just about the tokens, it's also about the work that is happening within that business. In the case of sales, it would include the workflow that's needed to go call and create the lead, as an example. In the case of service, it's the work done to actually go understand that user's intent and then go close the case or, like, create incidents, and so on and so forth. Each one of those, the Agentic Work Unit will capture that math of what is the actual work done in that system of context or in the system of work, so that we can give a more comprehensive thing of how AI is actually helping your enterprise. This is really important because we believe the agentic business needs a canonical metric where we are showing that valuable work is getting done. When we measure AWUs, that is not internal use of Agentic Work Units, that's not trial use of Agentic Work Units, that's not even the use of Agentic Work Units when customers are testing, which is super valuable, by the way. We want to hold ourselves and this industry to the standard of: Is real work happening in production? I think having a canonical metric that can measure that is really, really important for us to understand how we're creating value with our customers. To Madhav's point, we welcome the rest of the industry to join us in this effort so that we can actually have some common metric across the industry to represent how work is actually getting done. Awesome. Our next question, I'm gonna combine two questions with into one. Matt VanVliet from Cantor Fitzgerald is asking about super agents. Are they gonna have different monetization elements to encourage uptake? I'm also gonna pull in a question that's tied to super agents and multi-agent orchestration. Specifically, if you're bringing in a third-party agent, how are you thinking about the data ontology? Do you have a layer that would help you understand and map the data across different systems? Maybe that second part can go to MK, and the first part can go to Madhav. Yeah, absolutely. You know, I mentioned the different monetization models that we had. I think another really important point here is we have really learned over the last year, just as we've innovated on the product, and you saw some of the incredible capabilities that we've built already and some of the things that are coming, we've also really innovated on the go-to-market and the pricing motion. I think where we are is making sure that customers have flexibility and making sure that we're meeting customers where they are, where they are in the journey. If what they want is a model where they are still thinking about productivity in their employee use cases, great, let's make sure that we have offerings and we have licenses that they can buy, that they can leverage all this capability. If they wanna move to these more complex agents that they're building, including super agents in the future, let's move them to a more consumption model so they can really understand the real specific work that that agent is accomplishing, and the monetization model is tied to that. That same argument is gonna apply in the case of super agents. When you think about super agents, there are gonna be actions that are executed across these agents, either within Agentforce or into external systems. We will absolutely think about how we monetize those actions as we do today. They're also gonna be pulling in things at the data layer, that data layer will all be monetized with the way we think about our credits, our data layer monetization. It's very likely in those super agent systems, they are going to be tying across the enterprise, so they have governance, so they have observability, so they have control, which means our MuleSoft capabilities will also be involved. You've probably noticed over time, we're really moving towards a model where all of our consumptive products are on our single Flex Credit system. It's fungible, it's movable across all these capabilities, and we make it as easy as possible for customers to say, "I need the agentic capability, I need the data capability, I need the analytics capability, I need the fabric and the governance across my enterprise. I can get all that with one mechanism with which I wanna buy." That's really what the super agents are gonna represent. They don't represent just Agentforce, they really represent that full unified stack that MK talked about to give customers the ability to take advantage of it. Mm. MK, do you wanna talk about the data side? Yeah, I think that you've sort of raised it very, very well. One of the things that I think you saw in one of the earlier Madhav's slide is, for us, extensibility and working with your enterprise is a very, very critical part at every level of our stack, right? From the model layer, to the data layer, to the agency layer, work layer, and so on. We are extending that same thing to multi-agents as well. The question specifically was around context, and this we all know, right? Even humans, when we get transferred from one operator to the other, we have to go repeat all the context back again to saying what my problem is, and so we wanna avoid that. To that extent, the Data 360 layer that is creating the context with our Agentforce has open APIs through REST APIs, MCP, JDBC, et cetera, that all the other agents can also leverage. So when there is an agent-to-agent handoff, there is no loss in context or translation. So that's one. Second, to Madhav's point earlier, as these agents are running, if you're using our Agent Fabric, all the logs across those agents are also gonna come back into Data 360 and surface through our Agentforce Studio. So that means you can actually understand how the lineage is working, how these agents are calling, and actually start optimizing as well, and that helps into that circular loop that we can actually do to go optimize your agentic enterprise. The short answer is, our data layer can help you go across these agents and to also grab all the logs. Our MuleSoft layer can help you govern and monitor these agents, and our Agentforce Studio layer can actually help you go optimize them through our analytics. Awesome. The next one here comes from an investor who's wondering about the maximum margin impact Agentforce can have on gross margins. Let me start, and then, Madhav Thattai, you can jump in on some of the things we're doing to optimize. First, we, of course, have a product portfolio that's pretty broad and diverse, and as we launch new products, we always are looking to long-term optimize what the gross margin structure looks like. Our expectations that we've been clear with investors about is we expect to maintain our gross margin structure. We have some things working through this year. As we invest in Hyperforce, we invest more in third party. That longer term, we actually expect some efficiency on the gross margin side. Importantly, when we think about the construct from monetization through to optimization, the monetization side captures more than just sort of pass-through cost for LLM. As you've seen today, there's so much more in that overall agentic enterprise architecture that needs to be right, that needs to be working in order for these to scale, to be reliable, and to be really successful for our customers, and that includes much more than just kind of a pass-through cost. I'd say when companies are out there saying, "Oh, we're worried about LLM pressure and that impact," you know, there's a lot more that we're doing than just sort of a pass-through. The second side of how we're thinking about optimizing is we can view the kind of margin by customer view of when early adopters launch, how that scales and ramps through time, how we adopt things like hybrid reasoning, determinism, the Testing Center that you saw us show in demo. There are a lot of ways that we can optimize, fine-tune, and then, of course, importantly, we're able to leverage a lot of different models in that architecture to be able to use the right model for the right task, to be able to leverage some of that efficiency. Maybe you can touch on some of that. Yeah, absolutely. Look, efficiency at the infrastructure layer is something that we do every single day, and that applies to compute, it applies to storage, it certainly applies to the use of tokens in the model layer. This is the newest kind of infrastructure, and the newest kind of swappable infrastructure, especially as we have model choice with customers, that we will continue to leverage how we are efficient at that infrastructure layer. There's a really important point here that I think ties back to the Agentic Work Units. What the Agentic Work Units allow us to do now is they allow us to compare the work being done with the infrastructure supply, in this case, the inference capability and the intelligence capability measured by tokens that are going into those work units. Over time, we can understand which kinds of work are leveraging how many tokens over time. There are probably some kinds of work where as we build richer and more complex experiences, the amount of tokens go up for a little while, and then we plateau as we start to think about it. There's other kinds of work, We talked about this earlier, as reasoning becomes more deterministic, as we're not relying on LLMs for complex task execution, the number of times we have to use an LLM in that reasoning will drop. We now have the ability to say for those kinds of work units, are we driving efficiency from a system design perspective, from an agent construction perspective? This really allows us to kind of dial in the amount of infrastructure costs we are spending for the work that's delivered. Now, this is not different from what we used to do, you know, with regular compute technology and regular storage technology, but now we're going to be able to do the same thing with this new model technology. We also fully expect, just as happened on the infrastructure layer, in the model layer as well, there's going to be continued improvements, efficiency, lowering of cost in these models as they continue to get more commoditized. We're already seeing some of that, and we expect that trend to continue in the future as well. Great. Our next question is about MCP. Now that MCP allows external AI agents to interface directly with enterprise data, how do you prevent other companies, foundational model companies, from eventually bypassing Agentforce entirely and utilizing their own agent orchestration capabilities, as those are getting better and are maturing? How do you prevent that from happening? I think that, I think even before agents were in play, we were an open company. We shared all our data, yet people are still coming to us for doing all of the data processing for all their work needs. Same thing here. We still had all our APIs open. Anybody could have built an agent or outside us. Truth be told, a lot of customers did try it two, three years ago when LLMs came out. They said: "Oh, all I need is just an LLM, and I'll just give all the APIs and things will just work." Gabe showed the demo and others, and we showcased it. What we have is really an understanding of the business over the last 20, 30 years. What our customers have done is really build those business workflows, business data context, and metadata, and all of those. To really get your business successful, it's not just that data context or just the raw data, it's really everything that goes on top of it, including your system of work, your agency, all of the hybrid reasoning, everything that we talked about, and the context that gets built. It's not just raw data, it's really the context that you need to go build as well. That's kind of why we are very, very confident that people need that stack that we talked about to get real business success. You know, we touched on this when we showed a little bit of, yeah, what the model companies had talked about earlier as well. There is no question the context layer is incredibly critical. There is no question that the business process and the workflow layer is incredibly critical. There is no question that the interface where a customer engages with a company, where employees work, is really critical. These experiences are not just unlocked by connecting up a bunch of MCPs together. It sounds easy in theory, but the experience really matters, the efficiency matters, the accuracy matters, the latency matters. These are implementation decisions that are really, really important, that can be kind of talked about in a theoretical way of, well, you can hook up any two things together and get them to work, but that's not actually how CIOs and companies implement things. How efficient and how well these systems work really does matter. By the way, you know, our partners at the model companies really agree with us, on this point. The question that you should be asking yourself is: Are customers going to recreate all that from scratch? An entirely new stack to maintain, an entirely new stack to absorb, an entirely new stack that, yes, you vibe coded, but now you have to vibe operate over the next several years. Are you going to recreate where your employees are working when they are actually getting incredibly productive work done today on surfaces like Slack? Are you going to recreate every single business process that you have spent years and years really honing in sales, and commerce, and marketing, and service? That is where we believe the real work gets done. Capabilities like MCP are going to be incredibly impactful. We're going to be tying those to agents outside of Salesforce. Agents outside of Salesforce are going to be tying into us, using all of that, and those are important building blocks. A building block is not an architecture, and it's not an implementation, and that's really what we're focused on. Great. Our next question is on Tableau. Specifically, is there any competitive threats or challenges with LLMs and agentic analytics that you're seeing today? Obviously, Tableau had a weaker performance in Q4. What is happening there if that's not the case? MK, do you want to start? Yeah, I can start there. I think one of the big things, Tableau as well. With Tableau, I think it's subtly different. The agentic analytics is where sort of analytics itself is going, and you want to get the answers right. This cannot be a hallucinated answer, like if Mark wants to say: "Hey, what's going to be my quarter next year, and what's your thing?" It can't just say it could be 80%, it could be 50%, it could be 30%, right? You need precise answers, and that's really what Tableau always has strived for, making your data available to all of us. That is guaranteed. One of the key things that we are working on very closely is to make sure those agentic analytics can get you the right answers, and that starts with making sure you get the right, what we call a semantic data models right, and out of the box, we now ship for all the customer domains and also making sure that the conversion into SQL and the semantic models is correct, and that is kind of how we had a bunch of acquisitions for data as well to make that better. This is what we believe is the future of analytics. Like, how do we make analytics really give you in a conversational pattern and embedded in your line of work? In fact, some of the demos that you might have seen already, where we now have Tableau, through Agentforce, Tableau through Slackbot, all of those experiences, we are trying to bring in Tableau relevant in your line of work. All the applications that we now ship, like marketing and business, everything, you saw the Agentforce analytics and so on, is also now all built on Tableau. Tableau is much more deeply integrated into our stack, so we have expanded the TAM for Tableau into all of our existing Salesforce stack as well. Plus, we are making sure Tableau will be the premier solution that you use when we have this agentic analytics taking over. Madhav, do you want to add anything more? I think you answered the Tableau question, but I think this is kind of the broader point we made earlier, which is when you think about Agentforce, it's not just the Agentforce part of the technology, it's the impact and the uplift that it has on every part of the portfolio. We're making our apps better with these agentic capabilities. As customers use the platform, they now will leverage Tableau to do the analytics that MK said. They're gonna be leveraging Data Cloud and Informatica to really harden that context layer. They're gonna be using MuleSoft to connect across. When you really think about the Agentforce momentum, you should really think of it in terms of all of these pieces coming together to create these experiences. Leverage many, many parts of our stack to create that overall experience. I completely agree with MK, the utility of a tool like Tableau in a world where the optimization and the management of agents is going to be a critical part of how every business works, incredibly valuable capability in that world. Great! We're gonna take our last question here, which is on Data Cloud or Data 360. Clearly, Data Cloud is growing really well. It's appears to be a prerequisite for preventing AI hallucinations in Agentforce deployments. Are customers who adopt both Data 360 and Agentforce together showing materially better retention and expansion rates, than those who are using Agentforce alone? Yeah, I'm happy to start and toss it to MK. We see a huge overlap in the customers that are using Data Cloud to connect across their systems and the customers that are using Agentforce. Data Cloud is also a key part of the Agentforce architecture. We use Data Cloud to make sure that we get all the analytics. Gabe showed you a slide that showed as you're testing the agent, every single moment that the agent is making a decision, executing something, we call that a session tracing. All of that session tracing really sits in Data Cloud so that we can leverage the power of all of these analytics in this data. The two products are very closely tied together. Of course, customers also use Data Cloud to extend across the enterprise, bring in all of this context. A huge overlap in that customer base, and I do think that the products really are complementary and drive each other's momentum, and we expect that to continue. MK, anything you want to add on Data Cloud? Yeah, it's. See, one of the things that we have also seen, in fact, even recently with a very big customer, is that as we lay the foundations of this, we can easily upsell so many different technologies, because all our platform works together. That means somebody who is using Agentforce and Data Cloud, we can now upsell our Tableau stack onto them. If they're using Service, now Marketing works better because the same data and the same agentic experience now can work with our marketing deeply. This thing causes us to be able to go upsell and cross-sell all our technologies together because foundationally, we have architected our stack so that the data and the agent stack underlies all our application experiences and all our systems of engagement. That is a huge boost to us. It's not just about customers retaining. I mean, retaining and growing our customers with Data Cloud and Agentforce, it's really growing and upselling all of these other clouds as well. Awesome. Well, thank you all for joining. Thank you, Madhav, MK, Gabe, for hosting today. We look forward to seeing you on the road over the next few weeks, and we have a bunch of questions here that we'll get back to you on, but we really appreciate the time. Have a good rest of your weekend.