How Long Does It Take to Build a Small Business Website?

A small-business website can go live in a few days or take several weeks. The number of pages is rarely the deciding factor. The model (managed presentation versus a custom build), how ready the content is, and how fast decisions get made matter more. When services, photos and a contact path are clear, a presentation site launches much faster than a site you are still inventing during production.

Short answer

If copy and photos are ready, a realistic range looks like this:

• Managed presentation for a local business: days to a short week through review and launch.
• A more demanding managed site with extra features: a week or more, depending on integrations.
• Custom website: a first proposal in about a week, launch usually after several weeks.

These are planning ranges, not hourly guarantees. If the content is missing, every range stretches - often more because of waiting than because of the build.

What actually sets the timeline

Delivery time has four parts. The technical build is only one of them.

1. Scope. What the site must do: present the business, collect a call, send people to a booking, or something more.
2. Content. Copy, photos, prices or ranges, proof, company details.
3. Build and review. Structure, brand adaptation, form, mobile layout.
4. Launch. Domain, hosting, basic SEO, legal pages, a working form check.

Most delays sit in 1 and 2. Sites do not stall because “the code is slow”. They stall because the offer is still fuzzy, or because photos arrive a week after the agreed review.

That is why a brief before a fixed quote is useful. It is not paperwork. It is how the calendar stays honest.

Managed sites: when they move quickly

A managed small-business website already has a known structure: who you are, what you offer, why someone should trust you, how to get in touch. Production is adapting that path to your business, not inventing an architecture from scratch.

The sequence is short:

1. you send services, photos, brand details and the action you want visitors to take;
2. I prepare the site and share a review link;
3. we tighten the content together, then the site goes live.

That can be fast when the materials are usable. “Usable” means:

• a service list a buyer understands;
• some real photos (space, work, result);
• name, phone, email, service area;
• one clear next step (call, form, booking).

If those are missing, we are gathering content first. That is not production. It should show up on the timeline as its own step.

Custom sites take longer - and should

On a custom website, the first week is usually consultation, scope, a content plan and a first proposal on a staging link. The build continues from week two. Launch happens when structure, content, basic SEO and any integrations are actually ready.

It takes longer because you have to define:

• a unique information architecture;
• a visual system, not just a colour palette;
• more paths (services, examples, languages, forms);
• connections to tools the company already uses.

If you squeeze that into “same as a presentation site, just faster”, you get a weak custom site. The timeline has to follow the scope. So does the price - see what determines the cost of a custom website.

Content is the bottleneck

The same pattern repeats. The agreement is clear, the layout moves, then everyone waits for:

• a logo in a usable resolution;
• photos that are not only a dark phone shot - or any photos at all;
• a decision on whether prices go on the site;
• permission to name a reference;
• legal company details.

None of that is “design”. All of it blocks launch. A site without real services and a real contact should not go live just to hit a date on paper.

If the content is not there yet, two honest options exist:

• collect the minimum (offer, contact, 5–10 photos) and launch a narrow site;
• or wait to start production until the business knows what it wants to say.

The second option is often cheaper. Less looping, fewer rewrites.

What speeds up launch

If you want a short timeline, prepare this before the first call:

• one primary job for the site - call, enquiry or booking;
• a service list in the buyer’s language, not internal labels;
• photos that show the work, the space or the result;
• a contact you actually read;
• what is in the first release and what can wait.

You do not need final copy. You do need enough that the site is not guessing on your behalf. If you want a budget range next to the timeline, read how much a small-business website costs in Slovenia.

What stretches the date

Common delays that are not technical:

• changing the offer during review;
• “just one more section” after scope is closed;
• several equal decision-makers and no single content owner;
• waiting on photos that “a cousin will take”;
• wanting a blog, a shop and bookings in the first release.

Every extra feature is a new timeline. A booking system, a second language or a calendar integration is not a small add-on. It is scope.

Same “one-pager”, two calendars

A local service with clear packages, ten photos and a phone number can review a presentation site and launch in a short cycle. The same trade with unnamed services, no photos and a brief that says “something modern so we stand out” is a different project. The second case needs decisions before you start counting production days.

Do not only ask “how long does a website take”. Ask how long this website takes, with this content.

Frequently asked questions

Can you launch in a week?

If it is a managed presentation and the materials are ready, a short timeline is realistic. If the content is missing or the project is custom, a week is usually not an honest promise.

What if I do not have copy yet?

We can start from a skeleton and write the essentials together. We cannot launch a site that invents your prices, service area or services.

Do a blog, shop or bookings stretch the timeline?

Yes. The first release should include only what the site needs to do its main job. The rest can follow once that path works.

Do the domain and hosting affect timing?

A domain you already own speeds launch. A transfer, a new registration or waiting on logins can add a day or two - rarely weeks, unless the old provider has locked the account.

Closing

A website timeline is mostly a readiness question, not a tooling question. A managed presentation can move quickly when you know what you sell. A custom project needs more time because it solves a larger scope. In both cases, content and decisions set the calendar more than the build.

If you want a timing estimate for your case, the package details are on small-business websites and on pricing. Send a short description of the business via contact; I reply in under 24 hours.

← Back to the blog