Can a website be built in a week?

A single page with your offer, proof and a contact route — yes, if the content is ready. A five-to-ten page site in a week means either the content already existed in finished form or corners were cut somewhere you will find later.

What if I do not have any content ready?

Say so at the start rather than mid-project. It changes the plan, not the possibility: either the scope shrinks to what you can fill properly, or content becomes a paid part of the work with its own deadline.

Does adding a blog or an AI agent change the timeline?

A blog barely, since it is a template plus your writing discipline afterwards. An AI agent does, because it needs your real answers, real edge cases and a round of testing against actual customer questions. Treat it as its own project.

Is a redesign faster than a new site?

Usually slower, which surprises people. A new site has no legacy: no old URLs to preserve, no rankings to protect, no content to migrate. A redesign carries all three, and skipping the URL work is how sites lose their traffic on launch day.

How long does it take to build a website?

Two to four weeks for a focused small-business site — and the delay is almost never the code. What those weeks actually contain, why the client is usually the bottleneck, and what makes a project run long.

Key takeaways

Plan two to four weeks from an agreed scope to launch for a focused small-business site.
Under five days should make you suspicious. Over a month, at this size, usually means the scope was never fixed.
Building is rarely the constraint. Decisions and content are.
The single biggest accelerator is having your text and photos ready before the project starts.
One named decision-maker shortens a project more than any tool does.

How long does it take to build a small-business website?

Two to four weeks from a signed scope to launch, for a site of five to ten pages. That assumes decisions get made within a day or two and content exists in some form when you start.

Both ends of that range mean something. Under five days is suspiciously fast — it usually describes a template filled with placeholder text and stock photography, which is a different product sold under the same name. Beyond a month, for this size of project, is almost always drift rather than craft: the scope was never fixed, or nobody was chasing the decisions.

What those weeks actually contain

The calendar is not full of coding. It is full of five things, and only one of them is technical.

Scope and decisions (2–4 days). Who the site is for, the one action it should produce, what goes on which page, what the price policy is. Get this wrong and everything after it is rework.
Content (the variable). Text, photos, proof. This is the phase that decides whether you finish in two weeks or two months.
Design and build (5–10 days). The part people imagine is the whole project.
Review (2–3 days). One consolidated round of feedback, not a trickle of messages.
Launch checks (1 day). Accessibility, speed on a real phone, analytics, indexing, forms actually delivering to a mailbox someone reads.

Why projects run late — and it is usually not the code

Four causes cover almost everything.

Content that does not exist yet. "We'll send the text next week" is the single most common reason a two-week project becomes a two-month one.
Feedback by committee. Three people with opinions and no one with authority turns a two-day review into a fortnight.
Scope added mid-flight. Every "while we're at it" resets the clock, and the ones that sound smallest — a booking system, a second language, a shop — are the ones that reset it hardest.
Missing access. Nobody remembers who registered the domain. This surfaces on launch day, reliably.

What you can do to make it faster

Four things, all free, all under your control.

Write the content first, or at least the rough version. Bad text that exists beats perfect text that is coming.
Name one decision-maker. Others can advise. One person approves.
Agree the scope in writing and hold new ideas for a version two list. The list is not a rejection — it is a schedule.
Book the review slot in advance. A review that waits four days for a free afternoon costs four days.

The preparation itself is a short job — we listed exactly what to gather in what to prepare before your website project starts.

What your partner should be doing to keep it short

You can judge this in the first conversation. A partner who intends to finish on time will fix the scope in writing before quoting, show you something running within the first week rather than a static picture of it, keep the whole project in one channel instead of scattered across email and messages, and tell you explicitly what they are blocked on rather than going quiet.

Going quiet is the signal that matters. A project that stops reporting has usually stopped moving.

Both extremes are warnings

The five-day site. It exists, and sometimes it is the right purchase — a one-page site to stop losing enquiries while you decide what you want. Just buy it knowing what it is, rather than believing you bought the other thing.

Longer than a month at this size and the useful question is not "when will it be ready" but "what is it waiting on". Ask for the blocker list. If nobody can produce one, that is the answer.