How long does it take to build a website?

Nobody can give you an exact timeline before seeing your project. Here is what moves the schedule, and the part that is up to you.

Open monthly planner on a wooden desk
Illustrative photo.

The short answer

A small showcase site of a few pages usually takes a few weeks from the first conversation to launch. A shop, a multilingual site or an application takes longer: there is more to design, build and test. A precise schedule only makes sense once the scope of the project is written down.

What moves the schedule

  • The number of pages. Each page is planned, written, built, then checked.
  • The features. A contact form is quick. Online payment, customer accounts or a booking system take far more design and testing.
  • The languages. Each language has its own texts, to translate and proofread. Arabic also needs a right-to-left layout.
  • The content. Texts, photos, logo: this is the first cause of delay. You cannot finish a site that is missing half of its words.
  • Your answers. Each approval lasts as long as you take to reply.
The most expensive delay is the one spent redoing what was never decided at the start.

The stages, and where the time goes

We start with a conversation: your goals, your visitors, what the site has to do. It ends in a written brief. It is tempting to rush it, but a vague goal is paid for in rework later.

Next comes the mockup: how the pages are organised and the general look. You approve it before a single line of code is written. Moving a block on a mockup takes ten minutes. On a finished site, it is another story.

The build is the most visible stage, not always the longest. Pages are assembled, features connected, and you follow progress on a private version. Then we test on phone, tablet and several browsers, check every link and every form, and apply your feedback. What remains is the launch: domain name, hosting, secure connection, and a walkthrough so you know how to use the site.

A concrete example

Take a ceramicist who wants a five-page site in French and English. The first week goes on conversations and the brief. Then come the mockups, whose length depends mostly on how fast she approves them. After that, the build and the tests, and the last days go to corrections and launch. Nothing unusual in that. But at each handover between her and us, a day can turn into a week if answers drag.

How to avoid delays

  • Gather your texts, photos and logo early, even as rough drafts.
  • Name one person who has the final say, so the feedback does not contradict itself.
  • Answer approval requests quickly, even with a “not yet, but here is what I think”.
  • Keep the first version modest. Extra ideas can wait for a second phase, after launch.

Be wary of promises that are too fast

A site delivered in two days is almost always a ready-made template with your logo on it. That can be enough for a very simple need, but it is not custom work. If a provider announces a fixed timeline without asking how many pages, which features and what content, ask what is really included.

On the other hand, a provider who takes the time to ask questions, test and wait for your approval saves you from rework. A schedule that leaves room for your feedback is also more honest than one that assumes you approve everything the first time.

At YC DIGITAL

We start with a conversation, then send a written quote with the scope, the price and an estimated schedule. If the scope changes, the schedule is updated, plainly. To see how we build custom websites, or to read more answers, go to the FAQ. And to get a schedule for your own project, write us a few lines.

Have a project in mind? Let’s talk it over, simply.

Describe your idea. We reply with questions first, then with a written proposal fitted to your case.