Kinaxis Inc. (KXS) Earnings Call Transcript
August 11, 2026
Earnings Call Speaker Segments
All right. Hello, everyone, and welcome to our webinar today. Our topic today is the next phase of supply chain AI from promise to accountable outcomes. So I'm excited about the topic today. My name is Justin King, I'm Field CTO with Kinaxis. And we have the privilege of having some interesting support. A research director from IDC, Eric is joining us with some really interesting research that he's done. And this isn't across a couple of dozen of respondents. This is thousands of companies or thousands of responses across companies around the world, different industries, different geographies. So really excited about the perspective that we're going to get today.
So as we kick off, Eric, why don't you introduce yourself to everyone? And maybe just give us a little bit of perspective of what you guys do generically, and then we can dive into this particular research project that you are working on.
Yes, of course, excited to be here, excited to talk about, gosh, what's really kind of a front-of-mind concept for all of us. So for those that don't know me, I actually kind of come more from the practitioner side of supply chain. I worked at Nike for 21 years, just kind of navigated all parts of the company, different geographies and functions, and as you can imagine, you might do in that amount of time. I have a pretty deep background in supply chain planning, in particular, and have kind of brought that over to IDC, where we -- as you mentioned, we research across just about every company in the world that has a supply chain. And we kind of dive deep on data and information and just bring that sort of practitioner side that I bring, but also IDC brings some really heavy data focus throughout supply chain and gives us an opportunity to kind of spot trends, have some insights. We work with a lot of people who kind of look like customers of people like yours. So just nice to be here, and excited to chat.
Yes, absolutely. So this is not going to be a sales pitch, right? This is really a research-led discussion. I'm going to give some perspective on -- from what our customers have been talking about and asking. And of course, opinions, there's no shortage of opinions in AI and what it means and what's real and what's not, what's hyperbole and how organizations can start to be successful with AI. And I think that's really where some of your research starts to uncover where supply chain leaders are, where their heads are at. And we're going to talk today about what comes after initial adoption of AI. And it's the stuff that's not as exciting and sparkly and shiny, right? It's the things like trust and governance and data readiness and guardrails and human oversight and maybe most importantly, how do we get to real measurable outcomes, right, that are aligning to our business objectives and our KPIs. And I think there's a lot of nuggets of important information that we can extract from the research that you guys are doing. So let's jump right into that. Eric, why don't you kind of set the stage in terms of who was this -- what was your out -- who are you reaching out to? Who's responding to this survey? And I think what you found is that in terms of AI readiness and adoption, most everyone was saying they had started something, but at the same time, no one was really saying that they were a leader, right? Everyone was kind of clustered together somewhere in the middle. So I'm curious on what's your perspective in -- what does that tell us, right? Where are companies on their journey? Do you think we're overestimating, underestimating where you're at? Do you think that's fair in terms of where the market is today with AI? So why don't you start with painting the picture of this research project and who your respondents were and some of the basic learnings in terms of the pool of responses?
Yes, yes. Great point. And actually, before I even answer that, maybe I'll even go back because you just triggered kind of a thought to one of the many roles I held at Nike. I was a Strategy Director for a little while. And I like the way you just worded something, which was sometimes maybe we're not talking about what sounds like the glamorous and exciting stuff. And that was the way I viewed that. There were times where people would come to me and say, "Oh, you're a Strategy Director, that's really cool. How can I get that kind of job?" And I would often tell people actually a lot of it is the discipline. A lot of it is building a strong foundation. And when you do that, then you have something you can really build a larger structure on top of a strong foundation. So sorry, you just kind of reminded me of that thought. I thought that was worth underlining because I think it's going to show up through our conversation today, too. I mean, you just mentioned adoption. And I mean, probably most of our listeners today, I mean, are like us. We've all been dabbling with whether you're using ChatGPT or you're using Claude or whatever other tools you're using. And then, of course, supply chain vendors are now embedding these tools within our supply chain functions. We've all kind of played with it. So to your point, we were asking, I think it was over 2,000 respondents around the globe, kind of all geographies, all industries, different levels of companies, executives, directors, different functions like logistics and planning. And we had almost 98% of people say on some level, they're touching AI or AI is touching their supply chain, let's say. And so the question isn't really adoption, per se. It's just kind of how much, how far. And then in particular, are we realizing value from it. And I think you maybe said too, so maybe forgive me if I'm repeating, but we saw through this data that only like 12% of the respondents, almost barely more than 10% kind of say, hey, we're kind of in the lead here and would -- I think back to my Nike days, we were very competitive. We wanted to be at the leading spot of a lot of things we did. And so there's only like 10% of companies saying that they view themselves as a leader in the space. So it's clearly something emerging, and people are still figuring it out. And then something else we saw -- and forgive me for maybe throwing around a few numbers, I'll flash up some slides here in a minute to try to land home on those. But like 50-plus percent, more than half of companies are saying, what's actually slowing us down from going farther and really becoming a leader is just a trust issue with our data, with our systems. Do we even think as we play around with, say, agentic AI, is it really going to do what we want it to do? Is it going to give us the outcomes we want? So kind of seeing all of that.
So okay. So you hit on a really interesting topic, right, and that's trust. And what we're seeing, and even as a software company, what AI has enabled is it's so much easier for us now and for our customers themselves to do a pilot, right, to do a POC and to kind of do some vide coding and say, look, this is the realm of what's possible. Which is amazing because it's democratized access to our data, it's democratized access to mathematical solves and even like machine learning routines and such. So we can quickly and easily see what's in the realm of possible. But of course, that's being built with no security in place, no governance in place, no logging, no -- none of that structural stuff that I was talking about that's going to enable that trust, right? So as you look at your response, I think you said about half of them are saying, "Hey, trust is a real barrier." What do you think companies are most concerned about, right? Do you think it's like a technology issue? Or is it more of a process, governance, operating model, that sort of thing?
Yes. And I think back to those days when I was maybe a Strategy Director, one of the issues with really realizing value from your systems is, is your organization even ready? Do you have the skills? Do you have the ways of working even across functions? You mentioned democratizing, I mean, as agentic AI, as large language models, different things like that, as they help us to cross functions, if I'm an executive at a company, I'm asking, well, okay, but if I unleash all of this, are my teams even going to work together? Are they going to get the right outcomes? What's happening to roles? How do we shift roles? Do I have the skills to leverage all of this? So I think that's just part of the conversation. And if I may, maybe I will share something. Give me one moment, apologies. Hopefully, this is showing now. Can you see that on your screen?
I do, yes.
Okay. Well, so I think one of the things -- I'm going to come back and answer your question, too. But -- so we see -- we talked about everybody's piloting. And I like that you said proof of concept, whether you want to call it walk before you run or whatever it is. But companies are saying, well, let's at least start to see what we can do in that sort of art of the possible. But what's interesting is today, if we ask these 2,000-plus respondents in companies all around the globe, like I said, every geography, every industry, every company size even we looked across, we get consistent answers. You might think maybe some more mature companies might answer differently than others. But we actually got pretty consistent data where we see that companies are kind of saying, today, in terms of automating things, having autonomous supply chains, we have these conversations about always-on supply chains and lights off warehouses and things like that. But the actual autonomy right now, companies are saying it's only like maybe 6% have any form of sort of, I'll call it, real autonomy. Meanwhile, 40% say in the next couple of years, they aim to get there. So that's a heck of a jump. And so the question then, if they're telling us out of one side of their mouth, they're having problems trusting the data, trusting the tools, maybe even trusting themselves to get the outcomes they want. But then they're also saying, yes, in the next couple of years, we plan to just kind of 7x the amount of autonomy we have. So one of the things I think -- and here's where I'll kind of come back to your question is if we look at it through the lens of governance, I'm asking even from my old roles, people I know, I'm sort of challenging even -- it's not just the technical side that needs to solve this. I would suggest even there's sort of three, I don't know, legs to a stool or something like that, that the capabilities are coming. The tech is advancing perhaps faster than we've even sort of prepared ourselves to use it. Now that -- there's an optimistic side to that because that then means, wow, there's a lot coming that I can really improve my supply chain and improve the outcomes. And so I think what needs to happen is there's sort of a business strategy. Where do we think we want to even use these tools, where do they best apply? And by the way, I know this slide says agentic, but we're talking AI overall even. I would even almost expand out and talk about a complete AI strategy. Where do we believe from a business win, and there's even force ranking from time to time. Are we going after logistics? Are we going after, I don't know, warehousing? Are we going after supply chain planning? Where do we think we really want to sort of place our bets here in terms of the business side? And how are we working together? That matters. But then also, what I'm suggesting is there's two other pieces. One is the technical side of things, where even what are the guardrails for these tools? What are they allowed to do? When is human in the loop? We talk about that. How are we going to allow autonomy versus where do we actually want to engage, like I said, with sort of human insights. I think it will be something we may talk about today, too, where are we bringing in domain expertise from the humans and things like that. And then I think an under sort of, I don't know, an undertracked side of all this, we all know that there's some kind of economics emerging here in terms of the use of compute power, whether it's tokens, whether it's value-based pricing, all these things that we're starting to see emerge. So what are the guardrails even around -- I myself, the first month, my company gave us the sort of, let's call it, Claude tools. I tapped out my tokens within like the first few days because I was just trying to do all kinds of things with it. So how do we put guardrails around even where is the spend and how much are we spending? So I think forgive me for rambling a bit there, and maybe I'll even stop sharing here for a minute. But I think just companies maybe contemplating their governance around these issues and how do we even -- what's our own internal strategy. Because then that informs even what are the partners we work with and how do we work with them and all of that.
Yes. I think to -- from what we're hearing from our customers is the magnitude of the impact of the decision can change even inside of supply chain, right? And so you could have thousands of decisions made maybe inside of a warehouse that are much lower risk. And you can look at that in an aggregate and say, okay, is efficiency increasing, is accuracy increasing. But then you can pivot to the polar opposite side and say, well, in planning, if one decision means I'm cutting a $1 million purchase order, well, the risk and the trust behind that decision has to be -- are both much higher, right, because there's real constraints in play. If they were not considered, then I cannot produce the finished goods. There's customer commitments. Like if I miss this customer shipment, there's financial trade-offs. There's operating all these different things that are behind one decision versus just being able to roll it up and look at it in a consolidated number. So planning is a really interesting one, I think, because of the magnitude of information that's behind every decision, the context that's behind every decision and in turn, the risk of making the wrong decision. So I agree with you, I think trust is a big part of it. And I think that then leads a little bit into the data side of it, right? So does your agentic system have the right data to make a decision that you can trust. And I think, if I'm not mistaken, your data had some pretty strong opinions from your responses on how important -- well, not only how important data readiness is, but maybe it being a bit of a barrier, right, and kind of holding companies back a bit. So what can you tell us from what your respondents are saying about maybe their readiness and how they saw the importance of their supply chain data in order to move into more agentic decision-making?
Yes. I think that question definitely came out pretty strongly in the data, Justin. It's where we look at -- and I would even go back. Data quality has just kind of -- it's an evergreen field. It's something we always need to focus on in supply chain. We had data management teams in my time at Nike. I'm sure it's still there. It's something we need to keep focusing on. So I almost look at it as a coin with two sides because on the one hand, this survey work that we did in the field would say 62% of people, almost 2/3 of our over 2,000 respondents are saying that better data quality, better integration would actually be an accelerator for AI. So there's certainly a focus we need to have on data. And I would even say, again, from that sort of business practitioner lens, we need to find the right partners, too, that are helping us with that and have contemplated these issues and thought that through. But on the flip side, I would also say -- and now just personal opinion, this is not necessarily the data. I wouldn't say that we should use that as an excuse to not move forward either. Because sometimes at IDC, I think we find -- some of us have a personal point of view that even the act of moving forward with projects in this space sometimes itself creates improvements in our data quality. And so it's kind of like it's a chicken or the egg kind of discussion. Do I have to clean up my data to use AI? The answer is yes. But does the act of moving towards these solutions also kind of yield sort of data improvements? And the answer is also yes. So I guess it's something that absolutely the sort of survey findings have sort of fleshed out in terms of AI readiness. It's kind of a what's my data quality question. But I also think it's not this like go/no-go checkpoint. It's just something we need to really solve and continue to move forward.
Yes, that's a good point, Eric, because AI can even help us with our data quality issues, [ can it not ], right? So you've heard concepts like the self-killing supply chain where maybe you're working with a certain lead time. And you can look historically and figure out, am I building my supply chain plan based on accurate information. AI can help us project it, detect seasonality, all these different things. So I couldn't agree more, and it's -- I think there's two ways to look at it. One is more traditional data quality, like is the data there? Is it proper in the field within some sort of bounds? And then it is the context correct, right? I mean, are we defining our constraints correctly, our dependencies correctly, our demand signals correctly? And then you got the unstructured data side of it, where there's just having unstructured risk signals available, right, which can give us directional guidance to picking alternate suppliers in those sorts of cases. So there's a lot of use cases where AI can use not clean, structured data to help guide decisions in the same way that more structured data and operational context is important as well. So as we -- so we kind of covered the data side of it, right? And now we're looking at the foundations that are in place, and now we're looking for decisions to come of that. But then we need to balance that with measurable outcomes, right? It's not just better decisions, but it's about the right KPIs, the right business objectives and making sure we're just not using technology for the sake of technology, but we're actually achieving our business objectives. So in a way, AI needs to be accountable to the business, not just accountable to technology that checked the box, we successfully deployed it, right? So I think some of your findings were -- we were kind of highlighting the clear ROI, one, is important; and two, it would be a driver to accelerate that investment, right? As we look at it less about decision-making and more about achieving business objectives. Did you glean that from the data as well? What are you hearing from -- in terms of the [indiscernible]?
Yes. I think both from a data standpoint, yes. And then even anecdotally for myself, it's -- as executive teams or, let's say, execution teams are clear on your -- whether it's your metrics, your KPIs, your strategic imperatives, whatever it is at your company, when we clearly defined the goal, we had a lot better chance of achieving it. And I think we've even seen that -- I'll just even again say for myself in my own piloting with AI. When I don't get the outcome I thought I was going to get, I often find, oh, okay, I didn't make it clear, what I even really wanted from you. I'm sort of using quotes as the AI as a person. But -- and so I've learned to better articulate what the thing is that I want out the other end. And so now that's back to that governance and that strategic role of are we aiming at days in supply chain? Are we aiming at speed? Are we aiming at cost? What is it exactly we're solving for? And of course, we've got tools now that are starting to even maybe solve for more than one variable at a time, but there's still -- what's my strategic priorities? What are the real outcomes I want? And so you're right. I mean -- and I'm just kind of looking down at my notes, we had -- more than half were kind of saying, "Hey, if I'm going to move forward with these tools, I want to have what's the clear return I'm getting." But also, there's a lot of folks who are saying, "I'm sort of not sure what my business case is just yet, and so that's causing me to maybe slow down a little." And so there, again, I think whether it's through the lens of business governance and knowing clearly what my strategic priorities are so that I can even inform the AI itself to try to solve for those. And that's how it becomes accountable. I have to even know what my goals are to hold it accountable to my goals. And then besides that, even having a clear business case, why am I implementing these tools? Am I trying to have better execution across functions? Am I trying to reduce my days in inventory? It's just important to know what we're even trying to solve for.
Yes, that makes a lot of sense. So would you say that have we just not figured out how to measure the impact of AI the right way yet? Is that what it boils down to?
That's hard. I mean -- and that -- let me be fair almost to AI. I used to manage strategic projects, and measuring the real impact of them has always been a big issue. Like can we really define ROI of a specific project? And there's ways we all got around doing that, and there's best practice, of course. But yes, I think it's a good question you asked, like how do we even rightly assess what the AI did and what the outcome of it was? And I just think that continues to be a part, again, if I could sort of belabor the point of governance, like, okay, how am I going to measure this? How do I look at it? How do I determine if it did what I wanted it to? These are just kind of the things I need to be thinking about.
Yes. No, that's really good. Yes. I think -- so if I were to summarize, right, I think it's better insights, faster recommendations, increasing that speed does not necessarily correlate to getting better results, right? And so there's an opportunity here for organizations to, I guess, close that gap between just making a decision and genuinely achieving those business outcomes and objectives, right, that move the needle.
Well, it's interesting. And here, I'll be fair to people in your role, for example. We all ask on the business side, I want to do it faster, I want to do it easier. I want to do more. And so those are specific outcomes. You just talked about, can I get to a decision quickly? I don't remember your exact words, so I don't want to put words in your mouth. But I might measure from, "Oh, wow, it used to take me a week to come out of an S&OP cycle and answer an executive's question." I've literally been in those meetings. And you go back and you have meetings to follow up from the meeting and you have slide presentations you're building and questioning, and now the data is stale a week later. So it's certainly a value from some of these tools to get to information quickly, get to decisions quickly. But I think there's something underneath what you just said. And again, I don't want to put words in your mouth. But just because I get to a decision quickly doesn't always mean it with quality. And so there's both sides of this. And I can imagine from your side of the world, we're not so consistent on the business side, let's say, of demanding tools that give me automation, give me speed, help maximize my resources. But then on the other hand, am I really actually testing for, oh, was this the decision I wanted to make? Maybe it would be worth waiting a week. If I took 2 days of inventory out of my supply chain, there's a real value to that. So of course, we're all going to say we want both hands. So give me tools that are fast and accurate.
Yes. So we're ambitious, right? I think that's what you're saying. And you talked a little bit ago about, I guess, the ambition a bit outpacing readiness and seeing that in some of the data. So as an organization, like how do I decide when AI should come in and help me -- just recommend and give me guidance, when AI should help me act, right, and go ahead and do things autonomously? And maybe somewhere in the middle, like when humans should take the recommendation and take some guidance, but always be approving each step, right? That's kind of the governance side of it and the gaps there. So what's your view? And maybe, did the data tell you some things about kind of ambition versus readiness? And how do we land on deciding where to inject AI in this process?
Yes. Part of it is that governance, for sure. It's -- I'll go back. If you had -- maybe there's some monetary guardrail, for example. Like if I'm making a decision to purchase $1 million of product versus I'm making a decision to start a $1 billion project or something if I was in project manufacturing. Well, that's very different. And so there's some sort of scaling of decisions. And deciding for each company and each industry, that's going to be different. So I can't necessarily be overprescriptive about that. For your company or your industry, that -- it needs to be contemplated. Where are we okay allowing some automation, where do we feel like we need to be involved in the decision. And that's actually just kind of a roles and responsibility discussion. So if we kind of look at it that way, these are conversations we've had for decades in business. What are the roles and responsibilities? When does something need to escalate up the chain? When can you make a decision at your desk, if you're a junior person, a middle executive, a senior executive? Now we're just making that decision with agents in a way having the role. And so there's sort of roles and responsibilities and, I don't know, size of decisions governance piece. And then I will just kind of circle back on the data quality part again that -- I think there's a testing or there's some kind of internal effort and an effort with partners, too, to say, am I getting the outcomes I expected? If I do -- if 9 times out of 10, I've proposed something like a small PO change, let's say, okay, you're going to change the mode to airfreight on something, something like that, or reduce this purchase order by x units. If there starts to be a certain sort of statistical acceptance rate on some of this stuff, then if I was back in my roles leading teams that were planning around the globe, I'd say, hey, if we -- 90 times out of 100, we've accepted the recommendation, maybe we need to start thinking about automating that, too. So there's a lot of elements of roles and responsibilities and data quality that are just going to keep being in every part of this conversation, I think.
Yes, absolutely. Yes. We don't want to slow down because the opportunity is certainly there. But in all of our development and rollout, we have to make it safe. We have to make it explainable. We have to make it useful. We have to make it tied to a real operational environment. And someone said autonomy without governance creates risk. But governed autonomy creates confidence, right? And I think that's what we're looking for, for our team.
And by the way -- and forgive me for interrupting, too, but you've just reminded me something that I think is really important for anyone listening to us today. And I'll sort of like come from the place of having had roles like this. It's become my perspective, it's an evolving perspective that we give humans grace and we give machines a lot of judgment. And the reason I bring that up, you just mentioned explainability, and that is very important. We need to understand why it was a decision. But I think we're starting to kind of embrace the notion of acceptability, too. And let me say what I mean by that. Like take a Tesla automated car. I literally have two teenagers in my house. And so we've moved to the place of their driving. And it's like, okay, as a dad, you wonder, are they safe and have I trained them well and all of this. And if you look at perhaps automated driving, when we notice it making a mistake, it's headline news. On the other hand, if we looked at it statistically, it might actually be safer than my teenage drivers. So what -- where is the level where there's some kind of acceptance, let's say, back to these PO changes? If it turns out that it can do it more accurately, then maybe I'm freed up to do higher-level thinking and -- rather than sort of use fear-based thinking on, well, it got this one wrong out of 1,000. I might look at that and say, actually, that's still 99.9% accuracy. Maybe I can accept that. So just sorry for kind of tangenting on that. But I think on all of this, as part of the governance, there's even a contemplation of what's our rate of acceptability or something, what's our accuracy? And if it's within these guardrails of accuracy, I'm good.
Yes. No, that makes sense. Yes. So let's dive into that kind of the human side of it, right? As we're evaluating and as we're -- and maybe even evaluating our changing roles, right, as this technology comes in. I think some of your survey questions leaned heavily into like how it's going to change individual roles and such. Did any of that surprise you? I think I saw all the way as much as 80% seeing it more opportunity than threat, right, which I think that's a good thing. Did anything surprise you about the data that you saw coming back?
Yes. And so much so that myself and some others at IDC have even kind of wondered if we need to shift some of our perspective. We talked about sort of, I don't know, roles dis-ease and discomfort coming with AI. Am I going to lose my role and these kinds of things. We're starting to wonder if it's more like role clarity questions because to your point, we saw in this data, and we've seen in a couple of other areas where the level of optimism is actually higher than I've expected. And I even think that I've experienced this myself, where I've done some projects using agentic AI, and it's actually kind of moved me into doing the higher order thinking of being a supply chain domain expert, let's say. And there was even almost -- this sounds kind of funny to say, but there was almost a joy for me of, "Oh, I got out of the mundane work and I actually really got to use my higher-level thinking. That was kind of fun." And we're seeing that in the data that people are not so much saying I'm worried about the future as saying, "Oh, this is kind of interesting. I'm sort of anticipating being able to do more of the things I'd rather do." And I don't want to sort of sound Pollyanna here. We all know there's a discussion around our roles changing, how is AI scaling? What does that mean to the workforce? And I think we have to have those conversations. But definitely, if I just take an objective view of the data, it absolutely came through that here's over 2,000 people overwhelmingly saying -- like you said, it was north of 80% saying they have a positive outlook of where AI is going to take their roles and how they're going to interact with it. So I found that pretty interesting.
Yes. I think when you position it the right way, and you did a great job of that, it should build excitement about what you will be able to do in the future and how you're going to be able to leverage your skills in the best way for the organization and be recognized for that. What skills do you think are going to matter most as AI becomes more embedded in planning, decision-making, all these supply chain areas?
Yes, I'm really glad you asked that question because in my head, I was thinking, do I interrupt him again? Because I had another point I wanted to make. So perfect question. I kind of glossed over the word domain. I really think it puts a premium on specific expertise. Like I'm a logistics expert or I'm a supply planning, demand planning, inventory expert. I know maybe supply chain and finance, so I can really work in S&OP, things like this. Because at least so far, I'm finding the ability to supercharge oneself in a way to take these tools and now bring my brain to it and kind of come up with whether it's ideas on shifting my supply chain, building a better plan, and how would you even know what outcomes to seek if you don't understand your area of supply chain. And even things like, well, we made that decision before and that didn't work out so great. Like where is the knowledge of some of these kinds of things. So I think the combination, and that's -- here, I'm really guessing. This isn't data. Let me kind of preface this as a guess. I'm guessing a lot of the optimism comes from that place of, oh, I can bring domain expertise. These tools are going to kind of add horsepower. They're becoming -- I'm becoming more powerful at my job if I partner with these tools. And there's some kind of partnership outlook, I think, on these. But so -- forgive me for rambling a bit, I'll come back and just -- I think your question really was what are the skills. I mean, can I think analytically, can I guide tools to the tools themselves realizing a good outcome? Can I sort of input my domain expertise as I partner with these tools? I think these types of skills. So it's like AI skills. But if you only had AI skills and didn't know supply chain, I think the marrying of those two is very important. And that, for me, comes back to that business governance of what's my organizational plan? What's my skills plan? What's my training plan? How am I going to accomplish these outcomes by preparing my organization?
Yes. Yes, absolutely. So I like that because we're kind of getting into real practical guidance here. Maybe as we wrap up the discussion, we kind of -- we land here. We talked with a lot of different things. We've talked about how agentic systems and agents are valuable when they're grounded, right, in the business context, the supply chain context. Good, trusted data when you give it clear guardrails, when you give it defined work to do, right? So you need to surface issues and evaluate these different options, coordinate next steps, support my decision-making, that sort of thing. And we're moving away from just kind of blanketly saying, okay, how do we throw this AI and automation thing at this, but we're saying, okay, where is the opportunity? Where is the outcome where I can apply AI safely and help my teams move towards outcomes that are tied to KPIs and business objectives, right? Meaningful movements of the needle, if you will. So with all of the hype that's out there, but now some of the practical things that we've talked about. How do you think leaders should think about AI agents, automation without getting caught up in the hype? Like how do we keep this rooted in practicality and what we can do to scale our organizations responsibly?
Yes. I think there's a piece here where unless someone really thinks you're going to build everything yourself, and that's personally -- I wouldn't recommend that -- then there is kind of a step of finding the right partners, too, who are doing the type of work that you feel achieves those supply chain outcomes. And I've got certainly a biased view here. This is both in the data, but then also because of my background that you could pursue, let's say, strictly AI type of partners, you'll get some gains there. I think there's something there, especially in terms of productivity. But for me, what I feel like we're seeing in the data, what I hear when I speak to -- I get inquiries from different businesses around the globe, I feel like I'm hearing that there is a desire to find technical partners who understand supply chain. And I personally think that makes a ton of sense. I would be looking for that if I was a decision-maker in those spaces. And so I think that's probably part of the next step of even understanding, okay, what exists now? What is in the road map for the next couple of years? How do I prepare for that? How do I prepare my organization and my budget, but also, how do I have the right partners who are going to kind of get me there? And I thought through all these same things we're talking about. Have they thought through data quality? Have they thought through outcome-based thinking and actually having tools that are not just helping things go fast, but are actually achieving the right outcomes? And maybe even tools that start to incorporate the guardrails that we've talked about. So I think that's a big part of just finding the right partners to kind of, I don't know, go on this journey with.
Yes. Okay. So you mentioned something really interesting there. And I think your survey data had this as well because you were asking the respondents to rank how important like the, call it, the math side of their skills, right, the optimization, the AI capabilities, these sorts of things. But then you asked them about deep supply chain expertise, right, the domain expertise. And they were scoring like almost the same or very, very close, right? Why do you think that is? Because some people would say, you know what, hey, we're just going to go and find the technology partner that has all the tools, and we'll just build whatever we want. But it seems like folks are balancing that with deep domain expertise. And of course, we're talking about supply chain.
Yes. I think there's been some lessons learned in the last couple of years. And here, I want to be thoughtful. And so maybe I just won't name names, but there are large technology players who thought, well, we'll go over to supply chain, and I don't know, like you said, bring in kind of a technical expertise. And there were some -- I don't know if you want to call it stepping of toes or there are some lessons learned in terms of, well, you can't just throw tools at supply chain and expect these outcomes we've talked about. And so that's even part of the guardrails is companies -- and to your point -- it's an opinion of mine, but in this case, it's also in the data, where these 2,000-plus folks in supply chains around the world are saying, they feel like they're finding better success. And yes, we need the technical expertise, we need the tools. We all understand AI is this big wave we're riding right now. But supply chain AI specifically is what's going to solve supply chain needs. And again, I'll just sort of own my bias there, being a supply chain guy, I even have a masters in supply chain. But I do think it makes sense that if I was finding a partner, I want someone who has sort of been in the weeds of supply chain and understands what it takes and understands how to solve for the outcomes I'm looking for and understands multi-echelon inventory optimization or understands having, I don't know, if I was a large company, having dozens or even hundreds of distribution points, even thousands, what does it take to plan all of that and manage that well. And so I think, to your point, people are saying it's [ supposed to end ]. I really want someone who can deliver me technical expertise, and I really want someone who can come and be my partner who understands my supply chain, and that definitely has shown itself in the data.
Yes. That totally makes sense to me as a technologist because if I'm working with AI, one of the first things I have to do is if I'm going to throw a bunch of data at it, I have to give it the semantics of my data, right? I have to give it my -- the [ anthology ] and how all of these things relate. AI has to understand how my business works. So it only makes sense if I'm going to find a partner to help build some of this stuff out. Likewise, they need to understand the complexities of the supply chain, like how my decisioning actually works, how our business workflows operate, how our people work, and ultimately, what it means when I say I need these outcomes, right? They have to understand those things. Otherwise, you're going to get...
Well, I can tell you, too. I mean...
Sorry.
Well, expertise just matters. We're back to expertise a little bit, too. Like I had an example recently where I was experimenting and building kind of a deep analysis of a company just thinking about should I even invest, for example. And it happened to be a company in an area that I'm an expert in because of my time at Nike. And so I was challenging the AI with, well, did you think about this? Did you think about that? And it was consistently coming back to me saying, "Oops, you're right, I should have thought of that." And I'm sitting here going, "Well, okay." So clearly, you're not to the place where you have that domain expertise in this particular field. And I don't want to name the AI or the work, but I think it just continues to illustrate everything you just said, where if I can bring someone who can -- I think you used the word semantic. I think that made a bunch of sense to me. Where there's context, I can get better analysis.
Yes, 100%. All right. So as we kind of round this out, let's assume for a moment that those that are listening and watching are just like those that responded, right? Because it seems that the respondents were all starting, but not experts, right? We're all in this place where we're trying to figure this out, how to best adopt. So based on your research and all of these responses and the trends and all this work that you've been doing, if the supply chain leader has to take one thing away from this research that they can action, what would that be, in your opinion?
Boy, one thing. I think the biggest thing is just approaching these tools and your own business. And I think this is just learned business wisdom anyway with that outcome-based thinking, what are the goals I'm trying to achieve, and then work right to left in a way of, okay, what's -- how am I going to kind of work on achieving those? And I mean, we've talked about -- now I'm cheating and giving you multiple answers, just to warn you here. But we've talked about, okay, I got to strengthen my data. I've got to think about my organization. I've got to think about sort of a multi-tiered governance. It's procurement and spend, it's technical governance, it's business governance. I've got to think about my organization and prepare my people. And even whether it's the tools or the people, let's evaluate ourselves based on outcome and performance and all of that. So I think it's just -- the tools are coming. I think I personally am very excited about what's coming. The question is, are organizations preparing themselves so that these tools can really deliver the outcomes that you're seeking?
Yes, 100%. I could not agree more, and that's not just because we're having this conversation. But when you look at Kinaxis as a software provider, we're not immune to how our business is changing based on AI. And for us, it is -- if you look historically, software companies would develop a solution that would have feature and function. We present that to a prospect and we say, "Look, this is what the software can do. We can do it better than anyone else," and they would adopt it. And now we're seeing the same thing where in many cases, customers are using our software already, and they're coming back and saying, "Hey, this is great, but we have this particular outcome, and we don't know how to get there, how can AI help us get there," right? And exactly what you're saying, it's working, I think from right to left, kind of working backwards from what we traditionally look at things and say, what is that goal and how do we get to that goal? And how do we use the tooling that we have like Maestro in the case of Kinaxis, use that decisioning engine and AI to get us towards that outcome. So I like the response, and I think it's okay to cheat a little bit. I don't know that you can pin one thing to take away. That's a little difficult, maybe unfair challenge for you. But I think the name of the game is thinking about this differently, right? You have to think about it from an end state and work your way -- kind of work your way backwards. So this has been a really great discussion. I think that what we've learned is that AI adoption, it's happening. This isn't just hype. This isn't just hyperbole. It's happening, it's real. But just because companies are adopting, it doesn't mean they're achieving the impact and the outcomes that they want, right? And that type of AI is going to depend on all the things that we talked about: trust, data readiness, governance, human oversight and outcome-based solutioning. So I think it's about closing that gap. So we're going to do some Q&A here. We can get that pulled up if we can. And while that's happening, a couple of things that all of you watching can do. One, there is an IDC InfoBrief called Making Supply Chain AI Accountable. That's available to everyone who has been watching. You can see that either on your screen or as a follow-up via e-mail, we'll provide that. And then Kinaxis is also providing a companion report on how to move from AI-enabled decisions to those measurable business outcomes that we just talked about. So we've got some follow-up material that you can read that will not only help you in going on that journey, but also ways that Kinaxis can help you on that journey as well. So all right. So let's see. We've got time. We'll try to do maybe two or three of these. First one I have, what are the most important data readiness steps that supply chain teams should prioritize before we move into more autonomous or agent-based AI? Okay. Good question. So I'll give a perspective, Eric, and then would love to hear what you think. I mean, I think before you can trust AI agents to make decisions, you have to make sure that, that agent can see the same truth, understands the business the same way that you do and operates within the same guardrails that you do, right? So it's the stuff that we've talked about leading up to it. Those three pieces are key to be able to trust that the agent is going to come back with the right answer. I think there's a misconception that autonomous supply chains lives in kind of the data quality realm. And actually, it's a decision quality problem, right? Before deploying these agents, you have to have the trusted data, the business context. You have to do something maybe you've never done before, and that's codifying some of your decision policies, like things maybe that are physically on paper or in people's brains and just how teams have been operated. That needs to be codified so that an agent can follow some of those same processes. Because it's not about -- I mean, the agents and AI can, on their own, kind of look back and see what's happening -- what's happened in the past. What you need is for AI to -- or to teach AI, I guess, how your business makes decisions, right, so it can follow that same path. Yes. So Eric, what do you -- just underline something here?
Well, I actually -- I love something you just said. And so again, forgive me, but I want to underline it actually because I couldn't agree more. One of the methodologies we used at Nike was lean methodology. And so most people will be familiar, whether you use, I don't know, the Toyota Way or Lean or Six Sigma, they're all kind of variations of the same. And one of the things I found is the act of even asking yourself what are the decisions we're making, and like you said, codifying that can itself actually improve your organization's performance because you're spending time asking the why. That's the key part is, well, why are we making that decision? How did we -- well, because we always did is the old answer, right? And so I think even for me, I would personally be excited if I was still in some of those roles to lead an organization through, hey, we need the agents to run. So they need to know what decisions they're making. But now we've got to ask ourselves, are they even the right decisions? And are we doing the right thing? That in itself is also governance because you're going to have to take the time. And it's a bit of, I think, going all the way back to the beginning of this discussion, you said something about like it's not the glamorous work. And that's right, but it's actually the important work because then we say, what are the decisions we're making, why are we making them? What was the goal we were trying to accomplish. And a lot of times, that brings actually, improvement. So if I was -- some of the folks sitting, listening to this, thinking about your first steps, I wouldn't let that either be sort of a barrier. I would actually embrace that because what you're probably going to find is the very process of looking at all your decisions is going to actually improve the decisions you make.
Yes, that's good. All right. Okay. We get someone asking, how do we decide which decisions are appropriate for automation, which ones should stay human-led and which ones need human in the loop? That's a good question. I would say when -- well, you can kind of look at the cost aspect of it, right? So you can automate decisions where the cost of being wrong is low and the decision logic is well understood. Keep humans in control when the impact is high, the trade-offs are more strategic and have to be thought through. And I guess when the context is more difficult to define and it's outside of the data that agents would have access to, right? So that's great when humans are in full control. And then human in the loop kind of fits in the middle, if I think of it that way, right? And I think that will morph. I think that's a picture of where we are today with technology, where it sits today. I don't know, Eric, would you have a view on that?
I would just jump off where you said morph. I think that was good because over time, there's -- we go back to this trust factor. A lot of what we talked about today was trust. And if over time, I'm seeing, I don't know, an agent, a tool, a bit of analytics, whatever it is, is giving me what I would call the right answer or the desired answer or whatever, maybe even sometimes itself getting creative and thinking of something I missed, over time, I'm building trust. And a lot of these tools will kind of ask me, "Like, hey, do you want me to proceed?" And if I'm clicking yes all the time, eventually, I start to kind of say to myself, "Okay, this thing keeps being right. I'm good with this. Go ahead and now work quietly and just interrupt me when it's something that really bubbles up." So I think that word morph is good. This will evolve. And so even if on day 1, okay, we spent that time thinking about all the decisions we're making that we just talked about. And now we move forward, it's still going to keep evolving. Like, oh, actually, let me pull this one back in. Let me kind of release that one. We just have to treat this as -- I mean, and that's business. Every day, we're learning. 20 years ago, before we had these tools, we would evolve. You want to keep growing and learning and shifting, or -- I mentioned lean. There's a saying, read, check and adjust. And so all right, let's do that. And that's going to happen with these agents, where I'm going to say, I thought I was going to automate a certain process. It turns out I'd rather actually get in a room and discuss it with my peers. I didn't think I was going to automate this other thing over here and actually turned out pretty easy too. So I think we're going to have those learnings along the way, too.
Absolutely. Yes. All right. Let's do one more here. Okay. How can we prepare our teams for AI workflows without making them feel like AI is being imposed on them? Oh, that's a good one. I had someone tell me one time, let me think how he said it. The best way or the fastest way to create resistance is to deploy AI as a technology project. And the fastest way to create adoption was to roll it out as an empowerment project, right? So I like that. And I think the message to the team, to our planning team should be clear that, look, this technology is coming in. Eric, you mentioned this earlier. It's handling that repetitive work, the mundane work, the things that where your value is just clicking a mouse and dragging and dropping and exporting to Excel and doing some of this mundane stuff so that you can focus on the high-value decisions that require judgment, creativity. And your experience, right, the fact that you've been doing this for a decade, right? That's really your value of the organization. Imagine stripping everything else off of your plate and you being able to do your high-value tasks all the time and really moving the needle. I mean, who would walk away from that not excited and ready to adopt this new capability? That's my point of view. Eric, I don't know, what do you think? And again, some of the data in the report, right, was highlighting that there is an excitement, right? So I think we just need to harness that and lean into that and not play into some of the fear mongering that's...
It's just incumbent on leaders in particular. Whether you're a project leader or a tech leader, a business leader, there's a certain level of authenticity and honesty we have to have that -- I wouldn't want to promise my teams this is about empowerment, and then really end up doing something else. And so as long as I think we're being real about it, but I do think if that is really happening on your team and you have the opportunity to be authentic and say it and not just be pitching a story, absolutely. Because that's even happened to me in my own role now that there was stuff, honestly, that I kind of hated doing. Like if you're more of a creative and a strategic person, which I am, then the mundane is painful sometimes. And so when I got to set some of that aside and do that, like I said, the higher-order thinking, honestly, it's been more fun. And so there is a path for that. I guess I'm just saying, I'll couch that in. Executives need to make sure we're not telling fairytales either. And so let's just pitch that in the honest place. But I do agree with you 100% that if this is about, hey, we're going to give you tools that sort of supercharge you that give you horsepower. And we have -- honestly, it's back to thinking about the organization. We've contemplated what roles perhaps look like in this, I don't know, new shape, then you have a future to tell someone about versus just like you said, here's some technology plopped on your desk, now go.
Yes, absolutely. All right, folks. I think that's all we have time for today. Again, make sure you download that IDC InfoBrief, Making Supply Chains AI Accountable. And that Kinaxis companion report is available as well, moving from AI-enabled decisions to measurable business outcomes. Eric, great pleasure to have you on the webinar with us today. Thanks so much for joining us and all of the insights that you brought.
Yes. Thank you. It was great talking. I appreciate the opportunity.
All right. You bet. All right. Thanks, everyone, and we'll see you next time.
Read the full transcript via the API
You're viewing the first half of this call. Get the complete Kinaxis Inc. transcript - plus 251,000+ transcripts from 12,000+ companies, speaker segments and full-text search - through the EarningsAPI REST API or hosted MCP server.
Get an API key View API docs →For developers and AI pipelines
Programmatic access to Kinaxis Inc. earnings transcripts and 251,000+ others is available through the
EarningsAPI REST API and the hosted MCP server.
Quarterly plans from $105 - full transcripts, speaker segments, full-text search,
and the /api/v1/transcripts/recent polling endpoint for ETL pipelines.