Web development: website and application, built as one.
For large, content-heavy websites with many pages and multiple editors, we build an enterprise CMS: frontend, backend and content model with Payload CMS as one system.
Starting point
Sound familiar?
Multiple editors maintain the same website
Without a proper content model, they keep getting in each other's way.
Three vendors built the site
Website, content model and logic no longer fit together.
New content keeps coming in
But every change still needs a developer and a deploy.
The website was never one system, just a frontend, a CMS and logic bolted on separately.
The result
You get a large, content-heavy website in one system that holds editorial and engineering together, one an AI assistant can safely help maintain too.
- Running website with a content model built around your content
- An editing surface your team builds and publishes pages from
- Content an AI assistant can read and edit as drafts
- Operations in the EU, plus code, access and documentation
Client feedback
From client work
A hands-on mentality paired with broad technological know-how. This is what makes IT projects fun.
Process
How we go about it
01 / ASSESSMENT
We look at the site and the application as one.
We look at what your website actually needs to do, as a public site and as an application, not just as a content question.
02 / ARCHITECTURE
We define frontend, backend and content model.
We build Payload CMS as the foundation, with blocks, data model and application logic in one system.
03 / BUILD
We build frontend and backend together.
We ship in weekly cycles, with visible progress for editorial and engineering at the same time.
04 / HANDOVER
We hand over editorial and operations.
You get access, documentation and a short walkthrough for your team.
Team shape, cadence and handover in detail are covered on the How we build page.
Questions
Frequently asked questions
No. For a handful of pages that rarely change, this is too much machinery. A simple website builder is enough there.
WordPress is a CMS with application logic bolted on. Payload is an application framework that happens to include the CMS, so the site and the application are one system instead of two.
We take over the existing content, map it into the new content model, and only switch over once both systems show the same content.
Both are open source and TypeScript based. Payload is a Next.js application framework with a CMS built in, not a CMS with an app bolted on.
Self-hosted in the EU. Your data stays with you, not with a vendor outside the EU.
For content and page layout, yes, that is what the block system is for. New features still mean engineering, no CMS changes that.
You get the code, access and documentation. Payload is open source, so you can keep working with any team that knows TypeScript and Next.js.
No. We do not estimate work we have not understood. An analysis always comes first.
No. Whoever starts stays until handover.
No. After handover you decide when we lose access to your systems. There is no spare key.
The code is yours and so is the documentation, entirely from day one. We do not build dependency on us as a business model.
Contact
Tell us what your website can't do today.
A wish list is enough, we'll build the content model from it.
André Loreth
Andreas Neugebauer
You talk directly to the founders.
A reply within one working day.
On the call
- 01You describe what's going on: a new system, or one that isn't keeping up anymore.
- 02We ask questions and tell you honestly whether and how we can help.
- 03You get concrete next steps, whether or not we end up working together.