A scattered, effect-heavy marketing site rebuilt into a single navy-and-white design system, rolled out across the whole site, and kept honest with a custom screenshot-and-token audit pipeline.
The same homepage, before and after. Scroll either panel to compare the full page top to bottom — both stay in sync. Toggle light and dark to flip both sites.


Years of feature pages, free tools, and programmatic SEO pages had each picked up their own styling. For a product that sells precision to operations teams, the inconsistency undercut the pitch.
black, --navy, dark.DEFAULT, and --navy-bg used interchangeably across the codebase.
Blue, purple, and cyan applied as shapes, links, and buttons with no rule for which went where.
Glows, floating orbs, glassmorphism, and animated gradients layered onto sections that didn't need them.
Callouts, FAQ blocks, and CTA bands rebuilt by hand page by page — one change meant editing dozens of files.
Move more visitors to a booked call.
A trustworthy surface makes the product feel trustworthy. A clear hero and one obvious next action remove friction. And a maintainable system means future pages stay on-brand instead of adding new drift.
Several "dark" names collapsed into a five-shade navy scale defined once as CSS variables. Every bg-black and bg-dark reference migrated automatically.
Every reference resolves to a small set of source tokens
dark: modifiers everywhere.Tokens like surface, content, and line swap their values under a .dark class. A heading is text-content — navy in light mode, white in dark — without the component knowing which mode it's in. New pages get correct dark mode for free.
Almost every page is composed from Section, Heading (visual level decoupled from semantic tag), Button, and Eyebrow.
Out went the glows, orbs, glassmorphism, and animated gradients. What stayed earns attention: an animated document-flow diagram, a headline shine sweep, and word-by-word reveals. Restraint reads as confidence — which is the brand voice.
Landing pages and free tools, rebuilt on the same tokens. Each pair scrolls together, top to bottom.




A design system is only real if the site actually follows it. So I built pnpm design:audit — a pipeline that proves it, across the whole site, with one command.
Load every public URL from sitemap.xml.
Flag off-system styling against a library of violation patterns.
Capture full-page shots in both color modes.
Compare each page to a stored baseline and surface what changed.
Color references resolve through a small set of tokens — a palette change is one edit.
No off-palette colors or one-off components remain, verified by the audit pipeline.
Every page inherits correct light and dark styling automatically.
Every CTA is instrumented, so the visitor-to-booked-call goal can actually be read.
The redesign's wins are in consistency and maintainability. Conversion impact is tracked in PostHog over time against the booked-call goal, so I've kept this to what's verifiable rather than quoting a lift I can't yet stand behind.