How long does it take to build a business website? A typical one takes about six to twelve weeks to plan, design, build and launch when it is a straightforward service site with a clear page list. A larger site with more pages, integrations or custom features commonly needs three to six months. The biggest swing factor is usually not coding speed: it is how quickly content, feedback and approvals arrive.
Those ranges are planning guides, not promises. A one-page holding site can be live much faster, while a complex migration can take longer. What matters is knowing which kind of project you are actually starting.
Typical timelines by website type
Use these ranges to set expectations before you talk to a designer. They assume a professional build with discovery, copy and testing included, rather than a self-built page assembled over a weekend.
Simple brochure or service website
A small site with a home page, a handful of service pages, an about page and a contact page often fits within six to twelve weeks. It moves fastest when the services are settled, the photos exist and one person can approve the work. It slows down when the business is still deciding what it sells or where it works.
Growing business website
A site with many service pages, location content, case studies, booking tools or CRM forms usually sits around three to four months. There is more to plan and much more to check. Every extra form, integration and template adds testing time, even if it looks small on a sitemap.
Online store or custom build
Ecommerce, member areas, quoting tools and other custom functions can push a project into four to six months or beyond. Product data, payment options, shipping rules and stock workflows all need decisions. If the build replaces an existing store, migration and redirect planning add another layer.
The phases of a website build
Most projects pass through the same broad phases. Some overlap, but skipping one usually costs time later.
Discovery and planning
This is where you agree on the goal, audience, page list, features and responsibilities. It might take a week or two for a simple site. Rushing it feels efficient until the team discovers halfway through design that nobody agreed what the contact form must do.
Content and structure
Next comes the sitemap, page outlines and copy. This is often the slowest phase for small businesses, because the people who know the services best are also busy running the business. Copy written early gives the designer something real to design around.
Design
Design turns the structure into page layouts, usually starting with key templates such as the home page and a service page. Expect at least one round of feedback. Several rounds are normal when stakeholders see the site for the first time.
Development and content entry
The approved design becomes a working site on a staging environment. Pages are built, content is entered, forms are connected and any integrations are configured. On a simple site this can be a few weeks. On a store or custom project, it is often the longest phase.
Testing and launch
Before launch, the site is checked on phones, tablets and desktops, forms are submitted, links are tested and any old URLs are redirected. Then the domain is pointed to the new site and checks are repeated on the live version. Allow a week or two. This phase gets squeezed more than any other, and it shows.
What makes a website take longer
Few website projects run late because a developer typed slowly. The common causes are more ordinary.
Content arrives late. A designer can sketch a page without final copy, but cannot finish it. Missing photos, testimonials and service details stall the build.
Feedback comes from too many people. When several stakeholders send separate comments, the designer spends time reconciling them instead of building. One decision maker, with one consolidated list per review, keeps things moving.
The scope grows mid-project. Adding a booking system or ten new pages after design sign-off is a reasonable business decision, but it is a new piece of work with its own time cost.
Access is missing. Login details for the domain, hosting, analytics or the old site can hold up launch for days if nobody knows who holds them.
If a project does slip, our guide on what happens if your website project runs late covers your options.
How to keep your build on schedule
Start with a clear page list and a named approver. Gather what you can before kick-off: logo files, photos, service details and access to your current domain and hosting.
Ask your designer for a schedule with dates for each approval, not just a launch date. Then protect your review time like any other appointment. A two-day turnaround on feedback, held across the whole project, can save weeks.
Frequently asked questions
Can a website be built in a week?
A very small site can sometimes go live within a week if the content is ready and the design uses an existing template. You trade away discovery, custom design and thorough testing to get that speed, so it suits a temporary or starter site better than a main business website.
Does a website redesign take less time than a new build?
Not always. A redesign can reuse some content and structure, but it also needs URL mapping, redirects and checks that existing pages still perform. Treat it as a full project with an extra migration step.
Why do quotes from different designers list different timelines?
Each quote reflects a different scope, process and workload. One may include copywriting and testing while another assumes you supply content. Compare what each phase includes before comparing the end date.
When is a website actually finished?
Launch is the end of the build, not the end of the website. After it goes live, plan time for small fixes, analytics checks and content updates in the first few weeks.
Know your project before you set the date
Six to twelve weeks covers many small business websites. Bigger projects need longer, and the schedule depends on decisions as much as development. If you want a realistic timeline for your site, see how our website design and development projects run, or book a discovery call to scope it properly.
