INTAKE & ORCHESTRATION
“ Creating a frictionless intake experience while capturing the structured data needed by back-end systems starts with simplifying the user journey and eliminating redundancy across the process,” says Jonathan.“ Best practices include mapping the intake process across every function to identify and remove duplication, since functional teams often optimise their own workflows in ways that create repeated effort.”
After simplifying intake and removing redundancy, organisations should decide how closely their processes should conform to the orchestration technology.
“ Configuring technology is often more difficult than adapting processes. The most successful clients implement software with little to no customisation,” adds Jonathan.“ So unless procurement can create a sustainable competitive advantage, keep the software as designed and ask teams to adjust their processes to fit it.”
Dmitry approaches the same trade-off from a different angle; instead of asking how much the process should bend to the software, he asks how much the employee needs to know at all.“ Separate the human choice from what is known by the system,” says Dmitry.“ If the person is applying for a purchase order, then they shouldn’ t enter information such as vendor tax ID and cost centre. This should be contextual.” He adds:“ An intake process guided by AI, where employees go through a conversational process to provide comprehensive and accurate information, will reduce the effort and iterations that happen when you have a static form with required fields upfront.
“ AI will have the ability to read engineering diagrams and propose alternative materials and designs, saving the users time and the company money”
Dmitry Nazarevich CTO Innowise
114 October 2026