Rather than a long menu of tasks, we group ETRM work into five themes a business sponsor can reason about. Each is a lever on cost, risk or speed, and each expands into detailed workstreams once scoped.
Strategy and platform selection
Target operating model, build-versus-buy, vendor-neutral platform selection and a roadmap tied to business outcomes rather than a licensing agenda. Done well, this means the business can point to a specific, measurable improvement rather than a vague sense that things are better.
Trade lifecycle and valuation
Reference data, trade capture and lifecycle integrity, curve building and valuation correctness, so front and middle office finally agree on the numbers. Done well, this means the business can point to a specific, measurable improvement rather than a vague sense that things are better.
Risk, limits and reporting
Position, P&L, VaR and limit frameworks, plus regulatory and internal reporting that can be reconstructed on demand for an auditor. Done well, this means the business can point to a specific, measurable improvement rather than a vague sense that things are better.
Cloud, data and integration
Cloud-native architecture, integration with exchanges, brokers and the back office, and a data foundation that new products and feeds plug into cleanly. Done well, this means the business can point to a specific, measurable improvement rather than a vague sense that things are better.
Operations and managed services
Scheduling, settlement, run-books and optional managed services, so the platform is operated to a service level rather than left to a stretched internal team. Done well, this means the business can point to a specific, measurable improvement rather than a vague sense that things are better.
Strategy and platform selection is where the largest money is won or lost, long before a line of configuration is written. We define the target operating model, run an evidence-based, vendor-neutral evaluation, and produce a roadmap tied to business outcomes, so the platform you choose fits how your desks actually trade rather than a licensing agenda. Getting this wrong is the single most common cause of the expensive, ossified customisations that trap firms years behind.
In delivery, this theme is where we insist on separating the selection decision from any implementation incentive, and where we translate trading strategy into concrete platform and data requirements a board can sign off with confidence.
Trade lifecycle and valuation is the substance of a trustworthy ETRM. We get reference data, trade capture and lifecycle events right, and we prove valuation correctness against known cases, because this is what determines whether front and middle office can ever agree on a number. When this layer is solid, reconciliation stops being a daily firefight; when it is not, no amount of dashboards will hide the cracks.
We treat this as the proving ground for the whole programme, because if valuation and lifecycle are demonstrably correct on a representative set of trades, the rest of the build rests on solid ground rather than on assumptions that surface painfully at go-live.
Risk, limits and reporting turns a trading platform into one a regulator and a board can rely on. We build position, P&L, VaR and limit frameworks and reporting that can be reconstructed on demand, so the desk sees exposure clearly and the institution can evidence control. This is the difference between managing risk and merely recording it after the fact.
We design these frameworks so they serve both the desk and the institution: granular enough for a trader to act on intraday, and structured enough for a regulator or internal auditor to follow without a bespoke reconstruction each time.
Cloud, data and integration is what keeps the platform fast to change. We design cloud-native architecture and clean integration with exchanges, brokers and the back office, so new products and feeds plug in as configuration rather than core surgery. This is the layer that decides whether the business can respond to the market and to regulation in weeks or in quarters.
We favour open interfaces and event-driven patterns here, because the integration choices made at this layer decide, more than any other, whether the platform stays adaptable or slowly calcifies into another legacy estate.
Operations and managed services is the part most programmes underinvest in and later regret. We get scheduling, settlement and run-books right, and offer managed services where it helps, so the platform is operated to a service level rather than left to a stretched internal team. This is what reduces key-person dependency and keeps go-lives from turning into standing crises.
We document run-books and operating procedures as first-class deliverables, so the capability survives staff turnover and the platform is genuinely operable rather than dependent on the handful of people who built it.