Services / What we ship
A CMS your editors actually like and your engineers don't fight.
Payload gives content teams a real interface — typed fields, live previews, role-based permissions — and gives engineers a TypeScript-first backend they can ship features against. We design the schema, build the blocks, migrate the content.
Typical scope · 3–8 weeks · single team
Symptoms we recognise
What ships
/ 04 deliverablesSchema first
Fields, relationships, validation, access — all defined in code. Versioned, reviewable, code-shaped. The schema is the spec.
Editors love it
Typed fields, live preview, role-based permissions, draft vs. published states. Editors stop emailing engineering.
Owned admin
Custom field components, dashboards, your auth provider. Not a hosted UI you rent — a TypeScript app you own.
Migration done
We write migration scripts you can re-run. Dry-runs against production. Launch day with no editor downtime.
How this engagement runs
Week 1 · Schema design
We sketch the model in TypeScript and walk you through it before writing a line of admin code. Editors get a say in the field shapes.
Weeks 2–4 · Build
We build the blocks editors use day-to-day, integrate live preview against the live storefront, and wire role-based permissions.
Weeks 5–6 · Migrate
Existing content moves over via scripts in your repository. Dry-run against production, audit the deltas, re-run as needed. No manual copy-paste.
Handover · Train
One session with the editorial team. Source code, environment, deploy guide handed back. You own it from launch day.
Stack we ship against
We pass when
You need a page builder with no schema discipline, or you're shopping for the cheapest quote instead of ownership.
Field questions
No. Once the schema and blocks are set, editors publish, schedule, and preview without engineering. That is the whole point of Payload.
Yes — Payload runs anywhere Node runs. Vercel, AWS, your own Kubernetes. We pick what fits your ops team, not what we like.
We write a one-time script that reads from the old API and writes through Payload's local API. Versioned in your repository, re-runnable, idempotent.
Optional. Retainer hours are available, never mandatory. Most clients keep us for the first 4 weeks post-launch, then renew or not.
From the principal engineer
Editors should fight the work, not the tool. Payload makes that possible because the model is just code — readable, reviewable, yours.
Discovery
We pitch the problem, not the platform.
Reply within one business day · No discovery deck tax