Lorixen.
EN

What Slows Down a Small Business Website Project (and How to Avoid It)

Short answer: A small business website rarely runs late because of code. It stalls while waiting for copy, photos, logins to the domain, or a decision nobody feels entitled to make. Name one decision owner on your side, hand over every access detail in the first week, agree content deadlines before design starts, cap feedback at two rounds per stage, and hold a 15-minute check-in every week. Those five habits remove most of the waiting that turns a six-week build into a four-month one.

Where the time actually goes

When we look back at projects that overran, the calendar usually shows long gaps between short bursts of work. The developer finishes a page template in two days, then the page sits for three weeks because the "About us" text is still being drafted by a partner who is on holiday. Delays come in phases, and each phase has its own typical blocker.

Phase Typical blocker Who can unblock it
Kick-off Nobody can log in to the domain registrar or old hosting Owner or whoever bought the domain
Structure and wireframes Disagreement about which services to list Decision owner
Design Endless colour and font tweaks from several people Decision owner, with a round limit
Content Copy, team photos, prices, case studies not ready Content contributors with fixed dates
Build and review Feedback arrives in scattered emails and voice notes One consolidated feedback list
Launch DNS change needs a code from an old IT supplier Owner, prepared in week one

The pattern is clear: almost every cell in the right-hand column is on the client side. That is not a criticism. It simply means the schedule is in your hands more than you might expect.

Name one decision owner

Pick a single person who has the final word on layout, wording and launch. Other people can comment, but their comments go to that person, who merges them and sends one answer. Without this, a café owner, her business partner and the head chef may each reply to the same design with different instructions, and the designer has to wait while they settle it among themselves.

The decision owner also needs time in the diary. If they can only look at the site on Sunday evenings, plan the review cycle around that rather than pretending they will reply within a day.

Hand over access on day one

Missing logins cause the most frustrating kind of delay, because they often surface at the very end, on launch day. Gather these before any design work begins:

  • Domain registrar login, or at least someone who can change DNS records when asked
  • Current hosting control panel, if the old site will be migrated or backed up
  • Email provider admin, so mail records are not broken when DNS moves
  • Google Business Profile, Search Console and Analytics access
  • Social media accounts that will be linked or embedded
  • Booking, payment or newsletter tools the site must connect to
  • Brand files: logo in vector format, fonts, colour codes

If a former web designer or an IT contractor holds any of these, contact them now. Recovering a domain account through the registrar's identity checks can take days, and you do not want that clock starting the morning you planned to go live.

Set content deadlines before design starts

Content is the single most common reason a site misses its date. Writing about your own business feels easy until you sit down to do it. Break it into dated deliverables and assign each to a named person:

  1. Week 1: list of pages and one sentence on the purpose of each.
  2. Week 2: service descriptions and prices, even rough.
  3. Week 3: team bios, photos and testimonials with permission to publish.
  4. Week 4: legal pages such as privacy and cookie notices, reviewed by whoever handles compliance for you.

If a piece is late, agree in advance what happens: the page launches with a shorter placeholder written by the developer and gets replaced later, or the launch date moves. Deciding this rule at the start removes an awkward conversation later. Accessibility is easier to plan in at this stage too; the W3C planning guidance is a sensible reference for what to ask for.

Limit approval rounds

Unlimited revisions sound generous but they quietly destroy timelines. Agree a structure such as:

  • Wireframes: one round of feedback, one round of corrections.
  • Visual design: two rounds.
  • Built pages: one consolidated list per page, then fixes.

Feedback should be gathered into one shared document or spreadsheet with a column for the page, the requested change, and a screenshot. Scattered messages lead to missed items, which lead to a third and fourth round that nobody planned for. If you discover something genuinely new during review, such as wanting an online booking feature, log it as a change request with its own estimate instead of squeezing it into a revision round.

Run a 15-minute weekly check-in

A short, fixed meeting keeps small problems from growing. Use the same agenda every week:

  1. Done since last week (2 minutes): what was delivered on each side.
  2. Waiting on (5 minutes): every open item, who owns it, and the new date.
  3. Decisions needed (5 minutes): anything the decision owner must settle today.
  4. Next week (3 minutes): what each side will deliver before the next call.

Keep a running list in a shared document so the history is visible. If the "waiting on" list keeps the same items for two weeks, that is your early warning that the launch date is at risk. Working in short visible cycles like this is the same principle public sector teams use, described in the GOV.UK service manual on agile delivery.

Realistic timelines

How long a website takes depends far more on readiness than on size. As a rough example, a five-page brochure site with content ready on day one might take four to six weeks. The same site where content is written alongside the build can easily take ten to twelve. A shop or a site with bookings and integrations adds time for testing payments and connected tools. Ask your developer for a timeline that shows which dates depend on you, so you can see the cost of a late deliverable.

FAQ

How long should a small business website take to build?

For a simple site with content ready, several weeks is common. Add time for every feature that connects to another system and for any content still being written. Your own response times have the biggest effect.

What if we cannot finish the copy in time?

Launch with short, accurate text for the late pages and improve them after go-live. A clear, brief page is better than a finished site that waits a month for perfect wording.

Can several people give feedback on the design?

Yes, but route it through one person who merges it before it reaches the developer. That avoids conflicting instructions and extra rounds.

Why ask for domain access so early?

Because recovering a lost registrar login or chasing a former supplier can take days, and launch depends on it. Sorting it in week one removes the biggest last-minute risk.

If you would like a build plan with clear dates on both sides from the start, tell us about your project and we will map it out with you.

Sources

WhatsAppBook a call