Web development that loads, ranks and converts

A focused website goes live within a few weeks depending on scope, while complex web apps are planned in stages over several months. The timeline depends mainly on three factors: the amount of functionality, the availability of content such as copy and images, and how quickly decisions are made. A typical flow: first we clarify goals and structure, then the design takes shape, then implementation follows with regular intermediate versions you can test directly in the browser. For larger projects we define a first usable version that goes online early and build on it. You see progress instead of months of silence and can adjust priorities along the way. In my experience delays rarely come from the technology but from missing content, so I address that early. Describe your project and you will get a realistic estimate of the timeframe.

Yes, on request you get an editorial CMS that lets you update text, images and posts without a developer. I usually use Payload CMS for this: a modern open-source system with a clean interface that shows exactly the fields relevant to your content. No cluttered menus and no fear of accidentally breaking the layout, because design and content are cleanly separated. The handover includes a short introduction where we walk through typical tasks together: editing a page, creating a blog post, swapping images. After that your team can work independently. I stay available for changes to structure or functionality, but day-to-day editing is in your hands. Tell me which content you plan to update regularly and I will design the CMS around it.

Yes, privacy is designed in from the start rather than bolted on afterwards. In practice that means data-minimal integration of external services, fonts and scripts hosted locally instead of loaded from US servers, a clean consent solution where services genuinely require it, and hosting entirely in the EU if you want it. Often the cookie banner can be avoided altogether by skipping tracking services or using privacy-friendly alternatives, which improves the user experience as a bonus. Forms, newsletter integrations and analytics tools are also chosen so they can be operated on a legally sound basis. The final legal review of your privacy policy and legal notices belongs with a lawyer, and I provide the technical foundation for it. If you are unsure where your current site stands, we can look at it together.

The cost depends on scope, which is why I only quote a concrete figure after a short conversation. The main factors: the number and complexity of pages, fully custom design versus building on a proven foundation, CMS integration, multiple languages, connections to other systems and how much content needs to be created or migrated. A lean site with a few pages costs accordingly less than a portal with user accounts and booking logic. To keep the budget predictable I work in clearly cut stages: we start with what delivers the most value and extend deliberately later. Before the project starts you receive a written quote with a fixed scope, not open-ended hourly billing without a goal. Send me a short description of your plans and you will get an honest assessment of effort and sensible expansion stages.

It depends on the state of the existing website, and either can be the right call. A relaunch makes sense when the technical foundation is solid and it is mainly the design, content or structure that has aged: then we modernize selectively and keep what works, such as existing rankings and established editorial workflows. A rebuild is usually the better choice when the system is no longer maintained, security updates have stopped, the site performs poorly on mobile or every small change is disproportionately expensive. Either way, one thing is critical: existing visibility in search engines must not be lost. That is why an inventory of ranking pages and clean redirects from old to new URLs are a fixed part of my process. I will look at your current site without obligation and tell you honestly which route is more economical.

The technical SEO foundation is always included in my projects, while ongoing optimization is a separate topic. Every project ships with fast load times and good Core Web Vitals, clean semantic HTML, readable URLs, meta titles and descriptions, structured data, an XML sitemap and a mobile-optimized layout. That gives the site the prerequisites to rank well in the first place. Everything beyond that we discuss as needed: keyword research, content strategy, topic pages or a blog are separate work packages that stretch over months and need editorial input. I am transparent about what is inside the project scope and what is not, so there are no false expectations. If visibility is a central goal, we plan SEO as a fixed part of the project from the start, just bring it up.