All case studies
Case Study

Brand & Web·WinAI

WinAI marketing site redesign

A quieter, brand-first rebuild of winai.dev — editorial pacing, purposeful motion, and a clearer path from curiosity to consultation.

WinAI marketing site redesign

WP → Next

Stack move

marketing site

1 job

First viewport

brand + offer + CTA

Purposeful

Motion

GSAP · Lenis · Reveal

Before & After

Compare the old site and the redesign

Full-page captures side by side — scroll to move through both versions together.

Before

After

Before
Previous winai.dev full homepage
After
Redesigned WinAI full homepage

Scroll either column to move through the full page — both sides stay aligned

Why Next.js

Why we recommend moving marketing sites from WordPress to Next.js

WordPress is fine for quick publishing. It becomes expensive when the page is the product — when brand, motion, speed, and conversion path all have to feel intentional. For WinAI, the old WP stack fought the redesign: theme overrides, plugin weight, and limited control over the first viewport. Next.js let us own the experience end to end.

Faster first paint

App Router + static rendering ships lean HTML/CSS instead of a plugin-heavy WP payload — better Core Web Vitals and a sharper first impression.

Brand-level design control

No theme cage. Typography, motion, and section rhythm stay exact — the same system we use for client-facing marketing work.

Stronger security posture

Fewer plugins and admin surfaces to patch. A smaller attack surface than a typical WordPress install with page builders and form stacks.

SEO that stays maintainable

Metadata, sitemaps, and structured data live in code next to the UI — consistent, reviewable, and hard to accidentally break in a CMS UI.

Motion without the tax

GSAP, Lenis, and purposeful reveals stay performant because we choose every dependency — not inherit a theme’s animation kit.

Cheaper to evolve

New sections ship as components, not page-builder spaghetti. Future campaigns, A/B tests, and integrations land faster with less regression risk.

That is the advice we give clients too: keep WordPress when editorial volume is the priority; choose Next.js when the site must sell, load fast, and feel like a product — not a theme demo.

The challenge & approach

The previous WordPress site led with a dense first viewport and a chat demo that competed with the brand. We rebuilt on Next.js so performance, motion, and composition stayed under our control — then redesigned around a single first-viewport job: strong type hierarchy, full-bleed atmosphere, and a clearer path from curiosity to consultation.

Migrating off WordPress was the enabling move: once the stack stopped fighting the design, we could lock tokens, rebuild hero → services → proof → CTA, and ship motion that supports hierarchy instead of fighting page weight.

Ready to Transform Your Business?

Book a free consultation and we'll map out where AI automation can save you the most time.