If you are wondering how long a website takes to build, the short answer is somewhere between two and twelve weeks, depending on the type of project. The longer answer is that design time is rarely what blows up the schedule.
I have worked on enough projects to hold a clear opinion: websites are not delayed by technical complexity, but by whatever is expected to arrive from outside.
Rough timelines by type of website
These ranges come from my own experience, not from any standard. They count from the moment I have everything I need to start, not from the day you decide to get a website.
One-page site or landing page
Two to three weeks. One message, one action, very little structure. This is the fastest case, provided the copy is clear.
Simple business website
Three to six weeks. Home, services, about, contact and little else. This is the most common case for freelancers and small businesses.
Redesign of an existing website
Also three to six weeks, though it depends on how much content survives. If the material already exists, you save time; if everything needs reorganising, you lose it.
Website with an online shop or custom features
Six to twelve weeks, sometimes more. Catalogue, payments, shipping, bookings or client areas all add testing, and preparing the data matters more than the design.
What stretches the timeline (and it is almost never the design)
In practice, a project stalls for four reasons, and none of them is technical.
- Copy that arrives late. Without real content, the design is built around filler, and it inevitably has to be redone once the real text shows up.
- Images that never arrive. Low-quality photos, logos in unusable formats, or "I will send them over" for three weeks running.
- Slow or scattered feedback. A review that takes ten days to come back halts everything that follows. If it also comes back from three people with three different opinions, the delay multiplies.
- Scope changes. "While we are at it, let us add a blog" is fine, but it is another project with its own timeline.
The cumulative effect
Each one-week wait looks harmless. Added together, they turn a four-week project into a two-month one. Nobody in particular is to blame: the client's calendar and the designer's simply do not line up.
How to speed things up from your side
The good news is that almost everything that shortens a project depends on you, and none of it requires technical knowledge.
- Have the copy ready before we start. It does not need to be perfect, but it does need to be real. I can help you organise it.
- Gather images and your logo in one folder. A few good ones beat many doubtful ones.
- Appoint one person to decide. One voice, one consolidated round of feedback.
- Reply within short windows. It does not have to be instant; two or three days per round already makes a difference.
- Freeze the scope. Anything that occurs to you halfway through, note it down for a second phase.
When you can go faster (and when you should not)
Some projects allow reasonable haste: a small site, with settled copy, a single point of contact and no unusual features. In those cases, compressing the calendar is possible without sacrificing quality.
What does not work is cutting the review phases to gain a few days. A website delivered quickly but loosely tends to cost more time afterwards, in corrections, copy that does not fit and images that look wrong on mobile. Saving one week at the start and losing three at the end is not saving anything.
It is also worth remembering that launching is not the finish line. After going live there is room for small adjustments, and it is better to plan for that than to insist everything be perfect on day one.
What I do so I am not the bottleneck
My side counts too. Before designing, I put in writing what the project includes, what I need from you and by when. I work in short phases with visible deliverables, so that feedback arrives early and is specific, rather than a general opinion on the "feel" of the whole site.
If a week passes and nothing arrives, I do not treat it as a drama: I point it out, recalculate the calendar and tell you the real effect on the delivery date. I would rather give an honest timeline than a pretty promise that breaks later.
A realistic timeline starts with a conversation
Any general figure is only a compass. The real timeline depends on your type of website, how much material you have and how much time you can give it. That is why I always settle it after seeing the project, never before.
If you would like to know how long yours would take, tell me what you need through the contact page and mention whether you already have copy and images. With that, I will give you a sensible estimate, no frills.
