Almost every project I take on starts with the same question from the client: should my site be built in WordPress, Webflow or Next.js? I build in all three, so I don't have a favourite to push. What I have is a short set of questions that points to the right answer most of the time. Here they are.
The short answer
| If your site is mostly… | Choose | Why |
|---|---|---|
| Content: blogs, service pages, a team that publishes often | WordPress | The easiest editor for non-technical teams and a huge plugin ecosystem. |
| Design-led marketing pages that change every month | Webflow | Marketers can build and launch pages visually without a developer. |
| A product: logins, dashboards, custom features, heavy data | Next.js | Full control, top performance and room to grow into an app. |
Question 1: who will edit the site after launch?
This matters more than any feature list. A site the team can't update is a site that goes stale.
- If writers or a marketing team will publish weekly, WordPress is usually the kindest choice. A custom theme with well-named custom fields means they fill in boxes rather than fight a page builder.
- If a designer or marketer wants to build new landing pages themselves, Webflow wins. Its CMS collections and visual editor let them launch without waiting on me.
- If developers will maintain it, or content lives in a headless CMS, Next.js is the cleanest.
Question 2: what does the site need to do?
A brochure site, a portfolio or an agency website rarely needs custom application logic. WordPress or Webflow handle these well. Once you need user accounts, a booking flow with real business rules, a dashboard pulling from an API, or anything that behaves like software, Next.js with React is the better foundation. Trying to bend a CMS into an app usually costs more later.
Question 3: how much does speed and SEO matter?
All three can rank well. The difference is how much discipline it takes:
- Next.js gives the most control: server rendering, static generation, image optimisation and a tiny amount of JavaScript on content pages.
- WordPress can be very fast with a lean custom theme, good hosting and caching. It gets slow when it is stacked with heavy page builders and dozens of plugins.
- Webflow produces clean markup and hosts it on a fast CDN. You trade some control over the code for convenience.
Question 4: what is the budget over three years, not just at launch?
Look past the build price. WordPress needs hosting, updates and security care. Webflow has a monthly site plan, and the price rises with CMS items and traffic. Next.js can be hosted cheaply, but every new feature needs a developer. The right stack is the one whose ongoing cost matches how you plan to run the site.
How I decide on a real project
- I ask who edits the site and how often.
- I list the features that behave like software rather than content.
- I check the SEO and performance goals and the hosting the client already has.
- I recommend one stack, explain the trade-off in plain words, and only then quote.
Most agency and business sites I build end up on a custom WordPress theme. Design-heavy startups often go to Webflow. Products and dashboards go to Next.js. If you are unsure which one fits your project, send me a short brief and I'll tell you honestly, even if it is not the one I'd earn the most from.