How long a website actually takes

Timelines for small-business websites are quoted as durations and delivered as sequences of waiting. The build time is rarely the constraint. What decides the calendar is how quickly decisions are made and how quickly material arrives, and both of those sit with the client.

Any supplier quoting a duration is quoting a working duration — the time required if content arrives on schedule, feedback is consolidated, and access is granted when asked. That is a reasonable way to quote. It is an unreasonable way to plan, because the assumptions inside it are usually the parts that fail.

What shapes a website development timeline

Duration scales with three things, roughly in this order.

Page count and how different the pages are. Twenty pages built from four repeating patterns is a smaller job than eight pages that are each unique. Ask how many distinct page designs are in scope rather than how many pages.

Functionality. A site that presents information and captures enquiries is bounded work. A site that takes payments, manages stock, handles bookings against real availability, or connects to a system the business already runs is not bounded in the same way, because part of the estimate depends on how the other system behaves — which nobody knows until they are inside it.

Whether content exists. A project with finished text and usable photographs on day one behaves completely differently from one where both are still to be produced. This single factor moves the calendar more than platform choice ever does.

Rebuilds add a fourth: existing addresses have to be mapped to new ones, and existing content has to be migrated. That work is invisible in a mockup and unavoidable in a schedule.

The five things that actually make a project timeline slip

Content that does not arrive. The most common cause by a distance. Writing service pages requires the business to decide what it says about itself, and that decision has usually never been made in writing. If the words are not going to be written internally, buy them — website copywriting exists for exactly this constraint, and buying it at scoping is cheaper than buying it after the project has been idle for a month.

Approval by committee. Every additional stakeholder added as an approver adds a round trip and increases the chance of contradictory feedback, which cannot be actioned and has to be resolved before work resumes. Nominate one person who can approve on behalf of the business, and give the other stakeholders a consultation window that closes.

Scope added mid-build. A page added after the structure is settled is not one page. It has to be designed, fitted into navigation, written and linked from wherever it belongs. Additions are legitimate and often correct; they are simply not free of time, and a schedule that absorbs them silently was never accurate.

Third-party access. Domain registrars, hosting accounts, analytics properties, payment gateways, and the booking or accounting system the site must connect to. Access requests routinely take longer than the work they unblock, particularly when the credentials were held by somebody who has left. Assemble them during scoping, not during build.

The launch window nobody booked. Launch needs a date agreed in advance, with the decision-maker available and no trading peak, audit, holiday or campaign sitting on top of it. Projects finish and then sit unlaunched for weeks because the only person who can say yes is away.

What to ask at discovery instead of “how long”

Duration questions get optimistic answers. Structural questions, asked at discovery before scope is locked, get useful ones.

• What has to be in your hands before the clock starts, and in what format.
• How many revision rounds are included, and what happens after them.
• What is the longest you can wait for feedback before the project is paused and rescheduled.
• Which parts of this estimate are fixed and which depend on something outside your control.
• If content is late by a month, does the project resume where it stopped or re-enter the queue.

That last question is the one that surprises people. Suppliers run several projects concurrently. A project that goes quiet loses its slot, and returning to it is not instantaneous. A written pause-and-resume clause is worth more than a confident number, and it belongs in the agreement — see web design contracts in Australia.

Sequence and dependencies matter more than duration

Some stages can overlap and some cannot. Photography can be commissioned while structure is being decided. Build cannot meaningfully begin before structure is settled, and content cannot be finalised before the pages it belongs to exist — these are dependencies between phases, not arbitrary ordering. A schedule that shows every stage overlapping every other is a marketing document.

The practical consequence: start the slow, client-owned items first. Text, photographs, and account access are the three things a supplier cannot produce alone, and they are the three that determine whether the quoted duration bears any relation to the actual one. A Gantt chart with a milestone at the end of each phase is the usual way a supplier presents this visually, but the tasks and dependencies underneath the chart matter more than the chart itself — a beautifully rendered Gantt chart built on an optimistic content-arrival assumption is still an optimistic plan. Project management discipline here is mostly about naming who owns each task, not about the software used to draw the timeline.

Common questions about website timelines

How long does it take to build a website? The build time is rarely the real constraint. What decides the calendar is how quickly decisions are made and how quickly content and access arrive — and both sit with the client. A supplier’s quoted duration is a working duration: the time required if content arrives on schedule and feedback is consolidated, which are usually the assumptions that fail.

What makes a website project take longer? Three things, in order: page count and how different the pages are (distinct designs, not raw page count); functionality such as payments, stock, bookings or connecting to an existing system, which is not bounded work; and whether the content exists — finished text and usable photos on day one moves the calendar more than platform choice ever does.

Timelines and money

A longer project is not automatically a more expensive one, and a quick one is not automatically cheaper. Price follows scope and complexity, not calendar time — with one exception, which is compressed delivery. Work moved ahead of other commitments generally attracts a premium rate, and it should be quoted as a line item with GST stated, not absorbed into a headline figure. What actually drives the number is covered on what moves the figure in a quote, and the way durations are bundled into fixed offerings is covered on website design packages.