Verdant

Seven products, seven slightly different buttons.

The company had grown to seven web products, each maintained by a different squad. Brand drift was everywhere — three blues that were almost the same, four button heights, inconsistent focus states. Every rebrand was a multi-month, all-hands ordeal.

Leadership wanted one source of truth that designers and engineers could both trust — without slowing any team down.

Lead full-stack — from schema to docs.

I owned the platform end-to-end with a designer and a second engineer. My remit:

• Architect the token data model and versioning (Postgres + Prisma).
• Build the editor UI and live documentation site (Next.js, tRPC).
• Ship the theming engine that pushes tokens to consuming apps at build time.
• Define the contribution workflow so squads could add components safely.

Tokens as data, docs as a product.

Every token, component and theme became a versioned database record with a clean API. The docs site renders live, interactive examples straight from that data — never a screenshot, never out of date.

Accessibility was non-negotiable: contrast is validated automatically on every token change, and a component can't ship without passing focus and keyboard checks.

One system, adopted fast.

Within two quarters, adoption crossed 90% and the next rebrand shipped in days instead of months.