Case study
Pyth NetworkProduct Design Lead2026 — Now
Pyth Terminal
Self-serve market-data terminal for Pyth: 3,800+ symbols and 61 continuous indices, used by 129K people a month and driving nearly half of new revenue through touchless signups.
- Client
- Pyth Network
- Role
- Product Design Lead
- Timeline
- 2026 — Now2 months
- Skills
- Product Design, UX Design, UI Design, Design System, Data Visualization, Design Leadership, Frontend Development, React, TypeScript, Storybook, MCP, Claude Code, AI-Augmented Workflows
- 129KMonthly active users
- +44%Month-on-month growth
- ~50%New revenue from self-serve signups
- 3,800+Symbols in the catalogue
Pyth Terminal is the public front door to Pyth market data: a catalogue of every price feed and index Pyth publishes, and the self-serve on-ramp to Pyth Pro. Traders and developers search thousands of feeds across crypto, equities, FX, commodities, metals and rates, inspect any feed in detail, and get an API key without talking to sales.
I led the design and built product features: a new design system, AI-assisted workflows for specs and designs, product analytics, and new Terminal features. In September 2026 the Terminal reached 129,265 monthly active users (+44.1% month on month), and nearly half of the revenue added that month came from touchless sign-ups through it.
Process
- 01
New design system
I set up a new design system on shadcn/ui with a matching Figma library, and used the Figma MCP server to keep the coded components and the Figma components in parity.
- 02
Automated spec and design workflows
I built automated workflows across Linear, Claude and Figma to manage specs and designs, so tickets, specs and design files stay connected without manual hand-offs.
- 03
Deeper analytics with PostHog
I integrated PostHog for deeper product analytics, so we can see how traders and developers move through the Terminal, from finding a feed to signing up.
- 04
Building new features
I designed and built new Terminal features in React and TypeScript on top of the new design system.
- 05
Component library in Storybook
I maintain the component library in Storybook, documenting each component's variants and states so design and engineering work from the same reference.
Features
Fogo Sessions
Fogo
Session-based wallet for Fogo: one approval instead of constant wallet prompts and gas fees — designed in two weeks.
Read on