Skip to content
CactusLaunch

How Long Does It Take to Build a Business Website? A Real Schedule

Agencies quote eight to sixteen weeks. Builders say a weekend. Both numbers hide what actually consumes the time. Here is a day-by-day schedule for a real ten-page business site, the parts only you can supply, and why the same site takes months in one process and days in another.

Brian Simmons · Founder, CactusLaunch 6 min read
A wooden desk calendar with blank pages, a fine mechanical pencil, and a small potted cactus in soft window light

Ask five providers how long a business website takes and you’ll get answers from “a weekend” to “sixteen weeks,” and none of them will be lying. They are describing different processes applied to roughly the same amount of work.

The work itself is more bounded than the timelines suggest. Designing, writing, and building a five-to-ten-page business website is one to two weeks of skilled hours. What turns that into months is everything around the hours: waiting for decisions, waiting for content, waiting for feedback, waiting for the next person in the sequence. Here is what a real schedule looks like when the waiting is removed, what you need to have ready, and where the months go when they aren’t.

The short answer by type of build

BuildTypical durationWhat decides it
DIY on a builder (Wix, Squarespace)A weekend to several monthsYour available evenings, and how long you spend choosing templates
Freelancer template build2 – 8 weeksTheir queue, and how fast you send content
Productized custom build (fixed scope)7 days for ~5 pages; 10 – 14 days for ~10 pages with landing pages and tracking; 2 – 3 weeks with service/location architectureWhether your inputs are ready on day one
Traditional agency project8 – 16 weeksDiscovery, handoffs, and revision rounds
Custom systems (multi-location, integrations)4 – 12 weeksArchitecture and integration scope

The productized row is what we run, so the rest of this article shows that schedule in detail. If your provider quotes a different timeline, the day-by-day below is a useful lens for asking where their time goes.

A real schedule: ten pages, two landing pages, tracking

This is the GrowthStack™ shape — a ten-page site with two ad landing pages and conversion tracking — which is the most common build we do. Days are business days.

DayWhat happensWho is doing it
0You complete the intake form: offer, audience, services, differentiators, objections, proof, service area, existing assets. Access is shared (domain, hosting, old site, Business Profile).You (about 30 minutes)
1Kickoff conversation to clarify edges. Site map and page-by-page purpose confirmed. Migration crawl of the old site if there is one.Both, then us
2 – 4Copy and design produced together, page by page — headlines and layouts shaping each other. Imagery selected from your photos, curated stock, and concept visuals.Us
5 – 6Build: pages, forms with spam protection, thank-you routes, landing pages, structured data, sitemap, redirects mapped. Tracking events wired.Us
7One consolidated review: every stakeholder, one scheduled pass, all feedback together.You
8 – 9Revisions from the review round. Launch checklist run line by line: responsive layouts, links, forms tested from a phone, metadata, schema, tracking verified, redirects tested.Us
10Launch. Redirects live at the edge, staging blocks removed, sitemap submitted, forms re-tested on the live domain.Us, with you watching the first enquiry arrive
10 – 14Buffer for a second small revision pass or a migration with a large URL map.As needed

A five-page LaunchPad™ compresses the middle: about seven days from kickoff. An AuthorityBuild™ adds service and location architecture and an article engine, which is real additional writing, and lands at two to three weeks.

Notice what the schedule does not contain: a discovery phase, a wireframe approval, a “copy deck” waiting on you, and open-ended revision rounds. Each of those is a place where weeks hide. How to Launch a Premium Website in Days explains why each one was removed and what replaces it.

What only you can supply, and when

The schedule above holds when day zero actually happens on day zero. Here is the list, in order of how often its absence causes delay:

  1. Honest answers about the business. What you sell, to whom, why you win, what a lead is worth, what customers ask before buying. This is the intake form, and it replaces weeks of workshops. Vague answers produce vague sites.
  2. Access. Domain registrar, hosting or the current site’s admin, Google Business Profile, analytics, ad accounts. Chasing access is the most avoidable delay there is.
  3. Brand assets you own. Logo files (vector if you have them), any brand colours or fonts, and existing photography — of your work, your team, your premises. Phone photos from job sites are often your best asset.
  4. Proof you’re allowed to use. Reviews, credentials, licences, awards, project examples, before-and-afters with the customer’s consent.
  5. Availability for two moments: the kickoff conversation and the single review round. Not daily involvement, just those two.

What you do not need to supply: the copy. Projects that wait for client-written text are the ones that take four months, and clients are not copywriters and shouldn’t be. Copy written from your intake by the people building the site is both faster and better. How to Prepare Your Business for a Fast Website Launch is the full preparation guide.

Where the months actually go

If you have been quoted twelve weeks, here is roughly where they are:

  • Discovery (2 – 3 weeks). Workshops and a strategy document establishing what a structured intake captures in half an hour.
  • Wireframes and approvals (1 – 2 weeks). Grey boxes, a presentation, a wait for sign-off, a revision, another wait.
  • Design rounds (2 – 4 weeks). Homepage concepts, feedback from several people, reconciliation, more feedback.
  • Copy (anywhere from 1 week to forever). “We’ll send the text over.” This is where projects go to die. Content limbo is the single most common reason a website project quietly stops.
  • Development (2 – 3 weeks). Often the shortest phase, waiting on everything above.
  • QA and launch (1 – 2 weeks). Bug lists, another feedback round, a launch date that moves.

None of this improves the website. It ages it. Every week a better site isn’t live is a week of visitors judging you by the old one. And a project that takes three months usually launches a site that was designed for the business as it was three months ago.

What legitimately adds time

Fast doesn’t mean everything fits in a week. Some things genuinely take longer, and a provider who won’t say so is selling you a fantasy:

  • Migrations with large URL sets. Years of blog posts, hundreds of images, a plugin-generated tangle. The redesign SEO checklist is real work, and it is what protects your rankings.
  • Integrations. Scheduling systems, CRMs, patient or client portals, payment. Each one depends on a third party’s documentation and cooperation.
  • Multi-location architecture. Location templates, governance, per-location routing. Weeks, scoped as a system.
  • Photography shoots. Scheduling a photographer is calendar time, though it can run in parallel with the build using placeholders.
  • Legal and compliance review. Regulated industries need review cycles, and the schedule should include them rather than pretend they won’t happen.

The honest way to handle these is to name them in the launch plan with their own timelines, which is what a written plan is for.

How to hold your provider to a schedule

Ask three questions before signing:

  1. What do you need from me, and by when? A provider who can’t list it hasn’t planned the project.
  2. How many review rounds, and how are they run? “Unlimited revisions” is a timeline with no end.
  3. What is the launch date, in writing? With the scope and the price beside it.

That last question is the whole philosophy behind a flat-quoted launch plan: scope, timeline, and one number, agreed before day one. The packages page lists the typical timelines for each, and the cost guide explains what moves the number beside them.

Questions people ask

Can a good website really be built in a week?

A five-page site, yes, when the process is built for it — fixed scope, copy written by the builder from a structured intake, an established design system, and one review round. It cannot be built in a week if the week starts with an open question about what the site should be or ends waiting for text.

Why do agencies take so long?

Mostly because of how the work is organized. Discovery workshops, strategy decks, wireframes, design rounds, development, and QA happen in sequence, each waiting for the last, with days of queue time per hour of work. Add feedback rounds with several stakeholders and no deadline, and eight weeks becomes sixteen without anyone working slowly.

What delays a website project most often?

Copy that never arrives, followed by feedback from too many people with no deadline, followed by missing access — to the domain, the hosting, the old site, or the Business Profile. Solve those three before kickoff and most timelines hold.

Does a faster build mean lower quality?

Only when speed comes from skipping steps. When it comes from removing waiting, the same hours go into the work with less coordination overhead. A tight process is a quality tool; a long one mostly ages the site before it launches.

How long does a redesign with a migration take?

Add time for the URL map, redirects, and testing — typically a few days on top of the build for a small site, more for a large one with years of content. It is real work and it protects your rankings, so it belongs in the schedule rather than in the "we'll sort it after launch" pile.

This article is part of the website strategy & cost library. If it describes a problem you have, the service behind it is here: see packages & pricing.

Ready to launch yours properly?

Two minutes of form gets you a launch plan: exact scope, exact timeline, one flat quote.

Prefer to talk it through first? Use the chat button — a real person replies.