“How long does it take to build a website?” usually comes right after “how much will it cost?”, and often for the same reason: there is a date in the calendar. A grand opening, a new service, a trade show, a funding deadline. This guide is for small businesses, clinics, non-profits and founders in Cambridge, Kitchener-Waterloo, Guelph and across Ontario who want a realistic timeline before they hire anyone. I will give you typical ranges, walk through what happens each week, and be honest about the part most people underestimate: the work on your side.
How long does it take to build a website? Typical timelines
The honest answer depends on two things: what you are building, and who is building it. A five-page site for a new bookkeeping practice and an online booking system for a swim school are both “a website”, but they are very different projects. Here are the ranges I would use for planning.
| Type of project | Typical timeline | What sets the pace |
|---|---|---|
| DIY website builder | A weekend to a few weeks | How much time you can give it around running the business |
| Starter site, 3–5 pages (solo developer) | 1–2 weeks | Content being ready and quick design feedback |
| Business site, 6–10 pages (solo developer) | 2–4 weeks | Number of page layouts, integrations, content |
| Similar site through an agency | 2–4 months (estimate) | More people, meetings and approval rounds |
| Custom web app or booking system | 4–8 weeks to several months | Features, user roles, payments and data migration |
These numbers cover the whole project, not just the coding: the first call, the written scope, design, build, testing, launch and hand-off. You can see the packages they come from on the services and pricing page, and if budget is your next question, my guide to what a website costs in Ontario covers that side.
Calendar time is not working time
A “two-week” site is not eighty hours of non-stop work. It is a few days of design, a few days of building and testing, and gaps in between where you review, write and approve things. Most of the variation between projects lives in those gaps.
What happens, week by week
Every developer runs projects a little differently, but the stages are much the same. Here is how a typical business site runs with me. The five-step process on my services page has the same stages in short form.
Days 1–3: discovery and scope
A call about your business, your customers and what the site needs to do, then a written scope with a fixed quote and a timeline. This is the step that prevents most delays later, because everyone agrees on the pages, features and content before anything is designed.
Week 1: structure and design
Wireframes first (simple page sketches that show what goes where), then the visual design in your brand. You review, I adjust. One or two rounds is normal. Five rounds usually means the scope or the decision-maker was not clear.
Weeks 1–3: build and content
The site is built on a private staging link, a working copy only you and I can see, so you can click through it on your own phone as it takes shape. Your content goes in as it arrives. Accessibility, search basics and speed are built in here rather than patched on at the end.
Final week: testing and launch
Checking forms, phones, tablets, keyboard navigation and page speed; setting up analytics and the sitemap; and pointing your domain at the new site. If you are replacing an old site, this is also when redirects go in so old links and search rankings are not lost. Changes to a domain can take anywhere from a few minutes to a day or two to reach everyone, so I never plan a launch for the last possible hour.
What slows a website project down
In my experience, projects rarely run late because the code was hard. They run late because something the project needs is sitting in someone’s inbox. These are the usual culprits, roughly in order of how often I see them.
- Content that is not ready. Page copy, service descriptions, team bios and photos are the single biggest cause of delay. Writing about your own business is harder than it looks, and it always comes second to serving customers.
- Slow or scattered feedback. A design that waits a week for comments adds a week to the project. Feedback from three people who disagree can add more.
- Missing logins. The domain, the old hosting, Google Business Profile, the booking tool. If nobody knows who holds them, launch stalls. My post on who owns your website explains how to check before you start.
- Scope that grows mid-project. “While you are in there, could it also take payments?” is a reasonable request, but it is a new feature with its own design, build and testing time.
- Migrating an old site. Moving years of pages, blog posts and links takes planning. The WordPress migration guide covers what that involves and why redirects matter.
- Third-party approvals. Payment processors, booking platforms and some industry directories have their own review times that nobody on the project controls.
The one-week rule
A useful rule of thumb: every time the project waits on you for a week, the launch date moves by about a week. Developers fill gaps with other clients’ work, so time lost in the middle of a project is rarely made up at the end.
How to get your website built faster
You do not need to rush the developer to get a faster project. You need to remove the waiting. Most of this list is free, and all of it can be done before the first design is drawn.
Before the project starts
- Name one person who can approve designs and content, and give them a couple of hours a week.
- Write a rough draft of each page, even in point form. A developer or copywriter can polish it; nobody can invent it.
- Gather your logo, brand colours and the photos you want to use, or book a photographer early.
- Find the logins for your domain, current hosting, email and Google Business Profile.
- List the must-have features separately from the nice-to-haves, so the first version can launch on time.
- Tell your developer about any fixed dates up front, including holidays when you will be away.
The nice-to-have list matters more than it looks. Launching a solid first version and adding the extras a month later is almost always faster, and cheaper, than holding everything until it is perfect. If you are still comparing people to build it, my guide on how to choose a web developer includes the questions to ask about timelines.
Why web apps and booking systems take longer
A brochure site shows information. A web app does things: it takes bookings, stores customer accounts, handles payments, sends reminders and gives your staff an admin area. Each of those has to be designed, built and tested against real situations, such as two people booking the last spot at the same moment, or a customer who wants a refund.
That is why custom apps usually take 4–8 weeks at the very least, and grow from there. For a real example, the swim-school booking platform on my work page, with parent accounts, payments and an admin panel, took about two months to build. If you are weighing an off-the-shelf tool against something custom, start with choosing an online booking system; often a ready-made tool gets you running in days.
Moving existing data
If customers, bookings or records live in spreadsheets today, budget time for cleaning and importing them. It is easy to forget and hard to rush, because mistakes end up in front of your customers.
Planning around a launch date
If you have a date you cannot move, work backwards from it. Take the timeline for your type of project, add a week of buffer for testing and last-minute changes, and add the time you need to write content. That gives you the latest sensible start date. If it has already passed, it is better to shrink the first version than to squeeze the testing.
A few other things worth knowing when you plan:
- Launching is not the same as being found. Search engines can take days to weeks to notice and rank a new site. If the date matters for marketing, launch a little early.
- Avoid Friday-afternoon launches. Launch early in the week so any problem is fixed while everyone is around.
- Plan for the month after. Real customers find things testing did not. Every project I build includes thirty days of post-launch fixes for that reason.
If you have a date in mind and want to know whether it is realistic, tell me about your project and I will give you an honest answer, even if that answer is a simpler tool you can set up yourself.
Frequently asked questions
How long does it take to build a small business website?
With a solo developer, a 3–5 page site usually takes one to two weeks and a 6–10 page site two to four weeks, including design, testing and launch. Content readiness is the biggest variable.
Why do agencies take longer than freelancers?
Agencies usually involve more people, such as account managers, designers and developers, and more meetings and approval rounds. That adds coordination time, not necessarily better results.
Can a website be built in a week?
A small, focused site can be, if the content, photos and logins are ready on day one and one person can approve things quickly. Larger sites and anything with bookings or payments need longer.
How long does a website redesign take compared to a new site?
Often a little longer, because existing pages, links and search rankings have to be mapped and redirected. Plan an extra week or so for a site with a lot of existing content.


