Website development built around what your business already runs on.
Open systems as the foundation: Shopware, WordPress, Astro — and custom development where it is needed. From Zurich, for the whole of Switzerland.
Commissioning a website rarely means starting from nothing. Usually something is already there: a site that has aged, a system nobody enjoys maintaining, or a presence that is not found by the people looking for it. We build websites for companies where a piece of development belongs to the job — parts of the site are custom built for that purpose. That might be data coming from another system, a process that has to work on the page, or a site that has to function properly in two languages. From Zurich, for clients across Switzerland.
What custom development means in practice
For many projects a ready-made theme is the right choice: quick to set up, inexpensive to run, entirely sufficient for a site of moderate size. We deliver those projects too.
Our focus lies where that stops being enough, which usually begins at one of three points.
The content comes from another system. Products from the ERP, appointments from a calendar, documents from a repository. As soon as something is maintained in two places, the two versions drift apart — always. The answer is a connection between the systems, not more discipline in maintaining them.
A process has to happen on the site. An enquiry that branches depending on the answer. A calculation that prepares a quotation. A form that lands in your system rather than in an inbox. Those are custom components, not settings.
The site has to fit your landscape. Multilingual content that also works for search engines. A domain structure that has grown over time. Data protection requirements that rule out certain solutions.
What we build for that is code: our own components, our own data models, our own interfaces. How much of it your project needs becomes clear in the first conversation — often it is less than feared.
Open source: Shopware, WordPress, Astro
We work with open systems. Open source is not a matter of belief; it has four reasons that pay off in daily operation.
The licence does not belong to us. You can keep running the system if you change agency. Nobody can lock you out of your own website.
The source code is open. What the site does can be read. For a security review, for a handover, or for the question of why something works the way it does.
Security updates come from a large community, not from a single vendor — and they come quickly.
The entry cost is low. For a newly founded business that is the decisive point, and not only in the first year.
Which system fits depends on the project. WordPress for sites that are edited regularly and by several people. Shopware where the website and selling belong together. Astro where loading time and security come first — this website is built with it, serves static files and has no database that could be attacked.
Alongside those, we maintain systems we encounter at clients: WooCommerce, Ecwid, BigCommerce.
How a website project runs
A website project has four stages. How long each takes depends on scope — the order is always the same.
Analysis and scope. We look at what exists: the current site, its addresses, its content, the systems behind it. From that comes the scope — which pages carry over, which are dropped, which are new. This step determines the duration of the project more than anything that follows.
Build. Structure, design, development. You see a working version early rather than a result at the end. Feedback runs in rounds, not one item at a time.
Acceptance. Testing across devices and browsers, checking the forms, verifying the redirects from every old address. Only then do we switch over.
Go-live and handover. Domain, hosting and certificate are prepared before the switch, so the existing site stays reachable until the end. The handover includes an introduction on your own website — so that maintenance afterwards actually happens.
For the ONE24 relaunch these four stages fitted into fourteen days. Three days of analysis and setup, six of build and migration, three of acceptance with testing and campaign integration, and two for switching over with no downtime. That was possible because scope, content and domain access had been settled beforehand.
Built for people: accessibility, loading time, usability
A website is built for people, not for a score. Three things decide whether it holds up in daily use.
Accessibility. Sufficient contrast, keyboard operation, descriptions for images, a sensible heading structure. That helps more than people with a disability — it helps everyone standing in bright sunlight, holding something in one hand, or looking for something quickly. You can check how your current site stands with our accessibility check.
Loading time, measured on a phone. Not at a desk on fibre, but out and about. That is the difference between a site that feels good and one where you wait.
Usability. You get where you want to go without searching. It sounds obvious and still decides whether someone stays.
We check these three before go-live, not after.
And if a store belongs to it
Many projects start as a website with selling in the background — a range that should grow, or orders that currently arrive by email. That is not an exception; it is the normal case in our work.
Shopware, Shopify, WooCommerce and Ecwid can be combined with a site so that it remains one website for visitors. Where an ERP or inventory system is involved, that is the part we have specialised in.
Everything about it is on the page e-commerce.
Case studies
The relaunch for ONE24 — an existing website, fully migrated, switched over with no downtime.
The first website for Enziangarten garden centre — a newly founded business, an open-source system, training the team as part of the project.
The landing page for an Infinigate webinar — one page with one purpose, built around sign-ups.
Frequently asked questions
What does it cost to have a website built?
The effort is determined by scope, functionality and integration with existing systems. A site with five pages is a different proposition from a bilingual presence with a store and ERP integration. Once your requirements are clear, you receive a quotation for the specific project.
Can we maintain the website ourselves afterwards?
Yes, and we set the project up for it. The handover includes an introduction on your own website. What matters is that one person is named as responsible and a second can stand in — without that, maintenance tends to lapse regardless of the system.
What happens to our existing addresses?
Every old address receives a redirect to the new page that matches it in content. This is the part of a relaunch that decides whether the site is still found afterwards, and it belongs at the start of the project rather than the end.
Do you also continue with existing systems?
Yes. If your site runs on a system that is fundamentally sound, rebuilding part of it is often less expensive than starting over — and we tell you so even when it means less work for us.
What should your new website achieve?
Tell us briefly what you have in mind — we will tell you which system fits and where the effort lies.
Discuss a website project→