“When will it be ready?” is the second question after price. The honest answer: the technical work is often finished sooner than the part that depends on the client — text, photos and decisions. Below are orientation figures by type and, more importantly, the factors that actually determine the timeline.

Orientation by website type

These figures are orientation, not a promise: the concrete timeline is written into each project’s proposal according to material readiness and scope. It counts from receipt of materials and includes approval stages.

TypeTypical timelineDepends on
Landing page1–2 weeksOffer clarity, copy, visuals
Single-page business-card site1–2 weeksMaterial readiness
Multi-page business website (5–10 pages)3–6 weeksPage count, languages, design rounds
Corporate site in several languages6–10 weeksSections, translations, approvals
Online store4–10 weeksCatalogue, bank approval, delivery
Mobile app (MVP)2–4 monthsFeatures, backend, store review

If an agency promises a multi-page site “in two days”, that usually means a ready template with minimal adaptation — sometimes exactly what you need, but you should know it in advance.

What happens at each stage

  1. Discovery and structure (2–5 days). Goal, audience, page list, features. The written task everything else follows.
  2. Design (1–3 weeks). Wireframes first, then visuals. Most of this time is waiting for feedback: every round delayed by a day moves the final date by a day.
  3. Development (1–4 weeks). Building pages, forms, integrations, the mobile version. Technically the most predictable stage.
  4. Content placement (3–10 days). Text and photos, language versions. This is where most projects stall if material is not ready.
  5. Testing and launch (2–5 days). Device checks, form tests, domain connection, Search Console.

What delays projects most often

  • Text and photos are not ready. “We will send the text later” is the most common sentence that stops a project for weeks. Fix: prepare materials from day one, or include copywriting in the offer.
  • Several decision-makers. When three people approve the design and disagree, each round doubles. Fix: one responsible person on the client side.
  • Waiting on third parties. Merchant approval by the bank, domain transfer from an old provider, App Store review — neither we nor you can speed these up, so they must start in week one, in parallel.
  • Scope growth mid-project. “One more page”, “one more language” — each is logical but changes the timeline. Fix: clear boundaries for the first version and additions planned as a separate stage.
  • Migrating an old site. Moving content and planning redirects often takes longer than building new pages.

How to shorten the timeline

  • Prepare a first version of the text before design starts — even imperfect. Structure is planned better on real text.
  • Collect logo, colours, photos and old-site access in one folder.
  • Name one person who gathers feedback and makes decisions.
  • Launch the core pages first and add the rest later — staged launch is often better for the business too.
  • Start third-party processes (bank, domain, developer accounts) in the first week.

A detailed checklist: what to prepare before ordering a website.

Timeline and price together

Timeline and price are linked: the clearer the scope, the more accurate both are. An “urgent” project usually means either a smaller scope or a higher price — and that choice should be made up front. Price factors are covered in how much a website costs. If you have a fixed date (opening, season, campaign), tell us at the start — we plan backwards from the date.

Related pages