Why Luxembourg Asset Managers Are Restructuring Their Technology Functions

A technology function built around one person or a small team wearing several hats — infrastructure, vendor management, data governance, all at once — works well at a certain fund complexity level and stops working cleanly the moment that complexity genuinely increases. The restructuring that follows is rarely about headcount alone; it’s about whether the function’s structure still matches what the business actually needs it to do.

Luxembourg’s asset management sector has seen a steady stream of managers expanding fund ranges, adding new asset classes, and crossing AUM thresholds that trigger additional regulatory attention — and a technology function that was appropriately lean for a simpler fund complex often becomes the visible constraint once that expansion genuinely takes hold. This is a reading of what actually drives the restructuring decision, and what a well-structured function looks like on the other side of it.

Who this is for

• The COO or Conducting Officer at a Luxembourg-domiciled asset manager sensing the technology function’s structure hasn’t kept pace with fund complexity.
• The board evaluating whether to restructure the technology function ahead of, rather than in reaction to, the next expansion.

Generalist structures hit a specific ceiling

A single technology lead, or a small generalist team, covering infrastructure, vendor oversight, data governance, and regulatory reporting simultaneously works well when the fund range is narrow and the vendor set is small enough for one or two people to genuinely understand deeply. The ceiling on this structure is specific and predictable: it’s reached when the number of distinct vendor relationships, fund structures, and regulatory reporting obligations exceeds what a small team can genuinely hold complete context on simultaneously — at which point oversight quality degrades quietly, well before it becomes visible as an incident or an inspection finding.

Delegation oversight is where CSSF scrutiny concentrates, and where thin structures fail first

CSSF inspections of Luxembourg fund managers consistently focus on genuine delegation oversight — not whether a delegate exists and holds the right authorisation, but whether the manager can demonstrate active, ongoing monitoring of that delegate’s performance and risk. A technology function stretched thin across too many vendor relationships is precisely where this monitoring first becomes superficial — reduced to reviewing a delegate’s own self-reported compliance attestation rather than independently verifying it, because there genuinely isn’t capacity to do more. Restructuring the function to give genuine ownership of the largest or highest-risk delegate relationships to a specific, accountable person is often the single highest-value structural change available.

Specialisation should track where the actual complexity sits

The right restructuring isn’t a generic headcount increase — it’s specialisation that tracks where the fund complex’s actual complexity has grown. A manager that’s expanded primarily by adding new asset classes needs deeper specific expertise in the data and valuation systems those asset classes require; a manager that’s expanded primarily by AUM growth within existing strategies needs deeper operational and reconciliation capacity instead. Restructuring without first identifying which specific dimension actually drove the complexity increase tends to produce a function that’s better resourced in aggregate but still thin exactly where the real pressure is.

DORA has made the case for restructuring more explicit

DORA’s requirement for a named role monitoring ICT third-party arrangements, distinct from general operational duties, has given many Luxembourg managers a concrete, externally mandated reason to formalise a restructuring that internal pressure alone hadn’t yet forced. A manager using this requirement as the trigger to build a genuinely resourced technology governance function, rather than satisfying it with a token role bolted onto an already-stretched generalist, gets more durable value from the same regulatory obligation.

What a well-timed restructuring covers

1. An honest assessment of whether current oversight of delegates and vendors is genuinely active or has quietly become reliant on self-reported attestations.
2. A clear identification of which specific dimension — asset class breadth or AUM growth within existing strategies — actually drove the complexity increase.
3. Specialisation built to track that specific complexity, not a generic headcount increase applied evenly.
4. DORA’s third-party monitoring role used as a genuinely resourced structural change, not a token addition to an already-stretched team.

How we engage with this

We read a technology function’s structure against the fund complex’s actual complexity — vendor count, asset class range, delegation depth — as an Architecture Review. The output is a written assessment of where the current structure is genuinely stretched and what restructuring would address it.

We don’t hire or place technology staff. We don’t sell fund administration platforms. We read what’s there, identify what’s missing, and write it down for the people who have to decide what to do about it.

Pricing is published at /pricing/. If your technology function’s structure hasn’t kept pace with fund complexity, the place to start is a conversation.

Sixteen Pillars is a technology governance consultancy based in Cyprus. Engagements run remote across the EU, UK, and Middle East, with on-site time where the engagement requires it.