How long does a website take?
From idea to launch, how long does it realistically take? It depends on the scope, but there is a clear framework and a handful of things that speed a project up (or slow it right down).
The question that comes 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 is set less by the technology than by the scope, the content and the speed of decisions. Here is what that looks like in practice, and what you can do to make the project move faster.
In short
- Brochure site: usually 2–4 weeks.
- Site with features (booking, gallery): 4–8 weeks.
- Web shop or system: 6–12 weeks, depending on scope.
- The biggest accelerator: text and photos ready, and fast feedback.
Build time is not a fixed number off a price list. It is closer to a range that narrows the moment two things become clear: what exactly the site has to do, and how quickly you will take part in the process. The same size of project can wrap up in three weeks or stretch to two months, and the difference is rarely in the code. So instead of a single number we look at the phases, the factors that stretch them, and the concrete moves that shorten the deadline from your side.
The phases of a project
Almost every project goes through the same steps, whether we are building a simple site or a web shop. All that changes is how long each step lasts. You can see our order on the process section, and here is how the phases look in terms of time.
1 · Conversation
We understand the goal, the content and the users. (a few days)
2 · Design
We shape the look and confirm the direction. (1–2 weeks)
3 · Development
We build the site and the features. (1–4+ weeks)
Two more short phases follow development, and they are easy to forget. The first is review and refinement: we walk through the site together, fix the small things and check the copy. The second is launch and setup, where we move the site onto your domain, put analytics and basic SEO in place, and check that everything works on a phone and on a computer. Those two phases usually take a few days, but they have to be counted in when you are working towards a specific date.
Realistic timelines by type of site
The best way to judge your own project is to sort it into one of these groups. The ranges come from experience rather than from a rulebook, and they shift with the number of pages and features. A closer breakdown of scope itself is on the web development page.
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 to an enquiry. The fastest category, because there are no complex features.
Site with features
Restaurant, accommodation, salon, clinic
Gallery, booking or reservations, forms, more than one language. More moving parts means more time on design and on testing every single step.
Web shop or system
Shop, catalogue, more advanced integrations
Products, payment, delivery, customer accounts. Most of the time goes on connecting the systems and checking that every purchase scenario works.
A real example: a guesthouse on the coast that wants a gallery, a reservation enquiry and the site in Croatian and English realistically sits in the middle of the second range. The same guesthouse with nothing but a good presentation and a contact page drops easily into the first. It is the features, not the design, that move the deadline. With a web shop the same holds 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 somewhere on the same list. The good news is that most of it sits under your control.
| Speeds up ⚡ | Slows down 🐢 | |
|---|---|---|
| Content (text, images) | Ready on time | Waited on mid build |
| Feedback | Fast and clear | Slow or contradictory |
| Scope | Clearly defined | Changes along the way |
| Decision making | One person signs off | Several opinions, no agreement |
| Features | Standard | Plenty of custom integrations |
You will notice that four of the five rows are about people, not about technology. Late content is the most common reason a project stalls: the design looks finished, but the site is waiting on the text about the services or the photos of the space. Decision making is second. When feedback arrives from several people who do not 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 the decisions are quick. Technology rarely slows things down. Communication does.
How to make your project go faster
You do not need to know anything about building websites to shorten the deadline. A few things prepared before we start are enough.
- Get the text and photos ready in advance, or tell us at the start that we should produce them, so nothing is waiting on materials later.
- Appoint one person for decisions and feedback. The team can put forward suggestions, but sign-off should run through a single person.
- Start with a clear, realistic scope. Anything not essential for the first launch belongs in the phase after it, as a growth plan.
- Reply in one round. Gather all your notes on a draft and send them together, instead of drip feeding them over several days.
It sounds simple because it is. Projects that respect these four rules regularly land in the lower part of their range. With sole traders we put the emphasis on reaching a working site fast, without unnecessary steps in between. And if you are still weighing up whether you need a site at all, there is does my small business need a website.
A deadline tied to a date: season, opening, campaign
Plenty of projects carry a hard deadline: the start of the tourist season, the opening of a venue, or a campaign with a date on it. For tours and transfers that usually means the booking system has to be finished before June, not in June. In those cases we do not 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 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. That is often the smartest move: the site is online on time, and it keeps growing without the pressure.
Need a site by a fixed deadline (a season, an opening)? Tell us the date on the contact form and we will plan backwards from it. For more on how scope shapes the investment, read the guide How much does a website cost?
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 the photos are ready, and on how quickly feedback comes back. When the content is prepared up front, you land at the lower end of that range.
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 is not the design itself but the number of features, the connection to payments or reservations, and the testing of every step before launch.
What slows a website build down the most?
Usually not the technology but the content and the decisions. A project stalls when it is waiting on text or photos, when feedback is late or contradictory, 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 at the start and we plan backwards from it. The biggest difference comes from content that is ready, one person responsible for decisions, and a clearly defined scope with the extras left for the phase after launch.
Do we need the text and the photos finished before we start?
It helps if they are ready, but it is not a condition. If you do not have the content, tell us and we take on the copywriting and the photo preparation. What matters is agreeing on that at the start, so waiting on materials does not stop the build halfway through.
What happens after a website goes live?
Launch is not the end. A short stretch of small refinements follows, along with the analytics setup and basic SEO, plus maintenance if you want it. We move through most of those steps quickly because the main work is already done, but it is worth allowing for them in the plan.
Have a deadline in mind?
Tell us the date you are aiming for and we will give you a realistic read on whether it is doable.
Start a project