The question nobody answers honestly
"How long will it take?" is one of the first things a client asks — and one of the hardest for a developer to answer truthfully without losing the project to someone who just says "two weeks."
The real answer is: it depends. But that's not useful on its own. What actually determines the timeline, what's realistic for different types of projects, and what causes delays — that's what this post is about.
The short answer
| Project type | Realistic timeline | |---|---| | Simple business site (5–10 pages) | 2–4 weeks | | Business site with blog and SEO | 3–6 weeks | | Online store (simple) | 4–8 weeks | | Web app with login and user data | 8–16 weeks | | Complex web app with integrations | 4–9 months |
These ranges assume a single developer working on your project as the primary focus, a client who responds reasonably quickly, and content that is largely ready before development starts. Change any of those assumptions and the timeline shifts.
Phase by phase
1. Clarification and planning (1–2 weeks)
Before any code is written, there's a phase of figuring out exactly what needs to be built. This includes:
- What pages and features are required
- Who the users are and what they need to do
- Technical requirements (integrations, logins, payment, etc.)
- Content: text, images, brand guidelines
This phase is often skipped or rushed — and it's the most common reason projects run over. Decisions that aren't made up front get made mid-development, which costs significantly more time than making them early.
2. Design (1–3 weeks)
For a simple site, design might mean agreeing on a colour scheme and font from an existing component library. For a custom project, it means wireframes, mockups, and feedback rounds.
The design phase is highly client-dependent. A single round of feedback and sign-off keeps things moving. Multiple stakeholders with conflicting opinions, or decisions getting revisited after approval, can stretch this to twice the original estimate.
3. Development (1–10 weeks)
This is where most of the time goes, and the range is wide for a reason. A five-page business site built on a modern framework like Next.js can be fully developed in a week of focused work. A web application with authentication, a database, an admin panel, and external API integrations will take months — not because developers are slow, but because there's genuinely a lot to build correctly.
The key word is correctly. Fast development that produces fragile, poorly structured code isn't actually fast — you pay for it in bugs, security issues, and expensive fixes later.
4. Content and testing (1–2 weeks)
Once development is done, content needs to go in and everything needs to be tested: across devices, screen sizes, and browsers. Forms need to be verified. Load times need to be checked. If there's a CMS, the client usually needs a walkthrough.
This phase is routinely underestimated. It's rarely dramatic, but it takes real time.
5. Launch and stabilisation (a few days to a week)
Going live involves DNS changes, final checks, and — almost always — a handful of small fixes that only surface once real users start clicking around. Budget a week after launch for this.
Why projects actually run late
In my experience, delays almost never come from the development itself. They come from:
Content not being ready. The project can't finish without text, images, and brand assets. If these arrive three weeks after development starts, the project is three weeks late — regardless of how quickly the developer works.
Decisions being revisited. Changing the structure of a site or the logic of a feature after it's been built takes significantly longer than getting it right in the planning phase.
Stakeholder bottlenecks. The more people who need to approve things, the longer each feedback round takes. This is a process problem, not a technical one.
Scope creep. "While you're at it, can we also add..." is a phrase that extends timelines. Additional features take additional time. This isn't unreasonable — requirements evolve — but it needs to be acknowledged rather than assumed to be free.
How to move faster
The single most effective thing a client can do to speed up a project is prepare content before development starts. Text, images, logos, and brand guidelines — having these ready eliminates the most common source of delay.
After that:
- Designate one person as the decision-maker for the project
- Commit to feedback within 48 hours when a developer is waiting on you
- Agree on scope upfront, and treat additions as separate line items
A developer can only move as fast as the project allows them to.
A note on "we need it in two weeks"
Tight deadlines are sometimes real. A conference, a product launch, a grant application — there are legitimate reasons a site needs to go live quickly.
The honest answer to a two-week deadline is: it's possible for a simple site, but something has to give — either scope, quality, or cost. A responsible developer will tell you which. One who just says yes without asking any questions is telling you what you want to hear.
Frequently asked questions
How long does it take to build a website in Norway? A simple business website typically takes 2–4 weeks from start to launch. A site with a blog, custom design, and SEO optimisation usually takes 4–6 weeks. These timelines assume content is ready and feedback is given promptly.
What takes the longest when building a website? Content and decision-making are the most common causes of delay — not the technical development itself. Projects that have text, images, and a clear brief ready before development starts consistently finish faster.
How long does it take to build a web application? A simple web app with user login and basic features typically takes 8–12 weeks. More complex applications with multiple integrations, roles, and real-time data can take 4–9 months.
Can a website be built in a week? A very simple landing page can be. A proper business site with good SEO, a contact form, and a clean design typically cannot — not without cutting corners that you'll regret later.
What slows down a website project most? Missing content, changes to agreed scope, and slow feedback from the client side. Technical problems are rarely the main cause of delays.