Sites that load before you can blink
Next.js, a headless CMS and hosting matched to your traffic. A site your team can run without a developer, and one that does not lose positions to slow loading on a phone over 4G.
What is usually wrong with the current site
It is rarely the design. The three things that most often cost traffic and conversion are invisible from the outside.
- 01
Loading depends on plugins
A WordPress site with twenty plugins fires a dozen requests before it renders the first line of text. Every update is a lottery and performance degrades each quarter.
- 02
Nobody can change anything without a developer
Editing a heading on the homepage becomes a two-week Jira ticket. In practice that means the site freezes in the state it launched in.
- 03
SEO bolted on afterwards
Missing canonicals, accidental titles, a sitemap generated by a plugin, structured data pasted into one template by hand. Fixing that later costs more than doing it correctly up front.
What we build
Scope flexes with the project, but these parts are always there.
Interface design
Wireframes and a component system built around real content, not around a screenshot for a portfolio. We design mobile-first and in both themes where they are needed.
Next.js implementation
App Router, server-side or static rendering, AVIF and WebP images, code splitting. No heavy animation libraries where CSS does the job.
Headless CMS
Sanity, Payload or Strapi — chosen to fit how your team works. Editors get live preview and cannot break the layout.
SEO in the foundation
Metadata generated from content, hreflang, sitemaps, structured data, canonicals and redirects from the previous site. All of it versioned in the repository.
Performance as an acceptance criterion
A performance budget enforced in CI. A deploy that breaks Core Web Vitals does not ship — this is not something checked once at the end of the project.
Analytics and consent
GA4, Consent Mode v2 and a consent banner that neither blocks content nor destroys your performance score. Configured and ready for paid campaigns.
How the project runs
- 01
Weeks 1–2 — scope and content
Workshop, sitemap, inventory of existing URLs and traffic. We decide what moves across, what gets rewritten and what disappears behind a redirect.
- 02
Weeks 2–4 — design
Visual direction first, then the component system. You sign off the key templates rather than every individual page.
- 03
Weeks 4–8 — build
Two-week sprints with a demo on staging. Content goes in alongside, so sign-off does not collide with empty templates.
- 04
Weeks 8–10 — launch and stabilisation
Redirects, Search Console monitoring, fixes after the first week of real traffic. We watch indexing and rankings for a month after launch.
What it costs
from €4,000
A brochure site with a handful of templates sits at the lower end. A larger site with multiple languages, search and integrations is typically €8,000–16,000.
- Interface design and component system
- Next.js build with a headless CMS
- Content migration and redirect map
- SEO, analytics and consent configuration
- One month of post-launch care included
Common questions
You can, and sometimes it is sensible — WordPress as a headless CMS behind a Next.js frontend works well if your editors know the admin and do not want to relearn it. We only advise against classic themed WordPress when performance is a priority.
Vercel by default, because it needs the least maintenance. If you have data residency requirements or your own infrastructure, we deploy as a container in your environment with no code changes.
With redirects done properly and the structure preserved there is usually no lasting drop. You will see fluctuation for two to four weeks after launch, after which positions return — most often higher, because performance improves.
Yes. From the first commit we work in a repository owned by the client. We do not use code licences or anything else that ties you to our hosting.
It starts with an audit
Tell us in two sentences what you want to achieve. We reply within one business day.