how long a website takes to build
A straightforward business website takes four to eight weeks of calendar time, of which perhaps two are actual building. The rest is waiting: for content, for feedback, for decisions. Projects rarely overrun because the work was slower than expected. They overrun because nobody scheduled the parts that are not development.
Ask a studio how long a website takes and you will hear a number between four and eight weeks. Ask a business owner how long their last website took and you will hear something closer to four months.
Both are telling the truth. The four-to-eight weeks is the work. The four months is the calendar. The gap between them is almost never development, and it is entirely predictable once you know what is in it.
Where the time actually goes
A five-to-eight page business site breaks down roughly like this, assuming nothing goes wrong.
- Scoping and structure, three to five days. What pages exist, what each one has to do, who it is for. Skipping this does not save a week; it moves that week to the end, where changes cost more.
- Design, one to two weeks. Usually two or three key page designs, not every page. The rest are built from those patterns.
- Build, one to two weeks. The part everybody pictures when they think about how long a website takes, and rarely the largest part.
- Content loading, three to five days. Only if the content exists. If it does not, see below.
- Testing and fixes, three to five days. Real devices, real browsers, forms that actually deliver.
That is four to six weeks of work. The reason it becomes three months is in the next section.
Why does a website project take longer than quoted?
Four things, in order of how often they are the culprit.
The content is not written. This is the answer most of the time. A studio can design a page around placeholder text, but it cannot finish one. Every page waiting on copy is a page that sits at ninety per cent done, and a project where six pages are ninety per cent done is not nearly finished. It is stopped.
Feedback arrives in instalments. A round of review that takes the client four days instead of one adds three days, and a project has four or five rounds. That is a fortnight, invisible on any plan, spent entirely on waiting.
The decision-maker was not in the room. Designs get approved by a manager, then seen for the first time by an owner in week five. Whatever they say next costs more than it would have in week one, because the build is already sitting on top of it.
Scope moved. Not usually a dramatic change. It is a booking form, then a login, then a second language, each reasonable on its own, each adding work nobody removed anything to make room for.
None of these are the studio being slow, and none are the client being difficult. They are all scheduling failures, which means they are all avoidable.
What makes a project faster
Three things, and the first is worth more than the other two together.
Arrive with the content written. Not polished, just written down. Every page, in a document, before the design starts. A project that begins with real text often finishes in half the calendar time of one that does not, because nothing ever stops to wait.
Name one person who decides. Gather as many opinions as you like, but one person consolidates them and speaks for the business. Committee feedback is the most reliable way to turn a two-day review into a two-week one.
Book the review slots in advance. Put the feedback days in the calendar at the start, the same way the build days are. A review that has a date attached happens on that date. One that does not happens when somebody has a quiet afternoon.
How long for different kinds of site
Ranges, assuming content is ready and feedback is prompt. Double them if either is not.
- One-page site: one to two weeks. - Business or corporate site, five to ten pages: four to six weeks. - E-commerce: eight to twelve weeks, and the extra time is mostly products, photographs, payment setup and delivery rules rather than the shop itself. - Custom application (bookings, accounts, anything that talks to software you already run): three months and upwards, quoted properly rather than estimated.
Our own ranges sit inside those, and what they cost is on the services page. What moves a project above its floor is covered in what a website actually costs in Kolkata, and it is largely the same list as what moves it past its deadline, which is not a coincidence.
The five questions that make a timeline real
Ask these before you agree to a date. They take a minute each and they are the difference between a timeline and a hope.
- What do you need from me, and by when? If the answer is vague, the deadline is fictional. There should be a date for content and a date for each review.
- What happens to the date if my content is two weeks late? A studio that says "no problem" is either not scheduling properly or not telling you.
- How many rounds of revision are included, and what does a sixth cost? Unlimited revisions are how projects become permanent.
- Who writes the copy, and is that quoted separately? If it is not named, it is assumed to be yours.
- What is the launch checklist, and who signs it off? Ours is what to check before you sign off a website; the point is that one exists and you have seen it.
The answers matter less than whether they come readily. A studio that has thought about its own timeline has answers; one that has not will improvise them.
The honest version
Any competent studio can build a five-page site in two weeks. Almost none deliver one in two weeks, because delivery is not a development problem.
If you want a website in six weeks, the thing to fix is not who builds it. It is having the words written, one person deciding, and the review days already in the calendar. Do those three and most studios will hit the date. Skip them and none will.
If you have a deadline that matters, like a launch or an exhibition, tell us the date first and we will tell you honestly whether it is reachable, which is more useful than agreeing to it and finding out in week seven.
Questions people also ask
A one-page site can, if the text and photographs are ready on day one and there is a single round of feedback. A multi-page site cannot be done well in a week, and anyone promising it is either using a template with your logo dropped in or planning to skip testing.
Missing content, by a wide margin. Design and development can both proceed in parallel with other work, but a page cannot be finished without its real text, so every page waiting on copy is a page stuck at ninety per cent while the deadline moves.
Eight to twelve weeks is realistic for a straightforward shop, and most of the extra time compared with a brochure site is not the shop itself. It is product data, photography, payment gateway setup, delivery rules and tax settings, all of which need decisions from the business.
Rarely worth it. Paying more can add people to the build, but the build is not usually the bottleneck, and adding people to a design project often slows it down. Money spent on getting your content written professionally buys far more speed than money spent on the development.
Indexing usually takes days to a few weeks once the site is submitted through Search Console. Ranking for anything competitive takes months, so treat launch day as the start of that clock rather than the end of the project, and plan for it before the site goes live.
In short: Write your content before the build starts; it is the single thing that decides whether a project lands on time.