A typical business website takes 3 to 8 weeks to build in 2026 — about 2–4 weeks for a small 5-page site with content ready, 4–8 weeks for most custom business websites, 6–12 weeks for eCommerce, and 3–6 months for a custom web application. The surprising truth: design and development are rarely the bottleneck. Around half of all project delays come from content — copy, photos, product data, and approvals arriving late. This guide gives you the honest phase-by-phase timeline, explains exactly what happens in each phase, flags the delays that actually happen, and shows you how to be the client who launches on time.
If you are planning around a trade show, a seasonal peak, or a funding announcement, work backwards from this article: pick your launch date, subtract the timeline for your site type below, then subtract two buffer weeks. That date is when you need to start — and, just as importantly, when your content needs to exist.
The Timeline by Website Type
| Website type | Realistic total timeline | Build phases involved |
|---|---|---|
| Landing page | 1 – 2 weeks | Discovery (light), design, build, launch |
| Small business site (5–10 pages) | 2 – 4 weeks | All standard phases |
| Custom business site (10–25 pages) | 4 – 8 weeks | All phases, more design & review rounds |
| eCommerce store | 6 – 12 weeks | All phases + catalogue, payments, delivery setup |
| Custom web app / portal | 3 – 6+ months | Extended discovery, development sprints, testing |
Phase by Phase: What Actually Happens
Phase 1 — Discovery and planning (3–5 working days)
Goals, audience, competitor scan, sitemap, and a written scope with a page list and feature list. This short phase prevents the most expensive sentence in web projects — "can we just add…" — from arriving in week five. Deliverable: signed scope and sitemap.
Phase 2 — Content (1–3 weeks, runs in parallel)
Copy for every page, photography, logos and brand files, product data for stores. This phase belongs mostly to you, the client, and it is where timelines live or die. Professional copywriting adds cost but removes the single biggest delay risk; if you write your own copy, start the day the scope is signed, not when design finishes. Two free helpers: keep drafts at a sensible keyword balance with the Keyword Density Checker, and plan every page's title and description in advance with the Website SEO Metadata Worksheet.
Phase 3 — Design (1–2 weeks)
Homepage concept first, feedback round, then inner-page designs using your real content (or realistic drafts). One consolidated round of feedback from one decision-maker takes days; feedback from five people across three rounds takes weeks. Deliverable: approved designs for desktop and mobile.
Phase 4 — Development (1–3 weeks; 4–8 for eCommerce/apps)
The site is built on a private staging link: CMS setup (WordPress for most business sites), responsive build, forms, maps, analytics, and integrations. For stores, add catalogue import, payment gateway configuration and test transactions, shipping rules, and tax setup. For Laravel/Next.js builds, development runs longer and in visible sprints. Deliverable: a complete staging site you can click through.
Phase 5 — Review, testing, and revisions (1 week)
You review the staging site against the scope: content proofread, links, forms tested end-to-end, checkout tested with real payment methods in test mode, speed checks, and cross-device testing. Compress any heavy images the content phase produced with the Image Compressor and convert heroes with the Image to WebP Converter. Deliverable: one consolidated change list, completed and re-tested.
Phase 6 — Launch (2–3 working days)
DNS and hosting cutover, SSL, redirects from any old pages, sitemap submission, final metadata verification with the Meta Tag Analyzer, and a post-launch smoke test. A structured pass using the WordPress Business Website Launch Checklist keeps this phase boring — in launch week, boring is good.
Phase timeline for a typical custom business website (weeks) — hover or tap each bar for details.
Where website project delays actually come from (share of delayed projects, editorial estimate) — hover or tap each bar for details.
A Real Project Calendar: The 6-Week Custom Site, Week by Week
The phases above, laid on an actual calendar for the planning-estimate case — a custom business site, content being written in parallel. This is what 'six weeks' really looks like from inside:
| Week | What happens | What the client does |
|---|---|---|
| 1 | Kickoff, discovery, sitemap and scope signed; hosting and access gathered | Names one approver; hands over logins, brand files and the old site's access; starts copy |
| 2 | Homepage design concept; content continues | One consolidated feedback round on the concept; copy for the first pages delivered |
| 3 | Inner-page designs approved; development begins | Approves designs; finishes remaining copy and photography |
| 4 | Development continues: pages built on staging, forms and integrations wired | Reviews staging link as pages land; collects any missing product or policy details |
| 5 | Development completes; full review and testing round | One full review session; single consolidated change list; tests forms and checkout personally |
| 6 | Changes completed and re-tested; launch checks; go-live early in the week | Final sign-off; team briefed; launch announced once the live tests pass |
Notice the shape: the client's heaviest work lands in weeks 1–3, while everything is still cheap to change. Projects that slip almost always compress those weeks instead — copy arriving in week 5, approvers appearing in week 6 — and the calendar responds by moving the only date it can: the launch.
The Five Real Causes of Delay — and Their Fixes
- Content isn't ready. Fix: content starts in Phase 1, in parallel, with a named owner and a hard date.
- Too many approvers. Fix: one decision-maker collects all internal feedback into a single list per round.
- Scope creep. Fix: new ideas go on a Phase-2 list, priced and scheduled after launch — the site ships on time and still gets the feature.
- Third parties. Payment gateway approvals, registrar access, and old-developer handovers stall builds. Fix: gather logins, DNS access, and gateway documents in week one.
- Feedback by drip. One change a day for two weeks costs more calendar than a full review day. Fix: schedule your review sessions in the project plan like meetings.
What Your Developer Is Waiting For: Client Inputs by Phase
Half this article's delays reduce to a short list of things only the client can supply. Gathered in week one, they cost an afternoon; chased in week four, they cost the launch date.
- Before design: logo and brand files in their original formats, the final page list, and any must-keep content from the old site.
- Before development: domain registrar and hosting access (or a delegated contact who can act), copy drafts, photographs, and — for stores — the product spreadsheet and gateway application documents.
- Before review: the real details the site must state: prices or price ranges, service areas, opening hours, policies (delivery, returns, privacy), and the inbox that receives enquiries.
- Before launch: one approver's final sign-off, DNS access for the cutover window, and someone reachable on launch morning.
Can It Be Done Faster?
Yes, with honest trade-offs. A template-based build with finished copy can launch in 1–2 weeks. What you give up is distinctiveness and depth, not legitimacy. Conversely, beware any promise of a custom 25-page site "in 5 days": design, build, and testing can be compressed, but approvals and content cannot — the corners being cut are usually SEO setup, testing, and mobile polish, which you pay for later. A phased launch is the smarter acceleration: core pages live in week 4, secondary pages and features in the weeks after, revenue and rankings starting earlier.
Redesigns vs New Builds: How the Timeline Changes
A redesign is not simply a new build with a head start. Two phases shrink and two grow. Design often moves faster — brand, audience and content structure already exist as a starting point. Development is similar. But discovery grows: the old site needs an audit (what ranks, what converts, what must be kept), and launch grows with it — the redirect map, migration testing and post-launch monitoring from the launch checklist are redesign work, not new-build work. Content decides it either way: a redesign that rewrites everything carries the same content phase as a new build, while one that reuses proven copy can be the fastest project of all. Net effect for planning: estimate a redesign at roughly the same total as the equivalent new build, with the time redistributed — less invention, more migration. Our redesign cost guide prices the same redistribution for US readers.
Launch-Date Estimator: Worked Examples
You cannot pick a launch date from a calendar widget — but you can estimate one in about a minute. Every professional timeline starts from a planning estimate for the website type, then adjusts for the single biggest variable: whether your content is ready.
| Website type | Typical range | Planning estimate | If your content is ready | If your content is NOT ready |
|---|---|---|---|---|
| Small business site | 2–4 weeks | 3 weeks | Launch in about 3 weeks | Launch in about 5 weeks |
| Custom business site | 4–8 weeks | 6 weeks | Launch in about 6 weeks | Launch in about 8 weeks |
| eCommerce store | 6–12 weeks | 9 weeks | Launch in about 9 weeks | Launch in about 11 weeks |
| Custom web application | 3–6 months | 20 weeks | Launch in about 20 weeks | Launch in about 22 weeks |
How to estimate yours: find your website type in the table and take its planning estimate. If your copy, photos and product data are not finished, add two weeks — unfinished content is the delay this article keeps coming back to. Then count that many weeks forward from your start date, and treat the result as a window, not a promise: gateway approvals, feedback rounds and holidays all eat buffer. If the date matters (a trade show, a season, a campaign), work backwards from it and start the content this week.
Questions to Ask Any Developer About Their Timeline
Before you sign, five questions separate a real schedule from a hopeful one. What does the estimate assume I deliver, and by when? A credible answer names your inputs and their dates — if the timeline silently assumes finished copy, it is already wrong. Where do I see progress? A staging link you can open any time beats weekly status promises. How many feedback rounds are included, and how do changes re-price? Vague answers here become the week-five argument. What happens at launch, exactly? Redirects, sitemap submission and post-launch tests should be named, not implied. And what is the busiest-season effect? A developer who knows their calendar will tell you which weeks to avoid. None of these questions is hostile — good developers answer them in the proposal already, because a client who understands the timeline is the client who launches on it.
Conclusion
Plan on 4–8 weeks for a custom business website, 6–12 weeks for eCommerce, and 3–6 months for a custom application in 2026 — and start your content the week you sign, because that, not coding, is what decides your launch date. A written scope, one approver, and a disciplined launch checklist turn a hopeful estimate into a real date.
Asad Webs works to a published phase plan like this one on every WordPress, WooCommerce, Laravel, and Next.js project, with a staging link you can watch progress on. Tell us your deadline and your pages — we will tell you honestly whether it fits, and what a phased launch would look like if it doesn't. More planning guides live on the Asad Webs blog.
Have a launch date in mind? Book a free consultation — tell us your deadline and your pages, and we will tell you honestly whether it fits, and what a phased launch would look like if it doesn't.
Frequently Asked Questions
How long does it take to build a small business website?
Two to four weeks when content is ready: roughly one week for planning and design, one to two for development, and a few days for review and launch. Unfinished copy is the most common reason it stretches to six.
How long does an eCommerce website take to build?
Six to twelve weeks for most stores. Beyond the standard phases, catalogue preparation, payment-gateway approval, shipping and tax configuration, and checkout testing add real time — starting product data early is the biggest accelerator.
Can a website be built in one week?
A simple landing page or small template-based site, yes — if copy, images, and approvals are ready on day one. A custom multi-page website in a week means testing and SEO setup are being skipped, which usually costs more to fix than it saves.
What delays website projects the most?
Late content and approvals cause roughly half of delays, followed by mid-project scope changes and waiting on third parties such as payment gateways and account access. All three are preventable with a week-one checklist and a single decision-maker.
When should I start if I need a website for a specific date?
Work backwards: subtract your site type's timeline, then add two buffer weeks. For an eight-week custom site tied to a fixed event, starting ten weeks out is the realistic minimum — and your content work should start the same week as the project.
Do I need to wait until the whole site is finished to launch?
No — a phased launch is often the smartest schedule move. Put the core pages (home, main services, contact) live on the main date, then add secondary pages, case studies and extra features in the following weeks. You start collecting enquiries and search visibility earlier, and the remaining work proceeds without launch-day pressure. The requirement is a scope that separates 'launch-critical' from 'phase two' honestly at the start.
How do holidays and busy seasons affect website timelines?
Directly: feedback rounds stall when approvers are away, gateway and registrar support slows, and developers run reduced cover. A six-week project spanning a major holiday period is realistically seven to eight. If your launch date is fixed and important, either start early enough to clear the holiday entirely or plan the phases so the holiday falls inside development — the phase that needs you least.
Be the first to share a useful question or thought.