Vendor-centric procurement market layer
James McGillicuddy, CEO of BRM, on the problem with “little P” procurement
This reveals BRM’s core bet, that software buying will stop being a manual questionnaire exercise and become a data retrieval and comparison workflow. In practice, that means turning a purchase request into a live vendor brief that pulls public compliance material, internal usage and spend history, and side by side alternatives into one record, instead of making an employee chase answers across email, contracts, Slack, ERP, and vendor reps.
-
The compare Dropbox to Box to Google Drive example matters because these products are close substitutes for a common file storage job. Much of the first pass evaluation is already structured, like SOC 2, HIPAA support, ISO standards, admin controls, and pricing tier fit, so BRM is trying to automate the repetitive shortlist work before a human gets involved.
-
That is different from CLM tools like Ironclad, where the system is organized around contracts and approvals after a vendor is already in motion. BRM is organized around the vendor itself, then stitches together every trace of that vendor across ERP, email, spend tools, identity systems, and public data, which lets it answer should we buy this, do we already have something similar, and how should we negotiate.
-
It also shows why BRM prices by vendors under management instead of seats. The value is not a person logging into dashboard pages, it is the machine doing the legwork, finding security documents, filling questionnaires, pulling renewal dates, and assembling a recommendation packet that a buyer and seller can both confirm.
The next step is procurement software that behaves more like a market layer than a form builder. As vendor profiles get richer and more reusable, the winning products will prefill diligence, surface the best alternatives, and guide renewals and negotiations from the same vendor record, pushing buying toward faster, more standardized, lower labor transactions.