Vendor-Centric Solution to Procurement Fragmentation

Diving deeper into

James McGillicuddy, CEO of BRM, on the problem with “little P” procurement

Interview
despite there being more and more go-to-market tooling, it was getting harder and harder to transact
Analyzed 4 sources

The core problem is that software buying became decentralized faster than the systems for approving it. More sales and marketing tools helped sellers find prospects, but buyers still had to pull together legal, security, finance, usage, and contract data across email, ERP, CLM, spend tools, and chat, which turned a simple purchase into a cross functional project and pushed SaaS payback periods from about 22 months to 28 months.

  • Little P procurement means purchases now start with employees at the edge of the org, not a central procurement team. A product manager can want a roadmapping tool, then discover late that InfoSec, legal, and compliance all need to sign off, which creates delay even before pricing talks begin.
  • The stack has also fragmented. Zip handles intake to procure, Ramp and Brex handle spend and cards, Ironclad and Icertis manage contracts, and BRM tries to stitch the vendor record across those systems. More tools exist, but each one usually owns only one slice of the workflow.
  • That is why BRM is built around the vendor, not the contract or the card. It tries to assemble one record for a vendor from ERP, email, CLM, spend, and identity systems, then automate work like compliance reviews, renewal tracking, and side by side vendor comparisons that otherwise happen manually.

The market is heading toward buyer side automation that compresses the transaction itself, not just top of funnel lead generation. As AI agents get better at collecting diligence data, comparing vendors, and preparing renewal strategies, the winning tools will be the ones that remove internal coordination work and make buying feel as easy as discovering software became.