A single landing page takes about 1–2 weeks. A standard business website of five to eight pages takes 3–5 weeks. A full online store takes 5–8 weeks, and a large custom project can run 8–16 weeks. Those numbers assume one thing above all: that your content is ready and your feedback comes back quickly. In practice, that single factor decides whether a project lands on the short end of the range or the long one.
How long does each type of project take?
| Project | Typical timeline | What drives it |
|---|---|---|
| Landing page | 1–2 weeks | One page, one goal, one round of design |
| Business website (5–8 pages) | 3–5 weeks | Page count, custom sections, content readiness |
| Online store | 5–8 weeks | Catalogue size, payment and shipping setup, checkout testing |
| Custom platform (booking, portal, dashboard) | 8–16 weeks+ | Custom logic, integrations, user accounts, testing depth |
| Second language (added to any of the above) | +3 days to 1 week | Translation quality and layout review — if planned upfront |
These are working timelines, not marketing promises. Anyone quoting you "a website in 48 hours" is describing a template with your logo dropped in — which is a real option, but a different product from a site built around your business.
What happens in each phase?
A well-run project moves through five phases. Knowing which one you are in tells you whether "we're nearly there" is true.
- 1. Discovery and planning (2–4 days). Goals, audience, page map, references, and the exact list of what you need to supply. Cutting this phase is the most expensive saving in the whole project.
- 2. Design (1–2 weeks). The homepage is designed first and approved, then inner pages follow the approved direction. Two rounds of revisions is normal; five means the direction was never agreed.
- 3. Build (1–2 weeks). Design becomes a real, responsive, fast website. This phase is the most predictable one — it rarely slips.
- 4. Content and setup (parallel, 3–7 days). Real text and images replace placeholders, the second language is filled in, analytics and search indexing are configured.
- 5. Testing and launch (2–4 days). Devices, browsers, forms, speed, broken links, and search setup. Then the domain switch itself, which takes hours, not days.
Notice that only two of the five phases are "building". Most of a timeline is decisions and content — which is exactly where you control the calendar.
Why do website projects run late?
From building dozens of sites and stores, the causes repeat with remarkable consistency:
- Content isn't ready. Text, photos, product data, and licences arrive in pieces over weeks. This is the number one cause of delay, by a wide margin.
- Feedback is slow or scattered. Three people sending contradictory notes on different days costs more time than any design round.
- Scope grows mid-project. "Can we also add a blog, and a booking system?" Each addition is fine — but it is a new timeline, and it should be named as one.
- Third parties. Payment gateway verification, domain transfers, and hosting access sit outside anyone's control and can quietly add a week.
- No single decision-maker. Approvals by committee are the silent killer of launch dates.
How do you get online faster?
Five decisions that repeatedly cut weeks off a project:
- Prepare content before kickoff. Even rough text beats no text. A page can be designed around real content in one pass; placeholder text guarantees a second.
- Appoint one decision-maker. One person collects internal opinions and sends one consolidated response.
- Batch your feedback. One complete list per round, not a message a day.
- Decide the second language before design. Arabic and English layouts differ in direction and rhythm — planning both from the start costs days, retrofitting costs weeks. Our guide on bilingual websites covers why the second language is usually worth it.
- Launch phase one, then extend. A live five-page site earning attention beats a perfect twelve-page site that launches next quarter.
This is how our website and online store projects are structured — fixed phases, clear deliverables at each one, and a launch date that is agreed rather than hoped for.
Does a faster launch hurt SEO?
No — as long as the fundamentals are built in rather than bolted on later. Clean page structure, fast loading, mobile-first layout, correct headings, a sitemap, and search-console setup all belong to the build itself and add no meaningful time. What genuinely takes months is authority: rankings, links, and content depth. That work starts on launch day, which is one more reason not to delay it. If you have launched before and never appeared in results, our guide on why a website doesn't show up on Google explains what to check first.
What should you ask before you sign?
- What is the estimated launch date, and what has to be true for it to hold?
- What exactly do you need from me, and by when?
- How many design revision rounds are included?
- Who tests the site before launch, and on which devices?
- What happens if I'm late with content — does the timeline shift, or the scope?
Vague answers here predict a vague project. Our checklist on how to choose a web design company covers the rest of the questions worth asking.
Frequently asked questions
How long does it take to build a business website?
A standard business website of five to eight pages usually takes three to five weeks from kickoff to launch when content is ready and feedback is quick. Larger sites with custom sections, a second language, or integrations take longer.
Can a website be built in one week?
Yes, for a single landing page with content already written and no custom integrations. A one-week turnaround means fewer design rounds and a tighter scope, not a lower quality of build, so it works best for a campaign page or a launch announcement rather than a full company website.
How long does an online store take to build?
Most online stores take five to eight weeks. The build itself is not what stretches the timeline; product data, photography, payment and shipping setup, and testing the full checkout are. A large catalogue or a custom checkout flow can push it beyond two months.
What causes website projects to run late?
In our projects, the two biggest causes are content that is not ready (text, photos, product data) and slow or scattered feedback from multiple people. Scope added mid-project and third-party approvals such as payment gateway verification come next. The build phase itself rarely slips.
Does adding a second language make the project longer?
If it is planned from the start, a second language typically adds a few days to a week, mostly for translation and layout review. Retrofitting a second language onto a site that was not built for it costs far more time, which is why it should be decided before design begins.
How soon after launch will the site bring customers?
Launch day is the start, not the finish. Paid campaigns can bring traffic immediately, while organic search visibility usually builds over a few months. Plan for the site to be indexed within days and to gain search traction gradually.
Want a timeline for your specific project? Answer a few questions in our project estimator, or tell us what you're building and we'll come back with a scope and a realistic launch date.
Read next: How to choose a web design company · Website vs online store: which do you need? · Do you need a website if you already have social media? · Do you need a brand identity before your website?