Skip to content
Back to journal

WordPress or Next.js? How I choose for each client

Written byZaki Hattaon

A street sign reading new things against a pink wall and blue sky

I have shipped client sites with both. The right choice depends less on the technology and more on who will look after the site.

I have built client websites in WordPress and in Next.js, sometimes for the same client. People often expect a developer to have a favourite. I try to let the project decide.

When WordPress makes sense

  • The client's team wants to edit pages themselves, from day one, without training.
  • The site is mostly content: company pages, products, news.
  • Budget and timeline favour a proven theme or page builder such as Divi.

When Next.js makes sense

  • The site behaves like an application: logins, dashboards, ticketing, bookings.
  • Performance and custom interactions matter more than drag and drop editing.
  • The data lives in its own database or API.

The YPRO corporate site was a clear WordPress project. The AssistCare platform and the Seven Star ticketing frontend were clear Next.js projects. Most of the work is asking the right questions before writing any code.

A minimal computer setup on a wooden desk in natural light

Designing a ticketing flow that stays out of the way

Ocean waves rolling against a concrete seawall

Cutting alert latency from 677 ms to 37 ms

A yellow road sign with black chevron arrows pointing right

Rerouting evacuees when a shelter fills up

A hand holding a smartphone with a gradient screen

Ray casting, or how a phone knows it is in danger