Kinaxis and the “SaaS-pocalypse” test: why supply chain software may be different

Sean Silcoff’s Globe and Mail article frames new Kinaxis CEO Razat Gaurav as betting that the Ottawa supply chain software company can be a winner in the so-called “SaaS-pocalypse”: the market concern that AI will compress, disrupt or replace parts of the traditional software-as-a-service model.

The Radar signal is not just financial-market positioning. Kinaxis sits in a category where AI disruption is more complex than simple workflow automation. Supply chain planning depends on constraints, scenarios, network trade-offs, master data, exception ownership and cross-functional decisions. That makes Supply Chain Planning less vulnerable to generic AI substitution, but more exposed to vendors that can prove AI improves real decision outcomes.

Kinaxis’ own recent messaging supports this shift. The company appointed Razat Gaurav as CEO effective January 12, 2026, positioning him to lead the next phase of AI-driven innovation around Maestro and supply chain orchestration. Kinaxis also describes Maestro as an AI-infused platform for transparency, agility and orchestration across the supply chain.

The broader context is that Kinaxis is actively repositioning around AI agents, decision orchestration and supply chain optimization. Its newsroom highlights 2026 announcements on AI, NVIDIA-related large-scale optimization, forward deployed engineering, Kinexions North America and agentic AI.

The practical question is whether this creates durable differentiation. In generic SaaS workflows, AI can automate tasks, summarize content or generate interfaces. In supply chain, the harder value is consequence-aware planning: understanding how a demand change, supply constraint, inventory decision or transportation disruption affects service, cost, margin, capacity and risk across the network.

Dataleo angle

This is a relevant Radar insight because the “SaaS-pocalypse” debate becomes sharper in Supply Chain AI. The winners are unlikely to be vendors that simply add copilots. The stronger test is whether AI is embedded into a governed Decision Architecture: scenario logic, exception handling, human approval, model traceability and measurable planning outcomes.

For planning leaders, the Kinaxis case should be evaluated through decision impact rather than AI messaging. Does the platform reduce planning latency? Does it improve trade-off quality? Can planners understand and override recommendations? Are decisions logged? How does AI connect with APS, ERP, execution systems and financial planning? These questions matter more than whether the interface looks agentic.