Name: The Power of Smart Intake & Orchestration in Source-to-Pay
Uploaded: 2025-11-13T16:01:05.476Z
Duration: 46 min 12 s
Description: The Power of Smart Intake & Orchestration in Source-to-Pay

Transcript for "The Power of Smart Intake & Orchestration in Source-to-Pay": Welcome, everyone. I'm Ben Tornond, and I'll be your host for today's webcast. I work for the Hackett Group, and I lead their digital procurement practice for The UK and Ireland and Benelux regions. If you don't know Hackett, we are a pioneer in the digital procurement world. We've been working alongside Coupa for over twelve years, and we've delivered over one hundred one hundred digital procurement projects, supporting companies with their digital procurement strategies as well as the execution of their digital procurement transformation plans. Just a few, a few things I'd like to mention before we we get started and jump straight into the topic. This session is being recorded, and we will share the recording with all attendees via email after the session. We've muted all lines to ensure the quality of the call, but if you have any questions, please use the q and a tab on the right hand side of your screen to ask your questions or to report any issues during the webcast. We'll answer as many questions as we can today, but if we don't get to yours, we'll make sure to get back to you via email after the webcast. Today's webcast is all about intake and orchestration and the power and value it delivers for businesses across the source to pay process. I'll be joined by two experts today, Freddie White from Coupa, solution sorry, solution adviser at Coupa, and Nikhil, from SpendMatters, who is director of strategic project and research analyst. SpendMatters is a company that is now part of the Acce Group since May, and, I'm delighted to have both of them with me today to discuss the topic of intake and orchestration. So in today's webcast, we will start with demystifying smart intake and orchestration, and Nikhil will kick us off covering the core concepts of intake and orchestration as well as a few use cases and the benefits that this new technology provides for procurement organizations. Following this, we will move on to a live demonstration by Koopa, and Freddie will, walk us through the new smart intake features that are now available on the Coupa platform. We'll finish today's presentation with a fireside chat and a q and a session where we'll be discussing your questions as well as AI intake and orchestration and Koopa's roadmap for intake and orchestration moving forward. Again, if you have any questions, please feel free to ask them using the q and a section in the chats. But let's jump straight in. What is intake and orchestration? Intake and orchestration is a fairly new concept that was brought to life about four or five years ago. As Spend Matters describes it, it's a new core procurement capability, and, actually, it's the first new core capability in about ten years. So it's a massive new, technology that's available to procurement professional, and that's what we're gonna be unpacking today. Just to give you a few numbers, around the technology, there are about one in five organizations out there that is already using intake and orchestration. And out of this 20% of the population, about 70% of them are reporting benefits that are meeting or going beyond their initial expectations. So we're not just talking about a hype here. We're talking about something that's very real. And there is no one better place than my colleague, Nikhil, who's in charge of intake and orchestration for Spend Mathors to demystify the topic for us. So please, Nikhil, come on stage and tell us more. Yep. I I will do it. Thank you, Ben. Really appreciate it. Just getting my screen up here. Okay. So, yes, as Ben was saying, intake and orchestration, it's fairly new, but I completely agree that we are past the sort of hype stage. And at this point, it's a technology that's becoming, frankly essential for most procurement departments. So, you're in the right place if you're here to to learn about it. But, the the concept is not what's new. Right? It's really the prioritization of it because in a nutshell, intake management is really just about the capturing of demand of a request and routing that request to the right people or applications or wherever it needs to go. So whether it's saying that I need to purchase this item, I need to, renew a contract, or I need an RFP for something, that has existed for really as long as, enterprise software has. But what's new about it is the fact that this is all becoming productized in one, central location for people to make these requests. So what intake is doing then is it's really, creating one source for end users to go in and make different requests related to the business. And it's also a very, easy to use interface typically. So it actually goes beyond procurement a little bit because, finance, IT, legal, there are all these other, other functions that are using the intake solution because it's easy to use. So that's where a lot of the the value comes in. And once the intake request is made, there's typically a workflow that, comes up as a result where you just can track the status of the request. So, again, intake, it's not it's not brand new because, you know, you could argue that a lot of legacy solutions have supported this for, you know, a long, long time. But what's new about it is the fact that you have software that is dedicated solely to intake in a way that encourages end user adoption. And I'll talk a little bit later about why this has happened and and what has made it so popular, but you can't talk about intake without talking about orchestration as well. And, you know, these are two somewhat different concepts, but they're very closely related. So if intake is about making the request, orchestration is about ensuring that the request actually gets done. And orchestration, one important aspect of it is that it very often can leverage information that comes from outside of the solution. So via integrations, in many cases, after an intake request has been made, you're leveraging integration to actually ensure the request gets done. So maybe it's a purchase request. Right? You can actually complete the purchase in the intake and orchestration solution via integration with the catalogs or punch outs or whatever your organization is using without actually leaving the intake and orchestration solution where it's all done via integration. So, obviously, guided by is one, very popular use case for intake and orchestration. It's possible for an orchestration solution to manage manage requests that have been started elsewhere, like, if an intake request happened in another tool, but that doesn't necessarily have to be the case. The main point of it is that you're allowing users to execute steps to complete a process without having to actually leave the solution. And what you're seeing now that's a lot more popular is solutions that can cover both intake and orchestration in one place so that the entire department has one central location where they can, manage all the requests for the procurement department and always see the status of other requests so that everybody is up to date and working off of the same information. So why this market is so popular. Right? There are a lot of reasons, but a big one is that the focus on usability and configurability is a lot more than just buzzwords, right, because this software is typically extremely easy to configure from a workflow standpoint, where in the past workflows are something that maybe required IT involvement or only power users could access certain features, but now workflows could be configured via, drag and drop and no code or low code environment. So it's just a lot of a lot more of a smooth process for organizations. And just the usability overall, a big reason for the high end user adoption is the infrequent user. A lot of the value of intake comes from users who only use the software, you know, let's say once a month or several times a year. Those people in the past might have required training from IT or other forms of support in order to know what to do in order to make requests. But now this infrequent user sees the software and knows exactly what they have to do because it's very intuitive. It's not I mean, it can be filling out a form, but most commonly now it's just natural language where you're interacting with the chatbot or, you know, some sort of natural language form where you can just type out, I need this, and the system will know what to do next. So that's a big reason why there's high end user adoption is because the infrequent user doesn't require training. That's a huge benefit of intake and orchestration. And it goes beyond just the lack of training. It's also implementations. The implementation timelines for intake and orchestration are much quicker than the typical source pay implementation, and there are kind of two ways to look at it. Three to six months is typically what I hear of implementations, but the other side of that is if you're using, you know, let's say a suite like Coupa for a ticket orchestration, that implementation would also be quick because either you're already a customer of that suite, so the implementation process is much smoother. You already have the suite, you know, up and running. Or if you're a new customer, a net new customer, and you're starting you know, let's say you're doing p two p or source to pay and you're also onboarding intake and orchestration, that also makes the process quicker because you're already onboarding, you know, the rest of the product at the same time. So it's really not that much of a lift to also onboard intake and orchestration. So the quicker implementations are also a big reason, But, the ability for intake tools to really adapt to different processes is also a key. Yes. There are preconfigured workflows, but those workflows are adaptable and AI is one reason for that. Part of that too comes into the natural language text like I was saying. If somebody makes a request that has not been pre configured or might not be supported out of the box, there are still ways for these intake solutions to make sure it gets completed and to route it to the right places anyway. So there's a lot of value in that adaptability. And finally, tech stacks are growing quite a bit and that is, that's both from a procurement lens and from outside of procurement. So the ability for these platforms to integrate with each other and communicate with each other is becoming very important, and that also extends to agents and and AI. Right? Because a lot of large organizations have, you know, started to put forth broad AI strategies, And it's important for these organizations that the agents they're using can actually communicate not just with other software, but also with other agents. Right? So, these orchestration platforms in many cases are starting to act as the sort of intermediary for these agents to communicate. And obviously, that's just very important for for large organizations because, AI is so important to them that if the agents were not able to, you know, leverage the orchestration platforms, that would be a big issue for them. So, overall, there's a lot of trends happening right now that are converging, in a good way for this market and making it a lot more popular. But that's kind of just, like, the the brief overview, and I look forward to talking more about this market and how it's grown so much in the the fireside chat and the q and a later. Nikhil, thank you very much for your presentation. It was very informative. If you've got any questions for Nikhil, please feel free to ask them directly in the chat using the Q and A tab. But we'll get back to some of the statements that Nikhil has just made in the fireside chat and as we answer your questions later on as well. We'll now move on to to Freddie who's gonna live and he's gonna demo the capabilities the new capabilities that are available in the Coupa platform when it comes to smart intake. Over to you, Freddie. Absolutely. And thanks to both my co presenters. Good afternoon, everybody. Quick sneak peek there of Cooper's intake, but I am gonna run through a couple more slides just very, very quickly to set the scene a little bit. So as Nikhil and Ben have already touched on, of course, intake and orchestration come with this core mission statement, which is, of course, making requests easy for everyone, regardless of whether you're a procurement professional or just a casual infrequent, user, and we'll show how Cooper absolutely facilitates this, with with our solution in just a moment. Awesome. But, you know, where is intake and orchestration born out of Nikhil's already touched on this, so I won't dwell too long on this. But, you know, legacy solutions, maybe if you're using your ERP alone or maybe, you know, that process is so clunky, you're not even raising requisitions upfront. We see poor user adoption of these legacy systems or just complete lack of a process, as I say. Maybe there's complex or confusing processes in the mix there, necessitating, that streamlined request process, and the orchestration thereafter as well. Naturally, this often leads to, you know, bottlenecks and approval delays, and also a lack of visibility as well, once each step of those quite complex often processes are being completed, in the background after the request, has been initiated as well. And for a lot of organizations, naturally, those three proceeding points lead to an inability often to scale, their operations. You know, increasing invoice volumes or rest volumes become unmanageable, in a lot of those cases due to those first three points. And that's where a solution naturally, like Cooper, comes in to reduce that employee frustration, improve that control and visibility, as well, but in a compliant way and manner with your internal policies, too. So, of course, intake on one hand is all about making that end user experience an absolute delight for your end users. They don't need to be trained on the system. They don't need to go back and forth with procurement as to how to raise a request for those common or uncommon categories of spend they may have. And then orchestration, as well for those, you know, those processes, within, external solutions or the platform, as well because each object is landing in the correct place after the initial request. So how does Cooper kind of view intake and orchestration? Kind of three main users we like to think of. So the first being, of course, our imaginatively named Rebecca the requester. Nice bit of alliteration there for for all these users. And she is someone who accesses the system, like Nikhil said, maybe several times a year, maybe once a year, maybe a couple times a month, as well. So we wanna make it easy for her to access the system and to use it. Then on the other hand, as well, we've got Preston, the processor. So he's gonna be, actually advancing, Rebecca's requests, through those orchestrated processes. You know, perhaps an initial requisition has been raised, and we need a supplier onboarding request as part of that requisition and the contract. Our infrequent requester doesn't need to know any of that. They just need to be guided through the steps, that they need to take, to complete. And then our processor needs those objects to land in the correct system or in the correct module within a unified platform as well. With all of that being overseen by our equally imaginatively named Adrian, the administrator, who, like Nikhil mentioned, wants to leverage and can leverage within the Coupa platform a true drag and drop, system and configuration capability to maintain workflows, make any required changes, as well, that she needs to to keep her business running. And so with that, without further ado, I can jump into the Cooper platform for intake. So what you're looking at now is our infrequent requesters view. This is Rebecca the requesters view. I've actually got another user here, a matching team named Eaton intake. As you can see, it's a very sleek kind of home page. Every action I need to take can be undertaken from this home page. A few things to call out, any, you know, approvals I need to get done, any receipts I might need to provide are all surfaced to me immediately. Any of my draft requests, so I can come and jump back in and complete those requests or delete them. Maybe I made a mistake. Then I can go and view any of my recent requests as well. Google's really streamlined the status of these requests. So we just have in progress, completed, or rejected for these requests or draft, as well just to make it even easier. If I scroll down, we jump in and initiate a request in just a moment. I can view one of my in progress requests. And like I mentioned, for, you know, more end to end requests where we've got an initial requisition and we need to raise a supplier onboarding form and a new contract request. What we can see, within Cooper is, despite these processes being pretty complex, me as the infrequent, user, I can just jump back into any of my requests at any point, and see who's approved, previous steps such as the spot onboarding or the contract and the final requisition as well. I can very clearly see who that's with and who's approved it. And if I need it, you know, to communicate on any of those steps, I can do with my internal team as well to keep things moving along or for additional, visibility. So very, very much streamlined. I know where my, my request is without having to go back and forth with procurement or, perhaps, the supplier as the case might be. But I hear nobody ask because it's just me on stage at the moment. How do we actually get to that stage? Of course, it's by initiating a request. So I'll walk you through an end to end flow. So we just have one button. It's simple. I can't break it, which is very good for me. I enjoy breaking things, by accident. So I just click one button, and I'm brought to a fully configurable, perhaps you wanna call it, you know, your common categories that you at your organization see your end users most frequently, requesting. So I can select one of these common categories. So today, we're gonna choose software. I'm just gonna move my monitor up so I can actually see the bottom of it. We're gonna request some software today, and I'm asked to fill in a fully configurable form. So it can be as much or as little information that you need to collect from your infrequent requester to get this process step completed for them. In this instance, this is just to determine what steps need to be taken. So we'll be imaginative, and they are, software something imaginative for today. And the provider, again, will be equally imaginative and call it Freddy's software. But, actually, as I start typing in this, in this box just here, if I were to select or start typing and Cooper knows we've already onboarded this supplier, we can actually select from our suppliers that already exist, within the system today. And that will actually just go ahead and enable us to create a requisition because the supplier's onboarded. We've already got a contract. But if we don't have the supplier onboarded, it's gonna take us into a different process step. So I have to fill in the mandatory fields, of course, for today, and then I can just go next. We'll put a need by date, and we'll be really strict and say we need this tomorrow. Luckily, people will facilitate this for us, of course. Now the on the left hand side, you'll see the next process that I'm taken to as part of this. I need to raise a supplier onboarding form, but perhaps in a legacy solution, I don't know as an infrequent request of it. I just know I need software. I don't need to know that I need, to onboard a new supplier. I don't know that I need to, raise a new contract request within Cooper. It doesn't matter for our infrequent requestor. Based on their inputs, based on the supplier not being, onboarded already in the previous page, we're told we have to fill in a supplier's details, which we can do. Luckily, not many mandatory fields for us in this case. So I'm gonna be nice and lazy and just go onto the next page. Now we've got that logic built in very easily through drag and drop tick boxes, by Adrian, the admin that says, you know, when we have a new supplier, we wanna drive, you know, a 100% less ambitious, a 100% on contract spend, so I'm then told or required to fill in contract information so we can begin filling in these fields, of course. Not mandatory. And what's great about these forms as well for Preston, the processor, on the on the other end, on, you know, if he's onboarding supplier or filling in the contract request, is that all the metadata that we fill in during these requests are gonna pull over into, the platform side for Preston, the processor. So he doesn't have to double key in that data for him. So just we're driving a compliant, efficient, easy to use process, for Rebecca the requester. We're also driving efficiency, for Preston as well because he's not gonna have to double key in any of this information, including, you know, the the contract type, perhaps. So, of course, if we got a supporting document, we could upload it here as well. So we're just gonna go, next. I'll ship to address. Can default for us. There we go. We can input justification. Not mandatory. But as you can see, you know, we just filled in essentially three different requests, a requisition, a supplier ordering request, and a contract request in a matter of minutes in this case without having to know what part of perhaps multiple platforms if you're using several siloed solutions today. So when I go next, of course, I'll see a summary and all the steps which can be taken to complete my request. Very easily, I can just submit that and come back to my home page. But a few simple clicks, a few screens, without having the knowledge, I'm not a procurement professional, I can fill in what is actually a pretty complex request without having that knowledge. The system has taken the thinking out of the equation for me, and it will be dealt with, for me in lieu. Now jumping over to Adrian, the admin now for just a second. Of course, we can see the workflow, which is undergirding those steps that I've just taken. So we've got our initial button click, which is gonna take us, to our, those initial categories that I showed at the start. So, of course, we clicked onto our software request. So let's click into it and see what's actually going on behind the scenes. On the drag and drop point, look, I can literally drag and drop. I don't need to be a computer scientist, which is well and good because I'm not. So luckily, Cooper is very easy to configure for me personally and for our customers. If I click into the software request, we can see the logic which is undergirding and the processes which are being kicked off and which we followed as the, requester just now. So I can see that initial request details page, which has got those elements as to, you know, whether the supplier exists or not. So it's saying no. Supplier doesn't exist. So it brought to our supplier onboarding form. We've got a stringent on contract spend policy, so then we're guided to our contract details form. And this is the flow that we took as you as you can see here. But if we'd identified that supplier, like I mentioned in the request header, we could just go and, submit the requisition, of course, with the required approvals too. Now likewise, Cooper fully supports naturally, you know, the editing of those forms. So any fields I need to change, as you can see, it's that initial, initial page that we saw, including those dynamic fields as well, which you can label anything. It doesn't just say a supplier. Maybe that's perhaps confusing for our end users, so we call it software provider in this case. But like we said, with drag and drop functionality and tick boxes, we can edit all of those forms to be able to capture all the information that we need to be able to from our end users. In terms of what's going on on the platform side of things, so as our processor, of course, I'm two users in one in this case, I can see those initial requests are landing exactly where I need to, for to give me the visibility and to complete the task in this case as we're seeing, for our ability to approve and then start onboarding that supplier as well. So it's nice and streamlined for me as the processor. And then likewise, for, the contract as well. We can see our contract forms here. We've got a few that are pending approval. We can see one that's been completed, and we can go click in to that object. That's also a a key benefit of having, you know, intake and orchestration on one side, but also, of course, a platform approach therein as well. I'm able to click between all of these objects seamlessly from configuration from an end user to our processes objects that he's working on here, whether it's a supplier or a contract, as well. And then a little bit of a a bit of a teaser as well. So in the very near term, like Nikhil mentioned, in terms of a natural language processing to complete a request, Cooper will be fully supporting this with our Navi AI. So as Rebecca the requester, I can come in and put in a request perhaps for 50 software licenses being consistent with our initial request. We have to fill in a few basic details for our supplier. Perhaps we have an attachment to upload a contract, and then Navi will begin, extracting any information or additional information from that contract. And very easily, we can go and review our intake request. All our processes are built out for us, and we can go ahead and submit our request. And that is all she wrote. Freddie, thank you so much. That was extremely powerful. I hope everyone appreciated the demonstration and got to understand the power that smart intake can, can bring to procurement organization. Personally, what I noted is the very intuitive user interface and how easy it is for people to, use, especially people who are infrequent users. The improvement that you can bring for process efficiency because it's fairly straightforward. Don't need to click 500 pages and figure out where to go next. This is all guided. And finally, something that's usually understated on the topic of intake and orchestration is compliance, compliance enforcement. As you've highlighted, Freddie, people don't need to know what the procurement policies are. The procurement policies are directly embedded into the system. And so people will be, as a matter of fact, complying with the procurement policies that are sitting in the backgrounds. With that, we'll now move on to the fireside chat because I'm sure everyone's excited to hear about what's next in intake and orchestration, and we'll also be taking some of the questions that we've received, in the q and a tab, over the last thirty minutes that we've been together. We'll start with you, Nikhil. You've got deep expertise in, intake and orchestration as the leads analyst for, Spend Matters. We know that the intake and orchestration market is comprised of both phone solution and suite platforms. First question for you, Nikhil. What do you think are capacity strengths in this space in the intake and orchestration space versus the, the competitors? Yeah. It's a good question. So the way that I see intake and orchestration solutions in terms of how the solutions are actually comprised, there are kind of three components to it. There's intake, there's orchestration, and there's the platform. And the platform, like any other software platform, it's what underlies everything that the end user actually sees, in this case, the intake and the orchestration. So in terms of Coupa's strengths, I would say that Coupa's platform is extremely robust in that, the configurability that it allows for, the data modeling that it supports, I mean, you you would assume, right, that their platform is really strong given given their rep. So Koopa's platform is important intake orchestration as well for for several reasons, but a couple are like I said, the configurability on the workflow side of things And also just the amount of data and the even the community data, like, anonymized community AI data that that Coupa has that it can then serve back to users from an intake standpoint to suggest process improvements or, you know, if if it's a a buying related scenario, then then savings opportunities. Coupa has the unique advantage on on that front that other providers don't really get into. So combining that with the strength of the platform gives them a leg up, I would say, over the competition, in intake and orchestration just because other providers, even the other bigger ones don't really have that, that breadth. They might have a good platform, but they don't have both the platform and the data combined. So Coupa having both of those is a is a differentiator. Thanks, Nikhil. Moving on to a different topic, I I suppose everyone who's on on the call today is interested in understanding how AI is playing a role into intake and orchestration. So my next question for you, Nikhil, and we'll get to you, Freddie, I promise. But my next question is, what what's coming next when it comes to AI and intake and orchestration? What are you seeing on the market already, and what shall we expect in the near future? Yeah. Yeah. This is a question I get all the time. And, we even got a a presubmitted question from the audience earlier, which was how how is AI and how are agents disrupting orchestration? And to answer both questions, I don't see it as a disruption at all. In fact, I think the value prop of orchestration, right, is all about efficiency and and, you know, making it easier to work, and that's really very similar to what AI and what agents are trying to do. So I think that they're actually complementing each other. And what I've seen so far from an agentic standpoint in orchestration, it kind of varies because a lot of the agents I'm seeing are arguably more relevant to source to pay. Like, for example, a contract renewalization, like, nothing wrong with that. That's great. But I would I would say that's almost more of like a CLM feature that if an orchestration tool had it, that would be nice, but it's not mandatory. So specific to intake and orchestration, a couple of things I've seen. One is the workflow creation itself. A lot of people like the drag and drop interface, but not everybody. Some people would prefer to just literally draw on a piece of paper what they want the workflow to look like or to type out in natural language what they want the conditional logic to be. So I'm starting to see more support for different types of workflow creation, leveraging AI, like photo uploads, for example, or or typing in the text. Another would be on compliance. I think that there are a lot of, the compliance rules are changing all the time due to, you know, data privacy regulations and other changes happening around the world. And these changes are not always input rapidly into the intake and orchestration system or whatever software teams are using. Sometimes they are just file uploads, but the actual back end rules are not actually changed. So the use of AI to map file uploads to these rules to change them is is one thing I'm seeing. Or if it's not even changing the rules, then if somebody's making a request, but it's maybe something's not in compliance or the, the dollar value is high enough, it should trigger some extra rule. A lot of these or not a lot, but some of these systems now can check the request against the most recently uploaded policy documents to ensure that everything is within within policy and they use AI to do so. So that's kind of what I'm seeing starting to see now. I think in the future, like I said, agents are gonna be much more important to orchestration because of the similarity of their value propositions. So I think it'll be very important for intake and orchestration providers to not only offer agents, but especially to ensure that their platforms are strong and configurable enough to support agents that are coming from all sorts of directions to be able to interact with each other because there's so much data, the orchestration platforms that is gonna be important for users, and agents are gonna wanna access that. So it's not just about having agents, it's also about being able to support their activities essentially. Excellent. Thank you so much, Nikhil. That leads me to asking you a similar question, Freddie. How is Coupa leveraging AI within its intake and orchestration solution today? That's my initial. question for you. Yeah. Yeah. Good question. So, yeah, predominantly on the on the orchestrator side of things. So even though, you know, 80% of your user population is probably an infrequent requester, you know, 80% of the workflows and the tasks are actually being completed by Preston, the processor. Right? So that's why we see a lot of these AI features in the Cooper platform today on top of, you know, what I showed at the end there. But, there's a couple of really cool ways. So one is there might be a sourcing event request, for example, raised, by our, initial requester. And Google provides a really great tool, you know, Navi, our AI agent that we just sourced. One, help, our, processor actually build up and recommend, sourcing templates to be used. Then also after a sourcing event is completed, to actually summarize that sourcing event and provide a suggestion as to who, you know, those suppliers were that provided the best bid and the best response as well. And on the requisition side of things, on all these objects that we see, for example, for a requisition, if I'm able to scroll through what can, you know, oftentimes be quite a few requisition lines, and we use generative AI as well to actually summarize that requisition. So, you know, what suppliers are included, what's the total value, who requested it, of course, why is that processor in particular been bought into, the approval chain, for example. And then, yeah, something that Keel touched on. And it's actually something Cooper's been doing, for years and years as well on the on the workflow, side of things and that kind of insights, you know, side of things. So because we we've got this dataset of $8,000,000,000,000 in in spend data. From an approval. So it's workflow perspective. Cooper provides, you know, workflow insights so you can actually identify where bottlenecks in specific approval chains or workflows, are. And then, naturally, because there's a lot of approvals through an orchestrated process, that lends itself as well, to to intake and orchestration. Thank you for that, Freddie. Carrying on the topic of the future, what's on the horizon for Coupa's intake and orchestrations capabilities? Are there any exciting innovations or roadmap items that you could share with us today? I know you've already demonstrated some of the conversational kind of capabilities that are coming up, but what else shall we be expecting in this front? Yeah. Absolutely. So Cooper reinvest, as you know, around, you know, hundreds of millions, in r and d, every single year and intake and orchestration, of of course. You know, it's a, you know, a monumental shift we've seen in the last few years. So it's a key key area of, investment for us and, of course, at the intersection with AI, as well. So there's a few, kind of key developments up. One, of course, is is the AI topic that, you know, I did show just the just a highlight. So that natural language, processing just so you can ask. Navi, you know, I need x y zed. I need this. It will guide you to a preferred supplier or prompt you to provide a supporting document or to a buying policy perhaps or, you know, to go back to the drawing board entirely as as the case, is the case, might, be, as well. Again, on the orchestration side of things, so, very, very soon, as well from January on the processor side of things, we're gonna be finding our supplier on boarding agents. So servicing far more insights, as the supplier onboarding process is being undertaken as well. And then quite powerfully, probably the biggest of all of those, will be the Cooper Orchestrator, which is which is a big you know, has a big name. Right? And it's it's a very, very, big, feature. I can't get too much into details of, but let's just say, in terms of what's gonna be those 80% of use cases and workflows, regardless of what system, they're occurring in today. And, of course, Cooper already does support external callouts to third party systems, But the Cooper orchestrator is gonna make pressing the processor's job very easy. He's gonna spend, a lot of his day with his feet up. So I have lots on the horizon for intake and orchestration. Excellent. Thank you so much, Freddie. Very interesting and looking forward to the upcoming developments. We've got about five minutes left. So, I suggest that we we start going through the q and a. Maybe we'll start with a couple of questions that we've received ahead of, today's webcast. The first one is around orchestration capabilities beyond Coupa. So that that one's called We've Freddie. We've received a number of questions about Coupa's ability to orchestrate beyond the Coupa platform, especially in the context of CRM and TPRM with systems such as ServiceNow or others. Could you share with us whether this capability is already available or if it's on the road map? Yeah. No. Absolutely. So, yeah, Cooper provides, support for, calls call outs to, you know, external, third party systems as part of, you know, those orchestrated workflows. CLM is, you know, a great, example of that. Do we want it in a Cooper platform? Of course we do. But we do. You know, it's fully supported. We appreciate that a lot of organizations do have some tools. So, yeah, external call out is fully supported, today. And from January, we're supporting a lot more, use cases as well for actually pulling that metadata, back into across those processes. So yeah. Thanks, Freddie. Nikhil, the next one I think is for you. There are a lot of people asking about the benefits of intake and orchestration solutions. Could you let us know what benefits organizations usually, sorry, what benefits organization that implemented such technologies usually realize? Yeah. So, like like we said, it's mostly around improving efficiency and freeing up time, you know, just to spend on more important tasks. So really increasing, or I should say decreasing cycle times, making it a lot quicker and approval times being much quicker. And, you know, just getting the buy in from this from the organization is really important when you're looking for an intake and orchestration solution because it's something that procurement instantly understands why this is necessary, but other departments maybe might need some more, maybe not convincing, but just more education on the subject. And they might think, well, why don't you just use, you know, this ticketing platform for for intake and orchestration? How is it any different when in reality, they're they're extremely different? So I think it's very important to if you're, you know, if you're a procurement and you're trying to get buy in from across the organization, really driving home what makes this different from, you know, generic, ticketing, like IT ticketing platforms is is very important. It's something that I've actually been asked to do in a few cases for clients. So that's, like, the main the main barrier, I would say, to to getting buy in is is being told that there are other tools that might address the same problem when it's not really doing so. But but the benefits obviously are around efficiency and cycle times and end user adoption, you know, and and in some cases, going up by, I mean, anecdotally, over 50% is is what I've heard at large organizations. So there's definitely a lot of very quick time to value that these companies are realizing. Thank you, Nikhil. I'll start going through a number of the questions we've received in the chat now. There is one, that we've received, Freddie. I think this this one's for you around the ability to launch sourcing events from the smart intake stuff front if you'd like. Could you could you tell us more about this? Yeah. Absolutely. So, I just spoke to a customer recently, and, of course, with those labels I've shown that you could call, you know, the fields anything you like to make it more intuitive for your end users, or you could just call it a a sourcing request. In essence, one of our customers are gonna be calling that sourcing request, just procurement help, more broadly just to kick off, you know, a a sourcing event request. They wanna work with suppliers. They have a project in mind, for example. So, yeah, as part of that that workflow, you know, a good actually putting it in the context of a workflow. It might be the case that one of those fields, we hadn't identified a supplier and the spend was over a certain threshold. So the next step in the in the intake process would be to launch a sourcing event because we built rules in the say when no supplier is identified and it's over, you know, a 100,000, we need to go out to market for, you know, three bids in a buy, for example, which Cooper actually already does. It's been done for years on the platform side, but as part of intake as well, we we support that. We support that too. Thank you, Freddie. The next question, and I guess that will be the last one for today given that we've got about a minute left, but, there's a question around interfacing with catalogs and approved suppliers. I think in the demo in the demo that you, that you did, you went for a new vendor. But I think the question is around whether the system would prompt you to use an existing vendor over over a new vendor. Is that something that the system would be guiding you to do? Yeah. Absolutely. So, yeah, the catalogs question is a great one and Coupa intake. We've still got our much loved search bar, so you can search for those, you know, items as the case might be. So if I selected the items tab there at the start, we've got our search bar still in addition to our punch out catalogs as well. So you might be more comfortable using Amazon Business Punch Out, and we can pull all those items back into Cooper and into intake. So Thank you, Freddie. I just realized we are reaching the end of today's webcast. I just wanted to highlight that there are some additional documents available for you to to read at your own pace if you click docs. Next to the q and a tab, you'll find a number of of relevant documents to, further explore the topic of intake and orchestration. But we hope that you found today's content useful and insightful. If we didn't get the chance to get to your questions today, we'll answer them via email in the coming days. So please keep an eye out for our answers. And, again, I'd like to thank the presenters and everyone who turned up today for our webcasts. We hope that you had a great time, and we wish you a happy end of the day, and we hope to see you soon. Bye for now.