How long does a website project take?

Most brochure or service websites take several weeks once scope is clear. The silent timeline killer is content: photos, copy approvals and stakeholder feedback. Platforms get the blame; unfinished service lists usually move the date.

This article is about calendar risk from the client side. Our process is the delivery sequence. For a new marketing site see custom website design; for an existing site that needs a new experience, see website redesign.

Direct answer

A project with a written scope, a named decision-maker and content that is ready — or actively being written — can move through discovery, design, build and launch without drama. An undecided offer, a committee, and assets in a camera roll cannot. The stack changes the shape of the build. It does not abolish copy and sign-off. There is no honest universal week-count that fits a clinic, a retailer and a tradie business. What is honest is the sequence and the stalls you can prevent.

The sequence (and what each stage needs from you)

Treat these as gates, not as overlapping wishes.

Discovery and scope

Goals, audience, constraints, integrations and success measures. You leave with a written scope: templates, pages, what you will supply, what we will write or design, and what is out of bounds.

This stage is short when you arrive with examples, a service list and access to brand files. It stretches when the business is still deciding what it sells, or when two directors hold different homepages in their heads. Scope fights that happen here are cheaper than scope fights in the browser.

Structure and design

Information architecture, key templates and a visual system. This is where UX and UI earn their keep: enquiry paths, proof, and mobile forms, not decoration first.

Your job is to comment on whether the structure matches how you sell — not to pixel-nudge every heading on the first pass. Collect feedback into one voice. Parallel email threads from five staff are how design weeks multiply.

Build

Implementation on the agreed stack: content model, forms, SEO foundations, responsive QA. If the CMS is still a live debate, you are not in build yet. Settle Webflow versus WordPress or Shopify versus WooCommerce in discovery.

Build goes smoothly when content can be poured into real fields. Build stutters when we are still inventing page types because a new service appeared in a meeting.

Launch

Redirects if you have an existing site, analytics events, final content check, DNS and go-live support. Launch is a checklist. A preferred Friday before a long weekend is not a checklist.

Support

Optional maintenance for updates and small improvements. Leftover project scope does not belong in care-plan hours; name it as leftover scope.

Where projects actually stall

Content. The common delay. Someone must write or approve services, about copy, legal pages, and alt text. Photos must be selected, cropped and actually depict the business. If you need help producing copy, that is a scoped workstream, not a surprise.

Feedback without an owner. “Loop in the team” with no deadline and no single approver produces silence, then a flood of contradictory notes. Name one decision-maker. Give others a window to comment to that person.

Late integrations. Booking tools, CRMs and payment providers that appear after design will reopen templates. List them in discovery or accept a variation.

Migration ghosts. Website migration adds URL inventory, redirects and data cleaning. Pretending a redesign is “just a new look” while changing platform is how launch week becomes archaeology.

Legal and claims. Regulated industries — medical, legal, financial — need extra review. Book that reviewer at the start, not the day before DNS changes.

Operations data. Hospitality and retail sites stall when nobody owns hours or SKUs. A Fremantle venue that changes its menu weekly needs an editor plan, not a one-off PDF.

Hope-based dates. “Live before the expo” only works if scope shrinks to match. A date without a reduced template list is a wish.

Content readiness checklist

You are ready to move when most of this exists or has a named author and date:

• Final service or product list (not “we will add a few”)
• Who the site is for, in a sentence
• Logo files and any brand rules that are real
• Photos you have permission to use
• Current domain, hosting and DNS access if you already have a site
• List of URLs to keep or redirect
• Integrations with account access
• One approver who will actually reply

If half the list is blank, discovery should include a content plan. Skipping that plan does not make the project faster. It hides the delay until design is waiting.

Feedback cycles that do not melt the calendar

Agree the rules in the kickoff, not after the first PDF.

• One consolidated round per stage (structure, visual system, staging)
• Comments in the agreed tool, not a mix of SMS and hallway notes
• A response window, and what happens if it expires (we proceed on last approved, or we pause)
• New pages after sign-off are variations, not “quick adds”

Pausing is healthier than pretending. A paused project with a recorded decision is easier to restart than a zombie project where everyone is “waiting on someone”.

Launch is a checklist, not a date wish

Before go-live, someone must confirm:

• Staging signed off by the named approver
• Forms deliver to the right inbox or CRM, including auto-replies
• Redirects tested for important old URLs
• Analytics and conversion events fire
• 404 and privacy pages exist
• CMS logins issued, with roles that match who may edit
• SSL, DNS and email implications understood (changing DNS can disturb mail if you are careless)
• A rollback idea if a critical integration fails

Do not wipe URLs that already bring enquiries. Migration and redesign can run together, but they should appear as two workstreams so the calendar is honest. A landing page for a single offer can ship earlier than the whole site — provided everyone knows it is a slice.

What actually shortens a project

Not “working evenings”. These do:

• Arriving with examples you like and examples you reject
• Supplying content in the structure of the templates, not a 40-page Word dump with no headings
• Making decisions once
• Limiting unique templates to what you will maintain
• Keeping platform debates in discovery
• Treating cost drivers and timeline as the same conversation: extra templates cost money and weeks

Clarity beats ambition: covering a real service area and making quotes easy — a common brief for operators around Joondalup — is faster than a site that tries to be a magazine, a shop and a recruiting brochure at once. Our work shows finished shape, not a promise that every project takes the same time.

Next step

If you are really asking “can this be done before X?”, contact us with that date, the current URL, whether content exists, the service list, and the person who will approve copy. We will plan to the date with reduced scope, or say the date and scope are incompatible. Lock sequence and owners in the process. If budget is the open question, start with how much a website costs in Perth so scope and calendar are discussed together.