Every few months a client asks whether they should \”go headless\”. Sometimes the answer is yes. More often it is \”not yet\”, and occasionally it is \”please don\’t\”. Here is how we decide.
Three ways to build on WordPress
- Classic — WordPress renders the pages. Cheapest to run, easiest for editors, fast enough for most marketing sites.
- Hybrid — WordPress renders pages, but interactive parts are small apps mounted inside them.
- Headless — WordPress only stores content; a separate front end (we use Next.js) renders everything.
Go headless when…
- The same content feeds a website, an app and a kiosk.
- You need complex, personalised pages that a theme would fight against.
- Your team already runs a modern JavaScript stack and can own a second deployment.
Stay classic when…
- Editors rely on live preview and drag-and-drop page building.
- The site is mostly content: pages, posts, case studies.
- There is no developer on staff after launch.
Headless is an architecture decision, not a performance plugin. A well-built theme still scores 100 on Lighthouse.
Kenji Watanabe, Lead Developer
The honest summary: headless buys you flexibility and costs you simplicity. Pay for it only when you will actually spend the flexibility.