Guide

How long does a website take?

How long does it realistically take from the first meeting to launch? It depends on the scope, of course. But there's a fairly clear framework, and a handful of things that can speed a project up a lot, or slow it down just as much.

8 min read

It's the most common question straight after price. Honestly, a simple site can be done in a couple of weeks, while a web shop or a booking system takes longer. The deadline depends far less on the technology than on the scope, the content and how quickly decisions get made. So let's look at how that works in practice and what you can do to make the project move faster.

In short

  • A brochure site is usually done in 2 to 4 weeks.
  • For a site with features such as booking or a gallery, allow 4 to 8 weeks.
  • A web shop or system takes 6 to 12 weeks, depending on scope.
  • What speeds things up most is text and photos that are ready, plus quick feedback.

Build time isn't a number you copy off a price list. It's more of a range, and it narrows as soon as we know exactly what the site has to do and how quickly you'll be able to take part. A project of the same size can be finished in three weeks, or it can stretch to two months. The difference is rarely in the code. So instead of a single number, we'll go through the phases, what stretches them and what you can do yourself to shorten the deadline.

The phases of a project

Almost every project goes through the same steps, whether we're building a simple site or a web shop. The only thing that changes is how long each step takes. Our order of work is also described in the process section, and here are the phases with rough timings.

1 · Conversation

We work out what you want to achieve, what the content is and who your users are. (a few days)

2 · Design

We put the look together and confirm the direction. (1 to 2 weeks)

3 · Development

We build the site and all its features. (1 to 4 weeks, sometimes more)

After development come two more short phases that are easy to forget. The first is review and refinement, when we go through the site together, fix the small things and check the copy. The second is launch and setup. That's when we move the site onto your domain, set up analytics and basic SEO, and check that everything works properly on a phone and on a computer. Those two phases usually take a few days, but do count them in if you're aiming at a specific date.

Realistic timelines by type of site

The easiest way to judge your own project is to put it into one of these groups. The ranges come from experience rather than a rulebook, and they shift with the number of pages and features. There's more on scope itself on the web development page.

2 to 4 weeks

Brochure site

Sole trader, small company, freelancer

A handful of pages: home, about, services, contact. The goal is to present the offer clearly and lead the visitor to an enquiry. It's the quickest, because there are no complex features.

4 to 8 weeks

Site with features

Restaurant, accommodation, salon, clinic

Gallery, booking or reservations, forms, more than one language. The more moving parts there are, the more time goes into design and into testing every step.

6 to 12 weeks

Web shop or system

Shop, catalogue, more advanced integrations

Products, payment, delivery, customer accounts. Most of the time goes into connecting the systems and checking that every possible purchase scenario works.

Say you run a guesthouse on the coast and want a gallery, a reservation enquiry and the site in Croatian and English. That realistically sits somewhere in the middle of the second range. If all you need is a good presentation with contact details, the same guesthouse easily drops into the first. It's the features, one by one, that move the deadline, not the design itself. With a web shop the same goes for the price, which we broke down in how much a web shop costs.

What speeds the work up and what slows it down

When a project runs late, the cause is almost always on the same list. The good news is that you can control most of it yourself.

Speeds up ⚡Slows down 🐢
Content (text, images)Ready on timeWaited on during the build
FeedbackFast and clearSlow or contradictory
ScopeClearly definedChanges along the way
Decision makingOne person signs offSeveral opinions, no agreement
FeaturesStandardPlenty of custom integrations

You'll notice that four of the five rows are about people, not technology. Things most often get stuck on content. The design is practically finished, and the site is still waiting on the text about your services or the photos of the space. Decision making comes second. When feedback arrives from several people who don't agree with each other, every round of revisions takes twice as long.

The fastest projects are the ones where the content is ready, the scope is clear and decisions get made quickly. Technology rarely holds things up. Communication, sadly, can.

How to make your project go faster

You don't need to know anything about building websites to shorten the deadline. It's enough to get a few things ready before we start.

  • Get the text and photos ready in advance. Or tell us right at the start that we should produce them, so nobody is waiting on materials later.
  • Appoint one person for decisions and feedback. The whole team can make suggestions, but the final “yes” should come from one person.
  • Start with a clear, realistic scope. Anything that isn't essential for the first launch goes into the phase after it, as a growth plan.
  • Reply in one round. Gather all your notes on a draft and send them in one go, rather than drip-feeding them over several days.

It sounds simple, because it is. Projects that stick to these four rules regularly finish in the lower part of their range. With sole traders, we focus on getting to a working site as quickly as possible, without unnecessary steps. And if you're still weighing up whether you need a site at all, read does my small business need a website.

A deadline tied to a date: season, opening, campaign

Plenty of projects come with a hard deadline. The tourist season starts, a venue opens, or a campaign goes out on a set date. For tours and transfers that usually means the booking system has to be finished before June, not in June. In those cases we don't start from the question of how long it takes. We start from the target date and plan backwards. From the launch date we work out when development has to be done, when the design has to be done and when we need your materials. That way you can see straight away whether the deadline is doable at full scope, or whether we publish a narrower first version and add the extras after launch. The second option is often the smartest move. The site is online on time, and it keeps growing without the pressure.

Need a site by a particular date, say for the season or an opening? Tell us the date through the contact form and we'll plan backwards from it. For how scope shapes the investment, read the guide How much does a website cost?

FAQ

Frequently asked

How long does a simple website take?

A brochure site for a sole trader or a small company is usually finished in 2 to 4 weeks. The deadline depends mostly on whether the text and photos are ready and how quickly feedback comes back. If the content is prepared up front, you land at the lower end.

How long does a web shop or a site with booking take?

A web shop, a booking system or a site with custom integrations usually takes 6 to 12 weeks. The reason isn't the design itself, but the number of features, connecting payments or reservations, and testing every step before launch.

What slows a website build down the most?

Usually content and decisions. A project stalls when it's waiting on text or photos, when feedback is late or contradicts itself, and when the scope changes mid-build. The technical side is rarely the bottleneck.

Can you speed the work up if we need it by a specific date?

Yes. Tell us the target date right at the start and we'll plan backwards from it. What makes the biggest difference is content that's ready, one person in charge of decisions, and a clear scope where the extras wait for the phase after launch.

Do we need the text and the photos finished before we start?

It helps if they're ready, but it isn't a condition. If you don't have the content, tell us and we'll take on the copywriting and photo preparation. What matters is agreeing on it at the start, so the build doesn't stall halfway while we wait for materials.

What happens after a website goes live?

Launch isn't the end. There's a short stretch of small refinements, the analytics setup and basic SEO, plus maintenance if you want it. Most of that goes quickly because the main work is already done, but it's worth allowing for it in the plan.

Have a deadline in mind?

Tell us the date you're aiming for, and we'll give you a realistic answer on whether we can make it.

Start a project
Start a project