Web
development

Our core discipline. We plan, design and build websites and web interfaces — from the first idea through to the thing people actually use.

Why one team matters

Most digital projects lose their shape at the handover: the idea is one company, the design another, the code a third. Nobody owns the result. We are three people, and strategy, brand and engineering sit in the same room, so what gets built is what was meant.

We choose the stack per project rather than per habit — sometimes a static site is the honest answer, sometimes it is a full application. What does not vary is the floor: measured performance, accessibility to WCAG 2.1 AA, and documentation you can hand to someone else.

What is included as standard

Build

Technical concept, information architecture, responsive design down to 360 px, front-end implementation, integration with the systems you already run.

Performance

Core Web Vitals treated as a requirement rather than a report. Measured before and after, with the numbers written down.

Accessibility

WCAG 2.1 AA built in from the first component, not retrofitted once the law becomes a problem.

Multilingual

German and English as a first-class concern, including the hreflang plumbing most sites get wrong.

Findability

Clean markup, structured data, correct canonicals. A site nobody can find is a brochure.

Handover

Documentation, deploy instructions, and a codebase your next developer will not curse at.

How a project runs

  1. Review. What exists, what works, what is worth keeping. Ends with a written scope and a number.
  2. Concept and structure. What the site has to do, for whom, and in what order.
  3. Design. Interface and design system, with contrast and focus states checked as we go rather than at the end.
  4. Build. In our hands, with something you can click on early.
  5. Measurement. Load time, Core Web Vitals, accessibility — against the numbers we started with.
  6. Handover. Documentation, training if you want it, maintenance if you want it.

We hold our own site to it

Selling engineering is easy to claim. In September 2026 we cut this site's critical path from 334 KB to 80 KB, replaced a 133 KB pair of logo images with a 6 KB inline SVG, and subset the fallback font from 102 KB to 18 KB. The accessibility audit reports zero violations across every page, and we publish the limitations we have not solved yet.

Questions

What does a website cost?
It depends on how much of it is new. A focused marketing site is a different job from a shop with a custom checkout. We scope in stages and give you a number before anything is built, not a rate card that turns into a surprise.
Do you work with our existing site or start over?
Both, and the honest answer usually comes out of a short technical review. Rebuilding something that works is waste; patching something structurally broken is more expensive than replacing it. We will tell you which one you have.
Who writes the code?
We do. Strategy, design and engineering sit in the same team of three, which is the whole point — there is no handover where intent gets lost, and no subcontractor to chase.
What happens after launch?
Whatever you want to happen. Some clients take the keys and run; others keep us on for maintenance, performance work and the annual accessibility re-check. We hand over documentation either way.

Start with the review

Before anyone talks about budget, it helps to know what you actually have. Tell us the address and what is bothering you.

Start a conversation See the accessibility work