How long does a small business website take?

How long a small business website takes depends on how many pages you need, whether your content exists yet, and how fast decisions get made on your side. Anyone who quotes a number of weeks before seeing those three is guessing. Ask for a schedule built on your actual scope that shows what depends on what.

A simple site with a few pages

A homepage, a contact page, and one focused service page is the fastest build there is, if the offer is clear, the content is ready, the technical setup is sorted, and one person can say yes. Remove any of those and even a three-page site drags.

"Content ready" means you can hand over, today:

  • Your logo, or a clear brief for a simple wordmark
  • A short description of what you do and where you do it
  • Approved photos of your work, team, or equipment
  • Your public phone number, email, and address or service area

Other small-launch blockers have nothing to do with design: domain access nobody can find, form delivery, legal review, a partner who hasn't signed off.

A standard multi-page business site

Add an about page, service pages, coverage information, and a contact page, and there's real writing, design, a responsive build, testing, and review. For a contractor this is usually the site you actually need. The schedule holds when you have:

  • A clear brief and an approved scope at the start
  • A named owner and due date for content and photos
  • Agreed review windows and one final decision-maker
  • A way to approve, or price, changes to the scope

Ask for a milestone plan that shows dependencies. A round number of weeks says nothing about what happens when the photos are late.

Migrations, a gallery, a blog, booking integration, multilingual pages, custom functionality: each adds discovery, production, testing, and review. Content volume is the obvious cost but rarely the one that bites. Integrations, data migration, accessibility, performance, legal review, and getting decision-makers in a room can each take as long as the writing.

What actually slows things down

Delays come from both sides. Late projects usually trip on one of these:

  • Missing assets: photos, brand files, credentials, account access
  • Content that changes after design or development starts
  • Feedback from several reviewers and a decision from none
  • Scope changes that add pages, integrations, or revision rounds
  • Delivery problems on the studio side: underestimated work, defects, missed milestones

Cut the avoidable ones: gather approved business facts, service details, photos, logins, and legal requirements before kickoff. The studio owes you templates, deadlines, and feedback instructions.

Whose job is the timeline?

Both of yours. You provide accurate inputs and decide on time. The studio sets honest expectations, flags risks early, delivers reviewable work on schedule, and doesn't build on assumptions nobody confirmed.

Control scope changes: write each request down with its cost, its schedule impact, and whether it belongs before launch or after.

Before work starts, gather brand files, approved photos, service facts, contact details, logins, and a few sites you like (full list: what to give your web designer). Preparation shrinks the uncertainty. The schedule still comes from the whole project, which is why we scope on a discovery call rather than off a form.