One of the most satisfying moments in a customer conversation is when the architecture clicks into place mid-call.

One of the most satisfying moments in a customer conversation is when the architecture clicks into place mid-call.

Had a design session recently with an RIA ops team getting ready to move from discovery into a real pilot. They’d already mapped out their Box folder structure, had Salesforce running, and were exploring a wealth.com integration for estate planning documents.

The pain they described was straightforward but familiar: files coming in through an onboarding portal with no way to route them automatically. Someone was manually downloading each file and dropping it into the right client folder.

Then Simon said something that stuck with me:

“That doesn’t integrate with anything, so what we end up doing is heavy lifting — taking those files, downloading them, and then dropping them into each individual folder and filing them away.”

That’s the job right now for a lot of ops teams. Not complex judgment work. Just file movement.

When we walked through what the integrated version looks like (Box webhook triggers processing on upload, files route to the right folder automatically, wealth.com assets get generated in parallel), the reaction was immediate.

I think the point here is that the primitives are already in place at most firms. The blocker isn’t the systems. It’s the layer that makes them talk to each other.

This is going to be fun.