❯ git show --details cases/wealth-advisor.md
Platform

A platform launch that had to clear Compliance before an advisor ever saw it

Four years as the P&L, pricing and packaging owner for Morgan Stanley's Wealth Advisor multi-channel platform. The build was never the hard part. The hard part was getting Legal, Compliance, Product and hundreds of field advisors to agree on how it would run, then proving the unit economics.

role
AVP, Product Management
timeline
2020 – 2024, New York
users
Hundreds of wealth advisors and the ops teams behind them
partners
Product, Engineering, Sales, Legal, Compliance, Finance
outcome
25%+ engagement lift; P&L, pricing and packaging ownership

The seat

Morgan Stanley Wealth Management runs on its advisors. The platform I owned was the multi-channel surface those advisors used to serve clients, and my remit covered the commercial side of it: the P&L, the pricing and packaging, the marketing budget, and the roadmap that Product, Engineering, Sales, Legal and Compliance all had a vote on.

I spent most of my time between two groups. The field: hundreds of advisors who would tell me, bluntly, what broke. And operations: the teams that sit between the field and finance, who had to run whatever we shipped. A fix only stuck when the field, ops and finance all agreed on how it would work day to day.

Running the launch as an internal sell

A regulated launch is sequenced, not scheduled. Before a single client saw the product I had to take it, in order, through Product for scope, Legal for what could be said, Compliance for what could be done, and the field for whether anyone would use it. Each of those groups could stop the launch and none of them reported to me.

01
Business case firstA scenario model that showed engagement, revenue and cost per advisor under three adoption paths. Finance signed the base case before anyone saw a screen.
02
Compliance as a design partnerModel-risk and data-governance controls were in the requirements, not bolted on. Compliance reviewed prototypes, which is faster than reviewing a finished build.
03
Field championsA small group of advisors shaped the packaging and became the people other advisors asked. Adoption followed them, not the launch email.
04
Ops runbooks before go-liveEvery new flow had an owner in operations and a documented exception path, so the first week's problems had somewhere to go.

Pricing and packaging

Owning pricing on a regulated wealth product means defending every tier to Finance, Legal and the advisors who sell it. I built the packaging around how advisors actually bundled services for clients rather than how the product org had organised features, and tied the pricing to a long-range, driver-based revenue model that I maintained and reforecast quarterly.

The same model became the executive narrative. When the product took an ambiguous platform bet from concept to a funded roadmap, it was the value logic in that model that carried the decision, not the feature list.

Results

25%+lift in advisor engagement
P&Lowned, with pricing and packaging
4 yrsof roadmaps through Legal and Compliance

Engagement rose by more than a quarter after launch, with a measurable lift in revenue. The platform became the surface for later work, including the private markets access path that brought capital calls, secondaries and position reporting to advisors' clients.

What stayed with me

  • Compliance is faster when it is early. Reviewing a prototype takes a week. Reviewing a finished build takes a quarter, because every change is now a change request.
  • The field decides. No launch email ever moved adoption. A handful of respected advisors did.
  • Own the number. Having the P&L meant I could say no to features with a figure attached, which is the only kind of no that holds in a large organisation.
06.

connect()

Building something where a wrong number costs money?
Fintech, accounting, operations, applied AI. I am always open to talking with people who ship.

$ echo "Let's build something that survives an audit"