The Real Cost-to-Serve Question Asset Managers Should Be Asking

Fee pressure has become the universal backdrop to asset management. Active managers face a structural decline in fees, passive managers compete on basis points, and multi-asset and alternative strategies now meet institutional clients who expect the same discipline that has been applied to long-only funds for a decade. The numbers bear it out: the Investment Association’s latest survey of the UK industry put operating margins at 18 per cent, down from 31 per cent in 2019, with costs growing at 14 per cent against revenue growth of 10 per cent. The response has become almost rehearsed. Boards set reduction targets, cost-to-income becomes the metric of the year, headcount reviews follow, outsourcing conversations open. None of it is wrong, exactly, but almost all of it starts from the wrong question.

The question most firms reach for is where they can cut. The question that produces durable margin protection is a different one: what does it cost us to deliver our service, and to whom? Cost-to-serve sounds like a back-office abstraction, yet it is the single most useful lens an asset manager can hold over its own operating model, and very few firms can answer it with confidence.

The Visibility Problem

Cost-to-serve is so rarely understood because the data is scattered. Technology spend lives in the IT budget, operations headcount sits with the COO, vendor costs sit in procurement, compliance costs sit with legal, and fund accounting and administration are usually outsourced altogether. None of these views was designed to be aggregated into a per-fund, per-mandate or per-region picture of what the service actually costs. So recurring spend gets approved one line at a time. A technology contract is signed because the business case stands up, an operations hire is made because there is a gap to fill, an administrator’s renewal is accepted because it arrives with the renewal date. Each decision is rational in isolation, and none is ever tested against whether the firm is actually profitable on a given fund, mandate or region. That is not an accounting problem. It is a structural one: firms are organised around products and people rather than around the cost of delivering a service, and the accounting view follows the organisational one.

What Cost-to-Serve Actually Means

Cost-to-serve is more granular than cost-to-income. It is the total recurring cost of operating a fund, mandate or product, set against the revenue it generates. The components are familiar enough:

• Investment operations support, and fund accounting and administration.

• Compliance overhead, and the effort behind audit and regulatory reporting.

• Technology platform and vendor costs, allocated by usage.

• The share of operational headcount whose time the fund consumes.

• Client reporting and onboarding.

The difficulty is allocation. The fund accountant who covers five funds does not naturally split their time by fund, the platform that runs nine strategies does not bill by strategy. The total is visible; the apportionment is judgement. Firms that build a real cost-to-serve view invest in exactly that judgement, and the view does not need to be perfect so much as good enough to drive decisions. Once it exists, the conversations change. A fund whose cost-to-serve exceeds its fee revenue stops being a hidden drag, a mandate retained for relationship reasons becomes a visible trade-off, and a platform that costs more than it delivers finally becomes a candidate for review.

Why Cost-Cutting Without Visibility Undoes Itself

The firms that struggle with cost discipline are rarely the ones who cut; they are the ones who cut without visibility. The pattern is familiar. A board sets a ten per cent target, it is distributed across the functions, each function finds its savings, the numbers add up, and within six months the cost-to-income ratio has drifted back to where it started.

The reasons are predictable once you look at the service rather than the function.

• A trimmed operations team means more manual process, more senior time spent checking it, and the cost reappearing in a different line.

• A reduced technology budget means deferred upgrades, more incidents, and more support cost absorbing the saving.

• A vendor consolidated without the documentation and exit terms to leave it means deeper dependency, a weaker position at renewal, and the cost coming back the following cycle.

Functional cost reduction is simply too narrow a view to manage against. The work that protects margin has to be done at the service level, which is why the firms that succeed build visibility first and reduce second. When they do, the reduction lasts.

Service Consistency Is a Margin Issue

There is a second leak, less obvious than vendor spend but no less corrosive: inconsistent service. In most asset managers, the service that different regions, functions and client tiers receive is uneven almost by default. The largest mandates get responsive support because they are commercially important. The smallest get whatever capacity is left. One office gets next-day responses while another, several time zones away, waits three days. Investment operations is prioritised because it sits closest to the people who set priorities. Client reporting waits in the same queue as office moves.

This sounds operational, yet it costs commercially, because the under-served parts of the firm respond in predictable ways. They build workarounds, they hire locally to compensate, they escalate simply to be noticed. The regional office takes on an analyst whose job is partly to chase head office, the client reporting team builds its own data capability, and a shadow organisation grows in the gaps, none of it planned and none of it on a single line item. The remedy is not a larger central function but a service model that knows which workflows are tied to revenue, mandate retention and resilience, and resources them accordingly. Consistency by design is a structural contributor to margin. Consistency by accident is a steady leak.

In practice: one standard across fourteen offices A global investment group with 446 users across 14 offices in the Americas, EMEA and APAC, operating as three legal entities, chose a single L1 to L3 service run by Saragossa Deploy over a multi-vendor model. Two years in, average resolution is 3.44 hours against an eight-hour target and first-contact fix is 85 per cent against a 70 per cent target, held to the same standard in every office and time zone. The contract was renewed in 2026 with expanded scope.

Outgrowing the Operating Model

Underneath all of this sits a version of the same problem that reaches most institutional asset managers eventually: they have outgrown their operating model. Funds, mandate types, asset classes, regulatory obligations and offices have all multiplied. The internal teams have grown too, but not at the same rate and rarely in a structured way. The result is a service model that works in pockets and creaks under load. A reporting cycle misses a deadline because a data feed broke while the one person who understood it was on leave. A consultant’s due diligence question takes three weeks to answer because nobody is certain who owns the workflow. The team is good; the structure around them has not kept pace.

The instinctive response is to replace things: a new platform, a new operating model, a new set of providers. Often enough the result is a more modern version of the same problem, because the structural work underneath, who owns each workflow, how it escalates, what standard it is held to, was never done. The more durable answer wraps what already exists rather than replacing it: documentation, clear escalation paths, real governance over the platforms the firm already runs, and service-level discipline on the workflows that matter most. The team does not need rebuilding. The wrapper around it does. And this is where the cost-to-serve view earns its keep, because it makes that work concrete: where cost is concentrated, where service is inconsistent, and where recurring spend is no longer earning its place.

Where Saragossa Comes In

Of all the lines in a cost-to-serve view, technology and operations support is usually the hardest to read. It is spread across internal headcount, contractors, vendor contracts and the time senior people spend on things that are nobody’s job, and it varies by office in ways nobody has measured. Saragossa’s Deploy service turns that line into something a CFO can see: a co-managed layer alongside the internal team, inside the firm’s own tooling, standards and access model.

• Recurring spend becomes a defined scope with a defined standard. Data feeds, client reporting, regulatory reporting and the platforms underneath them each carry an agreed service level, reported monthly by workflow and by office. The spend maps to the service.

• Consistency is contractual rather than accidental. The smaller office and the smaller mandate get the same standard as the flagship, which is what stops the local hires and the shadow capability before they start.

• The wrapper gets built. Runbooks, escalation paths, a RACI across the internal team, administrators and vendors, and a governance cadence that reports repeat incidents and the senior time returned from firefighting.

At one specialist asset manager running more than 100 SLA-bound data extracts, that meant a 19×5 application support team live in six weeks, daily job failures down from 11 to 4 within three months, and senior engineers back on engineering rather than overnight failures, at 45 to 55 per cent below the cost of onshore equivalents. Control, documentation and evidence stay with the firm throughout, and nothing has to be unpicked at exit.

The Question That Actually Matters

The asset managers that protect margin over the next five years will not be those with the deepest cost-cutting budgets but those with the clearest view of what their service costs. Cost discipline is universal and cost visibility is rare, and it is the combination, applied consistently across funds, mandates and regions, that separates the firms that defend margin from those that defer the problem. So the question was never where you can cut. It is what your service costs, where, to whom, and whether that spend is still earning its place.

Start with one number

Give our team half a day for a workshop to stop by and model your current capability against the market.  We’ll work with your technology and finance leads to map where the support spend sits, how consistently the service reaches each office and function, and what a defined standard would cost against what you pay now. Speak to Jamie Smith or start at saragossa.io/contact

At Saragossa, we operate as a velocity execution partner to investment firms, bringing specialist talent through Connect, managed IT services through Deploy, and consulting and project delivery through Consult within a single relationship. Three capabilities, one accountability line for the operating model.