One rebrand, across the whole product surface.

Before fall 2025, Massive.com was Polygon.io. The new identity needed to reach well beyond a marketing launch: customers encountered the company through several distinct web applications, each with its own purpose, interaction density, associated data, and implementation history.

The work was therefore both visual and architectural. Every application needed to support the new brand without disrupting the existing Polygon experience before launch, and the organization needed a reliable way to move the whole product family together when the time came.

A marketing page, an operational dashboard, technical documentation, and a database interface do not need identical layouts. They do need a recognizable visual language, reliable primitives, and a clear way to vary density and emphasis.

The challenge was to prepare and validate the new experience while Polygon remained live. The applications could not drift into a partially rebranded state, and launch could not depend on a fragile series of unrelated changes landing at exactly the right moment.

Julie directed frontend strategy and engineering implementation across the client-facing web portfolio. She built configuration for each application to run in either Polygon or Massive brand mode, loading the appropriate styles and associated brand data from the same application architecture.

This allowed teams to build and validate Massive before launch while keeping Polygon intact. At cutover, the company could switch applications decisively from one brand to the other with little friction instead of coordinating a risky collection of last-minute rewrites.

The implementation centered design tokens, reusable components, and explicit brand configuration. Shared primitives carried color, type, spacing, and interaction decisions; brand mode selected the correct presentation and data; individual product surfaces composed those foundations according to their own jobs.

This made the rebrand a controlled systems change rather than a collection of matching screenshots. The same separation of durable foundations from product-specific content also reflected earlier work Julie had done on the company’s developer documentation.

Before her promotion to Director, while the company was still Polygon.io, Julie built its new documentation website on Stripe’s Markdoc framework. The new architecture made contributions easier and created room for capabilities that were difficult to support in the previous system.

She worked closely with design to clarify how API endpoints correlated with specific product pairings. Presenting those relationships directly in the documentation helped customers understand which products fit their needs, reduced confusion across the catalog, and created a clearer path from technical evaluation to purchase.