How Long Does It Take to Build a Website or Web App?

The honest answer is: it depends on the scope. But "it depends" doesn't help you much when you need to plan. So here we give you concrete timelines for each project type - and we also tell you what truly drives the duration. Because most delays don't happen during the coding; they happen before it and alongside it.

Realistic timelines by scope

As a rule of thumb, done properly and without constant back and forth:

• One-pager / landing page: around 1 to 2 weeks. A focused page with a clear structure, contact form and a clean mobile layout. The big chunk here is often the copywriting and image selection, not the build itself.
• Multi-page website with CMS: around 3 to 6 weeks. Several subpages, a content management system you can use to maintain content yourself, a blog, multiple languages or structured service pages. The range mainly depends on how many pages you really need and how ready your content is.
• Custom feature in an existing site: around 2 to 4 weeks. For example a booking flow, a configurator, a login area or a connection to a third-party system. The interface is the deciding factor here: is the external API well documented, or do we have to fight our way through?
• Web tool / SaaS dashboard: typically 6 weeks to several months. As soon as there are user accounts, roles, payments, databases and multiple views, you're no longer talking about a website but about software. That's a chapter of its own - more on that below.

What really drives the duration

Coding is rarely the bottleneck. These factors extend or shorten a project the most:

• Your content. Copy, logos, photos, product data. When it's ready, things move fast. When it isn't, the build often sits idle for days waiting on the one missing photo.
• Clarity about scope. A one-pager that grows into a multi-page site mid-project is no longer a one-pager. The clearer it is at the outset what's in and what's out, the more reliable the deadline.
• Number of feedback rounds. Two structured review loops are healthy. Ten small individual changes spread over weeks cost more time than the actual building.
• External systems. Payment providers, ERP, CRM, external APIs. Here you depend on the quality and availability of the other side - and that can't always be sped up.
• Approvals and decision-makers. When every colour has to pass three people, it's not the technology that's slow but the coordination.

Why a web app takes longer than a website

A website displays content. A web app processes data. That's a qualitative difference, not a gradual one. As soon as users log in, store data, pay or collaborate on something, topics come into play that aren't visible from the outside: permissions and roles, security, data protection, error handling, backups, test cases. It's exactly this invisible part that eats up the time - and exactly here that it's decided whether a tool holds up in real operation.

We know this from our own practice: we run seven of our own brands live in production - including an accessibility scanner, a cosmetics product portal with 177,000 products, a vehicle deal radar, a marine SaaS and an industrial marketplace. These systems run every day, not just as a demo. That's why we don't cost SaaS projects based on the first click-through prototype, but on what it truly takes to reach stable live operation.

How we make timelines plannable

To make a time estimate more than wishful thinking, we work with clear fixed-price tiers and a fixed scope rather than open-ended hourly budgets. That gives you two things: a predictable final price and a realistic delivery date. To put the order of magnitude into perspective: one-pagers run EUR 2,000-3,000, multi-page with CMS EUR 4,500-8,000, a single custom feature around EUR 9,000, and a larger tech or SaaS build, depending on depth, EUR 6,000-25,000.

A binding deadline always comes about in this order with us: lock down the scope, clarify content and interfaces, then name a date. An estimate before that clarification would be a guess - and guessed deadlines slip.

What you can do yourself to save time

• Prepare your content before the project starts - or tell us clearly that you'd like our help with the copywriting.
• Name one decision-maker who bundles the feedback instead of collecting three opinions separately.
• Say early what's absolutely needed for launch and what can be a phase-two addition. A lean, fast start almost always beats the grand solution six months out.

If you want to know which range your specific project falls into, you don't need a finished specification - a rough description is enough for us to give you an honest timeline.