How long does a typical business website take to build?
For a standard business website (5–10 pages, no custom functionality): 2–6 weeks from project start to launch. The range is wide because it depends on content readiness, revision rounds, and how quickly clients provide feedback. A prepared client who has content ready and responds within 24 hours can launch in 2 weeks. An unprepared client who takes 5 days to review each round will take 6+ weeks for the same scope.
What slows website projects down the most?
Content delays — by far. The most common cause of a website project running over timeline is waiting for the client to provide copy, images, or other content. Design revisions are the second most common cause, particularly when multiple stakeholders are involved and feedback takes days to consolidate. Technical complexity (custom integrations, e-commerce, membership systems) is the third cause, though this is predictable and can be scoped upfront.
Can a website be built in a week?
Yes — for a straightforward brochure website with an experienced designer/developer, a prepared client, and content already written. Evoke Studio offers 2–3 week delivery for standard brand + website projects when clients arrive prepared. The constraint is almost never the designer's speed; it's the client feedback cycle and content provision.
Timeline questions come before budget questions more often than not. And fair enough — for a business planning a launch, a product release, or an investor meeting, the schedule matters as much as the cost.
The problem with most answers to "how long?" is that they quote the designer's building time but ignore the client's feedback time — which almost always dominates the total.
Here's the complete, honest picture.
What Actually Determines Build Time
Website build time is not just how long the designer spends working. It's the total elapsed time from project start to launch — which includes:
- Designer working time: Actual hours of design and development
- Client feedback time: How long it takes the client to review and respond
- Revision cycles: Number of rounds, and how quickly each round completes
- Content provision: How long before the client provides all copy and images
- Technical complexity: Custom integrations, third-party APIs, special functionality
- Approval chains: How many stakeholders need to sign off
In most projects, client feedback time and content provision are the dominant variables — not designer speed.
Realistic Timelines by Project Type
Simple Brochure Website (3–5 pages)
Timeline: 1–3 weeks
Homepage, about, services, contact. No blog, no custom functionality. Used by tradespeople, consultants, local service businesses.
- Fastest possible: 5–7 days (prepared client, fast feedback, pre-written content)
- Typical: 2–3 weeks
- Slow: 4–6 weeks (late content, slow review cycles)
Standard Business Website (5–10 pages)
Timeline: 2–6 weeks
Homepage, about, service pages, portfolio/case studies, pricing, contact. The most common type of project.
- Fastest possible: 2 weeks (prepared client with a thorough brief)
- Typical: 3–4 weeks
- Slow: 6–8 weeks (multiple stakeholders, late content, extended revisions)
This is the range Evoke Studio delivers for brand + website packages — 2–3 weeks for prepared clients. Read What to Do Before Hiring a Web Designer to understand the preparation that makes fast delivery possible.
SaaS / Tech Product Website (8–15 pages)
Timeline: 4–8 weeks
Marketing site with feature pages, pricing, case studies, integration pages. Often requires close collaboration with the product team on messaging.
- Fastest possible: 3 weeks
- Typical: 5–6 weeks
- Complex: 8–10 weeks (large number of pages, multiple approval stages)
E-commerce Website
Timeline: 4–12 weeks
Depends heavily on the number of products, whether products need photography, and the complexity of the checkout and shipping logic.
- Small catalogue (under 50 products): 4–6 weeks
- Medium catalogue (50–500 products): 6–10 weeks
- Large catalogue or custom functionality: 10–16+ weeks
Custom Web Application
Timeline: 8–20+ weeks
Booking systems, client portals, member areas, marketplaces. These are development projects, not design projects — timeline depends on feature scope and the development stack.
The Client Feedback Multiplier
Here's what most designers don't say clearly: a slow client doubles the project timeline.
A 3-week project with a client who responds within 24 hours stays 3 weeks. The same project with a client who takes 4–5 days per review round extends to 5–7 weeks — through no fault of the designer.
Feedback cycle math:
- Typical project: 3 review rounds (initial concepts, revisions, final approval)
- Fast client (1-day review): 3 days of client review time
- Slow client (5-day review): 15 days of client review time
Fifteen days is a 3-week addition to the elapsed timeline.
How to be a fast client:
- Block time in your calendar for website reviews at the start of the project
- Consolidate all feedback in one round — don't send design feedback in pieces
- Designate a single decision-maker before the project starts (read What to Do Before Hiring a Web Designer for more on this)
The Content Provision Problem
The most common reason website projects stall is content. Specifically: the design is done and the developer is waiting for copy, images, and other assets that haven't arrived yet.
The pattern:
- Designer completes the site structure and design
- Designer needs final copy to fill the templates
- Client hasn't written the copy yet
- Project pauses for 1–3 weeks while client writes content
- Launch slips
How to avoid it: Draft rough content before the project starts. It doesn't need to be polished — rough drafts with approximate length and messaging are enough to design around. Final polish can happen during the project. Read How to Write a Web Design Brief for what to have ready before briefing a designer.
What the Designer Controls vs. What You Control
Designer controls:
- Speed of design and development work
- Quality of output
- Communication frequency
- Turnaround on revisions
Client controls:
- Speed of feedback
- Time to provide content
- Number of people in the approval process
- Number of revision requests
- Clarity of original brief
Most project delays originate on the client side. Understanding this isn't blame — it's useful information for setting expectations and planning your own availability before committing to a launch date.
Timeline Risks to Know in Advance
Scope creep: "Can we add a blog?" or "Actually we need a shop" mid-project. Each addition extends the timeline by the design and development time for that addition, plus the review cycle time.
Stakeholder disagreement: When multiple founders, partners, or executives need to align on design direction, and they don't align quickly, weeks pass between feedback rounds.
Brand not ready: If you don't have a logo, a colour palette, and font decisions before the website project starts, that work needs to happen first — adding weeks before development begins. Read Brand Before Website: Why Order Matters for why this order matters.
Hosting and domain delays: Setting up hosting, configuring DNS, and managing domain transfers can add days to a launch. Plan this in advance rather than discovering it at launch time.
How to Calculate a Realistic Launch Date
- Start with your designer's estimated build time (get this in the proposal)
- Add 1–2 days per review round for your feedback time (be honest about your availability)
- Add buffer for content provision if you haven't written it yet
- Add time for technical setup (hosting, domain, email)
Example:
- Designer estimate: 3 weeks
- 3 review rounds × 2 days each: +6 days
- Content writing time: +1 week
- Technical setup: +2–3 days
Total realistic elapsed time: ~5–6 weeks
Need a website built fast — without sacrificing quality?
Evoke Studio delivers brand + website packages in 2–3 weeks for prepared clients. Next.js, fast, mobile-first, and built to convert. Starts at $1,500.
Not necessarily in direct proportion. A $5,000 website from a senior designer who works efficiently may be delivered faster than a $2,000 website from a junior who needs more revision rounds. Price reflects quality, experience, and scope — not build time directly. The most reliable predictor of timeline is the clarity of the brief and the speed of the client feedback loop.
Start as early as possible. Projects always take longer than expected, especially if you're doing the content writing yourself. If you have a hard deadline (product launch, investment announcement, conference), work backwards: if you need the site live by date X, briefing the designer at least 6–8 weeks before that date is a safe minimum for a standard project. Build in buffer — you'll use it.
Most professional design projects include 2–3 revision rounds in the quoted price. The first round is typically the most significant (conceptual direction, major layout decisions); subsequent rounds are refinements. Additional rounds beyond what's included are usually charged at an hourly rate. Clarify this upfront — it's one of the questions to ask before hiring. Read [What to Do Before Hiring a Web Designer](/blog/what-to-do-before-hiring-a-web-designer) for the full list.
Most designers prefer to work to defined review points — completing a phase before getting feedback — rather than receiving feedback continuously throughout. This is because mid-build changes can affect already-completed work in ways that cascade through the project. Agree the review structure at the start: 'You'll see the homepage design first, then the inner page templates, then the full build.' Feedback at each defined stage is more efficient than continuous review.
First, identify who is causing the delay. If it's the designer, ask for a revised timeline in writing and confirm what milestones they're committing to. If it's your own feedback or content delays, acknowledge this and agree a new schedule. If the designer has missed multiple committed deadlines without explanation, that's a contract matter — your agreement should specify what happens in this case. Always have a written contract that includes a timeline before a project starts.