Digital data streams converging into a single point on a circuit board, representing trade surveillance vendor consolidation in financial services technology.

Best in Breed or Consolidation? The Vendor Strategy Question in Trade Surveillance

May 26, 20265 min read

For most of the past five to seven years, running multiple trade surveillance vendors was not a strategic choice; it was an accepted necessity. The coverage gap between exchange-traded and OTC asset classes meant that no single vendor could do what institutions needed. Complexity was built in, and it was accepted as the cost of adequate surveillance.

That may be changing. The conversation I am hearing consistently across institutions globally is about reduction: fewer systems, fewer vendor relationships, and whether the technology has moved far enough to make consolidation viable without sacrificing coverage. In my own survey work this year, approximately 70% of organisations are currently focused on vendor consolidation in trade surveillance. That is a significant shift in institutional appetite from where the market was three years ago.

How we got here

The multi-vendor model has its origins in a genuine and well-understood coverage gap. No single vendor could adequately cover both exchange-traded and OTC asset classes for institutions with meaningful risk in both. The market responded in two ways.

The majority of institutions selected one vendor for exchange-traded products and a separate vendor for OTC. In many cases, where legacy technology or acquisitions had added further layers, the result was not two systems but three, four, or even five running in parallel. A smaller group took a different route: identify the primary risk area, find the best available vendor for that domain, and build in-house solutions to cover what that vendor could not.

Both models acknowledged the same underlying reality. Full coverage from a single vendor, at the quality required, was not achievable. The operational cost of that was significant and well documented. Analysts needed to learn multiple systems; data integration was a persistent challenge, vendor management relationships multiplied, and risk oversight became harder to maintain at a consistent standard. Institutions accepted this complexity as the price of adequate surveillance.

The consolidation question

Something has shifted. I have been hearing a consistent theme across institutions globally: organisations are focused on whether they can reduce the number of vendors they manage and whether the technology landscape has changed enough to make that viable.

Two questions are driving this. The first: Can a single vendor now provide adequate coverage across the asset classes that matter, even if they are not the market leader in every category?

The second question: Is the cost and risk of managing multiple vendor relationships now significant enough that it outweighs the coverage benefits? In most of the conversations I am having, the answer is moving towards yes.

The internal dimension

The consolidation question does not sit in isolation. Technology teams at many institutions are expanding their capabilities and proposing in-house surveillance solutions across a range of functions. The question being asked is not simply vendor A versus vendor B. It is vendor versus build and what combination of the two best serves the institution given its risk footprint, budget, and existing infrastructure.

This adds a material dimension to the vendor assessment process. A firm simultaneously evaluating external vendor consolidation and an internal build proposal is not running a vendor selection exercise; it is running a strategic review of how its surveillance capability should be structured. That requires a different kind of leadership engagement and a broader set of inputs than a standard procurement process.

What is happening in the vendor market

These institutional trends are running alongside consolidation in the vendor market itself. The trade surveillance technology space has seen acquisitions, significant private equity activity, and meaningful capital raising across 2025 and into 2026. The competitive dynamic is shifting. Being the best-in-class provider for a specific asset class was the dominant strategy for several years. What the market appears to need now is broad adequate coverage combined with strong technology capability and a credible investment path toward AI. Smaller and more specialised vendors are facing a harder environment as a result.

The implications for institutions are material. Vendor decisions made now are being made in a market that is still forming. The options available in two or three years will not be the same as those available today. Some vendors currently in the market will not exist independently by then; some will have consolidated into broader platforms. This is not a reason to delay decisions; however, it is a reason to make them with a view of where the market is heading, not just where it is today.

Closing

A further dimension is also now playing a significant risk role in vendor selection conversations: the cybersecurity capabilities of third- and fourth-parties. Mythos has now elevated this concern in regulatory discussions, with its approaching potential threat for identifying and exploiting weaknesses expected to be greatest through these services. Vendors will have to have the cybersecurity maturity to address this, as well as all the other requirements for surveillance. The business case favours reduction: fewer vendor relationships, lower integration complexity, reduced vendor management cost, and greater clarity of oversight. Cost pressure in surveillance is real. In my discussions, though, it is rarely the primary driver. Risk management remains the central concern, and any consolidation case has to demonstrate maintained or improved risk coverage alongside the operational simplification.

The business case direction is becoming clearer; the path to get there remains institution-specific. What is consistent is that the question itself is now on the table in a way it was not two or three years ago. If you are working through this in your own programme, I would be interested in what you are finding.


Back to Blog