The stack behind a regulated consultancy.

A start-up-grant consultancy lives on precision. Prices, legal citations and deadlines change, and they have to be changeable without anyone touching code. That single fact decided the stack for Gründertisch.

Why a headless CMS at all

Gründertisch.de is a Next.js 14 site on Vercel, with all content managed in Storyblok. The frontend is rendered and served; the copy, the prices and the building blocks come from the CMS. That is more work than simply hard-coding a site — but it pays off from day one, because a consultancy is not a static shop window.

The separation is clean. What the visitor sees, I build in Next.js, where I control speed, layout and language. What changes — a service, a price, a line in the Impressum — lives in Storyblok, where Hans can touch it himself. Nobody has to wait on a developer to turn “149 €” into “159 €.”

An editorial workflow Hans runs himself

Storyblok is not just a database for text. It gives Hans a visual editor: he sees the page, clicks into a block, and edits it where it appears — not in an abstract form. Draft and publish are separate, so he can prepare a change, look at it, and only push it live once it is right.

For a regulated practice, that control is not a convenience, it is a duty. When the funding situation shifts or a price is adjusted, the person who owns the facts owns the edit — and can make it without a detour. Draft/publish also means a half-finished line never slips online by accident.

Four languages, one source

The site runs in four languages — German, English, Spanish and Italian — because Hans advises founders in all four. The translations live in Storyblok per field, not in four separate copies of the site. A new service is created once and maintained in each language, without the structure drifting apart.

That is the invisible part of multilingual work: not the translating itself, but the discipline that all four versions describe the same reality. A CMS that treats languages as variants of one piece of content makes that discipline the default path rather than the exception.

Consent Mode v2 — measurement and consent reconciled

Gründertisch runs Google Ads, so it needs conversion tracking. And it operates in Germany, so it needs real consent. Those two requirements are usually at war. Google Consent Mode v2 in its Basic configuration settles it: tags fire only after the visitor has agreed — before that, no Google tag runs at all.

Basic rather than Advanced is a deliberate choice. Advanced would send anonymised pings before consent; Basic sends nothing until consent is given. That is the more conservative, cleaner path for a compliance consultancy — and it still keeps Google Ads measurement compatible, because conversions are attributed correctly the moment consent arrives.

Cookieless by default

Audience measurement runs through Vercel Analytics — cookieless. There is no tracking cookie forcing a banner full of toggles, and no identifier following visitors across pages. I can see which pages work and which do not, without building a profile on anyone.

Cookieless here is not only the lawful choice, it is the honest one. A consultancy that advises its clients to be careful should not collect more data on its own site than it needs. The only thing that runs without consent is technically necessary.

Why this stack holds

Every piece has a reason. Next.js on Vercel for speed and control. Storyblok so the expert maintains his own facts. Four languages from one source, so nothing drifts. Consent Mode v2, so advertising stays measurable and lawful. Cookieless, because it mirrors the consultancy’s own promise. No part is fashion — each solves a concrete problem this practice has.

All prices exclude 19% VAT.

— Dimitrios