Most tech workers have most of their wealth tied up in their employer's stock. The existing advice ("diversify, talk to a CPA") is generic and unactionable. I built MyRSU to fix that.
It's a free, open-source MCP server that lets AI assistants give real numbers. Ask Claude "I have $700K in NVDA, am I dangerously concentrated?" and it returns:
What I shipped:
What I'm trying to figure out:
Built as a side project, no paid tier yet, no advisor license — stays on the "tool informs, you decide" side of the regulatory line.
Curious if anyone here has shipped finance-adjacent tools — the licensing tightrope is interesting to navigate.
This is a strong wedge, but I’d be careful not to frame it mainly as “MCP for personal finance.”
The sharper category might be closer to concentrated-equity risk simulation for tech employees.
That makes the pain clearer: not “ask AI about RSUs,” but “understand what happens if your employer stock drops, your job disappears, and your lifestyle depends on both.”
For B2B, I’d probably test financial advisors first, but not as a full advice tool. More like a pre-meeting scenario layer they can use to make concentrated-stock conversations more concrete without crossing into automated advice.
The licensing line is probably the positioning challenge as much as the product challenge. If the tool feels like it recommends actions, risk goes up. If it frames itself as scenario modeling and risk visibility, the category feels safer and easier to explain.
This is genuinely useful — both the category reframe and the advisor positioning. "Concentrated-equity risk simulation" is sharper than what I've been using, and the cascading framing (stock + job + lifestyle as a single event) is closer to what the product actually models than "risk score" suggests.
The pre-meeting scenario layer angle is the move, I think — advisors get a visual to make abstract risk concrete, the tool stays clearly on the modeling side of the line. Going to test exactly this angle with a friend who's a financial advisor next week.
One thing I'm chewing on: how do you handle the moment a user explicitly asks "so should I sell?" Deflect entirely and the tool feels useless; answer and you cross the line. Curious how you'd think about framing that boundary in the product surface itself, not just in disclaimers.
That is exactly the hard product moment.
I would not deflect with a generic disclaimer, because then the product feels evasive. But I also would not answer the sell question directly.
The frame I’d use is:
“I can show what changes under different choices, but I cannot choose for you.”
So instead of “yes, sell” or “no, hold,” the product should probably move into scenario paths:
what happens if you hold
what happens if you diversify gradually
what happens if the stock drops 30 to 50 percent
what happens if job income and equity value fall together
what questions to bring to an advisor before acting
That keeps the tool useful while staying in the risk-visibility lane, not the recommendation lane.
This is probably worth mapping carefully because it affects product copy, UX, advisor positioning, and trust. Drop your email and I’ll send over a tighter version instead of trying to squeeze the whole boundary flow into the thread.
Appreciate the help . Apology for the late reply . email:dalsaniavidhi@gmail.com
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.