Changing a price or a paragraph means writing to a developer and waiting.
We move all changing content into the CMS with clear fields. Editors update, check a draft preview and publish themselves.
A headless CMS your marketers can run without a developer
We pick the right CMS, design the content model and connect it to your site. Editors publish on their own, and developers stop being the bottleneck.
Quote and schedule after your brief
Who it's for
- Businesses where every copy change needs a developer ticket
- Companies running several languages, regions or brands on one site
- Teams that want the same content on a website, an app and in email
- Owners whose old WordPress or site-builder setup is struggling with a growing catalogue
Problems we solve
Content is scattered across the site, spreadsheets, chats and old files.
We design a content model: which record types exist, what fields they have and how they link. We migrate existing material with scripts, not by hand.
We worry the CMS will box us in or get expensive as we grow.
We compare Contentful, Sanity, Strapi and Storyblok against your volumes, languages and budget. We show where each plan has limits and what you will pay extra for.
Our last migration cost us Google visibility.
We carry over URLs, titles and metadata and set up redirects. Before launch we check old and new pages against a full list.
What's included
- CMS selection against your volumes, languages and budget, with a written comparison
- Content model: record types, fields, relations, validation rules
- Role setup: who edits, who approves, who only reads
- Connection to the front end (Next.js or Astro), with pages refreshed on publish via webhooks
- Draft preview mode so editors see the page before it goes live
- Reusable page blocks so editors can assemble landing pages without a developer
- Multilingual setup and SEO fields: title, description, social image
- Migration of existing content from the old site using scripts
- Image optimisation through a CDN
- Editor guide and a training session with your team
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Start
A small site where text and blocks need to move into a CMS
- CMS selection and a simple content model
- Connection to your existing site or a new landing page
- Draft preview
- Two roles: editor and admin
- Editor guide
02
Standard
A corporate site or blog with several languages and a migration
- Full content model with page blocks
- Content migration from the old site
- Multilingual setup and SEO fields
- Roles and approval flow
- Redirects from old URLs
03
Advanced
Multiple sites or brands, or a large catalogue
- Shared content model across several sites or apps
- Integrations with CRM, PIM or inventory systems
- Complex relations between records
- Permissions and change history
- Self-hosted Strapi on your own server if you need it
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
CMS choice and content model
We compare platforms for your case and sketch the records and fields. You approve the schema before development starts.
Pilot with a measurable KPI
We move one section, such as the blog or the services catalogue. We measure how long an editor takes to publish and compare it with the starting point.
Connection, migration, preview
We connect the CMS to the site, migrate the rest of the content, and set up roles and redirects. Payment is in stages.
Training and handover
We run a session for your editors. All accounts, keys and files belong to you under the agreed terms.
Scope and limits
- We do not promise that a CMS will raise traffic by itself: it speeds up content work, while SEO and ads bring customers.
- We do not choose the platform in advance: if a cheaper option or plain WordPress suits you better, we will say so.
- We cannot guarantee zero ranking movement after a migration: redirects and checks keep the risk low, but short fluctuations can happen.
FAQ
What is a headless CMS in plain terms?
It stores your content separately from how the site looks. Editors work in a friendly dashboard, and the site pulls content through an API. The same content can appear on a website, in an app and in email.
Contentful, Sanity, Strapi or Storyblok: which one?
Contentful suits larger teams with complex workflows, but costs rise with volume. Sanity is flexible for developers and can be shaped around editors. Strapi can run on your own server, but then someone must keep it updated. Storyblok is the friendliest for marketers thanks to its visual editor.
What will the CMS cost per month on top of your work?
We prepare a quote after reviewing your brief and requirements. A first stage can cover: cMS selection and a simple content model; Connection to your existing site or a new landing page. Scope, payment and schedule are agreed before work starts.
Can we keep our current site and add a CMS?
In most cases, yes. We connect the CMS to a new front end and move sections one at a time. If your old site runs on WordPress, it can stay as the content source during the transition.
Can we switch to another vendor later?
Yes. The CMS account, repository and hosting are registered to you under the agreed terms. We document the content model so any developer can pick it up.
What do you need from us to start?
Access to the current site, sample pages and a list of what editors change most often. You need one person who can make decisions on content structure. The project brief helps collect the rest.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.