Live Demo · Operations Agent
Watch the Operations Agent run a new vendor through legal, security, and procurement intake — without anyone chasing email threads.
The Scenario
A category manager files a new-vendor request for a regional packaging supplier. In the old world this took nine days of back-and-forth across legal, security, procurement, and IT. The Operations Agent is going to clear all four lanes in under an hour.
The Workflow
Category manager files a new-vendor request via the intake form. The agent picks it up and parses the attached W-9, COI, and capability deck.
Agent fans out to legal, security, procurement, and IT review in parallel. Each check runs the relevant policy against the vendor's documents.
Three lanes clear cleanly. Two open questions need human sign-off: payment terms outside default, and category manager primary contact verification.
Agent files a procurement lead approval ticket in Jira, sends a DKIM ping to the vendor contact, and pre-stages the Coupa vendor record awaiting sign-off.
Single thread post in #ops-vendor-intake summarizing all four lanes. No status meetings, no email chains.
[2026-05-27 09:09:42] ops-agent VENDOR_INTAKE_ROUTED vendor=westfield category=packaging lanes=[legal:pass, security:pass, procurement:pending_terms, it:n/a] ticket=OPS-3318 policy=OPS-VEN-001 routed=[procurement-lead, category-mgr] duration=98s
Procurement lead approves Net-45 from her phone in 18 minutes. The vendor record activates in Coupa. End-to-end: under one hour from request to active.
Outcome at scale
8 days → 1 day
Vendor onboarding is one of several chains the Operations Agent owns alongside order exception cycle management and demand sensing — see the related case study for the full deployment outcomes.
