How long does a website or app take to build?

A small-business website usually takes four to six weeks from the first call to going live. A mobile app usually takes eight to twelve weeks. Those are typical ranges, not promises. What moves them most is rarely the building itself. It is how quickly decisions get made and how soon your words, photos and details arrive.

What happens in those weeks?

Websites and apps go through the same stages.

1. Planning. We agree what the site or app must do, which pages or screens it needs and who it is for. This usually takes about a week.
2. Design. We decide how it looks and how people move through it, starting with how it works on a phone. You review the designs and tell us what to change.
3. Building. We turn the approved design into a working site or app that loads quickly and does not break.
4. Content. Your words, photos, prices and menus go in. This often happens while the building is under way.
5. Testing. We check it on different phones and browsers, and make sure forms send and payments go through.
6. Launch. We connect your domain and go live. For an app, this also means getting it approved in the Apple and Google stores.

The stages overlap more than the list suggests. Building can start on one part of a site while you are still reviewing the design of another. That overlap is how a website fits into four to six weeks. It also explains why one late item can hold up several stages at once.

Why does an app take longer?

An app has more parts to build. It usually needs customer accounts and sign-in, a way to take payments, somewhere to store data, and an admin area where you manage orders, bookings or users. It has to work on both iPhone and Android.

Before anyone can download it, Apple and Google each review the app. That review adds time at the end of the project, and more if a store asks for something to be changed and the app has to be sent in again. We plan for this when we set the launch date, but the stores decide how long they take, not us.

What slows a project down?

Most delays come from a few places, and you can avoid most of them.

• Content arriving late. Words and photos are the most common hold-up. A site cannot launch with empty pages.
• Slow feedback. If a design waits a week for comments, the project finishes a week later.
• Changing the plan halfway. Adding a booking system after the build has started means redesigning and rebuilding parts of the site.
• Too many decision-makers. When five people need to agree on every page, each step takes longer.
• Waiting on others. If we are waiting for access to your domain, a payment account or a supplier's system, work can stall for days.

How does one late item push back a launch?

Take a website planned for five weeks. Planning takes the first week. Design and building run through weeks two to four, and the final week is for testing and launch. The plan assumes your page text and photos arrive by the end of week two, so they can go in while the site is being built.

Now say the photos arrive at the end of week four instead. The building is finished, but the pages cannot be completed without them. Once the photos arrive, someone has to fit them into each page, check how they look on a phone and adjust any layout they do not suit. Only then can the full site be tested. Testing cannot start at the beginning of week five as planned, and the launch moves back by about as long as the photos were late.

Nothing about the build changed. Two weeks of waiting on one item turned a five-week project into a seven-week one. Late design feedback or a new feature added mid-build works the same way: the stages after it cannot start until it is settled.

How can you keep your project on time?

• Gather your text, photos and logo before the project starts, or agree who is writing them and by when.
• Name one person who gives feedback and makes decisions.
• Reply to design reviews within a couple of days.
• Decide the must-haves at the start, and leave the nice-to-haves for a second phase.
• Have your domain login, payment account and any supplier details ready before building begins.

Can it be done faster?

Often, yes, but something has to give. A faster project does less at launch, uses a simpler design, or asks the agency to move other work aside, which can cost more.

The route we usually suggest is to launch the essentials first and add the rest in a second phase. For a website, that might mean launching with your main pages and contact form, then adding a blog or online booking later. For an app, it might mean launching with the one thing customers most need to do, such as booking or ordering, and adding extras once people are using it.

What should a timeline from an agency include?

A good timeline gives a date for each stage. It also says what the agency needs from you and when, such as your content, your feedback on designs, or access to your domain. Those dates matter as much as the agency's own, because a late item on your side moves the launch in the same way.

If a quote has no timeline, or promises a complex app in two weeks, ask how they will do it. The answer tells you a lot about the agency.

Our websites usually take four to six weeks and our apps eight to twelve. We agree the dates with you before any work starts. If you want to talk through a timeline for your project, you can book a call.