Pricing and risk systems
Consulting on pricing and risk systems for trading platforms, including price distribution and the checks around an order.
What this work is
Pricing systems produce a price and carry it to the models, screens, and order checks that have to use the same number. Risk systems decide whether an order, a position, or a trader is inside the limits the firm has set. On a trading platform the two meet constantly. A change in the price changes the value of a position, and it can change whether the next order is allowed out. We consult on that software. How a price is made, how it is distributed, and how the checks beside an order use it.
A late price, or a price that differs between the screen and the check, is an operational incident even when every component is up. The work is to make the path of a price plain. Where it starts, what changes it, who is allowed to override it, and which consumers may keep a private copy. Risk checks belong on that same map. A limit that uses a stale price, or a limit the order path can skip, does not control the order.
We keep the scope on the trading platform. This is the pricing and the risk that sit next to electronic and algorithmic flow. When the price exists to drive an order, or to stop one, it is in scope.
Who it is for
Clients are desks and the technology teams that support them, in banks and in smaller firms. A pricing service may already exist and need a clearer distribution path. A risk check may still be a manual step that has to move onto the order path. A new asset, including crypto, may need a price source joined to limits the firm already understands. We have worked on these problems on large platforms and on systems built for a single team.
The person who calls is often trying to stop a specific disagreement. The trader saw one price and the check used another, or a limit fired on a position nobody could reproduce. The engagement starts from that disagreement and ends with a path the team can operate.
Typical work
Distribution is usually the first design. A price leaves a source, is validated, and reaches the strategy, the trading interface, and the risk check. We name those consumers and the age of price each of them is allowed to act on. A strategy may need to trade on a tick, while a screen may lag. They still have to be traceable to the same source when somebody asks why two numbers diverged.
Overrides and manual prices are the next design. Desks mark prices, pull a bad print, and sometimes type a level. The system has to record who did that and which consumers picked it up. An override that expires without a record, or one that the risk check never sees, brings the original disagreement back.
Checks on the order path follow. A limit may be a quantity, a value, a position, or a price collar. We place the check where an order can still be stopped, and we show the reason on the path the operator watches. The life of the order, including parent and child orders worked against a benchmark, is described on the benchmark execution page. The decision to send a child order can call a check. The check lives in one place, and the algorithms call it.
Pricing for an algorithmic strategy has a further requirement. The price the strategy used when it decided has to be recoverable afterwards, well enough to explain the decision. We include that record when the strategy and the price path are in the same engagement. Languages and the way we deliver are on the about page. Asset classes, from cash equity and listed derivatives through FX and crypto, are on the services page.
How an engagement runs
A review of a price path, or of a single limit, is a short engagement. Redesigning distribution, or putting a set of checks onto a live order path, is a larger block or a retainer. The sizes are listed on the packages page.
Contact us and describe the price the desk disagrees about, or the check that fires when it should not.