Quick version before the details: a simple landing page takes 1-2 weeks, a brochure or small company site 2-4 weeks, an online store 4-8 weeks. Those are realistic timelines at a normal pace, assuming your materials don't get stuck for a month. Because most often a project stretches out not because of the code, but because of content and revisions - I'll be honest about that below too. I build sites on Next.js and online stores, so let me break the process down stage by stage with the time each one takes.
Stage 1. Brief and discovery - 1-3 days
This is where we settle what we're actually building: what the site is for, who the customer is, which pages it needs, what sets you apart from competitors, what counts as a result. For a landing page a short call is enough. For a store or a larger company site it can take a day or two, because we need to go through the catalog, shipping, payments, customer scenarios.
What the time depends on: how clearly you see what you want yourself. If you know what the site is for, the brief goes fast. If it's "make something nice, we'll see" - this stage drags, because the decisions still have to be made, just later and at a higher cost. A prepared website brief helps: when the answers are written down, we start right away.
Stage 2. Structure and prototype - 2-5 days
Before anyone draws a single pixel, we lay out the skeleton: which pages, in what order the blocks go, where the buttons are, where each click leads. This is the prototype - no color, no photos, just the logic. A cheap stage to change things in: moving a block here takes a minute, on a finished site it takes hours.
A landing page wraps up in a day or two. A multi-page site or a store with categories and filters is closer to a week. A well-made prototype shortens every stage that follows, because from then on nobody is guessing what goes where.
Stage 3. Visual design - 3-10 days
We put the visual layer on top of the skeleton: colors, typography, the style of the blocks, how it looks on a phone. For a landing page that's 3-5 days, for a brochure site about a week, for a store more, because there are a lot of cards and states (product card, cart, listing, empty states).
This is where the first real pause on your side shows up - sign-off. One round of feedback is normal and built into the timeline. Five rounds, where each time someone new has an opinion, can add more days to the project than the entire build. The fewer people deciding and the more specific the feedback, the faster it goes.
Stage 4. Build and deployment - 5-15 days
The design turns into a working site: responsiveness, animations, forms with notifications, analytics hooked up, speed. This is where the difference shows between a pretty picture and a site that loads fast on a phone and works.
A landing page is 5-7 days, a brochure site 1-2 weeks, a store 2-4 weeks and up - because payments, shipping, an order panel, integration with a CRM or warehouse get added. Worth knowing: a lot of things take the same time regardless of how many pages there are. Setting up the site template, animations, forms - similar time for 5 pages and for 15. What multiplies is mainly unique content and unusual functionality.
Stage 5. Filling with content - 2-10 days
Text, photos, descriptions of services or products. Sounds trivial, and that's exactly why this is where everything stalls most often. Writing decent text and preparing photos takes anywhere from a few days to a couple of weeks if a specialist does it. If you promise to "send the materials tomorrow" - know that this is the most common hole that timelines sink into.
It goes fastest when content is created alongside the design, not after it. That's why I ask about text and photos at the start, not at the end.
Stage 6. Testing - 2-5 days
We check the site on different phones and browsers, click through every form, make sure submissions come through, measure speed, catch typos and awkward spots. For a landing page a couple of days, for a store longer, because you have to click through the full purchase path including a test payment.
A stage that's easy to cut corners on and then regret: a site that "works on my machine" can fall apart on someone else's phone or lose submissions. Better to give it those few days.
Stage 7. Launch and indexing - 1-3 days plus waiting
The launch itself - pointing the domain, the certificate, connecting email - is hours, a day or two at most with configuration. But there's a second clock I don't control: indexing in Google. I submit the site in Search Console right away, but actually showing up in results takes days, sometimes 2-4 weeks. That's not part of "building," but worth knowing: the day of launch and the day the site starts pulling traffic from search are two different dates.
What actually drags a project out
I'll say it straight, because it matters more than the code time. Sites rarely stall over programming. They stall over this:
- Content. Missing text and photos is the number one cause of delays. "It'll be there within the week" turns into a month and the whole timeline goes.
- Revisions and sign-offs. When five people decide and each one in a different week, the project drags on rounds of feedback, not on the work.
- Scope creep. "Let's also throw in a blog, a calculator and an English version" mid-project - every addition pushes the finish back.
- Silence. One day without an answer to a question is often one day of the whole stage standing still.
So you have the biggest effect on the timeline, not the developer. The developer keeps the pace, but won't write for you what only you know about your business, and won't sign off on the design in your place.
Table - site type, timeline and what's included
| Site type | Timeline | What's included |
|---|---|---|
| Landing page | 1-2 weeks | One page for one goal, design, text, form, analytics |
| Brochure site | 2-4 weeks | A few pages, design, basic SEO, contact form |
| Company site | 3-6 weeks | Services, case studies, blog, multilingual, deeper SEO |
| Online store | 4-8 weeks | Catalog, cart, payments, shipping, order panel, integrations |
The timelines assume a normal pace and materials delivered on time. With content lagging, every line can grow.
Can it go faster
Sometimes yes. A landing page or a simple brochure site can go up in a few days if the content is ready, one person makes the decisions and sign-off happens the same day. An urgent launch can be real.
But you have to understand the limit: "fast" usually means "on a template." A ready theme, minimal changes, your text dropped into someone else's structure - that can be done in no time, and sometimes it's enough. A custom site for your business, with its own structure, fast and built for SEO, just can't physically go at that pace, because half the work is thinking through your specific case, not clicking. If someone promises "a turnkey store in 3 days" - it's either a template or they're leaving something out. How to tell one from the other, I covered in the piece on how to choose a web developer.
Budget affects the timeline too, but differently than you'd think - you're not buying speed, you're buying readiness. More on that connection in the piece on how much a website costs.
How I work
I start with a short brief, then structure, design, build, content, testing and launch. I keep the pace and say straight which stage I need something from you at, so there are no silent standstills. If a specific date matters, we set it at the start and stay on top of the materials. Check out the website development service or get in touch via contact - I'll give you a realistic timeline for your project.
FAQ
How long does it take to build a website? It depends on the type. A simple landing page is 1-2 weeks, a brochure site 2-4 weeks, a larger company site 3-6 weeks, an online store 4-8 weeks and up. Those are timelines at a normal pace with materials delivered on time. The biggest factor isn't the code, it's how fast you deliver content and sign off on the stages.
What are the stages of building a website? Brief and goal-setting, structure and prototype, visual design, build and deployment, filling with content, testing, launch and indexing. Some of them run in parallel - for example, text can be prepared during the design phase, which shortens the whole thing.
What most often drags a website project out? Missing finished text and photos, several rounds of revisions with multiple decision-makers, adding new features mid-project, and gaps in responses. Those are factors on the client's side, not the developer's. Code is rarely the bottleneck - content and sign-offs are.
Can a site be built in a few days? A simple landing page or brochure site, yes, if the content is ready and one person makes the decisions. But "fast" usually means "on a template." A custom site for your business, with its own structure and built for SEO, can't go at that pace, because half the work is thinking through your specific case.
Does the number of pages drag the timeline out a lot? Less than you'd think. Setting up the template, animations and forms takes a similar amount of time for 5 pages and for 15. The timeline grows mainly from the amount of unique content and unusual functionality, not from the page count itself.
When will the site show up in Google after launch? The launch itself is a day or two, but indexing is a separate clock. I submit the site in Search Console right away, and actually showing up in results takes from a few days to 2-4 weeks. The day of launch and the day the site starts pulling traffic from search are two different dates.
How long does it take to build an online store? Most often 4-8 weeks. You add a catalog, cart, payments, shipping, an order panel and often integration with a CRM or warehouse - which is why the build and testing run longer than for a regular site. With a large catalog or unusual logic it can be more. I give a specific timeline after a brief on the product range and processes.
