Everyone who has ever ordered a website has asked: “When will it be ready?”. And almost everyone heard in reply: “It depends”. That is true, but it sounds like an excuse. So let’s break this “it depends” into parts: what affects the timeline, how long each stage usually takes and where the avoidable delays are.
In short: a small fix or an audit takes 1–2 days, a landing page — from 5 working days, a corporate website or an online shop — several weeks. But development is rarely the longest stage: in 8 cases out of 10 the delays come from content and approvals, not from code.
Approximate timelines by project type
| What is done | Approximate timeline | What it depends on |
|---|---|---|
| Small fix, configuration, audit | 1–2 days | Access and a clear description of the problem |
| Landing page on a ready design | from 5 working days | Readiness of texts, photos and forms |
| Corporate website (5–10 pages) | 2–4 weeks | Number of pages, design approval, content |
| Catalogue or online shop | several weeks (depending on scope) | Number of products, import, payments, delivery |
| Design from scratch | in addition to development | Number of screens and revision rounds |
| Bringing AI design to life | a page — 2–3 days, landing page — up to a week | Quality of the mockup and number of pages |
These are guideline values, not promises: we give exact timelines once we see the scope of the task. They nonetheless help plan campaigns and deadlines.
What stages website development consists of
- Brief and estimate. 1–2 days. You describe the task, we give the cost and plan. A well-prepared brief works best here.
- Structure and prototype. A few days. We agree on pages and blocks so the logic does not change after the design.
- Design. From a few days to two weeks, depending on the number of screens. Two or three revision rounds are normal.
- Coding and development. From a few days (landing page) to several weeks (shop). This is the least predictable stage.
- Filling in content. Texts, photos, products, translations. Often runs in parallel with development.
- Testing and launch. 1–3 days: checking on phones, forms, speed, domain and analytics setup.
What most often drags out a project
- Content. Texts, photos and reviews that “we will finish in a moment”. These lead among the reasons deadlines are missed. Keep a separate “content ready” date and respect it just like the launch date.
- Approvals. Every day spent waiting for a reply extends the project by a day. Agree: a reply to each stage within two working days.
- New requirements along the way. Added features mean new deadlines and a new price. It is better to record them as a “second stage”.
- Several people who decide everything. One responsible person on your side shortens the project by weeks.
- Missing access. To the domain, hosting, analytics. A small thing that blocks the launch on the final day.
How to speed up without losing quality
- Start simple: a landing page or a compact site, not “everything at once”. Expand after the first enquiries.
- Choose a template or ready design if uniqueness is not critical. This noticeably saves time and money.
- Prepare content in advance. Even draft texts are better than empty blocks.
- If the site is needed by a set date (exhibition, promotion), say so right away. We will allow a buffer or offer a simplified scope. The calculator has “faster” (+10%) and “urgent” (+30%) options.
Want a realistic forecast for your task? Fill in the 5-minute brief or calculate options in the calculator: it shows the approximate price and the range of days.
Example: a corporate website week by week
To make the timelines less abstract, here is an approximate calendar for a small corporate website with five to seven pages (this is an example, not a promise: exact dates depend on your readiness and approvals):
| Week | What happens | What is needed from you |
|---|---|---|
| 1 | Brief, page structure, prototype | Answers to questions, examples of sites |
| 2 | Design of the home page and main pages | Feedback on the mockups within 1–2 days |
| 3 | Coding, admin panel, filling in content | Texts, photos, contacts |
| 4 | Testing, revisions, launch | Final approval, domain access |
If texts and photos are ready from day one, the project can be completed in four weeks or sooner. If the content is written “on the go”, every week of waiting simply adds to the total timeline.
How to read other people’s timeline promises
- “A turnkey site in three days”. Possible, but only a landing page on a ready template with ready texts. Ask what exactly is included.
- A deadline without questions to you. If the developer did not ask about content and approvals, their estimate is worth nothing.
- Vague “roughly”. It is good when a range is given and what it depends on is described.
Frequently asked questions about timelines
Why can a landing page not be made in one day?
Because a day is just coding. It includes structure, design, revisions, forms, checking on different screens and launch. One day is realistic only for a very small fix.
Can a site be launched in stages?
Yes, and it is usually the best option: first the main pages, then the rest. The site starts working and bringing in enquiries, and you learn from real data.
What to do if the deadline is strict?
Mention the date at the start. We will propose a reduced scope, fix what moves to the second stage and, if needed, switch on an accelerated mode for an additional fee.
How long does support after launch last?
For 30 days after launch we fix anything that does not work as agreed, free of charge. After that — hourly support or a subscription.
Shall we discuss your task?
Tell us what you need and we'll name the cost and timeline. We work directly.
