Could you tell us a little bit more about what the undamental difference is between a standard automated workflow and one with Navi implemented within it? That ' s a question I get quite often, if you can do something with just code and integrations, why use Navi and what can you do with it differently? The biggest difference is intelligence. By intelligence, I mean the ability to analyse and reason, connect the different dots and apply all of that to ultimately take an action. That is not something traditional workflow-based solutions can do.

At this Coupa Inspire, we ' ve had the debut of DevCon. Can you tell us why this year was the right time to introduce that? AI is moving from paper to production. This is a time when organisations are not just talking about AI, or whether AI will actually solve procurement and finance challenges, it is about how it will change things and which parts of their organisation need to start using it.

When people talk about AI, they talk about agents taking over those low-value tasks. When do you decide when an agent can come in and take over a piece of work? The most important thing is to have a framework for what use cases you want to look at, what your team spends time on. Identify those and then consider: if you remove those tasks, where would they spend their time instead and what value are you going to get? You then build an agent around that idea, look at the improvement in your KPIs and assess whether it is worth the return on investment you are making.

When you start to build an agent, how do you ensure it remains purpose-built rather than becoming overly complex for the end user?

88 July 2026