Bringing fragmented procurement into one workflow

A technology company of more than 500 people ran its purchasing in disconnected parts: requests in one place, approvals in another, records in a third.

That made ordinary questions hard to answer without chasing someone. Which requests were waiting. Who owed the next decision. What had already been approved, what had been bought, and how much was committed.

A procurement system built around the company's own purchasing process rather than configured from a template. Purchase requests, approval routing, supplier records, purchase orders and spend visibility run in one workflow.

We built it for their internal use, and they own it. The system and the code are theirs.

• Routes a purchase request to the right approver and records the decision
• Shows the state of any request without anyone having to ask for an update
• Keeps supplier records and purchase orders against the request that created them
• Makes committed spend visible in one place

Purchasing moved out of disconnected requests, informal approvals and separate records, and into one workflow.

What was requested, who approved it and what happened next now sit in one place, which is what makes the process visible and controllable.

The full source-to-pay picture was not completed in the first build. We prioritized requests, approvals and purchase orders, and deferred the downstream capabilities rather than ship them half-built.