Advisor Platforms

The setting

Wealth-management advisor and client portals built on InvestCloud’s framework. I contributed to or led 0-to-production deploys across 50+ institutions, including Chase, Cetera, Northwestern Mutual, Voya, Silicon Valley Bank, East West Bank, and many more.

One platform underneath; per-institution branding and content on top. Fifty-plus deploys on the same codebase.

Where the design work was

The components came from upstream design teams that owned the Figma files and brand systems. The work was in the gap between Figma and a multi-tenant CMS that wasn’t built around modern token systems.

Most of the day-to-day was hand-written CSS implementing those handoffs at the institution level, without breaking the shared codebase underneath. That meant:

• Reading the intent behind a Figma file, then reproducing it in a CMS that didn’t always have a primitive for what was drawn.
• Holding per-institution branding inside a system that wanted to enforce its own.
• Keeping dense, data-heavy layouts readable across desktop, tablet, and mobile, often within design constraints authored mostly for one breakpoint.
• Coordinating with design, product, and QA tightly enough that “this looks right in Figma” and “this works in production” stayed connected.

Working with design

The best portals came from design and implementation working together. The worst came from a one-way handoff.

A good handoff names the constraints up front: which spacings are token-backed, which states are designed, and where the system can flex. A bad handoff is just a frame.

Most of the work was reproducing the design; the rest was closing gaps the handoff didn’t see.

What the platforms supported

• Portfolio management
• Advisor and client interaction
• Onboarding and lifecycle workflows
• Multi-account and multi-role environments

Takeaway

Working across many institutions taught me to read what a design team meant and what the system could support. Both skills have stayed useful.