TL;DR
Fintex builds an investor hub and an admin tool for a national wealth-management firm and its credit union and correspondent partners. They are two surfaces of one platform, and the platform has over 100,000 investors onboarded across the partner network. I own the product: the roadmap, the prioritization calls and the requirements, on a team of sixteen at Fintex working with two product people on the client side.
The problem
Every partner firm on the network wants a platform that feels like its own, and building one per client does not scale past the second or third. Credit unions add a second pull: they are member-owned, so the same platform has to serve a member checking a balance and an administrator running the book, without turning into two products.
What I owned
The roadmap and the prioritization calls, and defending the trade-offs behind them. The product requirements: user stories, acceptance criteria, and the edge cases that decide whether a release holds. Daily work with engineering and design, from technical design discussions through launch, and mentoring the two business analysts on the team.
What is not mine: the investors. They were on the platform before this project began, and the count comes from the team's analytics rather than anything I measure. The platform also runs in the client's environment, not Fintex's, and I do not operate that infrastructure.
The hard part
One product, many partners. The platform sits on a third-party wealth-data feed and two internal databases, with three platforms on top: the investor hub and the admin tool, which Fintex owns, and a vendor-owned advisor platform, which it does not. Every partner-specific request is a choice between configuring the one product and forking it, and the job is to keep choosing configuration, because each fork is a second product to maintain in an environment we do not control.
Outcome
The platform has over 100,000 investors onboarded and is still adding them. In my first month as senior PM I worked with the developers to descope lower-impact features, and showed stakeholders that address change carries heavy compliance scope with no viable minimum version. It moved to 2027, with the groundwork starting now rather than a half-built version shipping early. The project is ongoing.