How long does it take to build a website?

Published estimates disagree sharply. Wix says a professionally built site may take two to five months; one Australian agency publishes four to ten weeks for a simple brochure site. The difference is not necessarily competence. One estimate may start after the words and design are approved; another includes planning, writing, photography, feedback and testing.

Before comparing promises, ask each provider to start and stop the same clock.

There are four timelines, not one

1. Time to choose a provider

Finding candidates, comparing quotes and signing an agreement happens before production. Allow longer if several people approve the purchase or if the job needs a specialist. A rushed choice can save a week and create months of difficult support.

2. Time to become ready

The provider needs decisions and material: services, prices or pricing factors, contact details, page list, words, photographs, legal information and access to existing accounts. If those inputs are missing, the project has started commercially but not practically.

3. Time to design, build and test

This is the period most advertised timelines describe. It includes page structure, visual design, development, content entry, mobile checks, form or checkout testing and revisions. A repeatable small-site process can compress it. New features and many approval stages expand it.

4. Time to be found

A website can be live and still absent from Google. Google says crawling can take a few days to a few weeks, and repeated indexing requests do not make it faster. Launch day and search visibility are different milestones.

Realistic planning ranges

These are broad planning ranges synthesised from current provider estimates and Pithy’s project experience. They are not a promise for an unseen project. A page count alone cannot reveal the work.

What actually causes the delay?

A project timeline behaves more like a queue than a stopwatch. Ten hours of work can occupy three weeks when every two-hour task waits two days for a decision.

The content does not exist

“Use what is on the old site” is not content approval. Old prices may be wrong, staff may have changed and services may no longer be offered. Someone still has to check every claim. Photography also needs selection, permission, cropping and useful captions or alternative text.

Feedback arrives in pieces

One person changes the heading on Monday, another questions the page structure on Wednesday, and a third introduces a new service on Friday. The designer cannot tell which decision is final. Nominate one person to combine comments and approve each stage.

The scope changes after work starts

Adding a paragraph is a change. Adding appointments, deposits, customer accounts or live stock is a different system. The provider should state the extra time and cost before accepting it. If the deadline cannot move, something else must leave the first release.

Existing systems need careful treatment

A redesign can take longer than a brand-new site because old URLs need redirects, analytics and Search Console need continuity, email must remain working, and valuable content cannot simply disappear. Deleting the old site quickly is not the same as replacing it safely.

A third party controls the next step

Domain access, payment approval, booking software, product feeds and account recovery can sit outside the designer’s control. Identify every external account at the start, who owns it and who can approve changes.

Can AI build the website in minutes?

AI can generate a plausible first draft in minutes. It cannot make unknown business decisions true. The owner still has to verify services, prices, locations, licence details, product claims, photographs and contact routes. Forms need real delivery tests. Shops need real test orders and refunds. Accessibility needs human judgement as well as automated checks.

Use AI speed to shorten blank-page work, not to skip accountability. “Generated” describes how the draft appeared. “Ready” means a customer can rely on it.

How a ten-business-day website can work

Pithy builds small-business websites live within ten business days. That is achievable because the product is deliberately narrow: a clear service site, one decision-maker, established layouts, ordinary features and prompt access to content. It is not a ten-business-day promise for a marketplace, membership system or unplanned rebrand.

If the material arrives on day five, it is not a ten-business-day build with a five-day delay. It is a build that became ready on day five. The agreement should say whether a missed client deadline moves the launch date.

Prepare this before the clock starts

• One outcome: what should a suitable customer do after visiting?
• One decision-maker: who gives the final answer when opinions differ?
• A page and feature list: include forms, bookings, payments and integrations.
• Verified business facts: services, service areas, hours, phone, email, address and required licence details.
• Usable content: approved words, original photos and permission to publish them.
• Account access: domain, hosting, email, analytics, Business Profile and any connected software.
• Review appointments: reserve time before the project starts rather than when feedback is already overdue.

If the deadline cannot move, reduce the first release

Keep the work that supports the first customer action. A new restaurant may need its location, opening date, menu, hours and booking method before it needs a history page. A trade business may need services, area, proof and a working enquiry route before it needs twenty project stories.

Do not save time by skipping form delivery, payment testing, mobile checks, redirects or account ownership. Those are launch conditions. Delay secondary pages, elaborate animation, unusual filters and speculative features instead.

Put these dates in the agreement

• the event that starts the delivery period;
• the date each party must supply content, access and feedback;
• how many review rounds are included;
• what pauses or moves the launch date;
• how new work changes the price and schedule;
• what must pass before launch;
• who monitors and fixes problems immediately afterwards.

Under Australian Consumer Law, covered services must be supplied within a reasonable time when no timeframe is agreed. If you do agree a date, put it and its dependencies in writing. “Approximately four weeks” without a start condition is difficult for both sides to use.

The useful question to ask instead

Do not ask only, “How fast can you build it?” Ask: “What must be true for this to launch on that date, what would move the date, and what would you remove first if time runs short?”

A credible provider will name dependencies and trade-offs. An impressive date with no conditions is not a plan.

Related guides: how much a website costs in Australia, 15 questions to ask a web designer, and choosing a DIY website builder.

Commercial disclosure: Pithy sells fixed-scope small-business websites with a ten-business-day delivery promise. This guide explains the conditions behind that promise and the cases that should take longer.