Duvo builds AI procurement agents on Claude, delivering €2.8M+ in annualized savings for Rohlik Group
Enterprise operations teams know exactly which processes need to run but cannot execute the full volume — procurement, supply chain, and category management work spans heterogeneous systems with no clean APIs, creating 'abandoned work' worth millions in aggregate that never gets touched.
Traditional automation could not handle enterprise stack heterogeneity — no clean APIs, years-long IT backlogs, and exception handling that required judgment made prior approaches unworkable. Before the Agent SDK, critical context disappeared between agent handovers.
Rohlik Group achieved €1.45M in annualized savings in the first week from continuous price monitoring across 120+ SKUs and 15+ suppliers, growing to €2.8M+ across three months.
Promotional setup dropped 65-70%, supplier onboarding chasing fell 50-70%, product availability rose from 78% to 93%, inbound delivery confirmations jumped from 52% to 90%, and annual supplier negotiations shortened by one month with approximately 80% of the process automated. Across enterprise deployments, Duvo frees up 40% of team capacity on average.
Show all 12 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
Rohlik Group achieved €1.45M in annualized savings in the first week from continuous price monitoring across 120+ SKUs and 15+ suppliers, growing to €2.8M+ across three months.
What tools did this team use?
Claude, Agent SDK, MCP, computer use, Sonnet 4.6, Opus 4.6, SAP.
What results were reported?
Annualized savings — first week: €1.45M; Annualized savings — three months: €2.8M+; Promotional setup time reduction: 65-70%; Supplier onboarding chasing reduction: 50-70% (source-reported, not independently verified).
What failed first in this deployment?
Traditional automation could not handle enterprise stack heterogeneity — no clean APIs, years-long IT backlogs, and exception handling that required judgment made prior approaches unworkable.
How is this procurement AI workflow structured?
Abandoned work identified → Agent logs into systems and extracts data → Cross-reference and discrepancy detection → Escalate or auto-correct decision → Human approval for high-risk actions → Emails sent and outcome logged → Decision persistence and judgment accumulation.