Zycus Intake vs. Legacy Intake Systems

Legacy intake relies on disconnected entry points: email, spreadsheets, and rigid ERP screens that requesters avoid and that capture incomplete data. The result is low adoption, dirty data, and endless clarification loops for the procurement team. Merlin Intake replaces all of that with one intelligent front door, the AI Control Tower for every procurement request, that guides requesters conversationally and captures clean, complete data at the point of intake. Crucially, it sits on the Merlin Agentic Platform, so an approved request flows directly into sourcing, contracting, and purchasing rather than being rekeyed. The structural difference is a single governed entry point feeding the whole suite, instead of fragmented inputs feeding nothing.

Casual requesters bypass procurement when the system is hard to use, so Merlin Intake makes the compliant path the easy one. It works inside Microsoft Teams and Slack with a conversational interface, no forms and no commodity-code guessing, letting people describe what they need in plain language while the agent maps it correctly behind the scenes. Because it removes procurement jargon and rigid dropdowns, it earns adoption from the business rather than demanding training. Strong adoption is what shuts down maverick spend at the source. Across aggregate Zycus deployments, Merlin Intake is associated with 40% NPS growth and a 20% improvement in spend under management (Zycus 2025 customer benchmark aggregates).

Legacy systems force users through static forms and unfamiliar classification codes; Merlin Intake replaces that with a conversational request experience on the Merlin Agentic Platform. The agent interprets intent, asks adaptive follow-ups based on what is actually being bought, and auto-populates the technical parameters (UNSPSC categories, cost codes, required fields) that users used to get wrong. That means a request arrives complete and correctly classified the first time. Because the agent draws on supplier, contract, and policy data in the Zycus Data Core, its follow-ups reflect how the enterprise really buys, not a generic script. Clean intake is what makes everything downstream faster.

In legacy setups, buyers spend a large share of their time sorting, validating, and assigning unstructured requests. Merlin Intake removes that triage by validating each request at entry, so submissions arrive complete, compliant, and correctly classified. Its routing then dispatches each request to the right category expert, buyer, or legal reviewer automatically, removing days of manual hand-off. Because intake feeds the connected flows of the Merlin Agentic Platform, an approved request becomes a sourcing event, contract, or PO without rekeying. The cycle-time gain comes from eliminating the manual handoffs between steps, not just speeding up any one of them.

In legacy environments, a request disappears into a black hole after it is submitted. Merlin Intake creates an unbroken digital thread from request to payment, so a requester can see exactly where their project stands (in legal review, in a sourcing event, awaiting PO) on a live dashboard. Procurement leaders get the aggregate view: an early read on demand pipeline they can plan sourcing strategy against. Because that thread runs on the Merlin Agentic Platform and the shared Zycus Data Core, the status everyone sees is the same record, updated in real time. This is the front end of Intake-to-Outcomes (I2O): every request is tracked from the moment it is raised to the outcome it produces.