"And how fast can you do it?" — the question that follows the price within about ten seconds. "Two weeks" means nothing on its own unless someone tells you when the clock starts and what stretches it. Below are the real timelines by website type, straight from our price list, what each one is made of, and an honest list of the things that push a project to the right. Most of them, it turns out, are not on the developer's side.
The short answer
A landing page takes 7–14 days. A business-card site, 10–18 days. A corporate website, 21–35 days. An online store, 30–60 days. Complex systems with user accounts start at 60 days and go up. The clock starts not when you pay, but when the structure is approved and the content is in.
Timelines by type
- Landing page — from $190, 7–14 days.
- Business-card site, 3–5 pages — from $300, 10–18 days.
- Corporate website with CMS and blog — from $690, 21–35 days.
- Catalogue without checkout, B2B — from $850, 21–40 days.
- Online store — from $1,350, 30–60 days.
- Clinic website with online booking — from $960, 30–45 days.
- Learning platform — from $1,900, 45–90 days.
- Marketplace or aggregator — from $2,300, 60–120 days.
- SaaS web application — from $3,100, 60–150 days.
The full table with every type is on the pricing page. The range inside each line is not "depends how it goes" — it is the difference between the simple and the complex version of the same thing.
What the timeline is made of
Take the corporate website at 21–35 days. The schedule looks roughly like this:
- Brief and structure — 2–4 days. What the business does, who the customer is, which pages are needed and what goes on each. The output is a sitemap you sign off.
- Design — 5–10 days. Figma mock-ups: the homepage first, then the rest once you have said yes to it.
- Build and programming — 7–14 days. Including the admin area, forms and integrations.
- Content — in parallel. Copy, photography, price lists. This is where projects stop most often.
- Testing and launch — 3–5 days. Mobile, speed, forms, analytics, moving everything onto your domain.
The stages overlap, which is why the days-per-stage add up to more than the total.
What actually blows the deadline
Over ten years the reasons barely change, and the developer only comes fourth:
- Content. "We will write the copy ourselves" — and the project sits for three weeks. This is reason number one by a wide margin. If nobody on your side has the time, order copywriting up front (from $10 per 1,000 characters) rather than quietly delaying the launch.
- Internal approvals. When four people look at the mock-up one after another, a week disappears on its own. Name one person whose word is final.
- Revision loops. "Let's see one more version of the homepage" after the design is signed off adds 5–7 days. That is fine if you choose it deliberately — but the date moves.
- Access and credentials. Domain, hosting, payment gateway keys, shipping account details. Asking for them the day before launch is a classic.
- Stage payments. Work pauses while a payment is late, and that pause lands in the total too.
How to speed things up honestly
- Have the content ready before the start. Copy, photos, logo, price list. This saves weeks, not days.
- One decision-maker on your side who collects revisions into a single list instead of sending them one at a time by messenger.
- Launch in parts. Homepage and services first, blog and catalogue after. The site starts working earlier instead of waiting for the last section.
- Hand over access in week one, not in the final week.
- Do not start two weeks before your season. A new site still needs time to be found in search — that is a separate run of weeks after launch.
Why "I'll do it in three days" is a warning sign
In three days you can assemble a page from a ready-made template with your logo dropped in. That is not always bad — for a one-off promotion it works perfectly well. But if someone promises a corporate site or a store in three days, something has been cut: either there is no structure built around your actual services, or the copy was generated in a hurry, or there will be no testing, no analytics and no check on a phone.
The second sign of the same kind is a deadline with no stages in it. If a contractor cannot tell you what exactly will be ready on day seven, there is no deadline — there is a promise.
Frequently asked questions
When does the clock actually start?
From the approved structure and the delivered content, not from the payment date. We write that into the contract. Otherwise you end up with a site that is "late" because the copy arrived three weeks after everything else.
Can it be done faster than the minimum?
Sometimes — if the content is ready, one person makes the decisions, and we can take the project out of the queue. We discuss those cases separately: it is a question of team capacity, not a magic button. Halving the timeline without losing quality is not possible, and we do not promise it.
How long does migrating off a website builder take?
14–25 days and from $460: exporting the content, rebuilding it properly, moving the URLs and setting up redirects. Whether it is worth moving at all is covered in website builder or custom development.
When will the site start bringing in customers after launch?
If you are running ads to it, immediately. If you are counting on search, that is a different clock: indexing takes a few weeks, the first positions take months. For a local business the first enquiries from maps tend to appear sooner, usually within 6–10 weeks. More on that on the SEO page.
What happens if we are slow with the content?
Nothing dramatic, but the date moves by exactly that much — we do not count idle time as working days. The other option is to launch with placeholder content and swap the copy later through the admin area. Sometimes that is smarter than keeping a finished site closed for another month.
In short
Real timelines run from two weeks for a landing page to two months for a store, and the biggest lever is in your hands: ready content and a single decision-maker shorten a project far more than any acceleration on the developer's side.
Want a timeline for your specific project? Write to us through contacts — after a short conversation we will name both the timeline and the price, and put them in the contract.