Vendor identity is procurement's wedge
James McGillicuddy, CEO of BRM, on the problem with “little P” procurement
The real wedge in modern procurement is not approvals, it is building a clean map of what software the company already uses. Employees buy tools through cards, invoices, contracts, email threads, and SSO, so the same vendor can appear under different names across systems. BRM starts by stitching those records into one vendor profile, because without that view a company cannot spot overlap like two whiteboard tools solving the same job.
-
This is the difference between vendor centric and document centric systems. A CLM like Ironclad is built around contracts and approval workflows. BRM is built around the vendor itself, then attaches contracts, spend, usage, and renewal data to that vendor record.
-
The problem got bigger as self serve SaaS pushed buying to the edge of the org. A product manager can start paying for a tool before finance, legal, or security even knows it exists, which creates duplicate spend, missed reviews, and weak renewal leverage later.
-
That is why BRM prices per vendor under management, up to $200 per vendor per year, instead of by seat. The product is doing the work of finding the vendor, pulling the contract, extracting key terms, and alerting the team before renewal, which makes the vendor record the core economic unit.
The category is moving toward systems that combine intake, contracts, spend, and agent driven analysis, but the durable control point will be the system that knows every vendor across the stack in real time. If BRM keeps owning that identity layer, it can expand from duplicate spend prevention into renewal strategy, compliance automation, and eventually vendor discovery and transaction routing.