A straightforward small-business website can often be built in days or a few weeks. Larger sites can take much longer. In practice, the biggest delay is often not the coding or design — it is waiting for decisions, photographs and content.
That is worth knowing before a project starts because website timelines are often described as though they are purely a measure of technical complexity.
They are not.
A small site with a clear brief and a responsive client can move quickly. A similarly sized site can drift for months if nobody can decide what it should say.
A five-page site does not inherently take three months
There are agencies whose process genuinely requires several weeks because they have discovery sessions, copywriting, design sign-offs, internal handovers and scheduled development phases.
That can be appropriate for a large project.
But a straightforward small-business site does not automatically need that amount of process.
If the business is clear, the scope is controlled and the person building the site can make decisions quickly, the work can move much faster.
That is part of how I structure Built by Gavin.
You deal directly with the person designing and building the site. There are no account-management layers passing the project from one department to another.
What actually determines the timeline?
The first factor is scope.
A compact launch site for a single-service business is naturally quicker than a site with fifteen services, a large portfolio and multiple integrations.
The second is content. If there are good photographs, clear service information and a business owner who can answer questions quickly, the design has something real to work with.
The third is decision-making. A project with one owner who can say "yes, that feels right" moves very differently from one where every line needs approval from five people.
Functionality matters too. A contact form is straightforward. Connecting several external systems, migrating a large site or building custom functionality requires more testing.
Real-world example
One of the most common project delays is not development at all. It is waiting for a paragraph about the business, a price list, photographs or a final decision on services. That is why I prefer to get as much of the structure and draft content moving as possible instead of leaving a client staring at a blank document. A website can be technically straightforward and still sit unfinished for weeks if the content process is not managed.
Content is the delay nobody budgets for
I have seen this problem before in small-business work.
The website itself is ready to move, but the project stops because the client has been asked to "send the content".
That request sounds simple until you realise the client is being asked to become a copywriter, photographer and information architect in their spare time.
They mean to send it.
Then the week becomes a month.
My preference is to reduce that burden. I can get a surprising amount from a focused conversation, an existing Facebook page, a Google Business Profile, old leaflets, service lists and a handful of photographs.
The client still needs to verify that the information is correct and provide genuinely personal material, but they should not have to write a perfect website before I am allowed to build one.
That is why I have a separate guide on getting a website built when you have no content.
What can make a site move very quickly?
Clarity.
If I know what the business does, who it serves, the services, the location, the main call to action and the general visual direction, a lot of uncertainty disappears.
A small site also moves faster when the scope is sensible. Trying to add every possible feature "while we're here" is how a focused project becomes a moving target.
Choosing the pages the business actually needs at the start helps enormously.
What slows a project down?
Changing the brief halfway through is the obvious one.
So is adding new services, rewriting the brand, deciding a booking system is required after all or discovering that nobody owns the domain account.
Photography can also become a bottleneck. A site might technically be ready while waiting for the photographs that make the design feel finished.
None of these are disasters. They just mean the project is doing more than originally planned.
How fast is too fast?
Speed is not automatically a virtue.
A website can be produced very quickly and still be poor if nobody has thought about the business.
The goal is not to boast that a site was built in three hours.
The useful goal is a short, efficient project with enough thinking to make good decisions.
That balance is different from rushing.
Gavin's take
I think small-business website projects are often allowed to become much slower than they need to be. Speed should not mean rushing the thinking, but neither should a focused brochure site automatically become a three-month project with layers of meetings and hand-offs. My preference is to make decisions quickly, build a strong first version, then use focused feedback to finish it.
How Built by Gavin approaches turnaround
My projects are deliberately kept lean.
For a straightforward site, I would much rather establish the core information early, produce something tangible quickly and refine it than spend weeks creating documents about what the website might eventually become.
Every site is custom-built for the business. The speed comes from a focused process, not from dropping a logo into a generic template.
The exact delivery time still depends on the project, and I would rather give a realistic timeframe after seeing the scope than publish a fake "48-hour website" promise.
What should you prepare before the project?
You do not need a creative brief.
The most useful preparation is simply knowing the facts of the business: services, customers, areas covered, contact details, prices where applicable, photographs you already have and anything customers regularly ask before buying.
I cover that in more detail in what a web designer actually needs from you.
The bottom line
For a small business, website projects should not automatically drag on for months.
A focused site can move quickly when the scope is clear and the information is available.
The most common delays come from uncertainty and missing content rather than the act of building the pages.
That is why a good process should make it easier for the business owner to supply what matters instead of handing them a giant homework assignment.
Have a deadline in mind?
You can see my current website options or tell me what you need and when you need it.
I can tell you whether the timeframe is realistic once I understand the actual scope.
---