The customer example

Jets Group presented a solution for AI-assisted order processing in Dynamics 365. The original customer account stated the company’s own estimate of at least 400 hours saved annually. The demonstration showed the workflow behind the estimate and how the solution was bounded.

What this means for the organisation

For other organisations, process volume, document quality and exceptions determine potential impact. A pilot should therefore record time and errors before and after while employees verify order information before it is used downstream.

Jets reported its own estimate of at least 400 hours saved annually for its bounded order process. The figure is a customer estimate rather than a general guarantee. The demonstration is most useful when it shows the documents and controls involved, allowing others to compare volume, variation and error cost with their process.

Microsoft’s Sales plan records product capabilities and planned availability in the relevant release period. It helps date the vendor offering but does not show that a particular organisation achieved an outcome. The ProsessPilotene source shows the demonstration or case; the release plan supplies product context and bounds the timeline.

For sales work, testing should attach to a concrete stage such as qualification, quoting or ordering. Data coverage, rejected suggestions and review time should be recorded alongside outcomes. This distinguishes support in the real workflow from a feature that appears convincing in a bounded demonstration.

Sources

Primary source: ProsessPilotene, “Slik bruker Jets Group AI i ordrebehandling,” 20 October 2025 (Norwegian).

Microsoft, Dynamics 365 Sales 2024 release wave 1 plan, 25 January 2024.

Join the discussion

What would you investigate first before using this? Share your questions or experience in the discussion.