Daniel Greenwood// Product Design Engineer
Daniel Greenwood// Product Design Engineer
Vaylent & Zeno · Lead Design Engineer

Two brands, one system, one launch date.

Overview

Vaylent was going to market with no digital presence and a fixed launch date. The brand and the website had to arrive together.

I owned it end to end - IA, visual design system, and the production Webflow build. Then proved the system by spinning a second brand, Zeno, off the same foundation.

{{ s.label }} {{ s.value }}
Primary problem

A new name, three consolidated businesses, a conservative high-trust industry, and a date that wouldn't move. The site had to communicate precision and credibility before a single word was read - and stand up to sustained attacks from foreign actors since launch.

Approach

I built the token-and-component foundation before designing a single page. A brand-level change had to be one edit. Partway through I pivoted from a headless stack to Webflow - not for cost, but because the client needed to own the site after launch without a developer.

The work
Systems & frameworks

One token-and-component infrastructure, two brands. Vaylent and Zeno each got their own color, type, and identity - built on the same system. I drove the build through an MCP workflow against Webflow's API, keeping the token system, components, and launch-critical engineering precise.

Outcomes
{{ o.figure }} {{ o.label }}
PreviousHome Game SportsNextMLS Player & Game Stats
My workGet to know meResume