The problem
What needed
to change.
Vendor comparison and purchase preparation need consistent evidence while preserving human approval authority.
Project story
A governed workflow adds purchasing context, compares suppliers and pauses for approval before creating a purchase-order draft.
A governed workflow adds purchasing context, compares suppliers and pauses for approval before creating a purchase-order draft.

About the project
A procurement application that combines an AI-assisted command interface with a controlled purchasing workflow. It separates recommendations from the human decision that authorizes an award and purchase-order draft.
Procurement requesters, sourcing teams, technical reviewers, and procurement heads.
The problem
Vendor comparison and purchase preparation need consistent evidence while preserving human approval authority.
The solution
A governed workflow adds purchasing context, compares suppliers and pauses for approval before creating a purchase-order draft.
What we do
The capabilities and workflows that bring this project together.
Why we do it
Make vendor comparison and purchase preparation more systematic while preserving approval authority and a traceable explanation of the decision.
Inside the workflow
A requester states a business objective. The workflow adds ERP context, shortlists approved vendors, compares quotes, and pauses for human approval. Only an approved run proceeds to an ERP-ready purchase-order draft; rejection leaves no PO draft.
A closer look
A visual guide to the project’s scope. An application screenshot is not available for this entry yet.

Technology
Next.js/React, HeroUI, Tailwind, Zustand, Mastra agents/workflows, and LibSQL workflow snapshot storage.
Project scope
The documented current ERP and quote data are deterministic mock fixtures. The governed flow is implemented as a prototype foundation; live ERP/vendor adapters and model configuration are separate integration work.
Keep exploring
From project to possibility