In this note 7 sections
How long does it take to build a website? For a typical 5 to 10 page small business site, built properly by a professional, plan on five to seven weeks from the kickoff call to launch. A one-page site can be done in one to three weeks. A larger site with a store or online booking usually takes two to three months. Those are honest numbers, but they hide the part nobody puts in the quote: the design and build are rarely what make a project slow. Waiting is.
Below: timelines by type of site and by phase, the four places projects stall, and what to do before kickoff to land at the short end of the range.
How long does it take to build a website? Timelines by site type
The answer depends far more on what the site has to do than on how it looks. These ranges come from our own projects and from the proposals business owners bring us to review, not from an industry survey.
| Type of site | Typical time from kickoff to launch | What pushes it to the long end |
|---|---|---|
| One-page site or landing page | 1 to 3 weeks | Copy not written, ad tracking or form integrations, more than one approver |
| 5 to 10 page small business site | 5 to 7 weeks | Content late, several rounds of design feedback, booking or quote tools |
| Redesign of an existing small site | 3 to 8 weeks | Content being rewritten, a large number of old URLs to map and redirect |
| Larger site with e-commerce or bookings | 8 to 14 weeks | Product data and photos, shipping and tax setup, payment approval, staff training |
One-page sites and landing pages
A single page with a headline, a few sections, a form and your phone number is quick to build. It is not always quick to write, because one page still has to explain what you do, for whom, and why someone should call you instead of the next result. A landing page for a Google Ads campaign also needs tracking set up and tested, or you are paying for clicks you can't measure.
The 5 to 10 page small business site
This is the most common project we build: home, about, a handful of service pages, contact, maybe a service area page or two. On our pricing page you will see 4 to 5 weeks of delivery for a Launch site and 4 to 6 for a Business site. That is the window for our side of the work. Counted from the kickoff call to the day the site is live, including the time you spend writing, reviewing and approving, most of our marketing sites ship in five to seven weeks.
Redesigns with a migration
A redesign can move faster than a new build because a lot of the raw material exists: the services, the photos, the testimonials, the pages that already rank. Our website redesign projects for small sites usually take three to five weeks for that reason. What stretches them is an old site with years of blog posts, location pages and PDFs, because every one of those URLs needs a decision and a redirect. That process deserves its own post, and it has one: how to redesign without losing your Google rankings.
Bigger sites, stores and booking
E-commerce and booking projects take longer for reasons that have little to do with design. Someone enters every product with photos, variants and descriptions. Shipping zones and sales tax (GST, HST or PST depending on where you ship) get set up and checked. A payment processor approves your account on its schedule, not yours. Then come real test orders, refund and shipping policies, and training for whoever processes orders. A clinic or salon booking site has its own version: services, durations, staff calendars, deposits and reminders. None of it is hard. All of it takes days.
The web design process, phase by phase
Here is what a typical six-week project looks like for a 5 to 10 page site. Phases overlap, and the content phase runs alongside design, which is why the total is shorter than adding up each phase.
1. Discovery (about a week)
A kickoff call, then a few days of homework on our side: what a good lead looks like for you, which services make you the most money, who you compete with, and which current pages already bring in traffic. The output is a sitemap (the list of pages and what each one is for) and a dated list of everything we need from you.
This is also the week to sort out access: your domain registrar, your current host, Google Analytics, Search Console and your Google Business Profile. More on why that matters below.
2. Content (weeks 1 to 3, sometimes much longer)
Copy, photos, team bios, testimonials, service details, prices if you publish them. If you are writing the copy yourself, this is the phase that decides your launch date. A clear service page is not a paragraph you dash off between jobs. It answers what the service includes, what it costs or how it is priced, how long it takes, which areas you cover and what happens after someone calls. Our guide to writing website copy that sells walks through it page by page.
We design with real content wherever we can. A layout built around placeholder text tends to break when the real words arrive, and fixing that costs a second round of design.
3. Design (about two weeks)
Usually the homepage first, then the templates for inner pages: a service page, about, contact. The number of revision rounds shapes the schedule, since each round is a few days of your time and a few of the designer's. Our Launch plan includes one round and Business three or more. Whoever you hire, ask before you start.
4. Build (about two weeks)
Development, the content management system, forms, click-to-call links, booking or quote tools, speed work, basic SEO setup (titles, descriptions, structured data, a sitemap) and redirects from old URLs. It is the most predictable phase because it is mostly in the builder's hands. It slips when content arrives mid-build and pages have to be reworked.
5. Review and testing (about a week)
You review the site on a staging link, on your own phone, and ideally hand it to a few people who have never seen it. That last part is cheap and effective. Jakob Nielsen's long-standing finding at Nielsen Norman Group is that testing with five users found about 85 per cent of the usability problems in his studies. Ask three to five customers or friends to find your price for a service and send you a message through the form, and watch where they hesitate.
6. Launch (a day, plus a week of watching)
On launch day we point the domain at the new site, confirm HTTPS, submit the sitemap in Search Console, test every form and phone link on the live domain and take a backup. Our website launch checklist has the full list. Then we watch Search Console and form submissions for the first week, because problems that never showed up on staging tend to show up in the first few days.
Being live is not the same as being found. Google says that after you request indexing, crawling can take anywhere from a few days to a few weeks, and that requesting a recrawl of the same URL more than once won't speed it up.
Where website projects actually stall
When a six-week project turns into a three-month project, it is almost never because the code was hard. These are the four delays we see over and over, roughly in order of how often they happen.
Content from the client
The pattern goes like this. At kickoff, everyone agrees the owner should write the service pages, because nobody knows the work better. Then the phones get busy and "I'll get to it this weekend" happens four weekends in a row, while design waits for real words or goes ahead with placeholders and gets redone later.
The fix is not willpower. It is deciding, before kickoff, who writes each page and by when. If you know you won't get to it, pay for copywriting. It usually costs less than the weeks it saves, and a site that launches in May instead of August earns two extra months of leads.
Feedback that arrives in pieces
Feedback that trickles in by email, text and voicemail is slow to collect, and the second message often contradicts the first. Vague feedback is slow too. "Can it feel more premium?" takes a meeting to decode. "The hero photo looks like stock; use the Tuscany kitchen instead" takes ten minutes.
Ask your designer to set one place for feedback (a shared document or comments on the staging site) and agree on a turnaround for each round, such as three business days. Then collect everything into one list before you send it.
A decision maker who shows up late
Say an HR consultancy has two partners. One runs the project. The other sees the site for the first time at review, two weeks before launch, and doesn't like the direction. Now design restarts, and the build waits.
Anyone with the power to say no should be in the kickoff call and should approve the homepage design before the build starts. That includes the business partner, the office manager who will edit the site, and, for regulated professions, whoever checks your advertising against your college's or law society's rules.
Domain and DNS access
This is the one that stops a finished site from going live. The domain was registered years ago by a nephew, a former employee or the last web designer, and the account's recovery email belongs to someone who left in 2019.
To launch, you don't have to move your domain anywhere. You need someone who can log in to the account that controls its DNS records and change them. If you're not sure who that is, our website ownership checklist shows how to find out and how to get access back. If the domain does need to move registrars, plan ahead: under ICANN's Transfer Policy, a registrar can refuse to transfer a .com within 60 days of its registration or a previous transfer, and the old registrar has up to five calendar days to respond to a transfer request. Changing nameservers is faster, but Cloudflare's own documentation says to allow up to 24 hours for your registrar to update them, and to turn off DNSSEC at the registrar first or the domain can become unreachable.
The quieter risk is email. If your email runs through the same domain, the mail records (MX, SPF and DKIM) have to be copied over exactly when DNS moves, or your inbox goes silent on launch day. A careful developer checks this before touching anything. Ask yours how they handle it.
Smaller delays worth planning for
- Photography. A photo shoot needs a dry day, a clean job site and a free afternoon. In Calgary, that can mean waiting for the snow to melt.
- Seasonal timing. Launching a landscaping site in mid-May or an HVAC site during the first cold snap means nobody has time to review anything. Aim for your quiet months.
What actually speeds a website project up
Most of what shortens a timeline happens before the kickoff call. Here is what to gather.
| Have this ready | Why it saves time |
|---|---|
| A list of your services, ranked by how much you want more of each | Decides the sitemap and the homepage in one conversation |
| Draft copy, even rough, for each service | Gives design real content and cuts the longest wait |
| 20 to 40 real photos of your work, team and premises | Avoids stock photos and a second design pass |
| Three to five customer testimonials you have permission to use | Proof is the section most often left empty at review |
| Logins for your domain registrar, host, Google Analytics and Search Console | Prevents the launch-week scramble |
| The name of the one person who signs off | Stops design from restarting at review |
| Two or three competitor or peer sites you like, and why | Shortens the first design round |
A few habits help once the project is running:
- Block review time in your calendar on the dates in the schedule. A three-day review window that turns into ten days moves the launch date by a week.
- Launch the core, then add. Get the homepage, service pages and contact page live first. Location pages, a blog or a resources section can follow a month later.
- Use fewer page templates. Ten service pages that share one layout are faster to design and build than ten unique ones, and they are easier for you to edit later.
Some things don't help, even though they seem like they should. More people on the project usually means more opinions. Skipping review to hit a date moves the problems to launch week. And starting design before you have decided what you sell, and to whom, guarantees a second round.
How to tell if a quoted timeline is realistic
A timeline in a proposal tells you a lot about the work behind it. One week for a custom ten-page site means a template, or no testing, or both. Six months for five pages usually means you are in a long queue, or the project has no one driving it.
A trustworthy timeline has a start date, milestones (design approval, build complete, review, launch) and dates for what you owe. It also says what happens if you are late. We put our schedule in writing before we start and tell you exactly what we need, and when, so nothing stalls. If you are comparing providers, our guide on how to choose a web design company in Calgary has the questions to ask about process and timing, and our breakdown of what a website costs in Canada covers what should be in the scope.
Sources
- Ask Google to recrawl your URLs Google Search Central
- Site moves with URL changes Google Search Central
- Transfer Policy ICANN
- Change your nameservers (Full setup) Cloudflare Docs
- Why You Only Need to Test with 5 Users Nielsen Norman Group