ArticlesPlan a website

How long does it take to build a website?

Plan content, feedback and launch while separating development hours from the project’s calendar.

GlomivaUpdated November 10, 20262 min read

A useful delivery estimate needs a defined scope and an understanding of the available material. A small business website and a shop with product imports need different plans. Ask for a schedule for your particular project.

Separate working time from elapsed time. A developer may finish a task while the project waits for images, access or approval.

Agree the first delivery

List the pages, languages and features required at launch. Decide what can follow later. Investigate essential bookings, payments and integrations before announcing a date.

Ask the supplier to state the schedule’s assumptions: material deadlines, feedback turnaround and external dependencies.

Use four approval points

  1. Content and structure: agree the page list, main message and contact route. Assign each text and image.
  2. Design: approve the visual direction and important page types, including mobile. Collect the company’s feedback into one response.
  3. Complete test version: content and features are in place. Try what a real customer needs to do.
  4. Launch and handover: confirm the domain, access, redirects and hosting responsibilities. Test forms and important links again after the switch.

Some activities overlap. Ask for a joined-up calendar rather than adding generic weekly estimates yourself.

Prepare the material and access

Provide a logo and images you have permission to use; correct services, prices and contact information; a decision on who writes and reviews; access to the domain and existing website; and a list of content and URLs to preserve. Name one person who can coordinate decisions and approve delivery.

Transfer credentials securely, rather than putting them in open documents or unprotected messages.

Common reasons for delay

Late features, conflicting approvers and missing product material can shift the launch. Record changes in writing: what is added, the cost and the affected milestone. Then choose deliberately between changing the scope and changing the date.

For an event deadline, consider a smaller first version. Define what visitors need and give the remaining work its own plan.

When is it ready?

Launch when the agreed scope is approved and important customer journeys work. Check mobile, forms, links, old URLs and who handles problems afterwards. Record remaining tasks with an owner and date.

Use our agency selection checklist to include these decisions in the quote.