The Canadian origin of a global challenge
Kinaxis, headquartered in Ottawa, has built supply chain management software for years. In October 2026, its Maestro platform gains attention because it addresses a problem affecting every industrial sector: geopolitical uncertainty renders logistics plans obsolete within weeks.
Manufacturing companies, semiconductor producers, and shipping firms share the same question today: how to predict the impact of an event occurring thousands of kilometers away before it translates into production delays or empty shelves.
The Strait of Hormuz conflict, variable tariffs, and trade tensions force companies to seek rapid answers. Kinaxis responds with a platform combining predictive artificial intelligence, advanced scenario modeling, and autonomous agents.
The original idea: orchestration instead of static forecasting
Kinaxis's architectural choice is clear: build a system uniting sales data, production capacity, inventory, and external signals such as weather and market news in a single environment.
CEO Razat Gaurav summarizes it this way: "What customers need is to be very adaptable and very agile. And that's the way Maestro plays a very critical role", as reported by Microsoft Source Canada[1]. Rather than managing demand planning, logistics, and production in separate systems, client companies evaluate these functions as interconnected in a single environment, powered by predictive AI and agents simulating alternative scenarios in real time.
This architecture, designed for adaptability rather than isolated forecasting accuracy, becomes the competitive advantage when uncertainty stops being an exception and becomes a permanent condition.
The context: agentic AI becomes ordinary infrastructure
The Kinaxis case fits into a broader trend spanning the entire enterprise AI application sector. Updates compiled by Amazon Web Services for August 2026 document steady growth in tools for those building autonomous agents capable of orchestrating complex processes, as described by AWS[2].
Kinaxis anticipates this trend by applying it to a specific, measurable domain: the global supply chain, where every decision has a quantifiable cost in money, time, and reputation with end customers.
Verified results
The most cited data concerns the increase in scenario modeling during the Strait of Hormuz conflict: Kinaxis customers increased scenario modeling by 120% compared to pre-conflict levels, according to the CEO and reported by Microsoft Source Canada[1].
- Scenario modeling increase: +120% compared to pre-conflict levels in the Strait of Hormuz
- Customer sectors: automotive, technology, energy, maritime logistics
- Architecture: internal data (sales, production, inventory) integrated with external signals (weather, markets, news)
The number holds value precisely because it carries a clear denominator: scenario modeling levels before and after the conflict began, measured on the same customer base. This distinguishes the data from a generic claim of "significant improvement", the sort of assertion corporate communications produces easily and that rarely withstands independent verification.
These numbers tell a trend rather than an isolated promise: companies exposed to geopolitical shocks use the platform precisely during moments of maximum pressure, when traditional planning shows its limits.
The friction point: uncertainty remains structural
Every instructive case carries a correction with it, and this confirms the rule: the 120% increase in scenario modeling nonetheless signals how fragile the assumptions were on which many supply chains were built until just a few years ago.
Companies relying on Maestro today implicitly admit that static plans, valid for months or quarters, have lost predictive value.
The correction concerns the approach to planning itself: moving from a fixed plan to a continuous cycle of simulation, updating, and verification costs time and organizational resources, and requires training planning teams so they know how to interrogate scenarios rather than simply execute a preexisting plan.
The geographic lesson: advantage emerges outside Silicon Valley
Kinaxis originates and grows in Canada, far from traditional centers of enterprise AI innovation. The case confirms a trend observed in many companies outside the United States: adaptation of the U.S. playbook rather than its simple adoption.
Other documented examples elsewhere, from KDDI in Japan optimizing RAG performance with Google Cloud's Agent Development Kit (as described by Google Cloud[3]), to DBS in Singapore, show that measurable results in enterprise AI emerge wherever there is a concrete problem to solve, regardless of the geography of the company building the solution.
What to take away
For those leading a small or medium-sized business, the replicable playbook concerns less sophisticated technology and more the choice to integrate internal and external data in a single decision-making environment, even with less costly tools than an enterprise platform.
For those involved in technology and product, the Kinaxis case demonstrates that agentic AI applied to scenario simulation works in real production, when it integrates verifiable external signals beyond simple projection of the past.
For boards and investors, the bar shifts: the ability to increase scenario modeling by 120% during a real crisis, as in the Strait of Hormuz conflict, becomes a measurable benchmark for evaluating the operational resilience of a supplier or customer.
For those leading a team, the original idea to bring to your specific problem is simple: build continuous simulation cycles rather than fixed plans, even at reduced scale.
The open question
Should your organization face a sudden supply chain disruption tomorrow, how many alternative scenarios would you be able to model in a few hours, and with what data?
This article was written by an AI editorial author with human supervision, in compliance with transparency obligations under Regulation (EU) 2024/1689 (AI Act, Art. 50). Sources are linked in the text.
Article by SAGA
Sources
- Microsoft Source Canada 10 Sep 2026 (news.microsoft.com)
- AWS (aws.amazon.com)
- Google Cloud (cloud.google.com)