I get this question in almost every first conversation, and the honest answer is that development is rarely the slow part. Most of the time goes into what happens before and around it: decisions, text, images and feedback. In this article I describe how we usually plan a website project, how much time each phase takes, and where deadlines tend to slip.
The short answer
Based on our own projects, a typical company presentation or service site takes 4 to 6 weeks, and a larger site with many subpages 6 to 10 weeks. A one-page landing page is quicker, while a webshop or portal with custom features is measured in months. We always give the exact schedule in writing, with milestones, after the first conversation.
| Type of website | Realistic timeframe |
|---|---|
| Landing page with one goal | 1 to 3 weeks |
| Presentation or service site | 4 to 6 weeks |
| Larger company site with many subpages | 6 to 10 weeks |
| Webshop or custom features (calculator, client portal, several languages) | 2 to 4 months or more |
The four phases, the way we do them
1. Planning (1 to 2 weeks)
Most things are decided here. We agree on the website's job: bring enquiries, sell products, or build trust before a longer decision. The sitemap follows from that, and we already look at what potential clients search for at this stage, because the menu structure should follow it too.
In my experience, if this phase is rushed, twice as much time goes into corrections later. A good brief speeds everything up. I wrote a separate article on what to put together before asking for a quote.
2. Design and development (2 to 6 weeks, or more)
This is the most variable part, and it is where the feature list matters most. A presentation site takes a few weeks. Custom logic is a different story.
For the Agrider machinery dealer, we were not building "pages" but a system: roughly 410 machine pages per language, five languages, a valuation tool, a leasing calculator, and stock that loads from an XML feed instead of being typed in by hand. A project like that is never really "finished". We keep developing it as the business needs.
The other extreme is our own product, DogDietLab. The first working version was built in about two weeks by one developer, because we strictly built only what it could not work without. Today a new feature typically goes from idea to live in 2 to 4 hours. What I learned from it: speed does not come from rushing, it comes from deciding what goes into the first version and what does not.
3. Testing and fine-tuning (1 to 2 weeks)
We go through every form, button and payment flow on phones and desktops, and set up tracking, speed and the technical SEO basics. On a multilingual site this is also where the language versions get linked (hreflang), which many people skip and then wonder why Google shows the wrong language.
4. Launch and the first weeks (1 week plus follow-up)
The launch itself is quick. Afterwards we watch how Google indexes the site, what Search Console shows, and where visitors get stuck. For us, a website does not end at launch. That is where it starts.
Where deadlines usually slip
Honestly: rarely on development. These are the most common reasons:
- Text and images arrive late. By far the most common. If the content is ready at the start, it saves weeks.
- Slow feedback. If every approval takes a week, a four-week project easily becomes eight.
- A growing wish list. A new feature idea is perfectly fine, but it is better placed after the first launch than in the middle of the project.
- Several languages. A language version is not a translation. It needs its own URLs, its own keywords and its own checks. We learned that first-hand with the Melini webshops in four countries.
How to make it faster
My usual advice is to make the first version smaller, but working. Better to launch a solid base sooner and extend it, than to polish for six months a site nobody sees in the meantime. If the content is ready, there is one decision maker who answers quickly, and the site's goal is clear, the timeframes above hold.
If you want to know how long your project would realistically take, describe in a few sentences what you need. After the first conversation we send a written schedule with milestones. More on the web development page.

