How firms design for growth that compounds
Scalability is not a capability firms build directly. The three preceding articles showed what produces it: resilience, agility, and data trust, each built on a shared foundation and reinforcing the next. This article sets out the architectural decisions that determine whether a firm captures that compounding effect or loses it to friction: consolidating onto a shared core, treating data integrity as infrastructure, and directing recovered capacity toward the investment process. Firms that make those decisions early find that each new addition costs less than the last.
Storebrand Asset Management, a SimCorp client, more than tripled its assets under management in a decade without growing its operations team because it built the architecture before the growth arrived.
Growth compounds by design
Many firms measure scalability by available capacity: can the systems handle more portfolios, more positions and more transactions as AUM grows? It is a reasonable question.
The real test of scalability is whether the operating model can absorb growth without adding friction: whether new products, acquisitions, or channels extend the existing architecture or sit alongside it. Where that discipline is in place, growth compounds. Where it isn’t, cost and complexity build and begin to affect how investment decisions are made.
— Ben Keeler, Partner, Citisoft
Firms that improve margins, efficiency, and decision-making quality as they grow make deliberate architectural decisions early.
The cost that doesn't show up in the budget
A mid-sized active manager acquires a fixed-income boutique and keeps its order management system running in parallel. Three years on, both are still live. The middle office runs dual reconciliation workflows. The risk team produces two versions of the aggregate exposure report and manually resolves the difference daily. The firm now carries additional headcount, a recurring reconciliation gap at the monthly close, and a morning risk report that approximates current positions. Each sub-optimal outcome originated via discrete decisions, none looked significant at the time. The first two show up in the budget. An architecture that lags quietly shapes every investment decision the firm makes.
The timeline differs by growth model
Organic growth builds pressure gradually as firms add products, asset classes, and markets. Where the firm has established architectural discipline from the start, new strategies can be added with declining marginal effort, and the cost of each addition stays flat or falls. Where it has not, point solutions accumulate, data pipelines multiply, and bespoke workflows built for specific needs become load-bearing over time.
Acquisition-led growth follows the same logic, faster and with less room to absorb it. Running parallel operating models in the short term is a rational trade-off when migration complexity is real. The question of scalability is whether acquired capabilities can be integrated before fragmentation becomes structural. If left unresolved, the parallel model that was pragmatic at 18 months becomes expensive to maintain at three years and increasingly complex to integrate at five.

PE-backed consolidation compounds the pressure further. A sponsor rolls up three boutiques across 18 months. The investment thesis depends on cross-entity reporting, unified risk oversight, and a cost base that reflects one operating model rather than three. The organizational structure consolidates on schedule; the underlying systems do not. By the time the firm prepares for exit, the data team is stitching together weekly reports from three separate platforms. The consolidated number reaches the investment committee, but the underlying data falls apart under due diligence. Replacing the architecture by then competes with running it.
In each case, the architectural problem is the same; what differs is how much time the firm has before complexity becomes structural. The firms that pull ahead build long before the pressure arrives. This five-part series has tracked what makes that scalability possible. It starts with a single foundation, and three capabilities built on top of it: resilience, agility, and trust in the data itself. Each one compounds the others. Resilience built into the operating model means disruption doesn't consume the capacity needed to grow. Agility then puts that preserved capacity to work, closing the distance between opportunity and execution. Add data trust, and the front office acts on that narrowed gap without a verification cycle slowing it down. Deployed together, these capabilities produce what no single one can: scalability.
Three decisions that determine whether growth compounds
How Storebrand Asset Management More Than Tripled AUM Without Growing Its Operational Footprint
Storebrand Asset Management, a SimCorp client, is one of Norway's largest asset managers, with approximately NOK 1,650 billion in assets under management across equity, fixed income, index, quantitative and alternatives strategies: around 80% of this is managed inside SimCorp. Over the past decade, its AUM has more than tripled. That growth creates a specific operational test: whether the architecture beneath the business was designed to absorb it, or whether each addition would extract a progressively higher cost.
Built for where the firm was heading
In 2015, with around NOK 500 billion in assets under management, Storebrand was running across a portfolio of third-party systems. The infrastructure worked, but it carried a structural limitation familiar to any growing asset manager. Data was distributed across systems optimized for discrete functions. Reconciliation was a recurring requirement rather than an exception. Each system added capability, but also added to what the operations team had to reconcile and maintain. The operating model was performing. The question was whether it was built for where Storebrand was heading.
One system, front to back
Storebrand's response was structural. “Moving to a single integrated platform was a deliberate commitment, not just a technology decision. We needed a foundation that would grow with us, one we would not constantly need to work around,” explains Sara Thea Von Zernichow Sponheim, COO at Storebrand Asset Management.
The goal was a single source of truth, accessible to everyone in the investment process.
Having one system means everyone in the firm, from portfolio managers to external clients, works from the same information. That changes the quality of every conversation and every decision.
— Sara Thea Von Zernichow Sponheim, COO, Storebrand Asset Management
The scalability dividend
Storebrand's AUM grew from 500 billion to 1,650 billion NOK in a decade without a proportional increase in the operations team. "We are able to take on new clients, new mandates, new funds. The platform was built to absorb that growth, and it has," Sara Thea notes.
The clearest example sits in Storebrand's index and quantitative portfolio management function. “The scale of what our index and quantitative team manages relative to its size would not be possible without the right infrastructure. That is what a well-designed system enables," says Sara Thea.
How firms scale success is decided before the opportunity arrives
Every firm will face the next acquisition, the next strategy, the next regulatory demand. When the foundation stays intact, growth is absorbed without consuming the capacity needed for where the firm moves next. That is a strategic decision, and it is made long before the opportunity arrives.
When the architecture is ready, every moment of success becomes an opportunity to scale that success into a structural lead before competition catches up.
— Alun Cutler, Executive Director, Commercial Development, SimCorp
You may also like

.jpg)




