Fragmented little P procurement stack

This stack exists because no single tool owns the whole buying workflow anymore. One employee starts a request in Zip, pays with Ramp or Brex, routes the contract through Ironclad or Icertis, and still needs a separate system like BRM to answer basic vendor questions such as what was bought, when it renews, and whether the vendor meets security requirements. The result is better software than legacy suites, but also a new integration problem spread across finance, legal, IT, and security.

• Zip is the front door. It gives employees a simple intake form, then routes approvals and can trigger purchase orders, vendor setup, or payment. That makes it the workflow layer, not the full system of record for every downstream vendor detail.
  2 sacra
• Ramp and Brex enter from the money side. They began with cards and expense controls, then added procurement features because whoever controls payment data can expand into approvals, bill pay, travel, and treasury. Ramp reaching $1B annualized revenue shows how powerful that bundle can become.
  3 sacra 5 sacra
• BRM and CLM vendors solve different missing pieces. Ironclad and Icertis are largely contract and workflow systems, while BRM is built around a vendor record stitched from email, ERP, identity, and spend tools, then used for renewals, compliance checks, and pricing analysis.
  1 sacra 4 sacra

The next phase is consolidation around whichever product becomes the daily control plane for company buying. The winners will not just store contracts or move money. They will connect request, approval, contract, payment, and renewal into one live vendor graph, with AI doing the manual follow up work that used to live in spreadsheets and inboxes.