It’s challenging for investment managers to automate processes and workflows. There are many reasons why, some related to system(s) and some related to how the industry functions. We’ll go into detail in this post about the challenges, which are more easily overcome than others, and concretely how to automate more than today.
Four aspects make automation of processes and workflows a challenge for investment managers:
With one Front-to-Mid/Back platform, automation just becomes features within the software, without having to control and move data between systems and sources.
AlphaFMC have looked into investment in automation, and found 5 areas of investment (you don’t need to know what all of these mean to continue to read and understand the takeaways in this article):
Our interpretation of this list, is that these are all attempts to automate on top of existing systems. I.e. an attempt to add a layer between the system and humans using the systems (or “hack” the user interface). But the problem is that the systems aren’t built to support that. It‘s no surprise that AlphaFMC also found that most initiatives in automation fail to provide positive ROI.
Here’s the thing: there is no need to “do” operations anymore. Software can actually “do” operations by now, including tasks such as:
Below is the interpretation used throughout this article:
When I was on the buy side, we managed a $1.5bn macro portfolio. For this single portfolio, a colleague of mine had a process that started at 4 pm each day. She sat on the desk next to me, so sometimes I’d assist if I had the time.
Here’s how the next 3 hours would unfold:
Clearly, this process wasn’t great. But:
It had everything to do with subpar software.
We should’ve had more semi-automatic processes:
... And we shouldn’t have been waiting for a quarter of an hour for a system task.
Don’t get me wrong, I’m not saying everything should (or can) be automated. The entire operations role isn’t threatened by this automation (nor by AI, at least not in the next decade).
What I’m saying is that it’s possible to remove mundane, repetitive tasks from expensive team members (who, by the way, get bored with that type of task) and hand them off to software. Elevate your team to more rewarding tasks that software (and AI) can’t do: break resolution, process development and counterparty coordination.
In exception-based workflows, the software/AI takes over all “check that...” tasks and anything that resides as a calendar reminder. It automates those tasks as much as possible. As soon as something doesn’t go right (deviates from the “Happy path”), an issue is flagged for a user to resolve.
Ideally, at any point in time, you can see a status dashboard within your automated investment software. Here’s a visual analogy:
Car analogy | Software | |
Old way | Driver manually checks oil stick regularly | “Check that X” tasks in todo lists and calendar reminders |
Full automation (not possible) | The car drives to the petrol station and refills the correct oil (by itself). And identifies if there is a leakage, finds the issue, buys replacement parts and repairs itself | Software turns into a system user and replaces 90%+ of investment manager staff |
Exception-based (the future) | The car continuously monitors the oil level and notifies the driver when it’s low – even when the vehicle is parked, via mobile notifications | The software performs repetitive tasks and notifies users when issues happen or obstacles are faced |
How many firms do we see that have exception-based workflows at scale? Less than 25%, according to our proprietary research.
We all know exception-based workflows are the future. Here’s the effect automated investment tools have on the operations role:
We strongly believe that workflow efficiency should be given a significant emphasis in system selections. Most RFI/RFPs focus on features (yes/no), but forget the “how”, when evaluating automated investment platforms.
A client of Limina saved 50% on their entire operational cost when changing from another system to us. And it’s not a one-off case study, we have more cases that are in the same ballpark. Set Limina aside for a moment and just reflect on that number. That time is worth much more than the cost of the system.
Exception-based workflows really do provide massive efficiency improvements, in the real world, here and now. These benefits aren’t uncovered with a simple yes/no answer checklist.
Tactical advice:
The difference between providers might look like <5% on paper. But in reality, it can be more than 2x! As the referenced case study highlights.