01When it adds value and when it doesn’t
Next.js isn’t “faster WordPress” by default. It adds value when there is interactivity, a custom frontend, a product, or editorial content that the theme can’t cover.
WordPress is used as the CMS via REST/GraphQL and Next.js as the frontend. That separation has a cost: two systems, deployments, caching, preview, and maintenance. It is stated before starting.
The promise is concrete: a decision based on requirements, a documented architecture, and a maintainable delivery. Headless is not sold as a fashion, and performance is not promised without measuring.
Two systems mean more operations. If the team can’t take them on, a simpler solution is recommended.
02How it works alongside WordPress
Can add value
- A product or SaaS with real interaction.
- Editorial content that needs a custom frontend.
- Performance requirements that are measured, not assumed.
- A team with the capacity to maintain two systems.
- Preview and editing that the team needs to keep.
Doesn’t add value
- A simple informational or corporate site.
- A budget and team without the capacity to maintain Next.js.
- The problem is just a plugin, the hosting, or the theme.
- The content isn’t going to be edited.
- Chasing “what’s modern” without a requirement that justifies it.
The four decisions
-
01
Classic WordPress
If content and editing are the main thing, it is simpler and cheaper to maintain.
-
02
Headless with Next.js
If the frontend, the product, or the interaction justifies it, the cost of two systems is accepted.
-
03
Hybrid
WordPress for content and Next.js for a specific part of the product or of the funnel.
-
04
Don’t proceed
If there is no real requirement, it isn’t sold. The decision is documented before quoting.
03What we build
Next.js isn’t the service: the service is what gets built with it. These are the usual pieces, each one with its scope and its cost.
-
01
Architecture
Content model, API, routes, caching, and preview. Decided before writing the frontend.
Go to Custom web development -
02
Frontend
Next.js/React with components, routes, and states; tested in staging, not in a screenshot.
Go to Custom web development -
03
Integration
WordPress REST/GraphQL, media, content, and preview; what the team edits and what they don’t gets documented.
Go to Custom web development -
04
Deployment and continuity
Build, environment, CDN, and documentation; if the team can’t maintain it, that is said beforehand.
Go to Support and maintenance
04Performance and maintenance
Can be measured
- Routes and JavaScript per page.
- Caching, CDN, and rendering strategy.
- Images, fonts, and blocking content.
- API calls and response times.
Can’t be promised
- Guaranteed performance without measuring.
- That Next.js is fast because of its name.
- Maintaining two systems with no operational cost.
Maintenance
Next.js and WordPress are two systems: both have to be updated, and the API, the build, the cache, and the deployment have to be reviewed. Documentation doesn’t eliminate the work: it makes clear who does what and what breaks if it isn’t done.
Optional support starts at €50/month and includes updates, backups, security review, and alerts; frontend maintenance is quoted separately.
Price and timeline
The project is quoted after the architecture and the scope are decided. Headless isn’t charged as a label and no figure is promised before knowing what has to be built. The timeline is defined with the architecture and depends on content, integrations, and access.
What determines the costFrontend scope · content model · integrations · preview · performance · deployment
See the speed and WPO service05Proof: stated capability
We don’t publish a Next.js case with a name and metrics if we don’t have permission. The capability is real; public proof will be added when it exists.
What can be stated without inventing anything: Next.js is level 3 (build), not our main specialty. The specialty is WordPress and PHP; Next.js is taken on when the project justifies it.
If the stack requires Next.js and WordPress, it can be built. If it doesn’t require Next.js, that is said and the simpler option is proposed. The quote doesn’t come with a preset architecture.
See the projects06Frequently asked questions
Is Next.js always faster?
No. It depends on the architecture, the caching, the content, and the hosting. It gets measured; a figure isn’t promised because of a technology’s name.
Can I keep editing in WordPress?
Yes, if the content model and the API are designed for it. Preview and editing are included in the scope; if they aren’t, that is said beforehand.
Is it worth it for my site?
Only if there is interactivity, a product, or a custom frontend that justifies it. If not, classic WordPress is simpler and cheaper to maintain.
Who maintains two systems?
It is defined in writing. Support is optional from €50/month and frontend maintenance is quoted separately; the documentation makes clear what each side does.
How much does it cost and how long does it take?
It is quoted after the architecture and the scope are decided. The timeline depends on content, integrations, and access; dates aren’t promised before seeing the case.