From a plain-language buying request to a compliant purchase order in minutes.
from intake to requisition for a standard catalog buy.
- 5 to 7 business days to under 30 minutesintake to requisition, for a standard catalog buy
- An estimated 15 to 20 percentage pointsincrease in on-contract spend, helping teams capture negotiated supplier savings
- Roughly 30 to 40%of buyers' week reclaimed from routing and data entry for sourcing strategy and negotiation (estimated)
- Above 90%of requests correctly commodity-coded at intake, up from an estimated 60 to 70%
// The problem
Where time went
Buying meant navigating forms, catalogs, contracts, approvers, and budget codes. A standard catalog purchase took 5 to 7 business days of searching and sequential approvals. When employees struggled to find approved options, they bought off contract and missed negotiated pricing. Buyers spent much of their week routing requests and entering data, while purchases were often assigned to the wrong commodity category.
// The build
What we built with them
LevelUp worked with the procurement team to build a copilot that turns a plain-language request into a purchase requisition. It identifies the purchasing category, finds approved suppliers and catalog items, checks budgets and spending limits, and routes the request for approval. It then prepares the requisition and purchase order through the ERP APIs. A person approves the spend, and every action is logged for audit.
// Where it stands
The copilot brings policy checks into the buying process from the start, with human approval required for every spend.
// How we measured
Cycle time against the workflow baseline; commodity-classification accuracy, routing correctness against the delegation-of-authority rules, policy-compliance rate and catalog-match precision scored; spend shift and buyer time estimated with the team.
Build with confidence
Talk to us about testing your agents before launch.
