On 14 April 2026, we brought a group of clients and partners together at our Luxembourg office for the Depowise 2026 Product Roadmap presentation.
The format was deliberate. Not a product launch. Not a marketing event. A working session: here is what we are building and why, here is how we make product decisions, and here is where we want your input.
We think that kind of session matters, and we want to explain why.
Product decisions carry real consequences in this industry
Depowise operates in a regulated environment where the product is, in a meaningful sense, the governance. The platform generates the evidential logs that auditors require, supports the oversight controls that regulators inspect, and automates the processes that keep depositary teams compliant at scale.
That means every product decision carries consequences that go beyond user experience: what gets prioritised, what gets built, what gets deferred. A feature that works incorrectly in a fund oversight context is not just a bug. It is a regulatory exposure for our clients.
We presented our approach to product governance at this session: how we set objectives, how we structure delivery, how we define quality, and how we make sure the roadmap reflects what our clients actually need rather than what looks good on a slide. The goal is a product organisation that is structured, accountable, and continuously improving, because anything less is not good enough for the environment our clients operate in.
Outcome-focused, not feature-focused
One shift we have been deliberate about is moving from shipping features to delivering outcomes. The question we ask when evaluating anything on the roadmap is: what changes for depositary teams and the funds they oversee? If the answer is vague, the work is probably not the right work.
The five initiatives we are delivering in 2026 were each framed this way. Not what we are building technically, but what becomes possible for our clients that was not possible before. That framing keeps the focus where it belongs: on the people using the platform, in the operations it runs inside, under the regulatory frameworks it supports.
Why client proximity matters
The depositary sector is not a generalist market. It is specific, regulated, and operationally demanding in ways that are hard to understand from the outside. The gap between what a product team imagines depositary teams need and what those teams actually experience day-to-day can be significant.
That is why sessions like this one are part of how we work, not an add-on to it. When clients tell us directly what is working, what is not, and where the friction is, that information shapes the roadmap in ways no amount of internal discussion can. It closes the feedback loop between product decisions and operational reality.
We left the morning with specific input we will act on. That is the point.
The ecosystem we are building
Depowise started with the belief that the depositary function deserved its own purpose-built technology. Not adapted tools from adjacent markets, but a platform designed around what depositaries actually do.
That belief is as strong as it was when we started. What has changed is the scale of what we are building on top of it. The 2026 roadmap reflects a platform that is maturing: better governed internally, more capable for the depositary teams running it, and increasingly positioned to support the operational demands this industry is heading toward.
Depowise builds technology for depositaries. The Depowise platform supports Cash Flow Monitoring, Safekeeping, and Oversight in one operating environment, helping depositaries manage their core duties with greater consistency, control, and efficiency. Depowise serves institutions managing 2,500+ funds and over €2 trillion in assets.
