SoftVolt AI
Headless & Next.js

The Bulk Bag Man

A custom WordPress child theme exposes ACF fields, menus and a Supplies post type through the REST API; a Next.js App Router front end renders it on Vercel. Contact form submissions are proxied through a route handler, so the browser never talks to WordPress directly.

Open the live site Send us a brief
bag-man-live-six.vercel.app
The Bulk Bag Man — homepage
At a glance

Headless & Next.js for a uk aggregates supplier.

Headless architecture · WordPress child theme · Next.js front end

This one is on the site because it can be checked. It was delivered for a uk aggregates supplier in United Kingdom, our founder's part in it was headless architecture · wordpress child theme · next.js front end, and everything claimed below is either visible in the running site or in the code behind it.

4 things shipped in this build, listed in full below. It was made with Headless WordPress, Next.js, REST API, ACF, TypeScript, Vercel for a client in United Kingdom, and the site is still live — open it and check the claims against the real thing.

Client
UK aggregates supplier
Market
United Kingdom
Our role
Headless architecture · WordPress child theme · Next.js front end
Built with
Headless WordPress · Next.js · REST API · ACF · TypeScript · Vercel
What shipped

The work, in plain terms.

Client
UK aggregates supplier · United Kingdom
Role
Headless architecture · WordPress child theme · Next.js front end
Stack
Headless WordPressNext.jsREST APIACFTypeScriptVercel
  • 01WordPress child theme that exposes ACF fields, menus and a Supplies post type through the REST API
  • 02Next.js App Router front end deployed on Vercel
  • 03Contact form submissions proxied through a Next.js route handler, so the browser never calls WordPress
  • 04Content editing stays in the WordPress admin the client already knows

No traffic, revenue or ranking figures are published here. We only publish numbers we can show you — a Lighthouse run, a Search Console export, an error rate — and for this project we do not hold them.

If this were your brief

The same build, delivered under your brand.

As a white-label project this runs through the same five steps, with your agency on the staging URL, the commits and the handover — and our name nowhere.

  1. 01

    Send the brief

    Reply within 1 business day

  2. 02

    Scope & quote

    Within 2 business days

  3. 03

    Production

    Timeline fixed in the scope

  4. 04

    QA & review

    Published checklist, every build

  5. 05

    Agency delivery

    Handover doc with every launch

Next step

Send the brief — get a fixed price within two business days.

Send the brief and get a written scope with a fixed price within two business days. Client names can wait until the NDA is signed.

Send us a briefBook a 20-min scoping call