How a web project works - from idea to launch

Many clients having a website or web tool built for the first time share the same worry: they don't know what to expect, how long it will take, or what they need to contribute themselves. That uncertainty is understandable, because a web project is teamwork - even if most of the work sits with us. Here we walk you through, step by step, how a project unfolds from the first idea to launch, and where we need you.

Phase 1: Clarification and quote

It starts with a conversation, not a requirements document. You don't need to know which technology you need - that's our job. You describe what the site or tool should achieve for you: who the target audience is, what should happen in the end (an enquiry, a booking, a sale, internal work), and whether there are examples you like.

From that conversation comes a clear fixed price. We don't work with open-ended hourly budgets, but with defined tiers - from a one-pager (EUR 2,000-3,000) through a multi-page site with CMS (EUR 4,500-8,000) to a tech or SaaS build (EUR 6,000-25,000). You know what it costs from the very start.

Phase 2: Concept and structure

Before anything is designed, we define the structure: which pages there are, which content belongs where, and how a visitor finds their way to the goal. For a tool or dashboard, this is where we clarify the core functions and the data flow.

This phase prevents expensive rework later. A few hours of thinking about the structure save days of corrections down the line. From you, we mainly need feedback and decisions here - not a finished concept.

Phase 3: Design and implementation

Now the visible part takes shape. We build the layout, implement it technically, and bring it to life. In this phase, most of the work happens on our side, but there are two things we need from you:

• Content: text, images, logo, product data. If you don't have finished copy, we'll tell you early on - we often help with the writing or structure your bullet points. But content is the most common reason projects get delayed.
• Access: the domain, any existing hosting details, and access to accounts such as Google, payment providers, or shipping services, if these are being integrated.

We show you work in progress, so you're not surprised only at the end. Revisions are normal and built into the plan.

Phase 4: Testing and refinement

Before anything goes live, it gets tested - on mobile, in the browser, with real clicks through every feature. Forms have to arrive, payments have to work, load times have to be right. This is also where you review everything once more from your perspective: is the copy correct, is anything missing, does the flow feel right.

For larger tools and SaaS builds, this phase takes longer, because more can go wrong. We know this from our own experience: we run seven of our own brands live in production - from an accessibility scanner and a product portal with over 177,000 entries to a marine SaaS. These systems run every day, and that's how you learn what really matters before a launch.

Phase 5: Launch and handover

At launch, we go live with the site on your domain, set up SSL, and make sure everything is reachable. You receive the access credentials and a short briefing on how to maintain content yourself - provided a CMS is included.

A launch is not a goodbye. Search engines need weeks to index a new site properly, and small things only surface in real-world use. What makes sense afterwards in terms of maintenance or expansion, we discuss honestly - not every project needs an expensive maintenance contract.

What you realistically need to contribute

So you can prepare, here are the essentials at a glance:

• A clear vision of the goal - not of the technology.
• Content, or the willingness to develop it with us.
• Timely decisions and feedback at the right points.
• Access to the domain, accounts, and services.

The most common cause of delay isn't the technology - it's missing content or feedback that doesn't come. Those who are quick and clear here get their site live considerably sooner.

How long does it all take?

An honest range: a one-pager can be up in one to two weeks if the content is ready. A larger site with a CMS usually takes several weeks, and a tech or SaaS build runs over weeks to months, depending on the scope of functionality. The technology is rarely the bottleneck - coordination is. That's exactly why we keep the phases clear and the communication short.