Jonathan Simcoe

Mercury's design system documentation had split across code, Notion, Figma, and a divergent AI-built implementation. I led a two-person effort to build one resolved, structured system that both people and agents could use.

Stripe gave us early access to a new full-page app platform, but the tools were still taking shape. In four weeks, I used working prototypes to translate between Mercury and Stripe and help launch a new Mercury dashboard at Stripe Sessions.

Accountants were juggling logins and inboxes to serve clients on Mercury. The Advisor Portal gave firms one place to manage clients, teams, and referrals.

A bird's-eye view for Mercury's multi-org customers — designed mid-flight on a v0 spec, shaped by vocal beta users, and launched with the bulk workflows accountants actually asked for.

Customers were already funding SAFEs through Payment Requests, so we built them a real tool — Mercury's first business-graph play, shaped by a launch-and-learn philosophy.

How an impossible-sounding constraint — a public link that exposes bank details — became the core of Mercury's simplest way to request money.

Banking products are usually bought blind. We put the entire Mercury product online, ungated, and let anyone try the real thing before signing up.