"How long will it take?" is usually the second question we get, right after price. The honest answer tends to annoy people: it depends far more on you than it does on us. A five-page site for a Perth trades business can be live in three weeks, or it can drag on for seven months — with the same designer doing the same amount of work. The difference is almost never the building. It's the waiting.
The short answer
For a typical small business website — roughly five to ten pages, no online shop, no booking system — plan on four to eight weeks from deposit to launch. A single landing page can be done in one to two weeks. A larger site with custom functionality, a proper blog, integrations or an online shop is more like eight to sixteen weeks. Those ranges assume two things: that you can turn feedback around within a couple of days, and that your content is mostly sorted. If neither is true, add weeks rather than days.
Where the time actually goes
It helps to see a project as stages rather than one long blob of "building". A normal small business site breaks down roughly like this.
Discovery and planning — about a week. Working out what the site needs to do, who it's talking to, what services get their own pages, and what a good enquiry actually looks like for you. Skipping this feels fast and costs you later.
Copy and content — one to three weeks. Writing the words, gathering photos, collecting logos, certifications, licence numbers and testimonials. This is the stage that blows out. More on that below.
Design — one to two weeks. Getting the look and structure of the key page types right, then applying that pattern across the rest.
Build — one to two weeks. Turning the design into a real, responsive, fast site with forms, tracking and the technical SEO basics in place.
Review and refinement — about a week. You go through it properly, we fix what's wrong, you check again. One or two solid rounds is normal. Six is a sign something went wrong earlier.
Launch — one to three days. Pointing the domain, setting up redirects from old pages, checking forms actually land in your inbox, connecting analytics and Search Console. Domain changes can take up to 48 hours to settle worldwide, so nobody should be promising you a same-hour switch.
Content is the bottleneck, almost every time
If a project runs late, there's a very good chance it's waiting on words and photos. Design and build have a clear finish line. Writing about your own business doesn't — there's always a better way to say it tomorrow.
The fix is to treat content as a task with a deadline, the same as anything else on the job list. Decide upfront who is actually writing it — you, us, or a mix — and put a date on it. If you're supplying it, a rough brain-dump you send this week beats a polished draft you send in six. We can shape messy notes. We can't shape nothing.
Photos are the other common hold-up. If you're booking a photographer, book them at the start of the project rather than the middle, because good ones in Perth are often a few weeks out. If you're not using one, tidy phone photos of real jobs, real staff and real vehicles will beat stock images every time.
What quietly adds weeks
Feedback by committee. Three people sending three sets of conflicting notes by text, email and phone call is the fastest way to lose a fortnight. Nominate one decision-maker who collects everyone's input and sends it once.
Scope that grows mid-build. "While we're at it, can we add a booking system?" is a fair question, but it's a new stage, not a tweak. Better to launch the core site and add it after.
Missing access. Nobody can remember who registered the domain, the old developer has stopped replying, or the hosting is under a former employee's email. Chase this down in week one, not launch week — it's the single most common cause of a last-minute delay.
Vague approval. "Yeah, looks good" followed two weeks later by "actually, can we change the whole homepage?" restarts a stage. If something feels off early, say so early.
How to make it genuinely faster
Some things speed a project up without cutting corners. Have your service list and pricing approach decided before design starts, because page structure follows content, not the other way around. Gather your logins, domain details, Google Business Profile access and analytics accounts in one document at the start. Book a standing 20-minute check-in each week instead of ad-hoc emails. And be blunt in feedback — "the hero headline doesn't say what we do" is more useful than "something feels off".
What doesn't speed things up: asking for a compressed timeline and then approving in your own time. A three-week build with a two-week approval gap is a five-week project. The calendar doesn't care whose fault it is.
Frequently asked questions
Can you build a website in a week?
A focused one-page site, yes, if the content is ready and you're available for same-day feedback. A full multi-page business site in a week usually means something has been skipped — normally strategy, copy, or testing. It's rarely worth it unless there's a genuine deadline like a trade show or a rebrand announcement.
Do I need all my content ready before we start?
No, but the closer you are, the faster it goes. What genuinely helps upfront is your service list, your logo files, any accreditations or licence numbers, and a handful of real photos. The words can be developed alongside the design.
What if I don't have professional photos?
Start without them. We can build with good placeholders and swap in real photography later, which is much better than stalling the whole project for a shoot. Just don't let "later" mean never — real photos of your own work are one of the strongest trust signals you have.
Does a faster build mean a worse website?
Not inherently. Fast projects are usually fast because the owner was decisive and the content was ready, which are good signs, not bad ones. The risk is when speed comes from skipping discovery or launching untested forms. Ask what's being left out, not just how quick it is.
How long after launch before it brings in leads?
If you're running Google Ads, you can have traffic on day one. For organic search, a new site typically needs a few months of being crawled, indexed and building relevance before you see steady movement, and competitive Perth terms take longer than niche ones. Anyone promising rankings in a fortnight is guessing.
What happens after launch — is that the end?
It shouldn't be. The first month or two after launch is when the useful data arrives: which pages people actually read, where they drop off, what they enquire about. Budget a little time to act on that. A website that never changes after launch is a brochure, not a growth tool.
If you're weighing up a website project and want a straight answer about what it would take for your business specifically — timeline included — we're happy to talk it through.