How Long Does a Small-Business Website Take to Build?
By Parker Gawryletz · Local Cochrane Web Design · Last updated: · 8 min read
Most small-business launch sites take four to eight weeks from kickoff to launch, as a typical planning range — once the content is ready. Full custom builds usually run longer, and e-commerce longer still. The biggest variable is not the designer's speed; it is how quickly content, feedback, and approvals arrive.
"How long does a small business website take to build?" is usually the second question owners ask, right after price — and the honest answer is a range, not a date. Two five-page sites can take very different amounts of time, because the schedule depends on content, decisions, and feedback as much as design.
This guide walks through each stage, the typical planning ranges by project type, and the five delays you can prevent before they start. It reflects how custom web design in Cochrane projects actually run — with your role in the schedule stated plainly.
The short answer
- Launch sites typically take four to eight weeks once content is ready.
- Full custom builds and e-commerce projects usually run months, not weeks.
- Content arriving late is the most common cause of delay.
- Ask for a written schedule with milestones and your dependencies listed.
- Accelerated launches only work when content and decisions are ready first.
Typical ranges by project type
As typical industry planning ranges — not guarantees — a launch site of five to seven pages runs about four to eight weeks, a full custom build roughly two to four months, and an e-commerce or platform build three to six months. Every honest schedule depends on content being ready.
| Project type | Typical range | What moves it |
|---|---|---|
| Launch site (5–7 pages) | 4–8 weeks | How quickly content, photos and feedback arrive |
| Full custom build | 2–4 months | Page count, custom features and integrations |
| E-commerce or platform build | 3–6 months | Product data, payments and third-party systems |
| Redesign with URL migration | Similar to a launch build | Existing content quality and the redirect map |
Treat these ranges as planning guidance. The schedule that actually binds anyone is the one written into your proposal, with milestones and dependencies — what a web design quote should include covers that timeline line item in detail.
Week 1: discovery, goals and page map
The first week sets the whole schedule: a kickoff conversation about your goals, customers, and what success looks like, then a page map naming every page the site needs. Projects that skip discovery move faster for a week and slower for a month, because unanswered questions resurface as revisions.
You can shorten this week before it starts. Arrive with a plain list of your services, the customers you want more of, two or three websites you admire, and access details for your domain. Discovery is fast when the answers already exist — it drags when they are being invented in the meeting.
Content collection and copy development
Content is the longest and least predictable stage. Decide early who writes the copy and who supplies photos, then set a content deadline that lands before design approval. When owners supply their own content, this stage often takes longer than the design itself — plan for it honestly.
Whether the designer writes your copy or you do, the words need to exist before the build stage begins, because copy shapes layout. The website content preparation checklist lists exactly what to gather, page by page, so nothing waits on a missing paragraph.
Design concept and approval
Expect a design concept or mockup to review, two or three structured revision rounds, and a written approval before the build begins. This stage usually spans one to three weeks, and it moves at the speed of your feedback — consolidated comments within days, not scattered thoughts over weeks.
The fastest clients gather everyone's opinions once, resolve disagreements internally, and send one clear round of feedback. Ten separate emails over two weeks count as ten interruptions, not one revision — and each one restarts the designer's queue.
Build, integrations and responsive implementation
The build turns the approved design into a working website: pages assembled, forms connected, integrations wired, and the layout implemented properly for phones, tablets and desktops. For most small-business sites this takes one to three weeks — longer when bookings, e-commerce or custom features are involved.
Integrations are the quiet schedule risk here. Booking systems, payment accounts, review feeds and maps all need logins or approvals from third parties. Hand over that access at kickoff, because a build that stalls waiting for a password looks identical to a build that stalled for real reasons.
Quality assurance, redirects and analytics
Before launch, every page is checked on real devices, forms are tested end to end, redirects are mapped from any old URLs, and analytics and Search Console are set up. This stage is short — days, not weeks — but skipping it is how launches turn into emergencies.
- ☐ Every form tested end to end, with a test enquiry received
- ☐ Redirects mapped one-to-one from any existing site's URLs
- ☐ Unique page titles and meta descriptions on every page
- ☐ Analytics installed, with tracking on the contact action
- ☐ Layout and speed checked on a real phone, not just a laptop
Launch and post-launch verification
Launch day itself is short: the site goes live, redirects are confirmed by hand, and the sitemap is submitted. The first weeks after launch matter more — verify that forms deliver enquiries, pages index, and nothing broke. A 30-day post-launch fix window is a reasonable baseline to ask any provider for.
Small issues surface after every launch — a form quirk on one phone model, a typo nobody caught. That is normal. What separates providers is whether fixing those issues in the first month costs you extra, so get the post-launch window in writing before you sign.
The five delays clients can prevent
Most website delays are not design problems. The five most common are content arriving late, slow feedback, scope additions mid-project, missing third-party access, and approval bottlenecks when the decision-maker is unavailable. All five sit on the client side of the schedule, and all five are preventable.
- Content arrives late — pages cannot be built around missing words and photos, so the timeline pauses.
- Feedback is slow — every draft waiting a week adds a week; batch comments into one round.
- Scope grows mid-project — new features added mid-build restart design work that was already approved.
- Third-party access is missing — domain, hosting and booking-system logins stall integrations for days.
- Approvals bottleneck — name one decision-maker before kickoff, and keep them reachable.
When an accelerated launch is realistic
A faster launch is realistic when the copy is written, photos exist, the page count is small, and one decision-maker can approve within a day. It is not realistic when content is unwritten or features are undecided — compressing those projects just moves the delay past launch day.
If speed matters, say so in the first conversation and ask each provider exactly what they need from you to hit the date. Local Cochrane Web Design answers every enquiry with a written, itemised proposal within one business day, so the schedule conversation starts immediately. Still weighing providers on timeline and process? Start with compare Cochrane web design companies.
Frequently asked questions
How many weeks does a business website take?
As a planning range, a five-to-seven-page launch site typically takes four to eight weeks from kickoff once content is ready. Larger custom builds usually run two to four months. The exact schedule should appear in your written proposal, with milestones and your responsibilities listed beside the designer's.
What delays a website project?
The five most common delays are content arriving late, slow feedback on drafts, scope additions in the middle of the build, missing third-party access such as domain or hosting logins, and approval bottlenecks. Content is the biggest one, which is why it should be gathered before kickoff.
How long does a redesign take?
A redesign often runs on a similar schedule to a new launch site, because content decisions and approvals drive it the same way. Migration work — mapping old URLs to new ones with redirects — adds planning time. Ask for the schedule and the redirect plan together, in writing.
Can a website be built in two weeks?
Sometimes, but only when the conditions are right: finished copy, existing photos, a small page count, and a decision-maker who approves within a day. If content is unwritten, a two-week promise usually means launching with placeholders. Ask what any accelerated schedule assumes from you before agreeing to it.
When should content be ready?
Ideally before design approval, and at the latest before the build stage begins. Copy shapes layout, so pages designed around placeholder text often need rework once real words arrive. Agree a content deadline in the proposal, and ask whether the timeline pauses if content runs late.
How many revision rounds are normal?
Two to three structured revision rounds per stage is a healthy standard. The schedule should state how many rounds are included, how long each review window lasts, and how extra changes are priced afterward. Consolidated feedback in one round protects both the quality and the launch date.
Sources
Get a written project schedule — a scoped Cochrane build with milestones, your dependencies, and the launch checklist stated in writing before any work begins.