Transformation Every Day
00:20:55 · JP Haas
[00:20:55] S0: And importantly, we then also add additional context to this, wherever you have documentation, comments in the code, whatever that is. Right? But often even that is not enough. Because often the two meter the two meter truck rule is not... It's not documented anywhere. It's just in the heads of the business that was requesting it or the the consultant that that implemented it back in the day. And so whenever we come across these types of situations, we actually ask the user for input. Right? We basically flag that something is a bit of an exception, and it looks... That it's unclear why that that rule exists. We can we can then start capturing that knowledge from the user. And that I think is really important. Right? Because at that point, you're you're building you're building this living and breathing and ever growing intelligence layer that that keeps the knowledge about how and why your system and your company operates the way it does. You keep that in a platform that you always have access to and that doesn't leave the organization. And that's really, really important, we think. So that... That's how we that's how we approach it. And what we what we're seeing as a dynamic is that teams are starting to work differently because the having that that foundation to to argue about, right, and to discuss between teams in a much more transparent way, it flips the dynamic. It flips the dynamic from we're flying blind and we we need to we need to try and ensure that that every capability is captured to I know all of the capabilities are captured. Now let's talk about how we can get better as a company.
00:22:36 · Johannes Langguth, JP Haas
[00:22:36] S1: One sentence I read about you, I'm not really sure if you were stating it or if it was said about you, so you can comment about this, but I really liked it because I think it describes very well what you are what you are doing is AI operating system for enterprise IT. How should somebody who has not crossed roads with Conduct AI already, how should somebody like that who said, I really need that. And what I heard about this kind of, okay, I learned to understand my system based on the custom code. What are the first steps with Conduct AI? [00:23:09] S0: The first steps are thankfully very, very quick. And that's one thing that our our customers are always so amazed by and frankly surprised by because in the past and in the enterprise IT space, just because the stakes are so high, everything used to take a long time. The platform we've built works completely out of the box and is set up in a very rapid and hands off way. And that means you only have to have to install a small a small ABAP program on your SAP system. And the rest is happens, know, completely completely hands off. We can we can onboard and give you that level of transparency and insight into how your system operates within twenty four hours. And we've done this with, you know, some of the biggest Fortune five hundred and one hundred customers in the world, and it's always worked like that out of the box to to the incredible, you know, amazement.
00:23:09 · JP Haas, Johannes Langguth
[00:23:09] S0: The first steps are thankfully very, very quick. And that's one thing that our our customers are always so amazed by and frankly surprised by because in the past and in the enterprise IT space, just because the stakes are so high, everything used to take a long time. The platform we've built works completely out of the box and is set up in a very rapid and hands off way. And that means you only have to have to install a small a small ABAP program on your SAP system. And the rest is happens, know, completely completely hands off. We can we can onboard and give you that level of transparency and insight into how your system operates within twenty four hours. And we've done this with, you know, some of the biggest Fortune five hundred and one hundred customers in the world, and it's always worked like that out of the box to to the incredible, you know, amazement. [00:24:12] S1: And and how can somebody who has not yet crossed the roads, how can imagine these kind of steps? Do you are you looking for organizations who are now, okay, I am now in the beginning of a big transformation. That's why I need these kind of capabilities now. Or are you also seeing yourself friends with organizations that like, okay, I may have already or I'm past one of many transformation because I have more a stepped approach. I'm at the plateau right now, and I want to make the next steps because the first thing maybe was just like a platform change or something like this. Where do you see your target?
00:24:47 · JP Haas
[00:24:47] S0: We work with customers across across any SAP lifecycle stage. So before transformations, in transformations, beyond transformations just in the in the ongoing operations stage. And let me tell you why. Because you said earlier, you know, AI operating system for enterprise IT, and that's really what we think and are convinced that we are, which is we are the platform that makes IT much more, you know, digital, AI enabled, and quicker in everything they do. If you zoom one level out further, what is it that we're really doing and and why? We think that there's a there's an amazing opportunity to ensure that the way that the business wants to run and what it needs can be implemented and realized in the software that it runs on in perfect lockstep. Right? So whenever the business needs something to be changed about how it runs and how that's implemented in the system, that today takes a long time to actually realize. That's the ongoing state of my my procurement needs a new feature. It gets passed to IT. They try to implement it. It takes a bit too long. Yeah. And and you... These two things are out of sync. The same thing can be said about a transformation project or a migration project. Now the IT side needs to change something about the technical landscape. You're changing an ECC system to an s four system. How that impacts the business can also lead to these two things being out of sync. Right? IT and business are not in lockstep anymore. But if you you work with Conduct, and if you if you can if you can deliver that operating system for IT that makes sure that everything that can be changed and implemented at pace now, these two things are moving in perfect harmony and at perfect pace.
00:26:49 · Johannes Langguth, JP Haas
[00:26:49] S1: When you look back at your experience that you already have done in your customer interactions, what are considering that the two best stories where your own system surprised you yourself the most with the capabilities it shown and with the moments that you generated with that? [00:27:10] S0: I can think of two amazing... Well, more, but I give you two. Number one, we worked with a customer that identified a bottleneck on the production line. And they didn't understand why a certain order type always took six days to be scheduled and actually be produced, even though they expected it to be only two days. We were able to find out that two different edge conditions were interacting with each other in a way that led to this particular order type always taking six days to be scheduled and not the two days that they wanted. And that was hidden in some kind of custom code line, some edge condition that no one knew actually had an impact on the on the other one. And and so we we were able to figure that out and actually suggest how you could resolve that. And that has, you know, immediate operational impact on the company. The second thing is a company that that was working on on a performance issue in an SAP system system that had been reported by users, and they'd been looking for more than a week into what were the different what were the different causes that that might be that might be be leading to this. And we were able to figure out what exactly was the the cause for that performance issue and, again, suggest the fix. And within within one afternoon, I mean,
00:28:36 · Johannes Langguth
[00:28:36] S1: is literally on the first day of the pilot working together It's what they threw at the at the system in order to test to test its guts. They were able to to to completely resolve that. And and I really like these stories because to to reflect on that, because in the first part where you said like you have some had some interdependencies that nobody knew about and you found out about this. Those things exist a lot and they are nowhere documented. You just have to rely on people who may have known that, okay, I made something five years ago, which could have an effect to that what the other colleague made something eight years ago. But in most of the cases, nobody's aware of anything. And the the knowledge that you are not aware of that is, from my experience, quite common at customers. And this is one of the reasons, for example, why so many transformations get delayed. Because, I have, for example, one customer or I had one when I was at SAP, I remember it quite well. Big German company, they had around 120 ERP systems. And they were completely stuck like like a like a like a rabbit before a foxhole because they said, like, I I really need to start. I want to start. But I have the problem when I cut something over there, yeah, on the right side. If I cut something off because I changed the system, I do something new. I have absolutely no clue if something on the complete other side of my architecture falls down. And this kind of fear was like completely locking any progress in these kinds of of of initiatives that the customers do. And what for me is the good... The the the good news about your existence in that way is that you can can... With this possibilities and capabilities like that, gave more momentum to so many stock initiatives because you are giving transparency. And if I add something of a of a second example, the problem that that we always have in the SAP ecosystem is if you look at the why, what, how dimensions that I quite like because it gives you a 360 degree view on problems. The SAP ecosystem is traditionally very strong in the what because SAP can explain what their software is doing in the standard and can explain it quite well. Concerning the why, it gets a little bit different. But the thing that is more or less the most relevant for many customers in proceeding that way is the why topic. Sorry.