(upbeat music) >> Announcer: theCUBE presents UiPath Forward5. Brought to you by UiPath. >> Hi everybody, we're back in Las Vegas. We're live with Cube's coverage of Forward 5 2022. Dave Vellante with Dave Nicholson Ted Kumer this year is the Executive Vice President, product and engineering at UiPath. Brought on to do a lot of the integration and bring on new capabilities for the platform and we've seen that over the last several years. And he's joined by Dr. Edward Challis, who's the co-founder of the recent acquisition that UiPath made, company called Re:infer. We're going to learn about those guys. Gents, welcome to theCUBE. Ted, good to see you again. Ed, welcome. >> Good to be here. >> First time. >> Thank you. >> Yeah, great to be here with you. >> Yeah, so we have seen, as I said, this platform expanding. I think you used the term business automation platform. It's kind of a new term you guys introduced at the conference. Where'd that come from? What is that? What are the characteristics that are salient to the platform? >> Well, I see the, the evolution of our platform in three chapters. You understand the first chapter, we call that the RPA chapter. And that's where we saw the power of UI automation applied to the old problems of how do I integrate apps? How do I automate processes? That was chapter one. You know, chapter two gets us to Forward3 in 2019, and the definition of this end-to-end automation platform you know, with the capabilities from discover to measure, and building out that core platform. And as the platform's progressed, what we've seen happen with our customers is the use of it goes from being very heavy in automating the repetitive and routine to being more balanced, to now where they're implementing new brought business process, new capability for their organization. So that's where the name, Business Automation Platform, came from. Reflecting now that it's got this central role, as a strategic tool, sitting between their application landscape, their processes, their people, helping that move forward at the rate that it needs to. >> And process mining and task mining, that was sort of the enabler of chapter two, is that right? >> Well, I'd say chapter two was, you know, first the robots got bigger in terms of what they could cover and do. API integration, long running workflows, AI and ML skills integrated document processing, citizen development in addition to professional development, engaging end users with things like user interfaces built with UiPath apps. And then the discovery. >> So, more robustness of the? Yeah, okay. >> Yeah. Just an expansion of the whole surface area which opened up a lot of things for our customers to do. That went much broader than where core RPA started. And so, and the other thing about this progression to the business automation platform is, you know, we see customers now talking more about outcomes. Early on they talk a lot about hours saved and that's great, but then what about the business outcomes it's enabling? The transformations in their business. And the other thing we're doing in the platform is thinking about, well, where can we land with solutions capabilities that more directly land on business, measurable business outcomes? And so we had started, for example, offering an email automation solution, big business problem for a lot of our customers last year. And we'd started encountering this company Re:infer as we were working with customers. And then, and we encountered Re:infer being used with our platform together. And we saw we can accelerate this. And what that is giving us now is a solution now that aligns with a very defined business outcome. And this way, you know, we can help you process communications and do it efficiently and provide better service for your customers. And that's beginning of another important progression for us in our platform. >> So that's a nice segue, Ed. Tell about Re:infer. Why did you start the company? >> Right, yeah, so my whole career has been in machine learning and AI and I finished my PhD around 2013, it was a very exciting time in AI. And me and my co-founders come from UCL, this university in London, and Deep Mind, this company which Google acquired a few years later, came from our same university. So very exciting time amongst the people that really knew about machine learning and AI. And everyone was thinking, you know, how do we, these are just really big breakthroughs. And you could just see there was going to be a whole bunch of subsequent breakthroughs and we thought NLP would be the next breakthrough. So we were really focused on machine reading problems. And, but we also knew as people that had like built machine learning production systems. 'Cause I'd also worked in industry that built that journey from having a hypothesis that machine learning can solve a problem to getting machine learning into production. That journey is of painful, painful journey and that, you know, you can see that you've got these advances, but getting into broad is just way too hard. >> So where do you fit in the platform? >> Yeah, so I think when you look in the enterprise just so many processes start with a message start with a no, start with a case ticket or, you know, some other kind of request from a colleague or a customer. And so it's super exciting to be able to, you know, take automation one step higher in that process chain. So, you could automatically read that request, interpret it, get all the structured data you need to drive that process forward. So it's about bringing automation into these human channels. >> So I want to give the audience a sense here. So we do a lot of events at the Venetian Conference Center, and it's usually very booth heavy, you know, brands and big giant booths. And here the booths are all very small. They're like kiosks, and they're all pretty much the same size. So it's not like one vendor trying to compete with the other. And there are all these elements, you know I feel like there's clouds and there's, you know, of course orange is the color here. And one of the spots is, it has this really kind of cool sitting area around customer stories. And I was in there last night reading about Deutsche Bank. Deutsche Bank was also up on stage. Deutsche Bank, you guys were talking about a Re:infer. So share with our audience what Deutsche Bank are doing with UiPath and Re:infer. >> Yeah, so I mean, you know, before we automate something, we often like to do what we call communications mining. Which is really understanding what all of these messages are about that might be hitting a part of the business. And at Deutsche Bank and in many, you know, like many large financial services businesses, huge volumes of messages coming in from the clients. We analyze those, interpret the high volume query types and then it's about automating against those to free up capacity. Which ultimately means you can provide faster, higher quality service because you've got more time to do it. And you're not dealing with all of those mundane tasks. So it's that whole journey of mining to automation of the coms that come into the corporate bank. >> So how do I invoke the service? So is it mother module or what's the customer onboarding experience like? >> So, I think the first thing that we do is we generate some understanding of actually the communications data they want to observe, right? And we call it mining, but you know, what we're trying to understand is like what are these communications about? What's the intent? What are they trying to accomplish? Tone can be interesting, like what's the sentiment of this customer? And once you understand that, you essentially then understand categories of conversations you're having and then you apply automations to that. And so then essentially those individual automations can be pointed to sets of emails for them to automate the processing of. And so what we've seen is customers go from things they're handling a hundred percent manual to now 95% of them are handled basically with completely automated processing. The other thing I think is super interesting here and why communications mining and automation are so powerful together is communications about your business can be very, very dynamic. So like, new conversations can emerge, something happens right in your business, you have an outage, whatever, and the automation platform, being a very rapid development platform, can help you adapt quickly to that in an automated way. Which is another reason why this is such a powerful thing to put the two things together. >> So, you can build that event into the automation very quickly you're saying? >> Speaker 1: Yeah. >> Speaker 2: That's totally right. >> Cool. >> So Ed, on the subject of natural language processing and machine learning versus machine teaching. If I text my wife and ask her would you like to go to an Italian restaurant tonight? And she replies, fine. Okay, how smart is your machine? And, of course, context usually literally denotes things within the text, and a short response like that's very difficult to do this. But how do you go through this process? Let's say you're implementing this for a given customer. And we were just talking about, you know, the specific customer requirements that they might have. What does that process look like? Do you have an auditor that goes through? And I mean do you get like 20% accuracy, and then you do a pass, and now you're at 80% accuracy, and you do a pass? What does that look? >> Yeah, so I mean, you know when I was talking about the pain of getting a machine learning model into production one of the principle drivers of that is this process of training the machine learning model. And so what we use is a technique called active learning which is effectively where the AI and ML model queries the user to say, teach me about this data point, teach me about this sentence. And that's a dynamic iterative process. And by doing it in that way you make that training process much, much faster. But critically that means that the user has, when you train the model the user defines how you want to encode that interpretation. So when you were training it you would say fine from my wife is not good, right? >> Sure, so it might be fine, do you have a better suggestion? >> Yeah, but that's actually a very serious point because one of the things we do is track the quality of service. Our customers use us to attract the quality of service they deliver to their clients. And in many industries people don't use flowery language, like, thank you so much, or you know, I'm upset with you, you know. What they might say is fine, and you know, the person that manages that client, that is not good, right? Or they might say I'd like to remind you that we've been late the last three times, you know. >> This is urgent. >> Yeah, you know, so it's important that the client, our client, the user of Re:infer, can encode what their notions of good and bad are. >> Sorry, quick follow up on that. Differences between British English and American English. In the U.K., if you're thinking about becoming an elected politician, you stand for office, right? Here in the U.S., you run for office. That's just the beginning of the vagaries and differences. >> Yeah, well, I've now got a lot more American colleagues and I realize my English phrasing often goes amiss. So I'm really aware of the problem. We have customers that have contact centers, some of them are in the U.K., some of them are in America, and they see big differences in the way that the customers get treated based on where the customer is based. So we've actually done analysis in Re:infer to look at how agents and customers interact and how you should route customers to the contact centers to be culturally matched. Because sometimes there can be a little bit of friction just for that cultural mapping. >> Ted, what's the what's the general philosophy when you make an acquisition like this and you bring in new features? Do you just wake up one day and all of a sudden there's this new capability? Is it a separate sort of for pay module? Does it depend? >> I think it depends. You know, in this case we were really led here by customers. We saw a very high value opportunity and the beginnings of a strategy and really being able to mine all forms of communication and drive automated processing of all forms of communication. And in this case we found a fantastic team and a fantastic piece of software that we can move very quickly to get in the hands of our customer's via UiPath. We're in private preview now, we're going to be GA in the cloud right after the first of the year and it's going to continue forward from there. But it's definitely not one size fits all. Every single one of 'em is different and it's important to approach 'em that way. >> Right, right. So some announcements, StudioWeb was one that I think you could. So I think it came out today. Can't remember what was today. I think we talked about it yesterday on the keynotes anyway. Why is that important? What is it all about? >> Well we talked, you know, at a very top level. I think every development platform thinks about two things for developers. They think, how do I make it more expressive so you can do other things, richer scenarios. And how do I make it simpler? 'Cause fast is always better, and lower learning curves is always better, and those sorts of things. So, Re:infer's a great example of look the runtime is becoming more and more expressive and now you can buy in communications state as part of your automation, which is super cool. And then, you know StudioWeb is about kind of that second point and Studios and Studio X are already low code visual, but they're desktop. And part of our strategy here is to elevate all of that experience into the web. Now we didn't elevate all of studio there, it's a subset. It is API integration and web based application automation, Which is a great foundation for a lot of apps. It's a complete reimagining of the studio user interface and most importantly it's our first cross-platform developer strategy. And so that's been another piece of our strategy, is to say to the customers we want to be everywhere you need us to be. We did cross-platform deployment with the automation suite. We got cross-platform robots with linear robots, serverless robots, Mac support and now we got a cross-platform devs story. So we're starting out with a subset of capabilities maybe oriented toward what you would associate with citizen scenarios. But you're going to see more roadmap, bringing more and more of that. But it's pretty exciting for us. We've been working on this thing for a couple years now and like this is a huge milestone for the team to get to this, this point. >> I think my first conversation on theCUBE with a customer was six years ago maybe at one of the earlier Forwards, I think Forward2. And the pattern that I saw was basically people taking existing processes and making them better, you know taking the mundane away. I remember asking customers, yeah, aren't you kind of paving the cow path? Aren't there sort of new things that you can do, new process? And they're like, yeah, that's sort of the next wave. So what are you seeing in terms of automating existing processes versus new processes? I would see Re:infer is going to open up a whole new vector of new processes. How should we think about that? >> Yeah, I think, you know, I mean in some ways RPA has this reputation because there's so much value that's been provided in the automating of the repetitive and routine. But I'd say in my whole time, I've been at the company now for two and a half years, I've seen lots of new novel stuff stood up. I mean just in Covid we saw the platform being used in PPP loan processing. We saw it in new clinical workflows for COVID testing. We see it and we've just seen more and more progression and it's been exciting that the conference, to see customers now talking about things they built with UiPath apps. So app experiences they've been delivering, you know. I talked about one in healthcare yesterday and basically how they've improved their patient intake processing and that sort of thing. And I think this is just the front end. I truly believe that we are seeing the convergence happen and it's happening already of categories we've talked about separately, iPass, BPM, low-code, RPA. It's happening and it's good for customers 'cause they want one thing to cover more stuff and you know, I think it just creates more opportunity for developers to do more things. >> Your background at Microsoft probably well prepared you for a company that you know, was born on-prem and then went all in on the cloud and had, you know, multiple code bases to deal with. UiPath has gone through a similar transformation and we talked to Daniel last night about this and you're now cloud first. So how is that going just in terms of managing multiple code bases? >> Well it's actually not multiple Code bases. >> Oh, it's the same one, Right, deployment models I should say. >> Is the first thing, Yeah, the deployment models. Another thing we did along the way was basically replatform at an infrastructure level. So we now can deploy into a Kubernetes Docker world, what you'd call the cloud native platform. And that allows us to have much more of a shared infrastructure layer as we look to deliver to the automation cloud. The same workload to the automation cloud that we now deliver in the automation suite for deployment on-prem or deploying a public cloud for a customer to manage. Interesting and enough, that's how Re:infer was built, which is it was built also in the cloud native platform. So it's going to be pretty easy. Well, pretty easy, there's some work to do, but it's going to be pretty easy for us to then bring that into the platform 'cause they're already working on that same platform and provide those same services both on premises and in the cloud without having your developers have to think too much about both. >> Okay, I got to ask you, so I could wrap my stack in a container and put it into AWS or Azure or Google and it'll run great. As well, I could tap some of the underlying primitives of those respective clouds, which are different and I could run them just fine. Or/and I could create an abstraction layer that could hide those underlying primitives and then take the best of each and create an automation cloud, my own cloud. Does that resonate? Is that what you're doing architecturally? Is that a roadmap, or? >> Certainly going forward, you know, in the automation cloud. The automation cloud, we announced a great partnership or a continued partnership with Microsoft. And just Azure and our platform. We obviously take advantage of anything we can to make that great and native capabilities. And I think you're going to see in the Automation Suite us doing more and more to be in a deployment model on Azure, be more and more optimized to using those infrastructure services. So if you deploy automation suite on-prem we'll use our embedded distro then when we deploy it say on Azure, we'll use some of their higher level managed services instead of our embedded distro. And that will just give customers a better optimized experience. >> Interesting to see how that'll develop. Last question is, you know what should we expect going forward? Can you show us a little leg on on the future? >> Well, we've talked about a number of directions. This idea of semantic automation is a place where you know, you're going to, I think, continue to see things, shoots, green shoots, come up in our platform. And you know, it's somewhat of an abstract idea but the idea that the platform is just going to become semantically smarter. You know, I had to serve Re:infer as a way, we're semantically smarter now about communications data and forms of communications data. We're getting semantically smarter about documents, screens you know, so developers aren't dealing with, like, this low level stuff. They can focus on business problem and get out of having to deal with all this lower level mechanism. That is one of many areas I'm excited about, but I think that's an area you're going to see a lot from us in the next coming years. >> All right guys, hey, thanks so much for coming to theCUBE. Really appreciate you taking us through this. Awesome >> Yeah Always a pleasure. >> Platform extension. Ed. All right, keep it right there, everybody. Dave Nicholson, I will be back right after this short break from UiPath Forward5, Las Vegas. (upbeat music)

>> theCUBE Presents UiPath FORWARD 5. Brought to you by UiPath. >> We're back in Las Vegas live. You're watching theCUBE's coverage of FORWARD 5 UiPath's customer event. My name is Dave Vellante. I'm here with David Nicholson. Our third Dave Espinoza is here, Director of Transformation at Cushman & Wakefield. And Marshall Sied is also here. He's the co-founder of Ashling Partners. Guys, thanks for coming on theCUBE. >> Thanks for having us. >> We know Cushman & Wakefield, huge real estate firm. We'll come back to that, wanted to dig into some of the industry trends. But Marshall, what is Ashling Partners all about? >> Great question, Dave. So Ashling Partners was founded with modern automation and continuous improvement in mind. So a lot of us used to implement large ERP systems, accounting transaction systems. We viewed RPA and broader intelligent automation as kind of the wave of the future. So everything we do has continuous process improvement and automation in mind together. So we don't want to decouple, we want bring those together in an agile way. >> It's interesting, Rob Enslin this morning on the stage was talking about the waves of industry tech that used ERP was where he started and you know, et cetera, internet and now automation. He's sort of drawing that analogy. It's interesting that you're seeing the same pattern. >> David: Were were you fist bumping in the back of the room? >> Marshall: Absolutely. >> Well, I mean there's a lot of opportunity there. A lot of money to be made on both ends. Dave, talk about your firm. What's going on in the industry specifically? You joined sort of as we're exiting the isolation economy. Right? So what's happening in the industry now? I mean, real estate has been up and down and, you know, wild ride, you know, with COVID. What are the big trends in the industry that are informing your automation strategy. >> And actually I joined probably like right in the middle of the isolation economy. So it was a really interesting time to like to, I'm sure for most people also onboarding into groups. But coming on Cushman, you know, Cushman itself is an organization that formed predominantly through acquisition and through merger, right? So three large companies came together. And so a lot of the times the sort of headaches and the opportunities that we find are probably no different than other legacy organizations have when they're merging three companies together, right? So lots of disparate process, lots of paper, lots of process that isn't really very standardized. And so really it's a lot about us trying to make sure that we're continuing to double down on really that continuous process improvement but also bringing technology, lots of different types of technologies to bear to solve different problems throughout the organization. >> Well is the pandemic a catalyst for the automation initiative? Or actually you guys started before that I think, Marshall started about 2018. But was it like a rocket booster during the pandemic or was it more sort of steady state? >> I think it was actually a little bit of both Dave. 'Cause the reality is there was already top down executive support at Cushman pre-pandemic. So Cushman was already moving on this in a big way and they had executive sponsorship across the C-suite. Pandemic came, never a good time for a pandemic, but it came at a decent time for Cushman because they were prepared. They had the foundation of governance, everything you need in a large enterprise to run a program. They had that in place so they were able to kind of just put kerosene on the fire when the pandemic hit with certain automation candidates. >> Because I often said that pre-pandemic, you know, digital transformation was kind of this buzzword. A lot of firms were sort of giving it lip service. But it sounds like Cushman actually had started down the digital transformation path and then obviously everybody was accelerated. If you weren't digital business, you were out of business. But but how tightly aligned, 'cause we heard this in the keynotes today, I'd like to test it. How tightly aligned is automation and digital transformation at Cushman. >> They're pretty synonymous really for us, right? So like it is really about bringing different types of technologies, whether it's like NLP. The other really interesting thing that we were talking about the keynote, right? There's just so much that is going into the UiPath platform that is enabling us and enabling the things that we want to do across the organization, right? So like natural language processing, document understanding, you know, cloud based items. Like there's just so much that we can leverage and it's really about that continuous process improvement. It's trying to make sure that we're aligning ourselves to the strategy that the organization is absolutely pushing, but making sure that we're doing it in smart ways, right? And that we're empowering our employees as we do it, right? So it's not just very top down from a COE, it's also very bottoms up, very citizen-led throughout the organization. >> So I think of this as a strategic initiative that happens over time. But how does Ashling, and Marshall, how do you engage with Cushman? Do you engage on a project by project basis? Do you have sort of a long term strategic arc that you're working to? >> Absolutely. >> How does that work? >> No, that's a great question. So we started project based, so we were a part of the co-establishment of the intelligent automation COE. So very outcome driven, top down approach as Dave mentioned. But we also had a wider aperture than just RPA. It was broader end to end automation experiences that was project based. We had so much kind of quantifiable evidence at that point that we wanted to go bigger with the program. Over time we matured into more of an agile DevOps methodology with the Cushman team. And Dave should certainly speak about the size of the Cushman team and how that's evolved over time, but- >> Because the two of you are in a partnership in terms of proving out the ROI of what you're doing. >> Oh, absolutely. >> Right? >> Marshall: Every day, every day. We all have numbers we got to hit, right? And that's just the reality of it. But in order to do that, you know, agile DevOps approach where you're, you know, releasing every two weeks into production, you need a dedicated team that has like a longer term roadmap that is coinciding with the Cushman objective. So that's what we have in place today, something we call build as a service and mROC. So kind of think of that as as plan, build, and then run. We're infused. You have to be infused with your clients if you're going to run an agile DevOps program. >> Is automation more self-funding? Marshall, I want to draw on your experience with ERP. Is automation more self-funding than other technology initiatives? And if so, why or if not, why not? >> It is, and it's a double edged sword actually. We talk about this all the time at Ashling. We've never worked in an enterprise technology space where there's more accountability to value delivered because it's so quantifiable and measurable. So every time a transaction runs you can measure- >> Dave: How are we doing? >> Exactly, I mean the ERP days, nobody questioned. They just, they thought we just have to move to S/4HANA, we just have to move to Oracle. >> We'll let you know in a couple years. >> That's it, yeah. >> I mean the stuff that we just saw earlier from Javier Castellanos, right, from Orange. It is very much like each transaction has a value associated to it. Each part of that transaction has a value associated to it. We're constantly monitoring the numbers of looking at our performance, right? There's very real value associated to maintaining business as usual for the 50 plus automations that we have in production, right? So like the business is really counting on us to maintain and to make sure that we're continuing to perform. But also that we're continuing to work with them to find additional value and additional opportunities, right? To make sure that we are saving money and finding dollars- >> But it's dropping hard dollars to the bottom line, right, that are quantifiable to your point. But what's the governor, what's the barrier to your ability to absorb whether it's new automation? Is it just expertise, talent, or you bandwidth? Is it the prioritization exercise and thinking intelligently about, you know not- >> Dave: All of that. >> So how do you, I guess you guys work together, but take us through that a little bit. >> I mean, we're constantly refining our approach. So we were just talking about our DevOps approach. You know, we started with I think maybe five or six different teams based on specific service lines. We modulated that recently to go to two teams, right? One specific to build and one specific to enhance. So we're constantly looking for and building new automations throughout the organization. And then also looking for incremental value to enhance the automations that we've got out there, right? So making them better, faster, making them more resilient so resolving technical debt, doing a lot of different things to make sure that we're as stable as we possibly can be. But it's not only that, it's really like making sure like we're just as pinched by everybody else in terms of like the great resignation and looking for talent. I think everybody here is basically looking for the exact same talent. And so it's really making sure that we have interesting work, we're doing interesting work, we're making people feel valued, and we're bringing value throughout the business. >> So I remember Bobby Patrick called me when he joined UiPath. He goes, "You're not going to believe what I'm doing now. You got to get on this train." And so I started looking to it and we actually downloaded, you know, the package and started playing with it. And we tried to do it with the competitors, we, you know, we couldn't. It was like call for pricing kind of thing. We're like, well that's interesting. But what we saw was my perspective, this bottoms up adoption. And I know there was top down as well. But then, I remember I was in the meeting when they announced the sort of process gold acquisition and then started, I said, "Okay, they're going for platform now." And then Microsoft came into the market like, okay, they got to differentiate there. Now you're seeing everybody, all the software companies think they should own every dollar that's ever spent on software. So SAP's doing it and ServiceNow. And so Marshall, from your perspective, how has this platform evolved? And then Dave, to the extent you can talk about it, how is that platform adoption taking shape within the organization? I mean, platforms are much more complicated than products and they require integration. How is UiPath doing there? >> I think they're doing fantastic in that category. If you think about, and it's been a natural evolution. They're not fighting inertia, they're following challenges of their clients, right? So RPA obviously came onto the scene hot, everybody understands the business rule driven automation value. Easy to, you know, make a quantifiable, tangible evidence with RPA. But exceptions happen in a business and upstream processes break that, you know, cause challenges with downstream automations. So what do you do? You have to go upstream. You have to have more automations, you have to have process discovery, process mining with process gold. You need to have the ability to have a better user experience interface, which we've definitely incorporated into Cushman when we didn't get adoption with certain automations that we like. You build low-code apps. People want that consumerization of technology in the enterprise and that allows them to adopt more of the automation which triggers the robots and then you report analytics on it. So that expansion's been pretty natural with UiPath and I think the next acquisition they just made with Re:infer's really interesting, 'cause now you're going even more upstream with communication mining, turning that into structure data that you potentially could automate or analyze so it's been natural. It's truly the only platform that we've encountered that can do all of this at this point. >> So a couple things there. You know, one is the nuance of adoptions, not just the function of the potential savings or, you know, revenue production or productivity. It's, you know, the experience because you got to have a great UI. And then what are you going to do with Re:infer? I don't know if you guys are adopting Re:infer but what do you see as the potential. Marshall and Dave, if you guys have visibility on it? >> I know we've talked about it Dave so I mean the potential's huge. I think it's going to be more of a question of change management for each organization just to feel comfortable with that. But I mean, think about all of the communication and the semi and unstructured data in an organization that comes, you know, via Slacks, Teams, emails. It's huge and it's significant if you can figure out the right identifiers that you want to trigger for your business. And then figure out is that something downstream we can automate or can we just analyze and make our business more effective, more efficient, or provide a better experience. So I think it's huge. We don't know how big this is yet, but we know that it's something that, I mean, think about Cushman, get brokers all day long that are communicating with clients and third parties. So it could be extremely significant. >> Sounds like a potential to eliminate email hell, but. >> Marshall: Heard those promises before. >> Maybe that's like the paperless office eventually. >> Well in our organizations, like 50, 40 to 50,000 people, you know, globally, right? And there are definitely service lines within our organization where probably it doesn't make sense for us to leverage UiPath and provide them the, you know, studio and low code, no code automation tools. But a lot of this NLP stuff and a lot of the content mining and the communication mining stuff, really has the ability for us to be able to sort of pinpoint opportunities at levels that we couldn't possibly do it before. So it was really very exciting to see the stuff that we were in there. I think when you start your organization, a lot of times you're a hammer looking for a nail, right? And you need to quickly move away from that. And so I think a lot of the stuff that UiPath is introducing, a lot of the stuff that they're bringing into their platform, really helps us to be moving away from that sort of orientation. >> Well when you think of this in terms of CI/CD, you know, people maybe have a better understanding of sort of the life cycles and, you know, the iteration calendar. Can you give us an example of something that went from an idea, something like, "Hey, I think we might be able to automate this process" through "Okay, yeah, let's do it." You try it, at some point there's sort of quality testing involved to make sure that it's achieving that we want to do. Can you give us an example of a process that you've gone through? And then how long do those things usually take? Are we talking weeks, months? What are we talking about from idea to establishing that, "Yeah, this is something we want to keep in place." >> Dave: We always want to make it faster. So we're especially always trying to find ways, especially upfront parts of the process. So a lot of the analysis, requirements gathering, you know, stuff that's not actual building. We want to make sure that we're shrinking that as much as possible, that we're also being comprehensive so that we're not building something that doesn't meet someone's needs, right? Or that just completely misses the mark. But I mean, invoice processing is a good example. We do that internally. Obviously, we have corporate accounting. We also do that on behalf of clients. And so a lot of times, you know, we're bringing some of the internal processes, we're using the technologies for document understanding, optical character reading, and machine learning. And we're doing that on behalf of clients, but we're also doing that internally. So to be able to use some of those processes and automations, sort of client facing plus internally, are big changes. Big changes for us. But I think the other thing too is like, we're always trying to make it faster and better. I think that's one of those also processes where we put something in place and we're constantly looking to enhance it, make it better based on the process that's out here. >> And you're applying automation to that upfront piece, the planning phase? Is that right? Or? >> Yeah, yeah, so a lot of it is about sort of the work that we do on behalf of clients. And there are teams who are specifically tasked to accounts. And so we're looking to find ways to make it easier for those accounts to get their bills paid, to get visibility into, you know, accounts payable, accounts receivable, their full end to end accounts lifecycle. And so yeah, we're doing that directly on behalf of clients and then we're doing that internally. >> How about the why UiPath question. Marshall, I think I heard you say that you're pretty much exclusively UiPath as your automation partner. Why? Why not play the field? Why UiPath? >> So I think it started in like 2017, 2018 for Ashling. We did an analysis of kind of an outside in of what, at that point was the big three of RPA, the vision and the roadmap and the open platform architecture of UiPath and just the self-awareness that, "Hey, we need to operate with other technologies in order for our clients to get the most value from automation." That was really the main reason, outside of the fact that we like working with UiPath, but it was just that complete vision of a platform as opposed to a tool. We felt like everybody else was more of a pointed tool and then UiPath had this platform approach and it was going to be necessary to go end to end like we all are trying to achieve. >> And UiPath continues to deepen that, right? They continues to support us with tons of new technology- >> How so? Can you be specific? >> I mean, when we're talking about document understanding, I mean, we're trying to leverage that for manual handwritten time sheets. We're also using it for, you know, Chronos integration, right? So like there's a lot of stuff that we're using it for and we can go to a single shop, right? To be able to do it, a single platform from a scalability and a supportability perspective, it's also a big game changer for us, right? As you start, you want to be able to scale, but you can't spend a ton of money supporting, you know, a hundred different platforms. You really got to invest and be smart about it. And UiPath for us was a really smart play. >> Are you budget limited relative, you're competing with other initiatives within the organization? Where's the funding come from? Is it from the business? Is it from IT? Is it a combination? >> It had been centrally funded and we are now moving into a different model. So we are constantly looking at, you know, the justification of value, speed to value, and proving it out to our business partners from all service lines and within all different functions of the organization. So we're at an interesting inflection point, but I think we also have a really good background that we're building on. >> I've been saying it all day, I've said it for years, at the UiPath events that they are awesome about putting customers on theCUBE and we love to hear from the customer stories because we get to sort of map what we hear in the keynotes and then test it, right, in the real world. And I also really love the fact that Marshall, UiPath always brings implementation partners so we can get the expertise and you have a wider observation space. So guys, thanks so much for coming on theCUBE and thanks for sharing your stories and good luck in the future. >> Thanks for having us. >> Appreciate it guys. >> Very welcome. >> Thank you. >> All right, keep it right there. Dave Nicholson and Dave Vellante live from Las Vegas UiPath FORWARD 5. We'll be right back right after this short break.