Payload CMS development agency for Next.js sites and apps
Boffin Coders is a Payload CMS development agency for companies, product teams and agencies. We build on Payload 3 inside your Next.js app: the content model, access rules for every role, drafts and versions, and an admin your editors run without a developer. We also move sites to Payload from WordPress, Contentful, Strapi, Sanity or a custom admin. This website runs on Payload and Next.js, built by our own team.
- Code in your repository from day one
- A demo every week on staging
- Invoiced after you see the work
The Payload build you can check is the site you are reading
boffincoders.com runs on Payload 3 and Next.js, built and maintained by our own team. On a call we share the admin and the code behind each card below, and walk through client work under NDA the same way.
Payload 3 inside a Next.js 16 app
The admin, the API and the pages you are reading deploy as one Next.js application on our own server. Content sits in MongoDB, and uploads go to an S3-compatible bucket through the storage adapter. The site moved here from WordPress, with its old addresses kept as permanent redirects in the code.
More than twenty collections and four roles
Blog posts, case studies, portfolio entries, leads and the social media queue are collections. Posts and case studies stay drafts until published, with a capped version history and preview from the admin. Four roles decide what each user can open: an outreach user reaches one list, enforced by access functions on the server.
A custom API with the house rules in code
Scheduled jobs send blog drafts and social posts to a custom endpoint on the same app. It runs the writing rules and checks for a featured image and a named author, then refuses a submission that fails and names each problem. Scheduled publishing puts a draft live at its set time.
Admin screens built for the team using them
A posts view, a board of the week ahead and a database sync screen sit inside the Payload admin as custom views. Each shows only to the roles that use it, and the sync screen opens for one named operator.
What does a Payload CMS development agency do?
A Payload CMS development agency designs, builds and runs content systems on Payload, the open-source TypeScript CMS that installs into a Next.js app. The work covers the content model as collections and globals, the access rules for each role, the hooks that run when content changes, the admin screens your editors use, and the website or app that reads the content. Boffin Coders also moves existing content into Payload, with every old URL redirected, and keeps the project in your repository and your hosting account.
Collections and globals
Pages, posts and products as collections, site-wide settings as globals, written in TypeScript. Types are generated from the config, so a renamed field breaks the build before it breaks a page.
Access rules per role and per field
Functions decide who reads or changes each collection, down to one field or the rows a user owns. Server code passes the user with access checks on, because the Local API skips them by default.
Hooks and custom endpoints
Code that runs around a save: slugs, a search index, a webhook to your CRM. Nested writes pass the request, so a save succeeds or fails as one. Endpoints add the API calls your product needs.
Drafts, versions and live preview
Editors save drafts, compare versions and roll back a bad change. Live preview shows the page while they type, and scheduled publishing puts a post live at the time they set.
Content in several languages
Each translatable field is stored per locale with a fallback, so one record holds every language. The front end serves each at its own address, with hreflang tags between them.
Rich text and blocks in Lexical
Lexical is the editor in Payload 3. We add the blocks your editors need, such as a call to action or an embedded form, and render each with your own components.
Official plugins, set up for your site
SEO fields, redirects, the form builder and search come as official plugins. We set up the ones you need, and write our own when one feature runs across several projects.
Admin screens for your team
Custom fields, list columns, dashboard panels and whole views are React components in the admin. Each role sees only the screens and menu its job needs.
Should Payload run inside your Next.js app or beside it?
Payload 3 installs into a Next.js app, so the admin, the API and the website can deploy as one application. Payload can also run as a separate headless backend that a Next.js site, a mobile app and other services read over REST or GraphQL. Boffin Coders recommends the single app unless a second front end, a separate team or a different release cycle needs the split.
| Question | Inside your Next.js app | A separate Payload backend |
|---|---|---|
| How it deploys | One build and one deploy for the site, the admin and the API. | The backend and each front end deploy on their own schedules. |
| How pages read content | The Local API in server components, with no network call in between. | REST or GraphQL over the network, with caching on each front end. |
| Live preview | Built in, because the preview is the same app. | Works, with the preview address pointing at the front end. |
| Who it suits | One team that owns the site and the content model. | Several teams or front ends, such as a website and a mobile app, on their own release cycles. |
Most Next.js Payload CMS builds start as one app, and the split stays open later, because the content model and the API do not change. Still choosing a CMS? Our headless CMS comparison sets Payload beside the other options.
How do you move to Payload from WordPress, Contentful, Strapi or Sanity?
Moving to Payload is three jobs: rebuilding your content types as collections, importing the records, and keeping every address. Boffin Coders writes the import as a script against the Local API, so field validation and your hooks run on each record. The old rich text is turned into Lexical, media is copied to your bucket, and every old URL is mapped before launch.
| Moving from | How the content comes across | What needs care |
|---|---|---|
| WordPress | Posts, pages, terms, authors and media through the REST API. Post bodies are HTML, converted to Lexical. | Page builder layouts and shortcodes are rebuilt as blocks. |
| Contentful | Entries and assets through its APIs. Content types map closely to collections. | Rich text arrives as Contentful JSON and needs its own converter to Lexical. |
| Strapi | Collection types and single types become collections and globals. | Dynamic zones become blocks, and Markdown or the blocks field is converted to Lexical. |
| Sanity | Documents through GROQ queries or a dataset export. | Portable Text is converted node by node to Lexical, and image crop data needs a home in the upload fields. |
| A custom admin | Rows from your own database or your current API. | Business rules buried in the old code are written down, then moved into hooks and access functions. |
| Payload 2 | The same database, upgraded with the version 3 config. | The admin moves inside your Next.js app, and rich text saved in the older Slate format is converted to Lexical. |
Addresses get the same treatment as our website migration work: every URL listed before the move, one permanent redirect each, and the sitemaps compared on launch day. If your editors would rather keep WordPress, a Next.js front end on headless WordPress keeps it as the editing screen.
Which database, storage and hosting does a Payload project need?
A Payload project needs a database, a place for uploads and a Node.js host. Payload has official adapters for Postgres, MongoDB and SQLite, storage adapters for S3-compatible buckets and other object stores, and it deploys wherever Next.js runs. Boffin Coders sets each one up in your accounts. This website runs on MongoDB, an S3-compatible bucket and our own server.
Postgres for relational data
For joins, reporting or a database your analysts already query. Each schema change becomes a migration file, committed with the code and run on deploy.
MongoDB for a model still taking shape
New fields need no migration, which suits a content model that changes every sprint. A data change, such as splitting one field in two, still gets a script kept in the repository.
Uploads in object storage
Images and files go to an S3-compatible bucket through the storage adapter, never the server disk, so a redeploy or a second server keeps every file.
Vercel, your own server or a container
Payload deploys to Vercel like any Next.js app, or runs as a Node.js process or Docker container in your cloud account. Long jobs, such as a large import, run in the jobs queue, and database backups run on a schedule.
How does a Payload project with Boffin Coders run?
Every Payload project with Boffin Coders follows the same five steps. The scope comes first, then a first sprint that ends in something you can click through. Code lands in your repository from the first day, you see a demo every week on a staging site, and the invoice comes after you have seen the work.
A written scope
Your content types, roles, integrations and pages, priced line by line, with the open questions listed.
The first sprint
It ends with the content model and the admin running on a staging site, holding some of your real content.
Code in your repository
Commits and pull requests go to your GitHub or GitLab organisation, with a README your next developer can follow.
A demo every week
A short call on the staging site: what changed, what comes next, and anything we need from you.
Invoiced after you see it
Each stage is invoiced once you have opened the work and checked it. Nothing is paid before work starts.
Ask any Payload CMS development company, us included, whose repository the code lives in from the first commit and whose name is on the hosting account. If you would rather run the work yourself, you can hire a dedicated Payload developer by the month: a Payload CMS developer who works only on your project, under your management.
Can a Payload CMS agency build under your agency's brand?
Yes. Boffin Coders works as the Payload CMS agency behind yours: we build the content model, the admin and the front end into the repository you name, under your brand, and never contact your client unless you ask. Non-circumvention is signed before you share the brief. Agencies usually buy the work in two-week sprints, each invoiced after the agency has seen it.
Your brand on the work
Pull requests, the admin labels and the handover notes carry your agency name. Your client never sees ours.
Your client stays yours
We talk to you, not to them, unless you bring us into a call. The agreement is signed before you share the brief.
The product around the CMS
When the CMS is one part of a product with logins, billing and dashboards, the same team handles the web application development around it.
Published, not quoted on the call
In USD. Hourly and monthly rates move with the stack and the seniority, from a junior on routine work to a senior on complex builds. Nothing is quoted outside them, and if the number does not work for you, you have saved yourself a meeting.
- A Payload CMS build starts at
- US$4,000
- Scoped once, with the lines shown.
- Short pieces of work
- US$18-32 an hour
- By seniority and the work.
- A developer by the month
- From US$3,000 a month
- Month to month, a month’s notice either way.
- Agency sprint
- US$2,000 per two-week sprint
- Under your brand, invoiced after you see the work.
Before you hire a Payload CMS development company
What companies, product teams and agencies ask before they hand us a Payload build or a move to Payload.
Hire a Payload CMS developer when you have a technical lead who sets the priorities and reviews the code, and you want one person on your project every month. Work with an agency when you want a scoped result, with the content model, the build and the launch run for you. Boffin Coders offers both, and the same engineers do the work either way.
Not answered here?
Related reading
Planning a build or a move to Payload?
Twenty minutes with the engineer who would lead the work. Bring your current CMS, your content types and any deadline. You leave knowing whether Payload fits, whether it should be one app or two, and roughly what it costs from the published rates.