There's a conversation that repeats itself in almost every new web project. The client asks what technology to use, the developer responds with enthusiasm for the latest tool they've learned, and the client ends up paying more than they needed—or left with something they can't maintain on their own.
This article takes no sides. Neither is WordPress the default answer nor is Next.js always the "serious" option. They are different tools for different problems, and the right choice depends on your specific project, not on industry trends.
The right technology is the one that solves your problem at the lowest total cost, not the one that most impresses in a meeting.
What each one is, without sugarcoating
WordPress is a content management system (CMS) that has been on the market for over twenty years. It runs on PHP and MySQL, has a visual administration interface, and can be installed on virtually any standard hosting. More than 40% of the web runs on WordPress: from personal blogs to international media outlets.
Next.js is a React framework for building web applications. It doesn't come with an admin panel, database, or content editor. It's pure JavaScript—specifically from the Node.js ecosystem—and requires a developer to configure it, maintain it, and make almost any change beyond the code.
The real cost: what nobody tells you upfront
The most common mistake is comparing only the startup cost. A Next.js project may seem technically attractive, but if your team has no React experience, if the client needs to edit content without help, or if the maintenance budget is limited, the total cost skyrockets.
Watch out for this: Many projects start in Next.js for valid technical reasons, but without budgeting for the headless CMS (Contentful, Sanity, Strapi...) needed so the client can edit content. That cost can add €1,000–5,000 just in setup.
When to use WordPress
WordPress has a bad reputation in certain technical circles, but that reputation usually comes from bad implementations, not from the tool itself. Well configured, with a lightweight theme and the right plugins, WordPress is fast, secure and very maintainable.
Signs that WordPress is your choice
Consider WordPress if your project meets any of these criteria:
Content: The client needs to publish news, blogs, pages or products independently, without depending on a developer each time.
Budget: The total development budget is below €1,000 or the client cannot sustain a high maintenance contract.
Team: There is no internal technical team that can take on the maintenance of a modern JavaScript stack.
Functionality: The project needs e-commerce, forms, memberships, bookings or other features that already exist as proven plugins.
Time: The launch deadline is weeks, not months.
When to use Next.js
Next.js shines when the project has requirements that WordPress cannot reasonably satisfy. It's not a question of being more "professional"—WordPress is also used in production at massive scale—but of fit between the problem and the tool.
Signs that Next.js is your choice
Consider Next.js if your project meets any of these criteria:
Interactivity: The site has complex application logic: dashboards, real-time calculators, multi-step flows, synchronisation with external APIs.
Technical team: There is an internal development team with React experience that will maintain the project long-term.
Architecture: The project is part of a broader ecosystem: microservices, proprietary APIs, mobile apps that consume the same data.
Scale: Very high traffic peaks are expected and fine-grained control over performance, caching and rendering strategies is needed.
Differentiation: User experience is a key competitive differentiator and animations, transitions and behaviours impossible in a standard CMS are required.
The headless case: the best of both worlds
There is a third option that combines WordPress as a headless CMS with Next.js as the frontend. WordPress manages content through its REST API or GraphQL (with WPGraphQL), and Next.js consumes that data to build static or server-rendered pages.
It's a solid architecture for projects that need the editorial ergonomics of WordPress and the performance of a modern frontend. But it has a price: more complexity, higher development cost and more pieces to maintain. Don't choose it for fashion; choose it when you genuinely need what it offers.
Headless is not "the old way but better". It's a different architecture with its own complexities and extra costs.
The decision in one single question
If you had to simplify it to the maximum, the key question is: who is going to maintain this in two years?
If the answer is "the client themselves, or a generic freelancer", you probably need WordPress. If the answer is "an internal technical team or a specialised agency with budget for it", Next.js may be the right option.
Final verdict
Choose WordPress if… Your project is a content site, online store or corporate presence. The client wants editorial autonomy. The budget and team are reasonable for what you need. Launch speed matters.
Choose Next.js if… You are building a web application with complex logic. You have a technical team capable of maintaining it. Performance or user experience are key business differentiators. The budget allows for it.
The best technology is the one your team can maintain, your client can use and your budget can sustain. Everything else is noise.