I consider Next.js when a website needs a custom interface, integrations or a shared foundation with an application. For a small presentation site with a conventional editor, a ready-made content management system may be more practical. The decision depends on how the business works and who maintains the result.
What you are actually buying
Next.js is a React development framework. It is not a ready-made editor, hosting service or automatic SEO solution. Your supplier still needs to design content, data updates, forms, security and deployment. Ask about delivered capabilities and operational responsibility, rather than the technology name alone.
A small service business might need six service pages, references, an enquiry form and editable contact details. A manufacturer may also need a configurator, several languages and a product-data integration. Both can use Next.js; the difference in the brief explains why custom development might be worth funding.
1. Separate content from interaction
The informational part of a page does not need to send all its application logic to the browser. App Router lets developers combine server and client components. A configurator can be interactive while the surrounding product description remains on the server. Broad client boundaries can still enlarge the JavaScript bundle. Component documentation.
At handover: open an important page on a phone and measure what actually downloads. The word React in a proposal does not establish transfer size.
2. Navigation can remain continuous
Next.js supports prefetching linked routes and navigating without reloading the entire document. Default prefetching is associated with links entering the viewport; its extent depends on the route and configuration. Describing it only as loading on hover is inaccurate. Navigation and prefetching.
For a visitor, the meaningful checks are clear feedback after a click, a working back button and a form that does not lose their draft. Test the complete journey.
3. Image tools still need suitable source material
The Image component supports responsive sizing and image optimisation. A developer must still choose quality, dimensions, alternative text and priority for the leading image. Changing frameworks alone does not fix an oversized photograph or unnecessary autoplay video. Image optimisation.
4. Technical SEO can be configured explicitly
Metadata, canonical URLs, redirects and sitemap generation can be configured. Their correct values depend on the content and site structure. A migration still requires a redirect plan and checks that important pages remain available.
Google assesses the resulting pages. Good Core Web Vitals do not guarantee first positions; WordPress can also have sound technical SEO. Google: page experience. See the separate comparison when choosing between the two.
5. Adapt the editor to the team
Next.js can connect to a CMS so editors change service names, photographs and buttons without editing code. That integration must be part of the delivery: the framework does not add an article administration interface by itself. Try previewing, publishing, permissions and restoring an earlier version before accepting the site.
Worked example: From the editor to one specific section
illustrative example
| Field | In the editor | After publishing |
|---|---|---|
| Heading | Spring bicycle servicing | Same heading in hero section |
| Image | spring-service.webp | New servicing photo |
| Alt text | Technician adjusting brakes | Description of new image |
| Button | Book a service | Link to /booking |
Example field-to-output mapping; not a screenshot of a specific CMS.
6. Custom features can share a foundation
A catalogue, calculator and customer portal can share components and data access. This increases the need to test roles, authorisation and error states. One repository is not automatic security or a guarantee of cheaper development. Agree which parts can be deployed independently and who handles an integration failure.
7. Plan operations around the architecture
A static site has different needs from an application with a database and sign-in. Include hosting, CMS, email, storage, monitoring, updates and change work in the budget. A framework name does not determine their cost. Request accounts owned by your business and a recovery procedure.
| Item | What it costs with me (Next.js) |
|---|---|
| Website development | Starter from €800, Business from €1,200, Corporate from €2,400 |
| Website management | €200 / €400 / from €800 per month, 3-month minimum, or one-off edits at €40/h |
| Hosting | plan and running costs stated upfront in the quote |
| Paid plugins | usually none, features are part of the code |
These figures are my offer, not market averages. Scope and operating costs are specified in the website proposal. Both technologies need dependency maintenance. Static export being available does not mean every application is static or automatically secure. Static-export limitations.
When a simpler solution makes sense
If an existing template suits you, you need a conventional publishing workflow and have no reason for a custom frontend, WordPress or another managed platform may reduce development work. A functioning website does not need rewriting merely because another tool exists.
Decide using a small, testable brief: update a service in the editor, submit an enquiry, find it in the right system and restore content from a backup. The technology is a good fit when that process works at an acceptable cost with clear operational responsibility.