By Hedgebook Sales Director, Jason Gaywood
Nearly every FX broker firm I speak to at the start of their buying journey is having the same debate: do we build our own Treasury Risk Management System (TRMS) or buy something off the shelf to augment the tech stack we already have?
The question is coming up more often as firms look to create a positive point of difference in the market for two reasons – that generally sit side by side:
- Client retention and share of wallet. Brokers want richer, more data-driven conversations with corporate clients, especially when markets move and everyone is making the same call.
- Business risk and governance. More non-bank providers are realising their internal mark-to-market (MtM) and margin reporting is not as mature as it needs to be, and that blind spots can become expensive quickly.
If you are Head of FX Sales, you feel the first pressure every day. If you are Head of Treasury or Risk, you feel the second one in your gut more often than you’d like. Increasingly, you need a solution that gives you confidence you are achieving both.
Practical rather than theoretical outcome needed
In the UK, the regulatory direction of travel is clear: greater scrutiny, more evidence-driven supervision, and higher expectations around governance, controls and meaningful management information (MI). If you are going to get ahead on this you need a tool to help you do it.
The fscom 2026 UK Payments Regulatory Outlook report puts it plainly – in a way that applies far beyond payments: governance must keep pace with growth, boards must be confident that systems and controls are robust, and MI needs to drive action or it risks becoming meaningless
For FX brokers, the implication is practical rather than theoretical. If you cannot quickly value positions at scale, understand exposure by client and currency pair, and stress-test assumptions, it is harder to set margin policy, defend decisions, and respond with confidence when volatility hits.
The real choice is not binary
Most people frame this as build vs buy – with the view you have to make compromises whichever way you go. However, as I see it – you actually have three options to get the same ‘tailored to fit’ result:
- Build it internally
- Pay an external technology firm to build it
- Buy an off-the-shelf platform (like Hedgebook) and tailor it to your needs
The appeal of building it yourself is obvious: control of proprietary technology, security and the development cycle. The problem is most dev teams are stretched thin, many don’t have the specific build and test capabilities needed in-house, priorities conflict, and anything seen as a ‘value add versus ‘need to have’ can slip down the roadmap fast.
Even when a build starts well, I have seen teams get halfway through and then get pulled onto the next C-suite priority, or redirected by shifting regulatory requirements. The project does not fail with a bang. It simply limps along to a finish line that isn’t where the original vision sat.
Getting someone else to build it is even more problematic. First hand I have experienced the long learning curve for an external software development team to understand the basic requirements of what they’re building. Because nobody knows what they don’t know, questions go unasked on both sides and the project inevitably takes longer and costs more than it ever should.
What FX brokers are actually trying to achieve
If you’re looking to buy a solution there are fish hooks too. When I listen closely, broker requirements usually cluster into two outcomes.
1) A stronger client value proposition (Head of FX Sales)
Brokers want a way to differentiate with corporate clients using scenario analysis, clear visuals and consistent valuations. It means relationship managers can run better conversations and reinforce hedging discipline.
They also want the experience to feel like the broker’s own proposition, not a separate tool bolted on. That means:
- White labelling to match the broker brand
- Portal access so the client is not forced into “yet another login”
- Client-by-client control over what is visible, depending on sophistication and service model
Not to hold you in suspense – Hedgebook is designed to do all of the above. It can be tailored to support specific bank and broker environments and very quickly drive real value – in days, not months.
2) Better internal risk visibility (Head of Treasury or Risk)
This is where the conversation often becomes urgent.
Being able to value thousands of open positions quickly, and see exposure across your client base by currency pair and direction, should be front and centre for every risk and credit function inside a non-bank provider.
This is not just about being “better at reporting”. It is about understanding where you are over-exposed, how margin terms behave under stress, and how risks crystallise as the business grows. That is exactly the kind of board-level maturity fscom is pointing towards: clearer risk appetite, realistic stress testing and MI that drives action.
Again – this is built into Hedgebook’s functionality based on roughly two decades of experience of doing this in global markets.
The due diligence question I would ask early
Here is a common trap.
Some platforms that look like TRMS tools are commercially motivated to secure execution volume. They use their own pricing feeds, or the feeds of a liquidity provider, and the “analytics” is a pathway to flow.
So one of the simplest questions to ask any provider is: ”Can I use my own pricing feeds, or am I locked into yours?”
Hedgebook is not an execution solution. It is designed to be an independent valuation, analytics and reporting layer. It means you can integrate with Hedgebook via an API and have it present as if it were under your own brand using your feeds. No ticket clipping or conflict of interest.
My “build vs buy” checklist (the one I see winning internally)
If you are writing the internal paper that needs to satisfy both Sales and Risk, I would keep the decision tight around these criteria:
- Speed to value: can it be live in days, not quarters? (Hedgebook is typically up and running within 24 hours.)
- Integration: can it connect cleanly via API into your existing stack and portal?
- Client controls: can you tailor visibility per client, including ‘presentation mode’ vs shared workspace?
- Product breadth and future-proofing: can it handle your current products and the ones you will introduce as you scale? (Hedgebook supports a wide range of products from Spot to TARFs that can be enabled as needed).
- Risk capability at scale: can it bulk value hundreds or thousands of positions reliably for internal MtM and margin reporting?
- Trust and assurance: is it proven, supported, and built for non-technical users? (Hedgebook is used by audit firms globally to validate valuations and is designed to be intuitive with minimal training needed.)
Closing thought, and an invitation
If you are debating TRMS build vs buy, my advice is simple: do not treat client engagement and internal risk as two separate projects. The brokers winning right now are the ones aligning Sales and Risk around the same source of truth, so better conversations sit on top of better control.
If you would like to pressure-test your approach, book a meeting and I will walk you through an honest assessment as to whether Hedgebook is a good fit for what you are trying to achieve – or not.
