Web Development Dübendorf.

A developed website starts at CHF 3'000, a single landing page at CHF 2'500 and a business website at CHF 5'000. Once you need more than a presence, the numbers change: complex web solutions begin at CHF 15'000. An MVP — the first working version of a web application — sits between CHF 15'000 and 25'000, and a complete platform or B2B portal considerably higher. The spread is not created by the number of pages but by the logic underneath: user roles, interfaces to systems you already run, the data model and real-time features drive the effort. Hosting and domain add roughly CHF 100 to 500 per year. Our project calculator gives you a first order of magnitude in a few minutes.

Web design answers how a website looks and feels: layout, typography, colour, the way people move through it. Web development answers how it works: the code that turns the design into something a browser can run, the data structure behind it, the interfaces to other systems and the maintainability over years. For a plain company presence the two collapse into one job and we deliver both from one hand. As soon as logic enters the picture — a login, roles, calculations, a shop, a connection to your ERP — the weight shifts clearly towards development: the design is finished in days, the build takes weeks. The rule of thumb: if your website mainly has to convince, you need web design; if it has to do something that does not exist off the shelf, you need web development.

We build with Next.js and React on the front end, in TypeScript throughout, and style with Tailwind CSS; on the back end we work with Node.js and PostgreSQL. That is deliberately a narrow, modern stack rather than a bit of everything — we want to be able to maintain every line we ship three years from now. Next.js provides server-side rendering and static site generation out of the box, which is decisive for discoverability: Google and AI systems see finished HTML instead of an empty page that JavaScript has to fill in first. TypeScript catches a substantial share of errors while we write them, not once they reach your customers. For a technically literate audience like the one in Dübendorf that argument lands — and this website is built on exactly that stack.

A website goes live in roughly two weeks — the normal case for a company presence when content and approvals arrive promptly. More involved projects follow different timelines: an MVP of a web application ships in six to twelve weeks, and a complete platform with back-end logic, user roles and integrations takes three to six months. We work in agile two-week sprints, so after each sprint you see working features rather than a status report. The biggest time sink, incidentally, is rarely the engineering — it is waiting for content and decisions. If you want to hold the pace, we agree before kick-off who signs things off on your side and where the material comes from.

Yes, and it happens regularly — usually when the original agency has become unreachable or the project has stalled technically. We start by reviewing the code, the dependencies and the hosting setup, then tell you honestly whether extending or rebuilding is the better commercial decision. That answer does not automatically favour a rebuild: a clean codebase with maintained dependencies is something we happily continue, even though we did not write it. What argues for a rebuild is outdated dependencies with security holes, a tangle of plugins where nothing can be changed without breaking something else, or an architecture that simply cannot support the feature you want. Not having access to the code is no obstacle, as long as you control the domain and the hosting.

The difference lies in where the HTML is produced. A purely client-side JavaScript application hands the browser what is effectively an empty page and assembles the content afterwards in the browser. Search engines can process that these days, but they do it late and unreliably — and many AI crawlers render no JavaScript at all, so they see nothing. Next.js renders the page on the server or generates it at build time, which means every crawler receives finished HTML in the very first response. Add the performance effect, which feeds straight into the Core Web Vitals: our benchmark is 100/100 PageSpeed. Together those two points are why we treat discoverability as a property of the architecture rather than as later optimisation.