Web Design Adelaide
Honest timelines

How Long Does It Take to Build a Website?

The short version for Australia: a freelancer building a small business site usually quotes 2 to 4 weeks and lands between 4 and 10. An agency doing custom design for the same site quotes 6 to 8 weeks and commonly runs 10 to 16. Add ecommerce, a booking system or an integration and you are looking at 3 to 6 months. The uncomfortable part of that answer is that hardly any of it is design or code time. On a 5 to 8 page business website the production work is measured in days. Everything else is waiting, and most of the waiting happens on the client side of the fence, which is not what anyone wants to hear while their build sits quiet.

Freelance, small site
2 to 4 weeks quoted, 4 to 10 typical
Agency, custom design
6 to 8 weeks quoted, 10 to 16 typical
Ecommerce or integrations
3 to 6 months, often longer

The ranges you will actually be quoted

Timelines in this industry are quoted as production time and experienced as elapsed time, and those are 2 different numbers. Production time is how many working days the build takes when everything arrives on schedule. Elapsed time is what shows up on your calendar. The gap between them is the entire subject of this page.

A template site you build yourself. Squarespace, Wix or a Shopify theme, realistically 1 to 3 weeks of evenings for something small. The tool is almost never the bottleneck. Writing the words and finding photographs that are not stock images is the bottleneck. People who abandon a do-it-yourself build tend to abandon it at the copy stage, not the design stage.

A freelance web designer. Commonly quoted at 2 to 4 weeks for 5 to 8 pages, commonly delivered in 4 to 10. That is usually not dishonesty. It is how a 1-person business smooths its income: your project is fitted around other paid work, in a queue you cannot see. Progress arrives in bursts, and a quiet fortnight in the middle is normal rather than alarming.

An agency doing custom design. Quoted at 6 to 8 weeks, commonly 10 to 16 elapsed. That process typically runs discovery, sitemap, wireframes, 2 or 3 design concepts, a revision round on the chosen concept, build, testing, then launch. Every one of those stages ends in a handoff, and every handoff is a place your project can sit still while it waits on a reply.

Ecommerce, memberships and integrations. Plan on 3 to 6 months once a payment gateway, freight rules, product data, stock sync or a booking system that has to talk to something else is involved. Product data alone eats weeks. A catalogue of 400 items with variants, descriptions, images and freight dimensions is a data project wearing a web design costume.

Migrations, multi-language and anything enterprise. Between 6 and 18 months, where the timeline is set by content auditing, approvals and redirect mapping rather than by anything visual.

Where the weeks actually go

Ask any Australian web designer where projects stall and the same list comes back. It is worth reading as a client, because 4 of the 5 items are inside your control.

Content. This is the big one and it is not close. Copy for 6 pages, service descriptions, prices you are actually willing to publish, a logo file that is not a screenshot, photographs of the real business rather than a stock office, the trading name and ABN for the footer, and a decision about what the About page says. Writing 6 pages of copy is a genuine piece of work, and it is almost always handed to the busiest person in the business as a side task. A build waiting on copy can sit for a month without a single hour of design time being lost.

Approvals with no limit on them. Unbounded revision is the quiet killer. Round 3 reopens a question round 1 had settled. A change that takes 20 minutes to make costs 4 days of calendar, because it has to be requested, queued, made, deployed and reviewed. Multiply that across 5 rounds and 3 pages and the month is gone, with nobody having done anything wrong.

More than 1 person deciding. A business partner who sees the design for the first time in week 7 will have opinions, and those opinions arrive after the work they affect is already built. Each extra approver adds delay, and it does not add it in a straight line.

Third party access. The domain is registered to a former employee. DNS sits with an IT provider who replies in 3 working days. Email will break if the DNS is changed carelessly, so nobody wants to touch it. The booking system needs an API key from an account nobody can log into. This category is boring, unglamorous and routinely costs a fortnight.

The queue you cannot see. Your build sits behind other builds. No proposal has ever said so in writing, and it is the honest reason a job with 15 hours of work in it takes 9 weeks to appear.

Notice what is not on that list. Design is not on it. Code is not on it. On a standard small business website the design and build work is genuinely a handful of days. The other 9 weeks are handoffs, decisions and waiting.

Stuck in a normal build, or being strung along?

Both look identical from your inbox, which is why this is so hard to judge from the outside. A designer quietly working through round 5 of unpaid revisions and a designer who took the deposit and moved on to something else both go silent. So do not try to read the silence. Send 4 written questions and read the answers instead.

  1. “Please send the staging link exactly as it stands today, however unfinished.”
  2. “What is the single item blocking progress right now, and is it with you or with me?”
  3. “What are you still waiting on from me? Please list it.”
  4. “What is the date of the next milestone?” Not the launch date. The next one.

A build that is merely slow answers all 4 in a paragraph. The staging link exists and is ugly, which is exactly what a work in progress should look like. The blocker is named, and it is usually your photographs. The outstanding list is short and specific. The next milestone has a date on it.

A build that has actually stopped answers none of them. There is no staging URL at all after 5 or 6 weeks. The blocker cannot be named, only described as still working through it. The list of things needed from you changes every time you ask. Replies stretch past 5 working days with no explanation, and each one mentions a new problem you have never heard of before. Real progress produces boring updates.

What to do when a build has stalled

In this order, because the order matters.

Check who owns the domain.A WHOIS lookup takes a minute. The registrant should be your business, not the person building the site. Everything else here is recoverable. A domain sitting in someone else’s name at the moment a relationship sours is the one that costs real money and real months.

Ask for access in writing. Registrar, hosting, analytics, and any account opened in your business name. It is a reasonable request and a reasonable supplier hands them over.

Put a date on it. Send 1 email stating what you need, the date you need it by, and what happens if it does not arrive. Not a threat, just a stated position. A written position of that kind is often what gets a stalled build moving again when another polite follow-up would not.

Keep the content whatever happens. If you decide to start again, the copy, the photographs and the page structure you already produced are the expensive half and they come with you. The build is the cheap half. That is worth knowing before you write off the whole exercise as wasted.

None of that is legal advice, and if money is genuinely in dispute you should get some. It is simply the order that loses the least time.

How 5 working days is possible, and what it asks of you

Everything above explains the structure we run, because it was built against exactly those 5 delays. Sites here go live in 5 working days, and that is written into the agreement as guarantee 01: Live in 5 working days, or you do not pay a monthly fee for the first 12 months. It is worth being precise about why that is possible, because the reason is not that the work happens faster.

The clock starts at intake, not at signing. It starts once your content is in and the brief is answered, which is an honest place to put it, because that is where the real dependency has always been. If it takes you 3 weeks to gather content, the build takes 5 working days and the project takes a month. Better to say that at the start than let you discover it in week 4.

Scope is fixed before the clock starts. You are not buying a blank canvas and 3 concepts to choose between. What the site contains, what each page has to do, and the technical layer underneath it are settled first, which is what makes a short build survivable rather than reckless.

Approvals run in 2 written rounds. Not unlimited. This is the single largest compression on the list and it is also the one that asks the most of you. Round 1 is the substantive pass, round 2 is corrections. It only works because the scope was agreed before anything was designed.

Nothing waits on a diary slot. Guarantee 05 is: Everything by email. You stay in your business. We do the build. That sounds like a small thing until you count the 3-day gap that opens every time 2 calendars have to meet before a decision can be made.

The technical layer is not re-decided each time. Hosting, DNS, analytics, form delivery, page structure, schema and sitemaps are settled once and deployed the same way on every build, so none of that is discovered halfway through yours.

So the 5 days is real, and it has a price that is not measured in money. You supply content on time, and you give feedback inside 2 written rounds.

Who a 5-day build does not suit

Said plainly, because it saves everybody time.

  • You have not started on content and do not intend to. The clock cannot start, and pretending otherwise just moves the disappointment later.
  • Approval sits with 4 people and 2 of them are hard to reach. Consensus is slower than any build.
  • You are selling 400 products with variants, freight rules and a stock sync. That is a data project measured in months, and it is not this.
  • You are mid-rebrand with no logo, no photographs and no settled trading name. Fix the brand first, then the site takes care of itself.
  • You want 3 design concepts, an art-directed brand site and revisions without a limit. That is a legitimate thing to buy from an Adelaide studio. It is a different purchase.
  • You would rather talk it through at length than write it down. Guarantee 05 means everything runs by email, and that suits some people and not others.

If one of those is you, a longer engagement with a studio is the right call and we will say so rather than take the build and miss the date.

The honest total for your build

For most Adelaide businesses the real answer to how long a website takes is: as long as it takes you to get your content together, plus 5 working days. That first number is the one worth attacking, and it is the one nobody else will tell you owns the schedule.

If you want the detail underneath the timeline, what actually gets built in those 5 days covers scope and inclusions, and the sites already live on this structure are all clickable. The commercial side sits on the pricing page: nothing to pay upfront for the build, then $297 a month including GST, which is $3,564 in total across the committed 12-month term. And because the schedule question is usually asked alongside the money question, what a build is worth paying for in the Adelaide market runs the same honest survey across price rather than time.

Website build timelines: common questions

How long does it take to build a website?
In Australia, a small business website of 5 to 8 pages is usually quoted at 2 to 4 weeks by a freelancer and 6 to 8 weeks by an agency doing custom design, and commonly takes longer than either. Add ecommerce, a booking system or an integration and 3 to 6 months is realistic. The production work itself on a standard business site is a handful of days. The rest of the calendar is content, approvals and handoffs.
Why do website builds take so long?
Almost never because of design or code. The 5 usual causes are waiting on content and photographs, revision rounds with no limit on them, more than 1 person who has to approve, third party access such as domain and DNS logins, and the queue of other projects sitting ahead of yours. Of those 5, 4 sit on the client side of the fence, which is why the same designer can deliver in 2 weeks for a business that has its content ready and 4 months for a business that does not.
How long should a small business website take?
If the content is ready and there is 1 decision-maker, a 5 to 8 page business site is a matter of days of production work. Once a site that size passes about 6 weeks on the calendar, the delay is being driven by something other than the build, and it is fair to ask in writing what that something is.
Is it normal for a web designer to go quiet during a build?
A quiet week is normal, particularly with a freelancer fitting your job around other work. Past 5 working days with no reply is worth chasing in writing. Ask for the staging link exactly as it stands, the single item currently blocking progress, and the date of the next milestone. A build that is merely slow answers all 3 in a paragraph. A build that has stopped answers none of them.
How can a website be built in 5 working days?
By removing the waits rather than rushing the work. The 5-day clock starts at intake, once the content is in and the brief is answered. Scope is agreed before the clock starts, approvals run in 2 written rounds instead of unlimited ones, nothing sits waiting on a diary slot because everything runs by email, and the technical layer (hosting, DNS, analytics, form delivery, page structure and schema) is settled once rather than re-decided on every project.
What do I need to have ready before a website build starts?
Copy for each page or the raw material to shape it from, photographs of the actual business, a logo file that is not a screenshot, your services and any prices you are willing to publish, the trading name and ABN for the footer, and access to the domain. Gathering that is usually the longest single part of the whole project, so it is worth starting before you engage anybody.

Get a date, in writing, before you commit to anything

Send us what your business does and what you already have ready. You get a written answer on what your build would actually involve, an honest read on how long your content will take to gather, and no obligation after it.

Everything runs by email and through the client portal. No calls, no pitch deck.

CallFree review