WordPress agency
for sites that hold up to editors and growth.

We don’t publish fixed-price ranges for WordPress projects, because a lean brand site, a multilingual B2B platform and a WooCommerce setup with CRM integration are different worlds.

The path to a fixed price:

• Free discovery phase — we clarify scope, languages, integrations, editor needs, hosting and performance targets
• Transparent fixed-price quote with clearly separated phases: discovery, design / theme, migration, launch, care
• Exit gates after each phase — you decide whether to continue

No "up-to" pricing, no hidden surcharges. Work is usually billed as a fixed-price package, not via open hour quotas.

Premium themes like Avada, Divi, Bridge or BeTheme deliver a nice first hour — and after 12 months an expensive dead end. Tolerable for brochure sites under 10 pages; not for any growing brand site.

What premium themes actually bring:

• 200+ demo layouts and a page builder as a sales argument
• 600 KB of CSS per page as a performance anchor
• 80+ plugins as dependencies with their own update logic
• Page builder that stores content in proprietary shortcodes (migration away = data loss)
• Lighthouse scores under 50 mobile with standard demo content
• Editor UI with 200 options per block that scares off editorial teams

When it still fits: brochure site under 10 pages without a growth plan — e.g. an association site or a temporary event presence.

When it doesn’t fit: brand site meant to be maintainable after 3 years, with an editor team and multilingual growth. Then a custom theme with the native block editor is the more economical choice.

We build both and advise outcome-open — the choice depends on editor workflow, interactivity and maintenance ambition.

React / Next.js (headless or full-stack) is right when:

• You need highly interactive frontends or app-like workflows
• An extremely performant custom architecture is required (sub-second LCP, edge rendering)
• You have or want to build your own frontend engineering team

WordPress as CMS is right when:

• Editor workflow and quick content changes matter more than custom frontend logic
• You need the plugin ecosystem (WPML, ACF, Yoast, WooCommerce, BuddyPress, LearnDash, …)
• Time-to-market and long-term maintainability without a specialist team are priorities

In many cases WordPress is the economically correct answer, even if the tech Twitter bubble sees it differently.

We don’t actively recommend page builders like Elementor or Bricks — as the standard stack for new brand sites we prefer custom themes with the native block editor (Gutenberg) and ACF Blocks. But: if you deliberately want to go with Elementor or Bricks, we implement it cleanly.

Why custom theme + block editor is our default:

• Long-term maintainable without builder lock-in
• Lean code (no builder layer, no 80+ companion plugins)
• Better Core Web Vitals out of the box

When page builders still make sense:

• Existing in-house skills in the builder
• Existing library or design system in builder format
• Faster editor workflows for non-technical teams

The critical factor in that case is hosting: page-builder sites carry higher load through the builder layer and more plugins, but with properly configured hosting they are perfectly performant.

Hosting setup for performant page-builder sites:

• Suitable PHP and memory limit
• Object cache via Redis
• Clean CDN setup with HTTP/3
• Image optimisation (WebP, AVIF, lazy loading)

With the wrong host even a lean theme gets slow — with the right setup even a Bricks site can hit sub-second load times.

Both are legitimate — we choose per project. Polylang Pro for pure content sites with DE/EN, WPML for larger WooCommerce setups or complex translation-management workflows.

WPML — when we use it:

• Larger WooCommerce sites with multilingual products and variants
• Complex translation-management workflows (external translators, translation memory)
• Better WooCommerce support out of the box
• Trade-off: higher licence costs, heavier in the backend

Polylang Pro — when we use it:

• Pure content sites with DE / EN or DE / FR / IT / EN
• Leaner data structure, faster in the backend
• More elegant for brand presences without a shop component
• Trade-off: less translation-management comfort, less WooCommerce depth

The hreflang implementation we do cleanly in both cases per language region (de-AT, de-DE, de-CH, en-AT, etc.) — including x-default setup for international presences.

Three standard paths — all in Frankfurt with EU data processing. Which path fits depends on customisation depth and who-owns-the-hosting logic.

1) Hetzner Cloud or Dedicated — admin-managed by us:

• Best performance per euro
• Full customisation depth (Nginx, PHP tuning, Redis, MariaDB)
• Ideal for custom setups and higher load profiles

2) Fly.io Frankfurt with container setup:

• Good for multilingual sites with geo-routing
• Container-first operations with modern deployment

3) Raidboxes managed WordPress:

• When you prefer to hand hosting ownership to a WordPress specialist
• Solid standard setup with caching and monitoring

Hosts we deliberately don’t recommend: All-Inkl, World4You, IONOS, Anexia — performance, scaling or operations topics regularly cause stress there.

We cleanly implement the technical prerequisites for GDPR-compliant operation — a blanket "GDPR-compliant" guarantee is a legal assessment we don’t give as a WordPress agency.

What we deliver technically:

• EU hosting in Frankfurt (Hetzner, Fly.io, Raidboxes)
• Consent Mode v2 for correct pre-consent behaviour
• Cookie-banner plugins (Borlabs Cookie, Complianz) granularly configured
• Tracking pixels off by default — activation only after consent
• Data-processing agreements with all sub-processors documented

Distinction — what we don’t deliver:

• Which cookie categories you actually need
• How consent must be logged audit-proof
• Whether third-country transfers are sufficiently documented
• Concrete risk assessments per use case

The legally binding assessment belongs in the hands of your lawyer or data-protection officer. We deliver the technical template, not the legal opinion. The same applies analogously to FADP (Switzerland).

After payment the code belongs entirely to you — no vendor lock-in.

What you receive on handover:

• Theme code in your Git repository (GitHub or GitLab as preferred)
• Custom plugins as standalone packages
• Full hosting accounts in your name (Hetzner account, Fly.io account or Raidboxes account)
• Plugin licences issued in your name
• Backup strategy cleanly documented with restore runbook

Theoretically you could engage another agency after launch — we see that as a quality promise, not a risk.

In practice, over 90 % of our clients stay long-term — because maintenance and further development run with the team that built the site.

Yes — in two clearly separated paths, depending on whether the site should just run or keep growing.

1) WordPress maintenance as a standard product — from € 140/month net:

• For sites without notable further development
• Focus on updates, backups, security, monitoring
• Incident response with a clear SLA
• Published fixed price without consulting overhead

2) Consulting retainer in multiple package sizes:

• For sites with continuous content expansion
• New landing pages and smaller custom functions
• Regular editor training for internal teams
• Strategic advice on further development

Standard response: within 24 h on business days in both paths. Faster SLAs (4 h response in CET business hours or 24/7 on-call) as a contractual add-on.