Enterprise procurement is designed to reduce risk and control cost. Those are legitimate goals. But the process it runs to achieve them often compresses genuine differentiation into a feature checklist, and the firm buying the technology ends up with the wrong outcome.
This is the second in a series of articles on how commercial processes work in financial services technology. The first, in September, examined what buyers need to understand about B2B price negotiation. This one looks at enterprise procurement from the other direction: not how to survive it as a vendor, but what it inadvertently does to the quality of your buying decisions, and how to design a better process.
The central problem with most enterprise procurement processes in financial services is that they are optimised for the wrong objective. Procurement's mandate is risk reduction and cost control. Both are legitimate and important. But neither is the same as finding the solution that best solves the operational or regulatory problem the business unit is actually trying to fix. The moment a procurement team takes ownership of a vendor selection, the business case that motivated the search tends to get compressed into a requirements document, and that requirements document becomes a feature checklist against which two or three vendors are scored. The problem is that a feature checklist cannot capture context, cultural fit, implementation quality, or the difference between a vendor who will be a genuine long-term partner and one who will deliver the minimum required by contract.
How enterprise procurement compresses vendor differentiation at each stage of the process.
There is also a structural issue with the three-vendor policy that most financial services firms operate. Requiring a minimum of three quotes is sound governance in principle. In practice it often means that two of the three vendors in the process are there to satisfy the policy rather than because they are genuine contenders. Sophisticated vendors know this and will recognise quickly whether they are the preferred choice, a genuine competitor, or a benchmarking exercise. The way they engage with the process will reflect that assessment. A vendor who believes they are there to make up the numbers will not invest the relationship time and business case development that produces the best outcome for the buyer. The result is that the buyer gets less useful information from the process than they would from a more honest, smaller comparison.
The research on procurement effectiveness supports this. Gartner's analysis of B2B buying journeys consistently finds that the deals that produce the best long-term outcomes are those where the buying organisation's internal champion had already built consensus and shaped the requirements before formal procurement was engaged. When procurement defines requirements independently, they tend to reflect what can be measured in a scoring matrix rather than what the business unit actually needs. The vendor who shaped the conversation before the RFP was issued has a structural advantage that no amount of formal evaluation can fully neutralise, which means that by the time procurement is running the process, the most important decision has often already been made informally.
From my experience building vendor management frameworks at HSBC Alternative Investments and then operating as the vendor at Backstop Solutions, ONYX Capital Group, and in the RegTech sector, the deals that produced the best outcomes on both sides shared a common pattern. The buyer's internal champion had done serious diagnostic work on the problem before any vendor was invited in. The requirements that went into the formal process reflected genuine operational pain rather than a generic checklist. And procurement's role was to validate commercial terms and manage contractual risk, not to drive the selection decision. When procurement drives the selection, the process defaults to what it can measure, which is price, feature coverage, and reference checks. When the business unit drives the selection and procurement validates, the outcome reflects what the firm actually needed.
There are four things a financial services organisation can do to improve this. First, ensure the business unit has fully defined and quantified the problem before any vendor is approached. A vague requirement produces a vague process. Second, give the internal champion the mandate and the political capital to shape the requirements document, not just advocate for a preferred vendor after the fact. Third, use the pre-RFP period to have genuine diagnostic conversations with a small number of vendors, not to begin a formal evaluation but to test whether the requirements reflect the real problem. Fourth, be explicit with procurement about which elements of the decision are commercial governance and which are business judgment, and structure the process accordingly.
None of this is an argument against procurement rigour. Vendor governance in financial services matters enormously, as I have written about elsewhere, and the contractual, security, and compliance checks that procurement performs are genuinely important. The argument is for a clearer division of labour: procurement owns the governance process, and the business owns the selection decision. When those two responsibilities are conflated, the governance tends to crowd out the judgment, and the firm ends up with a vendor who passed the checklist rather than one who can solve the problem.