Add People. Bring In a Vendor. Watch It Change.
When technology delivery stalls in asset management, the instinct is to add resources or switch vendors. Both are understandable. Neither addresses what’s actually broken.
WHY HEADCOUNT DOESN’T HELP
Adding more people increases complexity.
Each new team member introduces more handoffs, more interpretation across groups, and more dependencies to manage.
The delivery structure that was failing stays exactly as it was — it just gets more crowded.
WHY GENERIC VENDORS FALL SHORT
Vendors contribute to parts of the work, but no single group carries responsibility for the final outcome.
With limited domain expertise in asset management systems, they contribute to the work — but no one owns the result end to end.
The Structural Problem Generic Fixes Can’t Reach
What makes delivery in institutional asset management uniquely difficult isn’t a shortage of skilled people. It’s that most delivery models were designed for environments where requirements are stable, systems are well-documented, and there’s meaningful tolerance for iteration at go-live.
Asset management technology doesn’t look like that. Regulatory requirements evolve mid-project. Legacy CRIMS and IBOR infrastructure carries undocumented dependencies. Business teams measure results — not sprints — and the window for failure at cutover is effectively zero. A model that works in another vertical will struggle here.
Why Industry Experience Changes the Math
“When a consultant already understands what an IBOR is and why it matters, you’re not paying for their education. You’re paying for work.”
Every hour a vendor spends getting up to speed on your systems, your compliance environment, and your business logic is an hour you’re paying for without getting closer to delivery. For firms managing $15B or more in assets, that overhead compounds quickly — especially when requirements shift and context needs to be rebuilt from scratch.
The difference between a team that operates inside the industry and one that studies it for the engagement is not just speed. It’s the ability to identify risks that don’t show up in a requirements document, to flag integration issues before they surface at testing, and to know what questions to ask the business before they become blockers mid-sprint.
Five Questions to Ask Before the Next Engagement
Before selecting a technology partner for your next asset management initiative, these questions separate vendors with relevant delivery capability from those who will learn the hard way on your project.
- How is risk validated before rollout?
- What happens when requirements change mid-project?
- Who owns the outcome?
- How is rollback handled?
- What similar work has this team completed?