BRM replaces procurement headcount with agents
James McGillicuddy, CEO of BRM, on the problem with “little P” procurement
BRM is trying to turn procurement from a tool that people operate into a labor product that operates on their behalf. The point is not just faster clicks. It is replacing the junior work of gathering contracts, checking compliance docs, chasing renewals, drafting emails, and stitching together data from ERP, email, spend, and identity systems around one vendor record. That lets BRM sell automation as headcount replacement, not as another seat based app.
-
The product is vendor centric, not contract centric. Ironclad and similar CLM tools organize work around documents and approvals. BRM starts with a vendor identity, then pulls in the contract, spend, usage, receipts, and renewal dates tied to that vendor, which is why it can sit alongside tools like Zip or Ironclad instead of always replacing them.
-
The agent layer is concrete. A compliance agent prepopulates security reviews, a renewal agent finds notice periods and reminds teams before deadlines, and a pricing or email agent helps prepare negotiation steps. In practice, BRM says this can cut vendor due diligence from hours to minutes, with a human still approving sensitive decisions.
-
The pricing model matches that services like position. BRM charges by vendors under management, up to $200 per vendor per year, because customers are buying completed work on each supplier, not user access. That differs from seat based procurement and CLM tools, and from Ramp style businesses that monetize a broader finance suite through payments and software.
If this model works, procurement software moves closer to software enabled operations. The winners will be the vendors that own the underlying entity graph and workflow data, then layer specialized agents on top. That points BRM toward a broader role in renewals, negotiations, and vendor discovery, while existing systems like Zip, Ramp, and Ironclad remain core systems around it.