The Honest Answer to "How Long Will This Take?"
The most common version of this question sounds like: "I need a website, how quickly can you build it?" And the frustrating — but honest — answer is: it depends on what you're actually building.
Not in the vague, non-committal way agencies use to avoid committing to a timeline. In the specific way that the following factors will determine your actual delivery date. Here are the real numbers.
Simple Business Website: 2–4 Weeks
A simple business website means five to eight pages of information — who you are, what you do, how to contact you. Built on a CMS like WordPress or Webflow, with a template that's been customised to your brand.
Two to four weeks is the realistic timeline when the content is ready. That last part is the part that always gets glossed over. The single biggest reason simple websites take longer than expected is not the development — it's waiting for the client to provide copy, photos, and brand assets. If you can hand over all of that in week one, your site can be live in two to three weeks. If the content trickles in over six weeks, the timeline extends accordingly.
Custom Design Business Website: 4–8 Weeks
A custom-designed website — where the screens are designed from scratch rather than adapted from a template — takes longer because design is a process that requires iteration. The first version of any design is never the final version. You'll have opinions. The designer will have opinions. Getting from first draft to something you're genuinely proud of takes time, and rushing it produces websites that look like they were rushed.
Four to eight weeks for a custom business website is realistic when the project is properly scoped, the content strategy is defined early, and decisions get made promptly. Extended client review cycles and slow feedback are the most common cause of projects in this category running long.
E-commerce Website: 6–12 Weeks
E-commerce has more moving parts than a standard business site: product catalogue management, inventory, payment processing, shipping logic, order management, customer accounts, email confirmations. Even on a platform like Shopify or WooCommerce, configuring all of this properly takes time.
The lower end of that range (six weeks) is for a relatively simple Shopify store with a standard theme and a small product catalogue. The higher end is for a WooCommerce build with custom functionality, a large catalogue that needs to be migrated or built out, and integration with inventory management or fulfilment software.
Web Application: 3–6+ Months
A web application — a SaaS product, a client portal, a marketplace, a booking platform — is a different category entirely. The timeline is driven by feature complexity, not page count. A relatively simple-looking application can take months to build because the work is in the backend: the data model, the API, the authentication, the business logic, the integrations.
Three months is a compressed timeline for a focused MVP with a well-defined feature set and no scope changes. Six months is realistic for a medium-complexity application. Anything with real-time features, complex multi-role permissions, financial transactions, or enterprise integrations should be planned at six months minimum.
What Actually Makes Projects Take Longer
In our experience building websites and applications, the things that cause projects to run past their deadline almost never come from the development side. They come from:
Undefined requirements
When a project starts without a detailed specification, developers build based on assumptions. Those assumptions are sometimes wrong. Rework is slower than building it right the first time. A proper discovery phase at the start of any project is the single highest-leverage thing you can do for the timeline.
Late content delivery
Every page of a website needs words and images. If those aren't ready when the page gets built, the developer either waits or builds with placeholder content that then needs to be replaced. Both options add time. The fix is to treat content production as a parallel workstream that starts on day one, not something that gets done after the design is finished.
Slow decision-making
Design review cycles, copy approval, stakeholder sign-off — these happen in every project, and how quickly the client side moves through them has a bigger impact on timeline than any technical factor. Projects where decisions get made within 24–48 hours finish on time. Projects where feedback takes a week per round finish significantly late.
Scope changes mid-project
Adding a feature after development has started is always more expensive than having that feature in the original spec. Sometimes the feature genuinely wasn't foreseeable — that's fine, and it's part of the process. But "while we're at it, can we also..." is a phrase that extends timelines. Every change is a cost, and respecting the original scope is how projects finish on time.
How to Get an Accurate Timeline for Your Project
The honest answer to "how long will this take?" requires three things: a detailed feature list, a conversation about your content readiness, and a developer who's willing to give you a real number rather than a vague range to avoid accountability.
If you tell us what you're building, we'll give you a written timeline estimate in 48 hours — broken down by phase so you can see exactly where the time goes.