Ask ten agencies how long a business website takes and you will get ten different answers, from a week to six months, and every one of them will sound confident. The honest answer is less dramatic and more useful: for most small business websites, the range is two to six weeks from the first proper conversation to launch, when the content and the feedback move quickly. A single landing page can be quicker. A store, a booking system or a large site with many pages takes longer. What decides where your project lands in that range is rarely the designer’s speed. It is how ready your content is, how fast decisions come back, and how much of the site is custom work.
The stages, and where the time actually goes
1. Discover: what the site has to do
The first stage is a conversation, not a design. A good builder asks what you sell, who your customers are, what a good enquiry looks like, and what the site must do that your current site or social page cannot. The output should be a written scope: the pages, the features, what is included and what is not. This stage is short, often a few days, but skipping it is the most common reason projects overrun later, because a site built on a vague brief gets rebuilt halfway through.
Our own process runs Discover, then Strategize, then Execute, then Launch and Grow, with most projects delivered in focused sprints of about two to six weeks. That sprint shape only works because the scope is agreed before design starts.
2. Strategize and plan the pages
Next comes the structure: which pages the site needs, what each page must say, and what the visitor should do next on each one. A small business site is usually a handful of pages: home, about, services, a few service or product pages, and contact, with a blog if the business plans to publish. This is also when the content list is agreed, page by page, so nothing is discovered late. A site with ten pages does not take twice as long as a site with five pages because of design. It takes longer because ten pages need ten sets of finished words and photos.
3. Content: the stage that most often stalls
Content is the honest bottleneck in most builds, and it depends on the business, not the builder. Page copy, service details, photos of real work, and the contact and enquiry details all have to come from you, or be written with you. A builder can design around placeholder text, but a site cannot launch on it, and a project that waits three weeks for photos will take three weeks longer whatever the builder does.
The fastest way to keep this stage short is to gather before the build starts: finished service descriptions, real photos of your work, your logo, and the exact details for enquiries and orders. If writing is not your strength, say so at the start. A builder who writes with you will plan for it. A builder who assumes you will deliver finished copy will be waiting.
4. Execute: design and build
Design and build is where the site takes shape: layout, pages, mobile layout, enquiry forms connected to the tools you already use, and the technical foundations for speed and search. Mobile comes first here, not as an afterthought, because most visitors will meet your business on a phone. A focused build for a small business site usually takes one to three weeks of working time, shared with you through a preview link so you can review as it grows rather than only at the end. Reviewing as it grows is worth insisting on. A problem spotted on a half-built page costs an afternoon. The same problem spotted at launch costs a week.
5. Review, fix and launch
Review is a few days to a week: your feedback, the fixes, and a final check across phones, tablets and desktops, plus forms tested from enquiry to inbox. Launch itself is about a day: the domain pointed at the new site, any old pages redirected, search tracking in place, and a final speed check. A launch that slips usually slips in review, not in launch day itself, because feedback that takes two weeks instead of two days doubles every stage it touches.
Timelines by type of site
Use these as planning ranges, not promises. Your scope and your readiness move you inside each range.
- A single landing page, one page and one goal such as a contact form or a booking link: often one to three weeks.
- A small business website, roughly five to eight pages: often two to six weeks, and up to about ten weeks when content or feedback moves slowly.
- A larger site, ten to twenty pages with a blog or lead tracking: often eight to twelve weeks.
- An online store or a site with bookings, member logins or custom features: often eight to fourteen weeks or more, because product setup, payments, integrations and testing each add real work.
- A custom web application or platform: months, not weeks, and quoted per project.
If a quote promises a full store in a week, ask what is being left out. If a quote promises a five-page brochure site in four months with no explanation, ask what is filling that time. Both answers tell you more about the builder than the timeline does.
What slows a project down, in order
First, content that arrives late or in pieces. Second, feedback that takes weeks per round, or feedback from several people who disagree. Third, scope added halfway through, such as a store added to a brochure brief, or a booking system added after design is approved. Fourth, missing assets: no logo, no photos, no access to the domain or the old site. None of these are faults. They are normal business realities. They only become problems when nobody plans for them, so name them early and build the schedule around them.
There is one more slowdown worth naming because it looks like progress. Endless design rounds do not make a site better after a point. Two careful rounds of feedback on real content usually land a stronger site than six rounds on placeholder text, because design decisions only mean something against the real words and photos that will live on the page.
How to get launched sooner without cutting corners
Start with content, not with a builder. Write down each page, what it must say, and what the visitor should do next. Gather real photos now. Decide who gives feedback, and agree that feedback comes back within a few days, not a few weeks. Approve the scope in writing before design starts, and treat additions after that point as a new decision with a new date, not as a free extra. Ask for a preview link early, review on your phone first, and test the enquiry form yourself before launch day.
If you have a hard deadline, such as a seasonal opening or an event, say so in the first conversation. A builder can often sequence a launch around it, for example a core site first with a store or booking feature following, but only if the deadline is known before the scope is set.
The question to ask instead of “how fast?”
Speed alone is the wrong measure. A site launched in a week that no customer can use, or that you cannot update yourself, has not saved time. It has spent it. The better questions are: what will the site do for a visitor, what will it look like on a phone, can I update it without the builder, and what happens after launch? A site is not finished at launch. It needs the same care after it goes live: new content, search tracking, and small improvements as customers use it. That is the Launch and Grow part of our process, and it is where a website starts earning its keep rather than simply existing.
If you are planning a site, bring your content, your deadline and your one clear goal for a visitor, and the timeline will largely take care of itself. Two to six weeks is realistic for most small businesses, not because building is fast, but because a clear scope, ready content and quick decisions remove the waiting that makes most projects feel slow.
Our team builds business websites, including stores and booking features, and we are easy to reach through our web development services page if you would like to talk through the timeline for your own site.