Websites

What we build

Company sites, service and product pages, multilingual sites, areas behind a login. Newly built — or replaced, when what is there no longer carries.

How we build

• Static where it can be static. What the server delivers is the page. Nothing gets assembled in the browser that was already settled beforehand.
• No scripts from other people’s servers. Fonts, images and styles sit on the same machine as the page. What is not loaded can be neither slow nor leaky.
• No cookies without a purpose. Whoever sets none needs no consent banner — and nobody has to dismiss anything before they are allowed to read.
• Content in the source. What stands there is what search engines and AI systems find. What a script fetches afterwards, often not.
• Accessibility in the design. Keyboard operation, contrast and labelling belong in the design, not in the remediation.

What does not happen

We build nothing whose operation depends on us. No site builder you cannot get out of again; no licence falling due every year just so the site continues to exist. If one day you no longer need us, you take the site with you.

What you get

• The site, the source code and the credentials — in your name.
• Instructions for changing the content, written for the people who will change it.
• An audit report from our own procedures: security, privacy, findability, accessibility.
• An accessibility statement and a privacy policy matched to what the site actually does — not to a template.

How it starts

With a conversation about what the site is meant to achieve and who will look after it. From that comes a scope, and from the scope a quote.

Scope, process and price are stated in the quote — once it is clear what the job is. All amounts net, plus VAT.