Vendor Centric System of Record
James McGillicuddy, CEO of BRM, on the problem with “little P” procurement
This reveals that BRM is trying to become the system of record for the vendor relationship, not just the filing cabinet for the contract. In practice, a document centric tool starts with the agreement and the approval flow around it. A vendor centric tool starts with the supplier itself, then pulls in contract terms, invoices, card spend, renewal dates, usage signals, emails, and compliance data so a company can decide whether to keep, renegotiate, replace, or expand that vendor.
-
In a CLM like Ironclad, the core object is the contract. The product is built around drafting, redlining, approval routing, signature, storage, and search. That makes it strong for legal workflow, but narrower when one vendor has many contracts, users, bills, and renewal signals spread across other systems.
-
BRM is built around identity resolution. It creates one profile for a vendor like Figma by matching records across ERP, email, contracts, spend tools, CRM, and identity systems. That lets it answer operational questions like, do we already use this tool, who uses it, what are we paying, when can we cancel, and what risk docs are missing.
-
The business model follows that architecture. Ironclad largely monetizes seats and workflow adoption across legal and adjacent teams, while BRM prices by vendors under management, up to $200 per vendor per year, because it is selling the ongoing work of monitoring and managing each supplier relationship.
The market is moving toward systems that treat every supplier like a live record that can trigger workflows, analysis, and negotiation, not just a signed PDF in storage. If that shift continues, vendor identity becomes the foundation for renewals, compliance checks, and AI agents that manage more of the buying process end to end.