How long a website takes to build
A typical SME website goes from first meeting to launch in 3–8 weeks. The building itself is the smallest part. The schedule is almost always decided by when the copy, the photos and the decisions exist. When the content is ready at the kick-off meeting, the same site comes together in a couple of weeks.
The phases week by week
| Phase | Typical duration | Who does it | What stretches it |
|---|---|---|---|
| Brief and goals | 2–3 days | You and us | Calendars and the number of decision-makers |
| Structure and content plan | 3–5 days | Us | An unclear service or price list |
| Copy and photos | 1–3 weeks | You or us | This is the phase that slips most often |
| Design and build | 1–2 weeks | Us | Changing direction mid-work |
| Testing and fixes | 2–4 days | Us | Waiting for feedback |
| Launch and redirects | 1 day | Us | Missing domain credentials |
The table scrolls sideways.
The phases overlap. Design work starts while the copy is still in progress, and testing begins before the last page is finished.
Where the delivery time is counted from
Kotipohja, our basic website package, is ready in 1–2 weeks, Brändipohja, the site and brand package, in 2–3 weeks and Kasvupohja, the growth package, in 3–4 weeks. Custom systems such as booking solutions and time-tracking tools take 4–8 weeks. The clock starts when the copy and photos are in place, and the completion date is written into the proposal before work starts.
If you need the site faster than in three weeks, express delivery carries a 25 % surcharge. That too is agreed in the proposal, not on the invoice.
What we need from you
- The basics: services, prices or a price range, service area and contact details
- Photos of the business, the premises or past work. Ten decent photos beat three perfect ones
- The logo in its original format, if one exists
- Credentials for the domain and the current site
- About an hour for the kick-off meeting and an hour per feedback round
Not everything has to be ready on day one. What matters is knowing what is missing, because missing content is the only real variable in the schedule.
What stretches the schedule
- The copy waits for that quiet week that never comes
- There are no photos, and the photographer's next free slot is three weeks away
- There are three decision-makers, and each comments on a different round
- Feedback arrives in pieces, so the same page is built twice
- An online store or booking system is added mid-project
- The domain credentials are with the previous builder, who cannot be reached
Not one of these is a technical problem. That is why a schedule holds best when it is agreed up front who delivers what, and by which day.
How the project stays on the agreed date
- Name one decision-maker who collects everyone's comments before giving feedback
- Gather the copy and photos into one folder before the start
- Give feedback in one go, not in three instalments
- Agree the number of feedback rounds in advance, say two
- Put the launch date in the calendar at the first meeting
- Sort out the domain and the credentials in the first week
What if there is no content at all
Then there are two routes. Either we write the copy for you from an interview, which takes about an hour of your time and a few days of ours, or we launch a smaller site first and extend it later. The second nearly always beats a project that waits half a year for perfect copy. A published site earns visitors and search engines' trust even while it is still being completed.
Speed is not the point
Fast delivery is a consequence, not a promise. It comes from deciding the structure before anything is built, and from having the content in place before the design is locked. A rushed site whose copy was written on the final evening still shows in the results a year later.
Our pricing page shows which package fits your need and its delivery time. If your date is tied to something, say a trade fair or the start of a season, mention it when you first get in touch. We will tell you straight whether it can be done.