Every agency answers this question with a range, and every client hears the bottom of it. That mismatch causes more friction than any design disagreement. The truth is that the build itself is fairly predictable: designers and developers work at a knowable pace. What is not predictable is how fast the copy arrives, how many people weigh in on round two, and whether the scope agreed in week one survives contact with week six. Here is what the calendar actually looks like.
Most US small business websites take six to twelve weeks from kickoff to launch. A simple five page brochure site can ship in three to four weeks. A twenty page site with custom templates and integrations runs twelve to sixteen. Content delays and slow feedback, not development, cause most overruns.
How long does a website really take?
Timelines scale with page count, how much of the design is custom, and whether anything has to talk to another system. Below are the ranges we see across the US market for small and mid sized businesses, assuming a competent team and a client who responds within a couple of days.
| Project type | Pages | Realistic timeline | Biggest risk to the date |
|---|---|---|---|
| Landing page or one pager | 1 | 1 to 2 weeks | Copy and offer not decided |
| Small brochure site | 5 to 8 | 3 to 6 weeks | Photography and content |
| Standard business site | 10 to 20 | 6 to 12 weeks | Approval chains and content volume |
| Larger marketing site | 25 to 60 | 12 to 20 weeks | Content migration and template sprawl |
| Ecommerce build | Catalog dependent | 10 to 20 weeks | Product data, shipping and tax setup |
| Site with custom functionality | Varies | 16 to 30 weeks | Integrations and testing cycles |
Two caveats. First, these are working timelines, not calendar guarantees: a two week client holiday in the middle is two weeks added, not absorbed. Second, a rush is possible on the smaller tiers and rarely possible on the larger ones, because you cannot parallelize a decision.
What happens week by week?
Take a twelve page business site on a ten week schedule as the model. Most projects follow this rhythm even when the labels differ.
- Week 1: discovery and sitemap. Goals, audience, competitors, what the site must do. Output is an agreed page list and a navigation structure. Content responsibilities are assigned here, which is the most important thing that happens all project.
- Weeks 2 to 3: content and wireframes. Page level outlines showing what goes where and in what order. Copy drafting starts in parallel. Design does not begin properly until the structure is settled.
- Weeks 3 to 5: design of key templates. Homepage, a service page and a conversion page. Two rounds of feedback, consolidated. Once these three are approved, the rest of the site inherits their decisions.
- Weeks 5 to 8: build. Templates get developed, made responsive and connected to the CMS. Real content goes in as it arrives. This is when a project either feels calm or turns into a scramble, depending entirely on whether the copy is ready.
- Week 8 to 9: quality assurance. Cross browser and cross device checks, form testing, analytics and conversion tracking, speed passes, accessibility review, redirect map if replacing an existing site.
- Week 9: client review. One consolidated round of fixes against a written list. Not a new design round.
- Week 10: launch and watch. Go live early in the week, never on a Friday. Recrawl, confirm tracking fires, monitor forms for real submissions rather than assuming they work.
Notice how much of that is not development. Roughly half the calendar is spent deciding and writing. Teams that treat those weeks as slack time are the teams whose projects run long.
We ask for the copy deck for the top five pages before design starts, even in rough form. Designing around real words instead of placeholder text kills an entire revision round later, because nobody discovers in week seven that the hero headline is forty words long. On a website design and development project this single habit saves more time than any tooling choice.
What actually causes delays?
Development rarely runs late on its own. Three things account for most slipped dates.
Content. Nobody wants to write fifteen pages of copy while running a business, so it gets postponed, and the build stalls behind it. This is the most common cause by a wide margin. It is also the most fixable: decide in week one whether your team writes, the agency writes, or you hire a writer, and price it accordingly.
Feedback loops. A round of feedback that takes eight days instead of two, repeated four times, adds nearly a month. Worse is contradictory feedback from several stakeholders at once, which forces the team to design by committee or wait for the tie to be broken. One named decision maker who collects internal opinions and delivers a single verdict is worth more than any project management tool.
Scope creep. Rarely a dramatic addition. It arrives as small requests: a blog after all, a team page with bios, a locations map, a newsletter popup, a second language. Each is a few hours. Together they are a fortnight nobody planned. The fix is not refusal, it is honesty about the trade: this can go in and the date moves by a week, or it goes in phase two.
Two smaller causes worth naming: waiting on third party access (hosting credentials, domain registrar, CRM keys) and photography, which almost always takes longer to arrange than anyone estimates.
What does the client control?
More than most clients realize. If you want the fast end of the range, these are yours to influence.
Name one decision maker before kickoff. Consolidate feedback into a single written list per round rather than a stream of emails. Commit to a response window, two business days is a fair standard, and say so out loud. Get content and photography moving in week one instead of week five. Gather access credentials early. And agree what is out of scope in writing, so that adding it later is a deliberate choice with a visible cost rather than a quiet argument.
Also be realistic about approval layers. If a project needs sign off from a founder, a marketing lead and an external brand consultant, that is not a two day feedback cycle no matter what the schedule says. Build that reality into the plan rather than pretending it away.
We put a dated content calendar in the proposal with the client's name against each item, and we flag the schedule the moment an item is three days late rather than at the end. Uncomfortable in week three, much better than a launch date quietly moving twice in week eight.
Can you go faster without wrecking it?
Yes, within limits. The reliable accelerators are narrowing scope to fewer templates, using an existing brand system rather than developing one, writing copy before design starts, and cutting the review to one consolidated round with a firm deadline. A five page site with decided copy and a clear brand can genuinely ship in three weeks.
The unreliable accelerator is adding people. A second designer on a small project mostly adds coordination. The other false economy is skipping quality assurance to hit a date. Launching with broken forms costs more than launching a week later, and it costs it in leads you never find out about. If a hard date exists (a trade show, a funding announcement, a seasonal push), the sensible move is to ship a strong subset on time and phase the rest, rather than ship everything half finished.
Why do two agencies quote different timelines for the same site?
Usually because they are quoting different work, not different speeds. One estimate assumes you supply finished copy and images. The other includes a writer, a photo shoot and a content audit of the old site. One assumes a template lightly adapted. The other assumes custom templates designed from scratch. Neither is dishonest, but they are not comparable until you make the assumptions explicit.
Capacity matters too. A studio with three projects starting the same week will schedule you differently to one with a free designer on Monday. Ask how many active projects the team is carrying and who specifically is assigned to yours. A short timeline from an overbooked team is a wish rather than a plan.
Then there is the revision policy. Two rounds included with a clear definition of a round produces a very different calendar to unlimited revisions, which sounds generous and reliably drags projects out for months. When comparing quotes, line up four things: who writes content, how many design rounds, what is in scope, and how many people from your side approve. Timelines that differ by a month usually differ on those, not on skill.
What should you ask before signing?
Ask who writes the content and when it is due. Ask how many design rounds are included and what happens on round three. Ask what the deployment and testing process looks like, and whether analytics and conversion tracking are part of the scope or an extra. Ask what specifically would push the date, and expect a straight answer rather than reassurance.
Then ask what happens after launch, because a live site is the start of the work rather than the end. The first ninety days are when you learn what the pages actually do, and where conversion optimization and a steady content plan turn a finished project into traffic and leads. Any agency that treats launch day as the finish line is answering the wrong question about time.
Frequently asked questions
How long does it take to build a small business website?
A five to eight page site usually takes three to six weeks from kickoff to launch. That assumes copy is ready or being drafted in parallel, logo and brand assets exist, and feedback returns within about two business days. Projects that stretch past eight weeks are almost always waiting on content or photography rather than on development work.
Can a website be built in a week?
A single landing page or a small template based site can ship in a week, but only under strict conditions: copy already written, images chosen, one approver, no integrations. Custom design across multiple templates cannot compress that far. Decisions and testing take the time they take, and skipping quality assurance to hit the date usually means launching with a broken form.
Why do website projects run late?
Three causes dominate. Content arrives late because writing fifteen pages while running a business is genuinely hard. Feedback stalls or arrives contradictory from several stakeholders. And small additions accumulate: a blog, a team page, a map, each a few hours until together they are a fortnight. Development itself is fairly predictable. Late projects are usually late on decisions, not on code.
How long does an ecommerce site take compared to a brochure site?
Expect ten to twenty weeks for a store against six to twelve for a comparable brochure site. The extra time is not design. It goes into product data and variants, shipping rules, tax configuration, payment setup and a much larger testing burden, since every checkout path has to be verified on every major device and browser before you take a real order.
What can I do to speed up my website project?
Five things help more than anything an agency can do. Have copy drafted before design starts. Name one decision maker. Send feedback as a single consolidated list per round rather than a stream of messages. Collect hosting, domain and CRM credentials in week one. And agree in writing what is out of scope, so later additions are a deliberate choice with a visible cost.
Should I launch everything at once or in phases?
Phase it whenever a fixed date is in play. Launching a strong core of pages on schedule and adding the rest over the following weeks beats shipping everything half finished. Search engines have no problem with a site that grows. Better still, real behavior on the first set of pages gives you evidence to shape the later ones instead of guessing at all of them at once.
The takeaway
Six to twelve weeks is the honest answer for most business sites, and roughly half of that time is spent on decisions and writing rather than design or code. That is good news, because it means the schedule is largely in your hands. Get the copy started in week one, name one approver, and treat scope changes as trades rather than favors. Projects that do those three things tend to land on the date they were given.