Depending on the scope, a website project typically takes a few weeks to a few months. The biggest factors are the feature scope, the number of feedback rounds and the timely delivery of content such as copy and images.
A compact company website is typically completed faster than an online shop with integrations and data migration – shop projects come with their own timeline factors, which we cover in a separate answer. Regardless of scope, every project at XICTRON follows clearly defined phases – creating transparency and predictable milestones. Our project process shows what these phases look like in detail.
Typical project phases
- Concept – defining requirements, site structure and goals during consulting
- Design – layout drafts, feedback rounds and approval
- Implementation – development of templates, features and content
- Quality assurance – testing across devices, browsers and screen sizes
- Launch – go-live, redirects and search engine submission
Which factors influence the project duration
Two website projects with a similar number of pages can differ considerably in duration. In practice, these factors determine the pace:
- Feature scope: A website with a contact form and standard pages is finished faster than one with multiple languages, protected areas, booking features or connections to third-party systems via integrations.
- Design ambition: An adapted, proven design system is implemented more quickly than a fully custom layout with bespoke components and animations.
- Content: Copy, images, logos and legal information need to be created, approved and entered – in our experience, missing content is one of the most common reasons for delays.
- Feedback speed: Every revision and approval round needs a dedicated contact person on the client side; long coordination loops noticeably extend the project.
- Relaunch vs. new build: A relaunch adds an inventory of existing content, content migration and a redirect concept to preserve existing rankings – a separate work package that should be planned for.
- Accessibility and legal requirements: Requirements such as accessibility-compliant implementation, privacy and imprint pages are not a timing problem when planned properly – retrofitting them, however, costs time.
Realistic orders of magnitude
Blanket deadline promises without a requirements analysis are rarely reliable. As a rough guide: compact company websites often fall within a range of a few weeks, while larger projects with custom design, many content pages or multiple languages tend to take two to four months. The schedule only becomes binding after the concept phase, once scope and content are fixed – which is why a realistic milestone plan is a fixed part of our free consultation and the subsequent concept phase.
It is also important to look beyond the launch: a website is not a one-off project but needs ongoing care through updates, backups and monitoring. We describe what happens after go-live in the answer What happens after the launch? – planning this early avoids surprises with hosting and maintenance later on.
In our experience, providing copy, images and access credentials early shortens the project timeline considerably – delays are often caused by missing content rather than development. We summarise what we need from you in the answer What do I need to contribute as a client?.