Cost gets all the attention, but the second question every business asks is "how long?" And unlike cost, where the market varies wildly, timelines in 2026 are surprisingly consistent, when projects run properly. Here are the real numbers from across our briefs, and the reason most late projects are late.
The 2026 timelines
- Starter site (3-5 pages): 1-3 weeks. Some competent independents turn these around in days when content is ready.
- Small business site (5-12 pages): 2-5 weeks. Design round, build, content load, SEO foundations, launch.
- Content-rich or multi-location site: 4-8 weeks. The extra time is content volume and migration, not code.
- Ecommerce: 3-8 weeks. Catalogue size and integrations set the pace; fifty clean products move fast, two thousand messy ones don't.
- Web application: 2-6 months. Different animal entirely; see our guide to web app timelines.
AI-assisted development shaved real days off the build phase since 2024. It shaved nothing off the phases that actually blow timelines, because those were never about typing speed.
Where projects actually stall
Across every late project we've post-mortemed, the same culprit appears: content. The developer finishes the build and waits weeks for photos, service descriptions, staff bios and pricing that "will be ready Friday". The site sits at 90% while the invoice ages. The second most common stall is feedback lag: design approval that takes a fortnight per round. The third is scope creep mid-build. The developer being slow runs a distant fourth.
Websites aren't late because code is slow. They're late because the About page copy has been "almost done" for a month. Fix the content pipeline and you've fixed the timeline.
How to actually hit your launch date
Front-load the content. Have photos, copy and pricing ready before the build starts, or pay the developer (or a writer) to produce them as part of scope. This one decision halves most timelines.
Agree a feedback rhythm. 48-hour turnaround on approvals, one consolidated list of changes per round, two rounds. Good developers will propose exactly this; agreeing up front makes it painless.
Freeze scope at kickoff. New ideas go on the v2 list, not into the build. The v2 list is where good ideas wait without costing you your launch date.
Ask for a staged launch. Go live with the core pages, add the rest weekly. Google prefers early-and-growing to late-and-complete, and so does your cash flow.
Reading timelines in quotes
When you compare quotes (ours arrive three at a time, free, within 24 hours), treat the timeline as seriously as the price. A quote promising a full business site in three days either has your content requirements confused or is shipping a template. One quoting twelve weeks for eight pages is queueing you behind other clients. The healthy middle, two to five weeks with your content dependencies stated explicitly, signals a developer who has actually planned your project rather than guessed at it.
The bottom line
A properly-run small business website takes two to five weeks in 2026, and the variable that matters most is sitting on your side of the table: content readiness. Sort that before kickoff and even the cautious quotes start looking fast.