“How long will it take?” is one of the first questions business owners ask, and most of the answers online are useless — either a salesperson’s optimistic guess or a range so wide it tells you nothing.
The honest answer is that a straightforward small business website takes two to four weeks, and the single biggest variable isn’t the developer’s speed. It’s how quickly decisions get made and content gets handed over.
That’s genuinely good news, because it means the timeline is largely in your control.
Typical timelines
| What you’re building | Realistic timeline |
|---|---|
| A focused landing page | 5–10 days |
| Standard small business site (5–8 pages) | 2–4 weeks |
| Site with location or service pages (10–20 pages) | 3–6 weeks |
| Custom features, booking systems, integrations | 6–12 weeks |
| E-commerce with real inventory | 8–16 weeks |
These assume a smooth process and reasonably prompt feedback. Every one of them can double if the project stalls waiting on something.
Notice what drives the jump between rows: it’s rarely technical difficulty. It’s the number of decisions and the volume of content. A twenty-page site isn’t four times harder to build than a five-page site — it’s four times more content to write, review, and approve.
What those weeks actually contain
“Two weeks” is meaningless without knowing what happens inside it. Here’s how a typical build breaks down.
Discovery — 1 to 3 days
A conversation about what the business does, who the customers are, what a new customer is worth, and what the site needs to make happen. Then a look at competitors — what they rank for, how they position, where the gaps are.
Skipping this is how you end up with a site that looks fine and sells nothing. It’s the cheapest phase and the one with the most leverage over the result.
Content and copy — 3 to 10 days
Usually the longest phase, and almost always the one that stalls.
Someone has to decide what every page says. If you’re writing it yourself, this is where projects die — not because business owners can’t write, but because writing your own sales copy is genuinely hard and easy to postpone. If copywriting is included in the build, this phase compresses to a couple of structured questions and a review.
Photography sits here too. Stock images are instant; real photos of your team, your work, and your premises take scheduling.
Design — 3 to 7 days
Layout, typography, colour, and the visual hierarchy that decides what a visitor notices first. For a standard site this usually means designing the homepage and one or two template pages, then applying that system across the rest.
Build — 3 to 7 days
Turning the design into a working site: responsive layouts, forms, page speed, structured data, accessibility. On a well-scoped project this is one of the faster phases, which surprises people.
Review — 2 to 5 days, or forever
Two structured rounds is normally plenty. This phase has no natural end, so it needs a defined one.
Pre-launch checks — 1 day
Mobile testing on real devices, speed testing, form submission tested end to end, analytics installed, SSL and HTTPS redirects confirmed, redirects mapped if replacing an old site.
Test the contact form by actually submitting it and confirming the message arrives in the inbox. A form that silently fails is invisible until you notice enquiries stopped, and by then you’ve lost weeks of leads.
Launch and settling — 1 day, then a few weeks
DNS changes, sitemap submitted to Google Search Console, indexing requested. The site is live the same day; Google takes a few weeks to work through it properly.
What actually causes delays
In practice, projects slow down for a short list of predictable reasons, and almost none of them are technical.
Content
The number one cause, by a wide margin. Waiting on photos, service details, pricing decisions, or copy approval. A project can sit for three weeks waiting for someone to send twelve photos and answer four questions.
The fix: gather materials before the build starts, or hire someone who handles copy and imagery for you.
Slow feedback
A project moves at the speed of its approvals. A review that sits for two weeks adds exactly two weeks. Nothing else happens in the meantime, because everything downstream depends on that decision.
The fix: block 45 minutes in your calendar for each review round before the project starts.
Scope creep
“Can we also add a booking system?” is how a two-week project becomes a two-month one. This isn’t a bad instinct — you’re seeing possibilities. But every addition has a cost in time.
The fix: keep a “phase two” list. Write additions down, launch without them, add them after. A live site earning leads while you build phase two beats a perfect site that isn’t live.
Too many decision-makers
When four people must agree on the homepage headline, you don’t get a better headline. You get a slower project and a compromised headline.
The fix: name one person with final say.
Indecision
The quiet killer. Reworking the same page for the fifth time, chasing a feeling rather than a specific problem.
The fix: tie feedback to outcomes. “This headline doesn’t say what we do” is actionable. “I’m not sure about it” isn’t.
Replacing an existing site
Rebuilds carry work new builds don’t: auditing existing URLs, mapping redirects, preserving pages that already rank. Budget an extra week, and don’t skip it — losing your rankings in a redesign is a genuinely expensive mistake.
What you can do before hiring anyone
Everything here is free, and it can cut a week or more off the build:
Write down what you actually want the site to do. “Get more calls from people needing emergency repairs” is a brief. “Look more professional” isn’t.
Collect your assets. Logo files (vector if you have them), photos of real work, team photos, licence and certification details, insurance info, service area list.
List your services properly. Not four words each — a sentence or two on what each involves, who it’s for, and roughly what it costs.
Find three sites you like and three you don’t, with a note on why. This communicates more in five minutes than an hour of describing.
Get your logins together. Domain registrar, current hosting, Google Business Profile. Hunting for a registrar password you set up six years ago is a classic week-long delay.
Decide who approves. One name.
Businesses that arrive with this ready routinely launch in half the time of businesses that don’t.
What a two-week build actually looks like
| Day | What happens |
|---|---|
| 1 | Kickoff call, goals, brand assets handed over |
| 2–3 | Sitemap and page structure agreed; copy drafted |
| 4–6 | Homepage design, then template pages |
| 7 | Review round one — your feedback, batched |
| 8–10 | Revisions, remaining pages built |
| 11 | Review round two — final adjustments |
| 12 | Speed, mobile, accessibility, forms, analytics |
| 13 | Pre-launch checks, redirects mapped |
| 14 | Launch, sitemap submitted, tracking confirmed |
Two days of that are yours. The rest is the builder’s. And those two days are precisely where the timeline lives or dies.
Warning signs in a quoted timeline
“We can have it live tomorrow.” Possible only if it’s a template with your logo dropped in. Fine if that’s what you want; not fine if you were promised a considered build.
“Three to six months” for a standard small business site. Either the scope is much bigger than described, or you’re being queued behind other work.
No timeline at all. A builder who won’t commit to dates on a project they’ve scoped is telling you something about how the project will run.
A timeline with no dependencies named. Any honest schedule says what it needs from you and when. One that doesn’t will quietly become your fault later.
There’s more on evaluating this in how to choose a web designer.
Why launching faster is usually better
A site that goes live in two weeks and starts generating enquiries beats a “perfect” one still in review after six months. Two reasons:
Every week offline is a week of lost leads. If your site would produce eight enquiries a month, four months of polishing costs you thirty-two enquiries. That’s a real number with real revenue attached.
Real visitors tell you more than internal opinions. Once live, you can see which pages people land on, which convert, and where they leave. Six months of guessing in a review cycle produces none of that. We covered how to read it in tracking website leads with GA4.
Launch a strong, focused site, then improve it with evidence. That’s a faster route to a good website than trying to design one perfectly in advance.
Does the platform change the timeline?
Somewhat, though less than people expect.
A DIY builder can be live in a weekend, if you do all the work and accept a template. The tradeoffs are real, but speed isn’t one of them.
WordPress adds setup, theme configuration, and plugin decisions. Usually a few days more than a static build, plus ongoing maintenance — see WordPress vs a custom website.
A custom static build is typically fastest for a marketing site, because there’s no CMS to configure and less that can go wrong at launch.
Platform choice matters far more for the five years after launch than for the two weeks before it.
Common questions
Can a website really be built in two weeks? Yes, for a standard small business site of five to eight pages, provided copy and design are handled for you and feedback comes back within a day or two. The build itself is rarely the constraint — approvals and content are.
What’s the fastest a site can realistically go live? A focused single landing page can launch in under a week. Anything faster is a template with your details swapped in, which is a legitimate choice but a different product.
Why do some agencies quote three months for a small site? Usually queueing rather than complexity — your project is scheduled behind other work. Ask directly how much of that time is active work on your site versus waiting.
Will a rushed site hurt my SEO? A fast build isn’t a rushed build. What hurts SEO is launching without redirects from an old site, without a sitemap, or without unique page titles — none of which take extra weeks, just attention.
What happens if I’m slow with feedback? The timeline extends by roughly the delay. Most builders hold your slot for a reasonable window, then move to other projects, which can mean waiting for the next opening.
Can I add features after launch? Yes, and usually you should. Launching without the booking system and adding it in month two means eight weeks of leads you’d otherwise have missed.
Our approach
We keep projects tight: a short kickoff call, copy and design handled for you, two structured review rounds, and a typical launch in about two weeks for a standard small business site.
You always know what’s happening, what’s next, and what we need from you. You own everything at the end (domain, code, and content) and there’s no retainer required to keep it running.
Ready to see a real timeline for your project? Get a free quote with a clear price and schedule, usually within one business day, or see what’s included and what it costs.
Want this handled for you?
SimplyGood builds fast, lead-generating websites for local businesses across the US. Get a tailored quote in one business day.