One of the most common questions clients ask before starting a project is: "How long will this take?"
It's a fair question. It's also one where you'll often get either an unrealistic answer ("a couple of days!") or an evasive one ("it depends").
Here's the honest version — a realistic breakdown of how long websites actually take to build, based on what's typical for each category.
The short answer
For a small business website:
- Landing page: 3–7 days
- Standard 5–10 page site: 1–3 weeks
- E-commerce store: 2–5 weeks
- Custom-coded site: 2–6 weeks
- Complex web app: 1–3 months+
Those numbers assume the client provides content on time, revisions are reasonable, and nothing unexpected happens.
Most projects take 20–40% longer than the developer's initial estimate. Not because developers are dishonest — but because clients underestimate their own contribution, and unexpected issues always come up.
What actually takes time
Non-developers often assume that "building a website" is one big task. It's actually a dozen smaller tasks, and each one takes time.
Here's where the hours actually go:
1. Discovery and planning
Time: 5–15% of the project
Before any code is written, the developer needs to understand:
- What the site needs to do
- Who it's for
- What pages are needed
- What features are required
- What the client's brand looks like
A good developer doesn't skip this. It's the difference between building the right site and building something that needs to be redone.
2. Design
Time: 15–25% of the project
Whether it's choosing a template or creating a custom design, this is where the visual direction is set.
For a template-based site, this might be a few hours of customization. For a fully custom design, it can be a week or more.
3. Development
Time: 40–60% of the project
This is where most of the work happens. Building pages, setting up functionality, integrating tools, testing, and fixing issues.
The more complex the site, the bigger this slice becomes.
4. Content entry
Time: 10–20% of the project
Adding text, images, products, and other content to every page. This is often faster than people expect — unless the content isn't ready, in which case it becomes a bottleneck.
5. Testing and revisions
Time: 10–20% of the project
Testing on different devices, fixing bugs, and handling revisions after the client reviews the site.
Revisions can be a small part of the project, or the largest part, depending on how clear the client was upfront.
6. Launch
Time: 2–5% of the project
Final testing, DNS configuration, deployment, and handover. Often a single day for simple sites, or a week for complex ones.
Timelines by project type
Here's a more detailed breakdown by category.
Landing page (3–7 days)
A single-page site designed to convert visitors into leads, signups, or buyers.
What's included: Hero section, features or benefits, testimonials, CTA, contact form.
Why it's fast: Only one page, standard structure, usually little customization.
What slows it down: Waiting on content, complex integrations, custom animations.
Standard business site (1–3 weeks)
A multi-page site presenting a business — home, about, services, contact, and a few more pages.
What's included: 5–10 pages, contact form, basic SEO, mobile-responsive design.
Why it's medium speed: More pages to build, more decisions to make, more content to write.
What slows it down: Client delays on content, lots of revisions, unexpected feature requests.
E-commerce store (2–5 weeks)
An online store with products, cart, checkout, and payment processing.
What's included: Product catalog, cart, checkout, payment gateway, order management, customer accounts (sometimes).
Why it takes longer: Every product needs to be added. Every edge case (shipping, taxes, discounts) needs to be handled. Payment integration takes time to test.
What slows it down: A large product catalog, complex shipping rules, custom checkout flows.
Custom-coded site (2–6 weeks)
A website built from scratch using React, Next.js, or similar frameworks.
What's included: Custom design, hand-coded pages, custom interactions, deployment to Vercel or similar.
Why it takes longer: No pre-built components to reuse. Every page, feature, and animation is built from scratch.
What slows it down: Custom features, complex interactions, integrations with external services.
Web app or platform (1–3 months+)
A full application — dashboards, user accounts, real-time features, databases, and complex logic.
What's included: Everything you'd expect from a website plus real functionality.
Why it takes the longest: Every feature is a mini-project. Real testing is required. Edge cases multiply.
What slows it down: Every additional feature, every integration, every unexpected requirement.
What actually makes projects take longer
Here's the honest list of what causes delays, in order of frequency:
1. Content isn't ready
By far the biggest cause. Developers can build fast, but they can't write your copy, take your photos, or choose your brand voice.
If you want a project done in 2 weeks, have your content ready before the developer starts.
2. Scope creep
Small additions feel harmless in the moment. "Can you also add a blog?" "Can we also include a booking system?"
Each one adds days. Multiple small additions can turn a 2-week project into a 6-week one.
3. Slow feedback
Every revision round requires the client to review, give feedback, wait for changes, and review again. If the client takes a week to give feedback, the project takes a week longer.
4. Underestimated complexity
Some features look simple but aren't. A "simple" contact form with conditional logic and email routing can take a full day. A "small" redesign can cascade into major changes.
5. Third-party delays
Hosting setup, payment gateway approval, DNS propagation, SSL certificates — external services sometimes take days to sort out.
How to make your project faster
If you want your website done quickly, here's what actually helps:
1. Have your content ready. All of it. Text, images, products, everything. Before the developer starts.
2. Be decisive. Every "let me think about it" adds time. Have a clear vision upfront.
3. Give feedback quickly. When the developer sends something for review, review it that week — not next month.
4. Limit revisions. Two rounds of revisions is normal. Five is a sign of unclear brief. Eight means the project is in trouble.
5. Don't add scope mid-project. Every addition delays the original goal. Save it for phase two.
6. Trust the process. Developers who've done this before know what they're doing. Fighting them on structure, timeline, or approach usually makes things slower, not faster.
Realistic vs unrealistic expectations
A few examples of common client expectations vs. reality:
| Client says | Reality |
|---|---|
| "It's just a small site — a few days?" | Only if content is ready and there are no changes |
| "Can we also add..." (mid-project) | Adds 2–7 days depending on scope |
| "The competitor site took a week" | Theirs was a template install, not a build |
| "We need it live by Friday" | Possible for a landing page, unrealistic for a store |
| "We're not sure about the design yet" | Then the project hasn't started yet |
The realistic timeline for most small businesses
For a typical small business website — WordPress, 5–10 pages, standard contact form, basic SEO — here's the honest timeline:
- Week 1: Discovery, content gathering, initial setup
- Week 2: Design, build, first draft
- Week 3: Revisions, testing, launch
Three weeks is realistic if content is ready from the start.
If the client provides content slowly, or asks for many changes, it can stretch to 5–6 weeks.
What to do with this information
If you're a client: Use these timelines as a rough guide. Ask your developer for their specific estimate — but be suspicious of anyone promising significantly faster than this. Either they're cutting corners, or they don't know what they're doing.
If you're a developer: Use these timelines to give clients realistic expectations upfront. Always buffer the estimate — you'll always use the buffer. And communicate early if you're going to be late.
Bottom line
Websites take time. The specific timeline depends on complexity, but here's the honest range for a small business:
- Fastest realistic: 3 days (landing page, content ready)
- Typical: 2–3 weeks (standard site)
- Slower: 5–8 weeks (complex site, slow content)
Anyone promising significantly faster is probably overselling.
Anyone telling you it "depends on everything" isn't giving you a real answer.
Use the ranges in this post to set your own expectations, and ask your developer to give you their specific timeline with confidence.
Want to know what actually costs what first? Read our honest pricing breakdown.
Hiring someone and don't know what to ask? Read our 10 questions before hiring a developer.
