Next.js Website Cost UK: Compare the Scope Behind the Quote

A useful Next.js website price separates the initial build, the work needed to move an existing site, and the cost of running it afterwards. Compare those against the same written brief. Check whether each quote includes the editing system, moving your content and launch checks before deciding which offers better value.

If you have two proposals in front of you and are finding them hard to compare, this guide will help. It gives you practical questions and a blank worksheet to uncover what each price covers. It is not an Ampliflow price list or a survey of average agency fees.

Next.js is a framework: a set of tools developers use to build websites and web applications. It builds on React, a library for creating the parts of a website people interact with. The tools alone do not determine how much design, content, connection to other systems or testing your project needs. Start with the job your website must do. Our Next.js development page explains where that approach fits.

What changes the cost of a Next.js website?

Two sites with ten pages can require very different work. One might use a few shared layouts and a contact form. Another might need customer accounts, a searchable catalogue and information pulled from several systems.

Ask each supplier to describe the work behind these six decisions:

A content management system, or CMS, is the editing tool your staff use. It is a separate decision from the public website's framework. Ask to see someone change a real page, preview it and correct a mistake. That demonstration helps you check whether “CMS included” covers the everyday tasks your team needs.

Use the Next.js project brief to describe the same first complete customer journey to every supplier. If the platform itself is undecided, read the Next.js versus WordPress comparison before paying for a more complex solution.

Compare three cost buckets

Use one comparison period and one currency across every proposal. For example, compare the initial build plus the first twelve months after launch. That is a budgeting choice, not a required contract term.

The comparison total is the agreed build price, plus separately charged launch work, plus recurring and usage-based costs over your chosen period. Keep optional work and unresolved amounts separate. Do not count the same item twice when a supplier includes it in a package.

1. The initial build

Identify what the quote actually buys: research, design, development, content entry, editing setup, integrations and testing. Ask who supplies copy, photographs and account access. Record the assumptions behind the price and how a changed requirement will be assessed.

Distinguish a fixed scope from an estimate for time spent. Neither label settles what is included. Ask which decisions must be resolved before a final commitment and whether the quoted amount includes VAT. Keep the tax basis consistent when comparing proposals.

2. Moving and launching

If you already have a website, the move needs its own plan. Someone needs to list its important page addresses, preserve useful content, plan redirects and check that the new site's forms and visitor tracking work.

Redirects send visitors and crawlers from an old address to its replacement. They are one part of a migration, not the whole job. Our WordPress-to-Next.js migration checklist includes a page-by-page ledger you can use to make that work explicit.

Ask who authorises the switch, when the team would switch back to the previous site if something goes wrong, and who checks the site afterwards. If a proposal says “SEO-friendly development”, ask the supplier to describe these responsibilities in writing.

3. Running and changing the site

List the services the finished website depends on and who pays for each. Depending on the project, those may include hosting, the domain, the editing system, email delivery, search, monitoring and other connected services. Some may be bundled or unnecessary. Verify the actual proposal rather than assuming every project needs every item.

Hosting is where the application runs. The official Next.js deployment documentation describes several deployment routes with different feature support. Ask which route the supplier proposes and why it fits your website. The framework name alone does not tell you the hosting bill.

For each recurring item, record the billing owner, included usage, what could increase the charge and how you would notice. Separate routine maintenance from new features. Ask what response or recovery arrangements are agreed; do not assume round-the-clock support from a monthly fee.

Use the quote-comparison worksheet

Download the Next.js quote-comparison worksheet (CSV). It opens in a spreadsheet and needs no email address. It is an original Ampliflow planning aid with blank cost fields, not a quote, pricing benchmark or automatic recommendation.

The worksheet compares the same scope items across up to three suppliers. In each answer column, write included, excluded, not applicable or unresolved, with any useful detail. In the separate amount and billing basis column, record the quoted cost and whether it is one-off, monthly, annual or based on usage. Add the relevant proposal section in evidence so you can find it again. A blank cell means unknown, not free.

Keep the original billing terms in the worksheet, then compare costs over your chosen period. For a twelve-month comparison, count a monthly charge twelve times or an annual charge once, not both. Check whether a price shown “per month” is paid monthly or annually upfront, and record any minimum commitment separately.

Then work through this sequence:

1. Match the scope. Confirm that every proposal covers the same customer journey and editing tasks.
2. Resolve exclusions. Ask who will do missing work and whether a separate price is needed.
3. Compare the full period. Include agreed launch work and relevant running costs without double-counting bundled items.
4. Record uncertainty. Keep unknown usage, optional work and undecided requirements visible.
5. Check the evidence. Choose using delivery proof and responsibilities as well as price.

Two similar quotes can describe different websites

Consider this illustrative example, not a client project or a price comparison.

A business wants an editable ten-page website. Proposal A includes the public pages and a form; the client must supply final copy, and the proposal does not explain content migration or editor training. Proposal B explicitly covers those tasks, but its ongoing support excludes adding new page layouts.

Neither proposal is automatically better. If the business can handle the content work, A may fit. If it cannot, the headline prices are not comparable until that work has an owner and a cost. B still needs a clear arrangement for later design changes.

The useful question is: what would our team still have to organise or pay for to get the same working result?

What evidence should support the quote?

Ask the supplier to demonstrate a comparable public project and explain which parts it delivered. A polished homepage does not establish how well an editor, account journey or migration works.

Our Kings Heath Business Association case study provides an inspectable website and dated performance evidence. It is an example of delivered work, not a benchmark for what your project will cost or a promise of the same results.

Before signing off the finished site, work through three questions:

• Does the journey work? Test the agreed tasks on phone and desktop, including what happens when someone misses a required form field or a submission fails.
• Can the team run it? Demonstrate routine editing, permissions, preview and recovery with realistic content.
• Can people find and use it? Check that search engines can read the content, page titles and descriptions are useful, and old links reach the right pages. Test keyboard access and loading performance on representative pages.

The official Next.js production checklist is a useful technical reference. The Ampliflow Next.js SEO checklist translates the search checks into a commissioning discussion. Neither replaces a project-specific acceptance agreement.

If a proposal relies on a speed score, ask which URL was measured, when and under what conditions. A controlled lab test and real visitor experience answer different questions; our Core Web Vitals guide explains how to read that evidence.

Questions to settle before appointing a developer

Is Next.js always more expensive than WordPress?

The framework alone cannot answer that. Compare equivalent designs, content work, customer journeys and ongoing responsibilities. A custom application and a straightforward publishing site are different purchases, regardless of the platform names.

Does the development price include hosting and maintenance?

Only if the written proposal says so. Ask for the provider, billing owner, included usage, renewal basis and maintenance scope. Record any excluded work and who handles it.

Can I move the website to another supplier later?

Ask who controls the domain, source code, hosting, content and connected accounts. Request a handover description that covers access, documentation and any dependencies. Confirm the relevant rights and restrictions in the agreement; a technology choice alone does not settle them.

Will a Next.js website rank better in Google or AI search?

Next.js does not guarantee rankings or citations. Implementation, useful content and discoverability still matter. Google's AI-search guidance requires normal search eligibility and does not prescribe special AI markup. A supplier should explain what it will implement and measure, rather than sell a position it cannot control.

Make the next conversation specific

You do not need every technical answer before speaking to a supplier. Bring the same brief to each conversation, note what is still unclear and ask for a demonstration of the work that matters to your team. Our agency-selection scorecard helps you assess the supplier; this worksheet helps you assess the proposal.

For Ampliflow's approach, see Next.js development for UK businesses. If it fits the job, Get unstuck.