The short answer: a professionally built small-business website takes 4–8 weeks from kickoff to launch. A DIY builder site takes a week or two of your own evenings, a small online store runs 8–12 weeks, and custom web applications are measured in months. Those are honest industry-consensus numbers — but the more useful answer is why projects land where they do in those ranges, because the difference between a 4-week launch and a 4-month stall usually isn't the developer. We build websites for a living, we don't sell a website builder, so here's the timeline conversation we actually have with clients.
How long does each type of website take?
| Website type | DIY on a builder | Professionally built |
|---|---|---|
| Landing page / one-pager | A few hours – 3 days | 1–2 weeks |
| Small business site (5–15 pages) | 1–2 weeks | 4–8 weeks |
| Corporate site (15–30+ pages) | Rarely sensible | 8–16 weeks |
| Online store (small catalog) | 1–6 weeks | 8–12 weeks |
| Online store (large / custom) | Don't | 4–8 months |
| Custom web application | — | 6–12+ months (different animal entirely) |
Two honest notes on the table. First, DIY times assume your hours — evenings and weekends you aren't running the business. Second, the professional ranges assume the project keeps moving; every range above stretches when the inputs stall, which brings us to what the weeks are actually spent on.
What happens in each phase?
A professional build isn't six weeks of typing code. The calendar splits roughly like this for a small-business site:
- Discovery and planning (week 1): goals, sitemap, who your customers are, what pages must exist and what each must accomplish.
- Design (weeks 2–3): real mockups, desktop and mobile, revised until right. More unique page layouts = more design time.
- Development (weeks 3–5): the build itself, CMS setup, forms, integrations. Overlaps design once directions are locked.
- Content (parallel — and pivotal): copy, photography, testimonials. More below, because this is where launches actually die.
- QA and launch (final week): device testing, performance tuning, redirects, analytics, DNS cutover.
Notice the actual engineering hours are a fraction of the calendar. A standard 10-page site is often only 30–60 working hours of build time — spread across weeks of feedback loops, approvals, and content arriving. When an agency quotes "six weeks," they're not padding; they're modeling the loops honestly.
What actually makes a website take longer?
Every article in this space says "it depends on complexity." Here's what the delays look like from the inside, ranked by how often we see them:
- Content isn't ready. The single biggest cause of late launches — not design, not development. A website can't launch before its words and pictures exist, and "we'll write the copy ourselves" routinely adds a month. Fix: before kickoff, inventory every page's copy, images, and proof (reviews, logos, case numbers). If half of it doesn't exist, either commission it or shrink the launch scope.
- Approval bottlenecks. One decision-maker who reviews within 48 hours keeps a project on rails. A three-person committee that meets weekly adds roughly a week per revision round — two rounds of design plus two of build is a month of calendar from governance alone.
- Scope creep. "While we're at it, can we add…" is how 6 weeks becomes 14. New ideas aren't bad; re-scoping mid-build is. Park them in a phase-two list.
- Regulated-industry requirements. Accessibility compliance, patient-data handling, payment security — legitimate work that belongs in the plan on day one, not discovered in week five.
Does the platform change the timeline?
Some, though less than platform vendors claim. A builder gets something live fastest — that's its genuine superpower, covered honestly in custom vs website builder. WordPress with a quality theme sits in the middle. A custom build on a modern stack takes the longest first time — and here's the nuance the platform blogs skip: on component-based stacks like Next.js (what we build on, including this site), the early weeks buy you a design system, so page eleven takes a fraction of the time page one did, and later additions ship in days. Choose by where you want to be in year two, not by launch week alone; the cost side of that choice follows the same logic.
Is a redesign faster than a new website?
Usually, yes — by roughly a third — because the content largely exists, the brand exists, and analytics tell you what's working. Discovery compresses from weeks to days; design and development take about the same. A small-business redesign typically runs 3–6 weeks against 4–8 for greenfield. What eats that saving: treating the redesign as an excuse to rewrite everything at once. If it's genuinely time for a redesign, migrate the content that works, fix what doesn't, and keep the rewrite surgical.
How do you launch faster without cutting corners?
The client-side moves that genuinely compress timelines:
- Have content ready before kickoff — or budget for the agency to produce it. This one habit beats every other acceleration tactic combined.
- Name one decision-maker and agree on 48-hour feedback turnarounds.
- Give real feedback once, not dribbled feedback five times. "The hero feels crowded and the tone is too formal" in one pass beats five single-comment emails a week apart.
- Launch at 90%. Ship the pages that sell, add the nice-to-haves in month two. A live good website beats a perfect one in staging — and Google starts aging your domain the day it's live.
- Fix the scope in writing. Our version: a scoping call, then a fixed, itemized quote with a launch window — typically within 48 hours — that holds unless the scope changes.
How long until the website starts working?
One timeline nobody puts in the proposal: launch day is when the clock starts, not when it stops. Visitors from ads, social, and your email signature arrive immediately — but organic Google traffic ramps over months, not days. A brand-new domain typically sees its first meaningful search impressions in weeks and real traction in three to six months as pages get indexed, earn internal links, and prove themselves against competitors. Two practical consequences: launch sooner rather than later, because the SEO clock only runs on a live site; and treat the first ninety days after launch as part of the project — submitting the sitemap, fixing what Search Console surfaces, and adding the content that earns rankings. A website finished in six weeks and then ignored takes far longer to work than one launched in five and nurtured.
If you want a real date instead of a range, book a free strategy call — tell us what you need and what content exists, and we'll give you an honest launch window with the dependencies spelled out.
Frequently asked questions
Can you really build a website in a day? A page, yes — builders and AI tools genuinely produce something presentable in hours. A website that represents a business — right messaging, right pages, performance, SEO — is a different product that happens to share a name. The day-one version is fine for testing an idea; it just isn't the finish line.
Can a professional website be done in under a month? Yes, when three things are true: modest scope (5–8 pages), content ready at kickoff, and fast decisions. Miss one and four weeks becomes eight; miss two and no honest agency will promise the date.
How long does the design phase take? One to four weeks for most business sites — a function of how many unique layouts you need and how many revision rounds it takes to converge, which is mostly a function of how clear the feedback is.
How long does an e-commerce website take? Eight to twelve weeks for a professionally built store with a small catalog; several months at large-catalog or custom scale. Product content — photos, descriptions, shipping and tax rules — is the long pole, same as copy is for brochure sites.
How long does domain and hosting setup take? Hours, not weeks — registering a domain is minutes, hosting setup is a day at most, and DNS changes propagate within 24–48 hours. It's the one part of the project with no meaningful wait, which is why "we're setting up the servers" is never the real reason a launch is late.
What's the single biggest cause of delays? Content. Not design, not development, not the agency's queue. Websites launch late because words, images, and approvals arrive late — which also means it's the delay you have the most control over.