We’re a small Next.js development agency for UK businesses, and this website runs on Next.js 16. We build fast websites, online shops and web apps where each page is either prebuilt or built on request, depending on what it does, and you own the code. Website packages start at £400, and custom builds get a fixed-scope price before any code is written. If WordPress would suit you better, we’ll say so.
Next.js suits a business that wants a fast site it rarely has to think about, or a site that has to do more than explain your services. We use it for three kinds of job, and each one has a price before we start.
Starter (£400, up to 5 pages, usually live in around 2 weeks), Business (£750) and Growth (£1,200). Every package includes a quote form and a reviews section. Tell us you want Next.js and we build it in Next.js.
A small shop for up to 20 products (£900) or an online shop for up to 50 (from £1,500). The Gift Sip is a Next.js store that pulls its products from Printify and sends each paid order straight back to it.
Customer portals, logins, booking flows and connections to the systems you already use. We quote these at a fixed scope once we know the job, and confirm the price in writing before any code is written.
Not sure which you need? Our web development page explains when a package is enough and when a custom build is worth the extra.
The quickest way to judge a Next.js developer is to look at what they run themselves. This website is a Next.js 16 build on React 19. Below is every kind of page on it and how each one is made. The counts are read from the site’s own data, so they stay right as we add pages.
/servicesHow many: 10pages
How it’s built: Prebuilt page
Why: Nothing on these changes from one visitor to the next, so each is built once when the site deploys and served from the nearest edge server.
/services/web-designHow many: 5pages
How it’s built: Prebuilt, one per item
Why: One template, one page per service, built from our service data. Adding a service is a data entry, not a new page file.
/services/web-development/nextjs-developmentHow many: 9pages
How it’s built: Prebuilt page
Why: Hand-built pages like this one. Every price on them is read from one packages file at build time, so a price change updates every page at once.
/industries/plumbersHow many: 10pages
How it’s built: Prebuilt, one per item
Why: One page per trade, each from a typed data file. The build checks every one before it can go live.
/articles/what-is-nextjs-used-forHow many: 21pages
How it’s built: Prebuilt, one per item
Why: Built from one JSON file. A link check runs before every build and stops it if an article links to a page that doesn’t exist.
/projects/evietekHow many: 4pages
How it’s built: Prebuilt, one per item
Why: The same pattern as the articles: one template, one page per project.
/tools/website-graderHow many: 2pages
How it’s built: Prebuilt page
Why: The tool pages are prebuilt like everything else. The check itself runs in the next row.
/api/contactHow many: 2pages
How it’s built: Runs on request
Why: Sending a message or checking a website has to happen fresh each time, so these run on the server on request and are never cached.
What the live site sends back
$ curl -I https://www.codekodex.com/
HTTP/1.1 200 OK
Server: Vercel
# the page was built in advance
X-Nextjs-Prerender: 1
# a nearby server sent it ready-made
X-Vercel-Cache: HITHeaders checked from a UK connection on 11 November 2026, on the homepage, an article, an industry guide and a service sub-page; all four were prebuilt and served from the edge cache. Page counts come from the site’s data when it builds.
Each one is written up in full, with the figures from its case study.
Evietek is an agency in London, Ontario. We turned its Figma designs into a Next.js site with an SEO-ready blog the team publishes on without a developer, about 12 posts a month since launch. Largest Contentful Paint is 0.8s, every Core Web Vitals check passes, and bookings and chats are up 25% since launch. Read the Evietek case study.
A print-on-demand store we built solo in 4 weeks. Catalogue pages are rebuilt on a schedule so they stay fast, and each product page is rendered on the server so the price and options are always right. Every paid order goes to Printify automatically. Read The Gift Sip case study.
A mobile car-detailing business in Tyler, Texas needed its packages easy to read on a phone and a quick way to ask for a quote. It didn’t need a content editor, so we built it in HTML, CSS and JavaScript with a small PHP mailer, in 2 weeks. Mobile LCP on the landing page is 1.9s, and contact form completions are up 18%. Read the Mobile Detailers case study.
Swipe the table to compare
Next.js isn’t the right tool for every business site. This is how the three compare for a small business, and who each one suits.
| What’s included | Next.js | WordPress | Plain React |
|---|---|---|---|
| Editing it yourself | Through a content editor, if we add one, or you send us changes | Yes: text, photos and pages in the dashboard | No. Every change goes through a developer |
| Speed on a phone | Pages can be prebuilt and served from the nearest server | Depends on the theme and how many plugins it runs | The page is drawn in the browser once the JavaScript has loaded |
| Showing up on Google | Google gets the finished page | Google gets the finished page | Google has to run the JavaScript before it sees the content |
| Upkeep | Framework and dependency updates | Core, theme and plugin updates, monthly | Dependency updates |
| Suits | Fast sites, custom features and online shops | Owners who want to edit everything themselves | Tools that live behind a login |
How Google handles JavaScript: Google Search Central, JavaScript SEO basics (2026). More detail in what Next.js is used for, Next.js vs React and our guide to choosing a website platform. Prefer WordPress? See our WordPress websites.
We build in Next.js, and in these four cases we’d still point you somewhere else.
Choose WordPress. You change text, photos and pages without ringing anyone, and almost any developer can take it over later. We build those too, at the same prices: WordPress websites.
If nothing needs to be found on Google, a plain React app is simpler and can sit on cheap static hosting. Server rendering earns its keep on public pages.
A one-off campaign page with no second phase doesn’t need a framework. Build it in whatever’s quickest.
A Next.js site needs framework and dependency updates. If neither you nor we will do them, pick something you can look after, or add a care plan.
Yes. React’s own documentation recommends starting a new app with a framework and lists Next.js first. The question worth asking is who keeps your site on a supported version.
Released on 21 October 2025 and in Active LTS, so it gets new features and security fixes (Next.js support policy, 2026).
Its security releases were extended past the original October 2026 end date. Version 14 and older get none.
21.5% of professional developers used Next.js in 2025, and 46.9% used React (Stack Overflow Developer Survey, 2025).
On a Care plan (£25/mo): framework and dependency updates, monthly, tested before they go live. Critical security fixes within 2 working days.
Next.js is free and open source under the MIT licence, so there’s no licence fee to pay.
Next.js websites cost the same as every website we build. Starter is £400, Business £750 and Growth £1,200, each a fixed price with the full list of what’s included. Web apps and integrations are quoted at a fixed scope.
A professional first website for a new or small business.
£400
A fuller site for an established business that wants to win more work online.
£750
For businesses ready to compete harder in local search.
£1,200
Selling products online? Our shop packages start from £900. Compare the shop packages
A Starter site is usually live in around 2 weeks, and a custom build usually takes 6–10 weeks from discovery to release. Either way, the steps run in this order.
We list your page types (services, articles, products, account pages) and write down how each one is built: prebuilt, rebuilt on a schedule or run on request. It sets how fast the site is, so it’s agreed before design starts.
You click through the real site on your own phone as it’s built, instead of looking at slides.
Forms, payments and bookings, with errors logged so nothing fails quietly. Then phone, browser, accessibility and speed checks, and a redirect map if your old pages have rankings to keep.
The code lives in a repository you own. Keep us on a care plan, or hand it to any developer.
You don’t need to be technical to judge a Next.js developer. Ask these six, and listen for answers about your site rather than about the framework.
A good answer names your page types and says why.
Open two of them on your phone, on mobile data. It takes two minutes.
The current version, with a named person or plan for updates.
In a repository you own.
If you already have a site, the answer has to include a redirect map.
Ask who works on it day to day, and whether you can talk to them.
Slow down if you hear “we’ll do SEO after launch”, get a fixed price before anyone has asked what your pages do, or see no mention of handover. We’ll answer all six on a free 30-minute call.
With us, the same as any website we build: Starter is £400, Business £750 and Growth £1,200, all fixed prices. Shops start at £900. Web apps and integrations are quoted at a fixed scope, confirmed in writing before any code is written. A Care plan is £25/mo, and it’s optional.
Yes. React’s own documentation recommends starting a new app with a framework and lists Next.js first. Version 16 is in active support, and version 15 gets security fixes until 31 January 2027. In Stack Overflow’s 2025 survey, 21.5% of professional developers used it. This website runs on Next.js 16.
It can send Google a finished page, which removes the main risk with JavaScript sites: Google has to render the JavaScript before it can index the content. It won’t rank a slow site with thin pages for you. We build page titles, schema, sitemaps and canonical tags into the templates, so nobody has to remember them.
No. Next.js runs with every feature on any host that supports Node.js or Docker, and a static export runs on any web server with fewer features. This website is hosted on Vercel, and Evietek’s build uses Netlify and AWS. We set hosting up on your own account, so it stays your choice.
Yes, if we add a content editor. That’s how Evietek’s team publishes about 12 blog posts a month without a developer. Without one, you send changes to us, and the Care plan includes 30 minutes of edits a month. If you want to change every page yourself, WordPress may suit you better.
Yes. We check two things first: which version it’s on, and whether it uses the older Pages Router or the App Router, because the router decides most of the work. We look at the code, then quote a fixed scope. If any URLs change, we redirect them so you keep your Google rankings.
WordPress, if you want to edit every page yourself and don’t mind monthly plugin updates. Next.js, if you want the fastest site, custom features or a shop, and you’re happy to send us changes or use a content editor. Both cost the same with us, and you own the code either way.
Tell us what the site has to do. We’ll tell you which pages should be prebuilt and which should run on request, what it costs, and whether WordPress would suit you better.
Tell us what you need built: a website, an online shop, an integration or a web app. We’ll reply within one business day with clear next steps.
A real person reviews your notes and comes back within one business day.
We go through what you need, your budget and your deadline, then tell you honestly which option fits.
Scope, milestones and pricing in writing within 48 hours of the call.
From £400