🤝 Choosing & hiring

How Long Does It Take to Build a Website? (Real Timelines)

How Long Does It Take to Build a Website? (Real Timelines)

TL;DR

  • A simple one-page site usually takes 2–5 working days. A site of several pages takes 1–3 weeks. A complex online store takes 4–8 weeks.
  • When the work drags on for months, it’s rarely because the job is hard. More often, new pages get added along the way. Or the program the site runs on takes a long time to set up. Or the developer is waiting for your texts and photos.
  • A lot of the timeline depends on you: how quickly you send your texts, photos and logo, and how quickly you reply to drafts.
  • Ask the developer for a timeline step by step, not one number. For example: “talking it through, 2 days; building the site, 4 days; launch, 1 day”. A developer who can answer like that knows how their work is organized.

You asked three developers how long your website would take. One said “two weeks”. The second said “eight weeks”. The third said “three months”. It’s the same project. Who’s right? And why are you so often promised eight weeks, and still waiting in month five?


Why Eight Weeks Turn Into Six Months

Usually, the developer isn’t lying. The timeline slips for five reasons that add up. And few developers mention them up front.

The site grows along the way. You started with three pages. Halfway through, you added a blog, a gallery and a booking form. Each addition means days or weeks. A site that keeps growing is the main reason timelines slip, and most often it grows at the client’s request. A good talk at the start pins down what the site includes. But new ideas still come up. What matters is whether you save them for later or let them push back the whole plan.

The website software needs a long setup. Some sites run on software that has to be set up first. For example, WordPress is a program many sites are built with. It needs a database, a collection of texts that WordPress builds the pages from. It also needs security add-ons (small extra programs that protect the site), and a check that the add-ons don’t get in each other’s way. That can take 1–2 weeks before the first page appears. You pay for work you can’t see. From your side, it looks as if nothing is happening.

The developer is busy with other clients. You’re rarely the only client. If a developer has 5 projects at once, eight weeks of work stretch over 16 weeks on the calendar. That’s not a lie, just arithmetic. But it’s rarely said up front. Ask how many projects the developer runs at the same time.

The developer is waiting for your texts and photos. Pages can’t be built without your texts and photos. If you take 3 weeks to gather them, the site is 3 weeks late. Many developers won’t chase you, so as not to seem pushy. This is the reason people forget most often, even though it’s the one you can fix yourself.

The changes keep coming. “I don’t like the top of the page.” “Can we have different colors?” “Let’s move everything around.” Each round of changes adds 2–5 days. Three rounds add almost two weeks. Changes are normal. But if nobody puts a limit on them, the timeline drifts. It works best with one or two rounds of changes, after which the work moves on.

Related: How Much Does a Website Cost in 2026? — the longer the work runs, the more the site usually costs.


What Your Timeline Depends On

The timeline depends on four things. Only one of them is about the developer.

How many pages. One, five or twenty. The more pages, the more work on design, texts and checking. A one-page site has one layout. A ten-page site has ten.

What the site has to do. A contact form is simple: a few hours of work. Online payments, booking or customer accounts take much longer. Each of these features has to be planned, tested and protected on its own. The difference between a page with a form and a page with payments can be weeks.

Whether your texts and photos are ready. If the texts, photos and logo are ready on day one, the work moves fast. If you’re still writing your About text in week three, the work stands still. This is the factor people underestimate most.

What the site is built with. Some sites first need a server, a database and security set up. A server is a computer that’s always on and stores the site. Other sites can be built straight away, without that setup. So the choice of what to build with can add or save a week before you see the first page. More on this: why your website doesn’t need to be complicated. That post explains why a simple site is faster and cheaper to build, and more reliable to run.


How Long Different Sites Usually Take

No “it depends”. Here are honest timelines for each kind of site.

A one-page site: 2–5 working days. One page, one job. The page itself is quick to build. More time goes into talking it through, the texts and your changes. If the texts are ready and you reply quickly, 2 days can be enough. If you need help with the texts or many changes, count on closer to 5 days.

Our Starter plan is a one-page site. It’s usually ready about 7 days after we have everything we need from you.

A site of 5–10 pages: 1–3 weeks. Home, services, about you, contact, maybe a blog. Each page needs its own design, its own text and its own check. The timeline depends on the number of pages and how quickly you send texts and reply to drafts. A 5-page site with ready texts can be done in a week. A 10-page site whose texts are written along the way can take three.

Our Business plan is a site of up to 10 pages. Bigger sites take longer. You get an exact date before the work starts.

An online store: 4–8 weeks. Product pages, a cart, payments, stock, delivery. The work really is complex, and the timeline reflects that. If someone promises you a full store in a week, it’s either not true or the store will be bad. A small store with 10 products and simple payments is closer to 4 weeks. A large store with hundreds of products and several delivery zones takes 8 weeks or more.

A complex program on a website: 8 weeks and up. Customer accounts, reports for clients, a custom database, links to other software. That’s no longer a website; it’s software development, with different timelines. It needs a programmer, not someone who builds websites.

We build only sites made of ready-made pages: each page is a finished file, with no program running behind it. We don’t build online stores with a cart, or complex programs. For simple sales, a payment link or a store on a service you already use is often enough.

All these timelines hold if your texts and photos are ready and you reply quickly. If you take 2 weeks to send photos, add 2 weeks to any timeline. The developer’s speed is only half of it. The other half is how quickly you reply.


Three Steps: Talking It Through, Building, Launch

A good developer can give you a timeline for each step. Here’s how it works with us.

Step 1: Talking It Through (Days 1–2)

You write a couple of sentences about what you do and send a link to a site you like. We have a short call or swap a few emails: about 30 minutes, whichever suits you. Within a day or two, you get a plan. It lists the pages, what goes on each, the look, the launch date and a fixed price. Nothing starts until you say yes.

This step is also where we pin down what the site includes. That way, the site doesn’t keep growing during the work. If you’re comparing developers, ask how they start. A developer who skips this step will “figure it out as we go”. That’s how a site ends up costing the most.

How the first talk works →

Step 2: Building the Site (Draft on Day 3 for a One-Page Site)

This is where the pages themselves are made: the design, the texts on the pages, how it looks on a phone, the contact form. The result is a working draft. On day 3, you open it on your phone and click through it. One round of changes is included in the price. Each further round is from €20, and we tell you the price first.

Why is this step short with us? We don’t spend the first week setting up a server, a database and add-ons. Our sites are made of ready-made pages, and they don’t need that setup. More on this: why your website doesn’t need to be complicated.

But not every site is this quick. A 10-page site in three languages takes longer than one page. We give you the exact timeline before the work starts, not after you’ve said yes.

How we build the site →

Step 3: Launch (Day 7)

You check the site and approve it. Only then do you pay. Then we put the site online at your domain (your own address, like yourname.com) and check every page. The site starts opening at your address.

The site’s files are kept in a GitHub account that belongs to you. GitHub is a service for storing files like these. Visitors get the site from Cloudflare, a company whose computers send it to everyone who opens your address. The Cloudflare account is in your name too. We also help you turn on two-step login for your Cloudflare account and for the account where you bought your domain (the registrar). Then logging in needs a one-time code as well as the password.

A site made of ready-made pages goes live almost straight away. There’s no server to set up and no security updates to install. Our post Free Website Hosting: What’s the Catch? explains how that works.

How the launch works →


Why Some Developers Work Faster Than Others

It’s not about who types faster or works longer hours. It’s about what the site is built with and how the work is organized.

What the site is built with. Many sites are built with WordPress, a program that runs on a server. WordPress keeps the texts in a database and builds each page again whenever someone opens it. To launch a WordPress site, someone has to install the program and set up the database. Then they choose and adjust a design, install the add-ons and check that they don’t get in each other’s way. That setup alone can take a week or more.

We build sites made of ready-made pages. Each page is a finished file, not a program on a server. There’s no database, no add-ons and no server to protect. So work on the pages starts on day one.

That route doesn’t suit everyone. WordPress suits you if you change the texts yourself every day. But most sites change a few times a year. For them, all that setup only adds time and cost.

How the work is organized. It helps when the work has clear steps and dates. Then there are fewer extra emails, fewer arguments about who was waiting for what, and less redoing halfway through. A developer who works like that almost always finishes sooner than one who “figures it out as we go”. If a developer can’t explain how they work, there’s probably no clear order to it.

How many clients the developer has. A developer with 2 projects finishes sooner than one with 8. It’s not about skill; it’s about free time. If a developer has 8 projects, your 5 days of work can stretch over 3 weeks on the calendar while you wait your turn. Ask how busy they are before you agree.

Related: Wix vs Squarespace vs Hiring a Developer — how long it takes to build a site yourself, and how long when you hire someone.


How to Keep Your Timeline on Track

Half the timeline depends on the developer. The other half depends on you. Here’s what you can do.

Get your texts and photos ready before the work starts. The texts for each page, your logo, all the photos. Nothing affects the timeline more. If everything is ready on day one, the work moves fast. If not, it stands still, however fast the developer works.

Decide early who writes the texts. Many developers don’t write texts well. If you wait for the developer to write them, the site may be late, and the texts may not sound like you. Write them yourself, or hire a writer early. We can write the texts too, at extra cost, and you check and approve them. Either way, the sooner the texts are ready, the sooner the site is.

Keep changes to one or two rounds. Decide what you want. Write your changes clearly and specifically. Don’t redo everything when you see the first draft. Each round of changes adds days. If you’re on round five, the problem is no longer the design: the site has grown.

Reply within two days. When the developer sends a draft or a question, answer quickly. A reply after 2 days and a reply after 7 days make very different timelines. Over several rounds of changes, the difference adds up.

Don’t add new things halfway through. Don’t ask for new pages or features in the middle of the work. If you need something else, save it for after launch. Every addition halfway through pushes back the launch date.


Website Builders: Quick to Start, Slow to Get Right

Wix and Squarespace are website builders: services where you put a site together from ready-made blocks in your browser. You can start straight away and have a site online in an afternoon. But a site that works and a good site aren’t the same thing. To make a do-it-yourself site look professional, load fast and get found on Google, you usually need weeks of extra work. And you’re still limited to what the builder can do.

With a developer, it takes longer before work begins: talking it through, a plan, building the site. But the site is done properly the first time. In the end, the total time is often about the same. The difference is in the result. On one side, a site made for your work. On the other, a template you filled in yourself between your real jobs.

Builders are useful for testing an idea, or for getting something simple online without spending money. But if you’re comparing “I’ll do it myself in 2 weeks” with “a developer will do it in 2 weeks”, don’t compare the timelines. Compare what you’ll get.


Check Whether You’re Ready to Start

Before you order a website, go through these five points:

  • I know which pages I need and what goes on each.
  • My texts, photos and logo are ready, or I know where to get them before the work starts.
  • I can reply to drafts and questions within two days.
  • I know what the site has to do (a form, booking, payments), and I won’t add new things halfway through.
  • One or two rounds of changes will be enough for me.

If two or more of these aren’t true for you yet, the work will take longer than the timelines above. Not because of the developer, but because of the preparation. Fix that before you start, and the timeline gets much shorter.


FAQ

Can a website be built in one day?

A one-page site, yes, if the texts are ready and the design is simple. A page with one job, your text and your photos can be built and launched in one working day. But only if you reply quickly and no big changes are needed. A 5-page site can’t be built in a day. Anyone who promises that is cutting corners on quality, and you’ll pay for it later.

Why was I promised 6 weeks, and it took 5 months?

Usually, there are several reasons:

  • the site grew during the work;
  • gathering your texts and photos took longer than you thought;
  • the developer had many projects at once;
  • setting up the website software took longer than planned.

Ask the developer for a step-by-step timeline and a written plan. If they can’t give you one, that’s a bad sign. Not because they’re slow, but because there’s no clear order to their work. Our post How Much Does a Website Cost in 2026? explains how timelines affect the price.

If a site was built fast, is it built badly?

Not necessarily. Speed depends on what the site is built with and how the work is organized, not on cutting corners. If a developer doesn’t need to set up a server, add-ons and a database, they’re not doing less. They’re just not doing work the site doesn’t need. The bad sign isn’t speed; it’s vague answers. You can trust a fast developer who tells you clearly what they’ll do, in what order and by when. The real risk is a slow developer who can’t explain the timeline.

What if I need my website next week?

Tell the developer straight away. A simple page can be built and launched in 2–3 working days if the texts are ready. A site of several pages in a week is possible too, but tight. You’ll have to reply very quickly, and the developer needs to be free of other urgent work. Give your real deadline honestly, and ask whether it’s realistic before you agree. A good developer will tell you the truth, even if the answer is “that’s not enough time for your site”.


Bottom Line

How long does a website take? A few days for a simple site. A few weeks for a site with many pages. A few months only for a truly complex project. The bad sign isn’t a big number; it’s a developer who can’t break the timeline into steps and explain each one.


Want to know exactly how long your site will take? We work in three steps, and each one has its own timeline. See how we work →

Ready to start? Get a free quote →