GuidesTimelines
How long does it take to build a professional business website?
Most small-business sites take four to nine weeks. The build is rarely what makes a project run long — waiting on content and feedback is.
Short answer
A straightforward 5–8 page small-business website takes 3 to 5 weeks. A larger 10–20 page marketing site takes 5 to 9 weeks. E-commerce runs 6 to 14 weeks. Those assume content is ready and feedback comes back within a few days; the two most common causes of delay are unwritten copy and slow review cycles.
On this page
01What happens in each phase?
| Phase | Typical duration | What you do |
|---|---|---|
| Discovery and scope | 3–5 days | One working call, then approve the page map |
| Content gathering | 1–3 weeks | Supply copy, photos, logins — usually the longest phase |
| Design | 1–2 weeks | Review layouts, one consolidated round of feedback |
| Build | 1–3 weeks | Nothing; we build |
| Review and revise | 3–7 days | Test the staging link on your own phone |
| Launch | 1–2 days | Approve go-live |
Notice that three of the six phases are waiting on you. That is not a complaint — it is the honest reason two identical projects can finish four weeks apart.
02Why do website projects run late?
- Content is not ready
- By far the most common cause. If copy, photos, and service descriptions do not exist yet, that work has to happen before design can finish. Deciding early whether you are writing it or we are removes most timeline risk.
- Feedback arrives in pieces
- Five separate emails over two weeks costs more time than one consolidated round. Gathering internal opinions before sending feedback is the single most effective thing a client can do to keep a project on schedule.
- Scope grows mid-project
- A new page, a booking system, a second language. All legitimate, all additive. We will tell you the timeline impact before agreeing to it.
- Third parties
- Merchant accounts, insurance directories, and domain transfers move at their own pace, and no agency controls them.
03Can it be done faster?
Sometimes, and honestly. If you have finished content, a clear brief, and can review within 24 hours, a small site can land in two to three weeks. What we will not do is compress testing or skip the redirect plan to hit a date — those are the two shortcuts that cause problems for years afterward.
- Legitimately faster: fewer unique layouts, content ready on day one, one decision-maker
- Not faster, just riskier: skipping cross-device testing, launching without redirects, no staging review
04What if I need it live by a specific date?
Say so in the first conversation, not after the proposal. A hard date — a grand opening, a trade show, a franchise deadline — changes how we scope. Usually we phase it: the pages you need for the date go live first, the rest follow in a second release. That is a much better outcome than a rushed full site.
Common questions
How quickly can you start?
Usually within one to two weeks of a signed scope, depending on current workload. We will tell you the actual start date before you commit, not after.
How many rounds of revisions are included?
Two consolidated rounds at design stage and one at build stage is typical, and it is written into the scope. In practice, projects where feedback is gathered internally first rarely need all of them.
Will my current site go down during the build?
No. The new site is built on a staging URL and only replaces the live site at launch, which is a scheduled step measured in minutes.
Do you work with fixed deadlines like a grand opening?
Yes, and phasing the launch is usually the right approach. Tell us the date up front so it shapes the scope rather than compressing the testing.