WordPress to edit, Next.js to fly.

Your team keeps writing in WordPress. Visitors get a Next.js front end that loads in about a second, with SEO, tracking and forms built in. Fixed price from $6,000.

Get a fixed quoteRun the free scan
How I fix it · 01 / 04

Model the content in WordPress.

Post types, fields and blocks planned so every page in Next.js has clean data to render. Editors keep the admin they know.

Design components once.

Each section of your Figma becomes a typed React component, mapped to a WordPress block or field group.

Build on Next.js with ISR.

Static pages that refresh when content changes, images and fonts optimised, served from the edge. Previews for editors included.

Launch and keep editing.

Redirects, sitemaps and schema checked, then the DNS switch. Your team publishes in WordPress; the site updates in seconds.

Planning the headless build0 to buildPlanning
Step 1 · plan0 / 5 live
  • WordPress CMSPlanning…
  • Page templatesPlanning…
  • Blog and casesPlanning…
  • Forms and CRMPlanning…
  • Search and AIPlanning…
  1. 01 / 04

    Model the content in WordPress.

    Post types, fields and blocks planned so every page in Next.js has clean data to render. Editors keep the admin they know.

  2. 02 / 04

    Design components once.

    Each section of your Figma becomes a typed React component, mapped to a WordPress block or field group.

  3. 03 / 04

    Build on Next.js with ISR.

    Static pages that refresh when content changes, images and fonts optimised, served from the edge. Previews for editors included.

  4. 04 / 04

    Launch and keep editing.

    Redirects, sitemaps and schema checked, then the DNS switch. Your team publishes in WordPress; the site updates in seconds.

  5. Launch day0 to buildLive
    Step 4 · launch5 / 5 live
    • WordPress CMS✓ Live
    • Page templates✓ Live
    • Blog and cases✓ Live
    • Forms and CRM✓ Live
    • Search and AI✓ Live
    Launched: mobile LCP 1.2 s, editors still writing in WordPress.
Planning: 0
What’s included

Six things every build ships with.

Standard on every headless build, not add-ons.

AreaWhat’s built inWhat you get
Content modelWordPress with ACF or blocks, via REST or GraphQLEditors keep wp-admin
RenderingStatic pages with ISR and editor previewsUpdates live in seconds
PerformanceEdge delivery, optimised images and fontsLCP around 1 s on mobile
SEOMeta, sitemaps, schema and redirects in codeReady to rank at launch
TrackingGA4, GTM, Consent Mode v2, server-side readyEvery lead counted
HandoverRepository, docs and Vercel projectYours to keep, no lock-in
Pricing

Fixed scope. Fixed price.

Before you sign, we agree the templates and a mobile LCP target. You see it measured at handover.

Starter$6,000Up to 10 templates · 6 weeks
  • WordPress as headless CMS
  • Next.js on Vercel with ISR
Get a fixed quote
FullMost chosen$10,000Up to 25 templates · 8–10 weeks
  • Live previews for editors
  • GA4, GTM and Consent Mode wired in
  • Content moved from your old site
Get a fixed quote
Headless + growthComplete$15,000Full site · 10–14 weeks · fast, found, counted
  • Everything in FullCMS, previews, tracking, content
  • Technical SEO auditstructure, internal links, redirects
  • Schema and AI readabilityOrganization, Service and FAQ markup
  • Offline conversionsclosed deals sent back to Google Ads
  • Leak watch for 3 monthsweekly checks after launch
Get a fixed quote
Prices exclude VAT · Vercel and WordPress hosting billed separately, design not included
The guide 5 sections · 5 sections · 1 min readHeadless Next.js, explained.

When headless is worth it

Headless pays off when speed is a competitive edge, when the site has app-like parts such as calculators or portals, or when several front ends share one content source.

For a simple marketing site with a small team, a fast custom WordPress theme or Webflow is usually the better value.

WordPress as a headless CMS

Your editors keep wp-admin, Gutenberg blocks and the plugins they rely on for content. WordPress just stops rendering the pages.

Next.js reads the content through the REST API or GraphQL and builds the pages. Editors get a preview button that shows changes before they publish.

Why it’s so fast

Pages are built ahead of time and served from the edge, close to every visitor. When content changes, only that page is rebuilt in the background.

Images are resized per device, fonts load without blocking, and there’s no theme or plugin code running for every visitor.

SEO on a headless site

Headless can be great for SEO or quietly break it. Meta, canonicals, sitemaps, redirects and schema all have to live in the front end now.

Every build includes them in code, generated from the content in WordPress, and checked against the old site before launch.

Running costs and ownership

You pay for two things: WordPress hosting for the CMS and Vercel or similar for the front end. For most B2B sites both stay modest.

You own the repository and the content. Any Next.js developer can work on it, and the WordPress side stays a normal WordPress install.

Not sure where your site stands?The free scan checks your speed, meta and schema on your real pages, in a few minutes.Run the free scan
Headless FAQ

Headless, answered.

Editing, previews, hosting and when not to go headless.

Something else?Write a line about your site. You’ll get a reply from me within one business day.
Contact

Yes. Editors use wp-admin and Gutenberg as usual, with a preview button for the new front end.

Usually within seconds. Only the changed page is rebuilt, in the background.

Content plugins like ACF and Yoast fields do. Plugins that change how pages render don’t, by design.

WordPress on any managed host, the front end on Vercel or a similar edge platform.

Yes, when meta, sitemaps, redirects and schema are built into the front end. All included.

For a small brochure site with rare updates. Then a custom WordPress theme or Webflow is cheaper.

Often done together

Custom WordPress themeNot ready for headless?See the serviceLeak watchWeekly checks after launch.See the serviceDeep auditSite plus every tool behind the form.See the serviceWebflow developmentA simpler no-code option.See the service