Skip to content

Next.js Development in the UK

We are an Indian engineering team working with businesses in the UK. Written scope before any code, and a fixed quote in GBP.

Working hours

Our day runs 09:00 to 18:00 India time, which is 03:30 to 12:30 in the UK, or 04:30 to 13:30 while you are on summer time, so most of your morning overlaps with ours.

Quoted in GBP

Quotes exclude the 20% VAT in the UK, shown separately on the invoice.

Data protection

Work for this market is scoped against the UK GDPR and the Data Protection Act 2018, agreed before development starts rather than retrofitted afterwards.

Written scope

Every engagement starts with a written scope and a fixed GBP quote within 24 hours, so the price is set before work begins.

About Next.js Development

Next.js is our default for any modern web project where SEO, performance, and developer experience all matter. We've shipped 8+ production Next.js apps on the App Router across SaaS dashboards, headless e-commerce, content sites, and marketing pages, including this one. Every build uses TypeScript, Tailwind, and the latest Next.js patterns, deployed to Vercel for the fastest possible iteration loop.

What the engagement includes

  • Next.js 16 (App Router) custom application development
  • Headless Shopify storefronts on Next.js
  • Headless WordPress front-ends on Next.js
  • Multi-region SaaS dashboards with auth (Clerk, Auth.js)
  • Server Actions, Suspense boundaries, and streaming SSR
  • Static export sites for content / marketing
  • TypeScript-first codebases with strict mode
  • Migration from Pages Router → App Router

Analytics, pricing and GOV.UK journeys in a UK Next.js build

In Next.js development for UK clients the cookie question changed in 2026, and setups copied from older projects predate it. The Data (Use and Access) Act 2025 added a PECR exception for storage used solely to collect statistical information about how your service is used, with a view to improving it. The ICO's final guidance, published on 29 April 2026, sets the conditions: clear and comprehensive information, a simple and free way to object, aggregate statistics as the output, and any analytics provider acting only to help improve your service. Advertising never qualifies. So the architecture comes before the banner. First-party measurement that meets those terms can run from the first page view, anything feeding an ad platform waits for consent, and those are two code paths rather than one tag with a toggle. A route handler in the same app suits the first kind, but moving a tag server-side does not take it out of scope: the ICO says regulation 6 applies server-side wherever information is stored on or read from the device. An objection has to stop collection, so it is read on the server before anything is recorded. Since 5 February 2026 the ICO can fine up to £17.5 million or 4 per cent of global turnover under PECR. Whether your analytics fits the exception is for your own counsel.

If the front end quotes prices to consumers, the Digital Markets, Competition and Consumers Act 2024 decides how the price component is built. Its unfair commercial practices provisions apply from 6 April 2025, and the CMA's price transparency guidance says the total price in an invitation to purchase should normally include mandatory charges, per-transaction fees included, even in early-stage advertising. On a Next.js site the headline figure turns up well beyond the checkout: product cards, the plan comparison on the pricing page, the structured data search engines read and the Open Graph card shown when a page is shared. If each works out its own number, a booking fee that first appears in the basket is the drip pricing the Act targets. So the total is computed once, on the server, and every surface renders that value, and a plan with a twelve month minimum term shows either the cost of the whole contract or the monthly price with the number of months it runs. The Act's subscription contracts regime is not in force yet; the government's response of 2 April 2026 anticipates commencement in spring 2027. Once it is, a consumer who can sign up online must be able to exit online without unnecessary hurdles, so a cancel route built now becomes a copy change later. Which of your fees count as mandatory is your counsel's call.

Public sector buyers bring a constraint that sits awkwardly with the framework's defaults. The GOV.UK Service Manual says all government services must follow progressive enhancement and tells teams not to build a service as a single page application, where pages are loaded by JavaScript rather than the browser. Client-side navigation is what next/link does by default, so on a transactional journey it is a decision to make deliberately rather than inherit. The App Router renders HTML on the server, and React documents that a Server Function passed to a form's action lets people submit before the JavaScript loads or with it switched off, so a journey can be built from server-rendered pages and forms that work when the bundle fails, and every journey is tested with JavaScript disabled. The Design System is the second decision. GOV.UK Frontend is published as Sass, JavaScript and Nunjucks templates rather than React components, so in a Next.js codebase the markup is ported by hand and kept in step with each release, and its JavaScript components are initialised after React renders them, with anything inserted later reinitialised in scope. If the service will not live on GOV.UK, the generic header component exists so you do not use the crown, the GOV.UK logotype, GDS Transport or the GOV.UK brand colours. Whether the Service Standard applies to you is for your service owner to confirm.

How we work with UK clients

UK engagements tend to start with procurement questions rather than technical ones. Who holds the data, which law governs the contract, whether you can produce a record of processing if the ICO asks. We answer those in the proposal instead of leaving them to a legal review three weeks in, because that review is where UK projects usually stall.

Invoicing is the other thing worth settling early. We are outside the UK, so services we supply generally fall under the reverse charge and your finance team accounts for the VAT rather than paying it to us. Our invoices say so explicitly. We quote in pounds, the figure does not move with the exchange rate mid-project, and payment by bank transfer avoids the card fees that make a five-figure invoice unnecessarily expensive.

Indicative pricing in GBP

Converted from our published Indian rates and rounded. Exchange rates move, so the figure on your quote is calculated on the day it is issued.

£360 – £890
We built one

ToolKiya

ToolKiya is Next.js with WebAssembly doing the processing in the browser, which is a harder build than a marketing site and a public one you can test yourself.

Full service detail

This page covers how we work with clients in your market. The complete Next.js Development page, with the full technical detail, process and frequently asked questions, is written in English.

Read the full service page (English)

Questions UK clients ask

How does VAT work if you are based in India?

For most business-to-business services supplied from outside the UK, the reverse charge applies: you account for the VAT in your own return rather than paying it to us, and it is typically neutral if you are fully recoverable. Our invoices state the position clearly so your accountant is not guessing. If your situation is unusual, for example partial exemption, we would rather your accountant confirms the treatment before we invoice than after.

Are you compliant with UK GDPR and the Data Protection Act 2018?

We build to it rather than claiming a certificate. In practice that means data minimisation designed in rather than bolted on, a documented lawful basis for each processing activity, retention periods that actually delete, subject access and erasure handled as features rather than manual database work, and hosting in a region you approve. Where we process personal data on your behalf we sign a processor agreement setting out exactly that.

We are a public sector body. Can you meet the accessibility regulations?

Yes, and it is scoped from the start because retrofitting accessibility is considerably more expensive than building it in. We work to WCAG 2.2 AA, test with a screen reader rather than relying on an automated scan, and produce the accessibility statement the regulations require. Automated tools catch perhaps a third of real issues, which is why the manual pass is not optional.

Which law governs the contract, and what about IR35?

We are happy to contract under English law with the courts of England and Wales, and most UK clients prefer that. IR35 does not apply to us: it governs individuals working through an intermediary, and you are engaging a company for a defined deliverable rather than a person for their time. Your accountant will want to see that the contract reflects that, and ours does.

Next.js Development: common questions

How much does a Next.js project cost?

Marketing sites: £360-£890. SaaS dashboards / web apps: £890-£2,700. Headless e-commerce or enterprise builds: £2,200+. Final cost depends on number of authenticated surfaces, integration count, design fidelity, and whether content is from a CMS or hardcoded.

Should I build on Pages Router or App Router?

App Router for any new project starting in 2025+. Pages Router is now legacy, Vercel is investing entirely in the App Router, and the developer experience is meaningfully better once you accept the server-first mental model. We migrate Pages Router projects to App Router for clients regularly.

Do you deploy to Vercel or somewhere else?

Vercel by default for ~80% of clients, it's the frictionless path and integrates natively with Next.js features. Netlify for static-export sites where the cost model is better. AWS via OpenNext when compliance dictates AWS-only deployments. Self-hosted Node when there's a specific reason.

Can you build the backend for the Next.js app too?

Yes. We build full-stack solutions, Next.js front-end + Server Actions/API routes for the data layer, with Supabase, Drizzle ORM, or a separate Laravel/Node backend depending on the data model and team. We pick the right backend for the project, not a default we always use.

Will the Next.js site have good SEO?

Yes. Every Next.js build we ship includes proper metadata API usage, generated sitemap.xml and rss.xml, JSON-LD structured data per page type, dynamic OG images, and Core Web Vitals tuned to 95+. We also handle Search Console verification and submit the sitemap as part of launch.

Other markets we work in

Working with the UK

Tell us what you are building in the UK

Send the scope, or just the problem. You get a written scope and a fixed GBP quote back within 24 hours, from the engineers who would do the work.