Something that contradicts how most enterprise software conversations happen in wealth management. After nine months of evaluating AI tools, one firm’s conclusion wasn’t to buy more capability. It was to build it themselves. That’s not hesitation. That’s clarity about what actually works.
The firm knew their data. They knew their workflows. They knew exactly what they needed a tool to do and, crucially, what they didn’t need it to do. After nine months of vendor demos, they hadn’t found anything that fit cleanly — not because the tools were bad, but because the tools were built for someone else’s problem.
The build decision wasn’t about cost or not trusting vendors. It was about specificity. A general-purpose tool that does 80% of what you need creates a workflow where someone still has to do the other 20% manually — and that 20% is usually the part with the highest consequence.
We see this more than you’d expect. Firms that have done the work of understanding their own operations well enough to evaluate vendors often know their own requirements well enough to build. The evaluation process itself is the design process.
What we try to offer is the part they can’t easily build themselves: the data connectors, the identity layer, the infrastructure that lets purpose-built workflows reach across systems. The firm’s domain expertise stays inside the firm.
#WealthManagement #AI #OperationsStrategy #BuildVsBuy