How long does a website take
The honest answer starts with "it depends", but it does not have to stop there. What it depends on can be listed, and most of it sits on your side of the table.
Most people assume the deadline on a website is set by how complicated the programming is. In practice development is rarely the bottleneck. Projects that run late almost never run late because something was hard to build; they run late because somebody is waiting, for text, for photographs, for the price of a service, for the one person who can approve a decision. This article separates the phases, shows where the time actually goes, and lists what you can have ready to shorten the whole thing.
Development rarely decides the deadline
Once the scope is agreed, the build itself is the most predictable part of the work. The number of pages is known, the features are listed, and the time needed to produce them can be estimated fairly closely. That is the part somebody who has done enough projects can put a number on without being far out.
Everything around it is what varies. How long the conversation about structure takes, how many rounds the design needs, when the photographs arrive, and whether a page nobody mentioned appears halfway through. Two projects of identical technical difficulty can finish a long way apart, and the difference is almost never in the code.
Four phases, and what each one costs you
The first phase is agreeing scope: what the site has to achieve, who it is for, which pages it needs and what content already exists. It is short if you know the answers, and it stretches when the conversation reveals that what the business actually offers has not been settled yet. The second is structure and then design, and it is the phase where the most changes happen, which is how it should be, because moving a block around is cheap and rebuilding a finished page is not.
The third phase is the build, and it runs evenly if the first two were closed properly. The fourth is delivery: testing on devices, checking speed and the SEO basics, putting it on the domain and handing it over. That last phase reliably takes longer than people expect, because it is the first time everything is seen together and the small things nobody noticed earlier get resolved.
Content is the critical path
If one thing decides the deadline, it is whether the text and photographs exist at the start. A site cannot be assembled around content that is not there. You can lay out empty boxes, but when the text finally arrives it turns out to be longer or shorter than the space left for it, and the layout gets done a second time.
The same goes for photographs. A photograph that does not exist cannot be optimised, and one you will "send tomorrow" rarely arrives tomorrow. This is not an argument for perfect content: a rough version of the text that exists beats a polished one still being written. A rough version can be shaped together, whereas a missing one can only be waited for.
What actually extends a deadline, and what gets blamed
The things that extend it have nothing to do with technique. It is unclear who makes the final call, so every round of changes passes through several people who disagree with each other. Content arrives in pieces. Something is added that was not in the agreement, which is fair enough but moves the date. Or the project depends on a third party: a booking system, a payment processor, somebody holding the existing domain who does not reply.
What usually gets blamed unfairly is the choice of technology. The difference between WordPress and a custom build is real, but it is smaller than the difference between a project with its content ready and one without. The same goes for page count: five more pages following the same pattern add very little, while one page that does something new adds far more than it looks like it should.
Why a short deadline is a warning
A deadline that sounds too short for what you described usually means one of two things. Either the other side understood a smaller project than you thought you were asking for, which you find out at handover. Or a template is planned with your content dropped into it, which is a legitimate product if you know that in advance and an unpleasant surprise if you do not.
More useful than the number itself is asking what it assumes about you. Ask by when you have to deliver text and photographs for that date to hold. A serious estimate always carries that condition, because nobody can promise a date that depends on materials they do not have yet. A deadline without that condition is not an estimate, it is a wish.
What to have ready before the start
- Text for the main pages, even a rough version we tidy up together
- Photographs at full size, your own rather than taken from the internet
- The logo in its original format, and your colours if you already have an identity
- Access to the domain and hosting, or at least the name of whoever holds them
- One person who makes the final call on changes
How a deadline actually gets shorter
You do not pick a shorter deadline, you remove the reasons for waiting. A project where the text and photographs are ready on day one, where it is clear who decides, and where the scope is closed before the build starts finishes considerably sooner than one of the same size that sorts all of that out along the way. If you are not sure yet how big your project is, that is a question a single conversation answers, and the estimate that comes out of it is worth something.