A professionally built small business website takes four to eight weeks from kick-off to launch (elementor.com, 2026). A simple brochure site can ship in one to two weeks; an online store needs eight to twelve; a custom web application needs months. Here is the part most guides bury: the technical build is the fast part. Content, decisions and revisions set the real timeline (wbcomdesigns.com, 2026).
Honest timelines by website type, where the weeks actually go, the two phases that stretch every project, and a realistic week-by-week plan — in that order.
Honest timelines by website type
Ranges below are for professional builds — discovery through launch — compiled from 2026 agency guides (elementor.com, 2026; wbcomdesigns.com, 2026; yellowcircle.co.uk, 2026):
| Website type | Typical professional timeline |
|---|---|
| Simple brochure site (5–10 pages) | 1 – 2 weeks (template) / 6 – 10 weeks (custom) |
| Business website with blog (10–20 pages) | 4 – 8 weeks |
| Online store | 8 – 12 weeks (simple) / 10 – 20 weeks (complex) |
| Custom web application / portal | 3 – 6+ months |
A serious B2B website with strategy, content and integrations typically lands around twelve weeks as a planning baseline (rubikdigital.co.uk, 2026). DIY builders are faster — days, not weeks — but a different product with different limits.
Where the weeks actually go
A six-week project is not six weeks of continuous building. It is a sequence of phases, each with its own milestone (rubikdigital.co.uk, 2026):
| Phase | Typical duration | Milestone |
|---|---|---|
| Discovery and scoping | 1 – 2 weeks | Signed-off scope, goals, sitemap direction |
| Information architecture and UX | 1 – 2 weeks | Approved wireframes and page hierarchy |
| Content planning and production | 2 – 4 weeks (often overlapping) | Final copy and images for priority pages |
| Visual design | 1 – 3 weeks | Approved homepage and page templates |
| Development and integrations | 2 – 6 weeks | Working site on a staging link |
| QA, UAT and SEO checks | 1 – 2 weeks | Issues resolved, redirects mapped, tracking tested |
| Launch and bedding-in | A few days – 1 week | Site live, team trained, monitoring on |
Notice that development — the part people picture when they ask "how long" — is only one row. Everything around it is decisions, content and verification. To de-risk the content phase specifically, assign every page an owner and a deadline in week one, and treat missed content deadlines the way you would treat a missed delivery from any other supplier: the timeline moves, visibly, the same week. Projects that track content like a deliverable ship on time; projects that treat it as "we will get to it" do not.
The two phases that stretch every timeline
Two phases cause most overruns, and both sit mostly with the client, not the builder (wbcomdesigns.com, 2026). Content is the most underestimated phase by far: copy that was "almost ready" arrives three weeks late, product photos need a reshoot, and suddenly the build team is waiting. Revisions are the phase most likely to balloon: each feedback round feels small, but four rounds with a committee cost a month. The fix for both is structural, not motivational — which is the next section.
What speeds a project up
- Content ready on day one. Final text and images for priority pages before design starts removes the single biggest delay risk.
- One decision-maker. Projects with a single approver move roughly twice as fast through design as those decided by committee.
- Frozen scope after discovery. Changes after the build starts are the most expensive kind — see our guide to the discovery phase for why this step exists.
- Template versus custom decided early. A premium template with custom branding ships weeks faster than design-from-scratch; the trade-off is originality, not quality.
- Third parties lined up. Domain access, hosting logins, payment-gateway approvals and API keys arranged in week one, not requested in week six.
- Async design reviews. Recorded walkthroughs with timestamped comments beat live meetings for keeping two revision rounds to two rounds.
- Reuse where it does not show. A proven contact-form pattern or CMS block library is not cutting corners — it is spending design time where visitors actually look.
What quietly drags it out
- Late content — the number one delay on small business projects, by a wide margin.
- Committee feedback: contradictory revision notes that cancel each other out across rounds.
- Scope creep: "while you are at it" features added mid-build without adjusting the timeline.
- Third-party dependencies: payment gateway approvals, app-store reviews, data feeds from another vendor.
- Skipped discovery. Rushing the planning phase feels fast and repays itself as rework in week five — the rework always costs more than the planning would have.
- Untested assumptions about integrations. "The API documentation looks fine" is not the same as a successful test call; one failed integration discovered late can idle the whole build.
If your project involves custom software rather than a standard site, the same dynamics apply at larger scale — our custom software development process maps the longer version of this timeline.
A realistic 8-week plan
For a typical 10–15 page business website, this is what "on track" looks like:
- Week 1: kick-off and discovery — goals, audience, sitemap direction, success criteria.
- Week 2: wireframes and content plan — page hierarchy approved, copy assignments with deadlines.
- Weeks 3–4: visual design — homepage first, then templates; feedback consolidated into two rounds maximum.
- Weeks 5–6: build — development on staging, integrations wired, content populated as it arrives.
- Week 7: content completion and QA — final copy in, testing across devices and browsers, SEO basics.
- Week 8: launch — redirects live, analytics verified, team trained on the CMS.
Four weeks is achievable when the client arrives with content, clear feedback and fast approvals; six to eight is realistic for most businesses doing this the first time (creatif.agency, 2026). And plan for weeks nine and ten as well: the bedding-in period, when real visitors find the broken link, the form edge case and the phone layout nobody tested. Budget a small block of the builder's time for the fortnight after launch — it is the cheapest QA you will ever buy, because your visitors do it for free and tell you about it.
FAQ
Can I get a business website in two weeks?
Yes — with a premium template, your branding, and content fully ready on day one. What you trade is originality and revision rounds. Two weeks is a sprint, not a process; it works when there is nothing left to decide.
Why do agencies take longer than freelancers?
Process: discovery, structured design rounds, QA, SEO checks and documentation. A freelancer can be faster for simple sites; an agency's timeline buys verification steps that catch the problems you would otherwise meet after launch.
Does an e-commerce site take longer?
Yes — typically eight to twelve weeks for a straightforward store. Product catalogues, payment testing, shipping rules and checkout edge cases add phases a brochure site never has.
What if I need the site by a fixed date?
Work backwards and freeze scope early: fix the launch date, then cut features — not QA — to fit it. Tell the builder the date in the first conversation; a good team will say plainly whether it is achievable and what has to give.
Planning a build? Contact us with your page list and deadline for an honest timeline.