← All work

Technology Industry

ProcureFlow

ProcureFlow helps procurement teams turn approved purchase requests into accurate, traceable purchase orders.

Role
Sole product designer
Timeline
9 months
Industry
Technology
Focus
Agentic workflows
Live prototype
Loading prototype…

01 · Project Overview

The Problem

Procurement specialists had to consolidate and re-enter purchasing data across disconnected systems before issuing purchase orders for company purchases. This fragmented process increased cycle time, introduced errors, and weakened traceability.

The Solution

ProcureFlow creates a controlled handoff between purchase request review and order creation. The Purchase Request Agent verifies that an approved request is ready for ordering, while the Purchase Order Agent carries the verified context into draft purchase orders and checks them against the original request.

The Impact

The key results, such as time saved, errors reduced, or adoption.

My Role

As the sole designer over nine months, I mapped the procurement workflow, defined each agent’s responsibilities and human checkpoints, and led the work from early concepts through prototype validation.

02 · Solution

Four screens carry a purchase request from review to purchase order.

Explore the platform

Created to help procurement teams prioritize exceptions and intervene when an agent needs human judgment.

Created to demonstrate how an approved request is validated against quotes, contracts, policy, and budget before becoming a financial commitment.

PR to PO handoff modal for PR-1048, paused for approval before PO creation

Created to show how automation pauses for a specific exception that requires human accountability before PO creation.

Created to demonstrate the final control point where procurement verifies and authorizes the vendor-facing order.

1 / 4

03 · Explorations

Interviews

I interviewed 7 procurement specialists to understand what happens after a purchase request is approved and how it becomes one or more purchase orders.

Main persona Procurement Specialist Turns approved purchase requests into one or more purchase orders.
“Approval tells me we can spend the money. It doesn’t mean the request is ready to become a purchase order.”From procurement specialist interview

Friction

The difficult work began after purchase request approval. Procurement had to turn an internal request into an external vendor commitment while preserving the approved scope, value, evidence, and decision history.

Three problems repeated:

01Scattered contextRequest details, quotes, contracts, and approvals had to be reconstructed across systems.
02One request, many ordersOne approved purchase request could create multiple purchase orders, making line-item allocation and total reconciliation harder.
03Untraceable changesChanges in price, quantity, vendor, or terms were difficult to trace back to the approved purchase request.

I defined the end-to-end procurement experience, including the workflows, decision points, and controls that connect purchase request review to purchase order execution.

Current Procurement Flow

I mapped the end-to-end purchasing journey to identify critical handoffs and ownership boundaries. The core design challenge was to preserve the control between internal approval and vendor commitment while creating a continuous workflow for procurement specialists.

  1. 01Employee submits purchase request
  2. 02Manager and budget owner approve request
  3. 03Procurement reviews request and documents
  4. Friction04Context gathered across systems
  5. 05Procurement manually re-enters order data
  6. 06Purchase order created in ERP
  7. 07Vendor receives purchase order
The current purchase request to purchase order flow. The highlighted step is where procurement pieced together context from disconnected systems before re-entering order data.

04 · Platform

A walkthrough of the ProcureFlow platform.

Agent Architecture

Engineering designed and built the agent architecture; I partnered with them on where people needed to stay in the loop. Early on, the agents handed requests straight to order creation, and specialists didn’t trust purchase orders they couldn’t verify. I resolved this by adding a review step: once the agent has checked an approved purchase request, a procurement specialist confirms the request is accurate before it's sent for purchase order creation.

Data sources

Purchase requestProcurement system
Quotes & documentsDocument repository
ContractsContract management system
Vendor masterERP

ProcureFlow orchestration

Trigger · Purchase request approved
Purchase Request Agent
  • Assembles request context
  • Checks quotes, contracts, vendor
  • Flags gaps for review
Controlled handoff Specialist reviews and approves verified context
Purchase Order Agent
  • Drafts one or more POs
  • Allocates line items
  • Reconciles totals to request

Systems of record

Purchase order document createdERP
Two agents split the work at the point of approval. The Purchase Request Agent gathers and verifies context from the source systems, a procurement specialist approves it at the controlled handoff, and the Purchase Order Agent turns that verified context into a purchase order document in the ERP.

Purchase Request Agent

1 / 5

Purchase Order Agent

Purchase order issued: PO-2088 has been sent to DisplayWorks and is awaiting vendor confirmation

1 / 3

Human Checkpoint

PR to PO handoff modal for PR-1048, Design equipment, paused for approval of the PO creation checkpoint

1 / 2

Dashboard

Live prototype
Loading prototype…

The working prototype. Start from the overview, open a request in the priority queue, or follow a PR through the handoff to its purchase orders.

05 · Validation

Testing revealed that procurement users wanted a more detailed view of the activities performed during the PR-to-PO handoff, including what data was being retrieved, which steps were completed, and why their intervention was required.

Before validation: the PR to PO handoff modal shows a progress bar and an approval request, without the steps or data behind it
BeforeThe original experience showed a loading state and requested approval without revealing the activities happening during the handoff.
AfterI redesigned the handoff to surface the retrieved data, completed steps, proposed PO details, and the specific exception requiring approval. This increased visibility and built trust in the outcome.

06 · Impact

I compared the average time and number of system switches required to move an approved purchase request through PO creation and submission to the vendor.

35% Less time to move an approved purchase request to a purchase order sent to the vendor
60% Fewer switches between systems to take a purchase request from approval to a PO sent to the vendor

07 · Reflection

What Worked Well

I focused on defining the right boundary between automation and human judgment in the PR-to-PO handoff. I designed the system to retrieve procurement data, validate documentation, and prepare the purchase order, while keeping users in control of exceptions and final approval.

Next Steps

Next, I would expand ProcureFlow into a unified procurement experience by bringing PR creation, internal approvals, the PR-to-PO handoff, and vendor collaboration into one place. I would also explore how a vendor portal could integrate with the system to enable a seamless exchange of quotes, documents, order updates, and exceptions between internal teams and external partners.

Next project ComplyOne

Available for full-time product design opportunities

Let's build intelligent systems together.

I'm always happy to connect about product design, emerging AI experiences, or new opportunities.

View resume