Every website quote carries a timeline, and most of them are wrong in the same direction. The honest answer to how long a website takes is that it depends on decisions nobody has made yet, which sounds evasive until you notice that it tells you exactly where the time goes. Growth Bully, a Malta performance marketing agency, has waited on enough builds to be confident the developer is rarely the slow part.
A more useful question than how long is what has to be live first. A full website and a working lead flow are not the same project, and treating them as one is what turns a two month build into a six month gap in the pipeline.
How long does it take to build a website?
A small brochure site with ready copy is a few weeks. A structured site with real content work, a handful of integrations and more than one approver runs to a few months. The build itself is the predictable part. Content, approvals and decisions are what move the date.
That range is wide because the variance does not live in the code. Two companies can commission the same page count from the same team and finish eight weeks apart, and the difference will be how fast somebody could answer a question about their own products.
Why will nobody sensible give you a date on the first call?
Because the two biggest variables are unknown at that point: how much content has to be written from nothing, and how many people have to agree before anything is signed off. A quote that names a launch date before scope and content are settled is a sales date, not a plan.
You can still get a useful answer on that call. Ask for the date range plus the three inputs that would move it, and ask what happens to the schedule if an input lands two weeks late. An answer that names the dependencies is worth more than an answer that names a day.
What actually makes one website take longer than another?
Five things, roughly in order of impact: how much new copy is needed, how many approvers there are, how many systems the site has to talk to, how many languages it ships in, and whether anyone owns the project internally. Page count barely registers next to those.
- New copy. Pages waiting on words are the single most common reason a build stalls, and nobody budgets time for writing.
- Approvers. Each additional sign off adds a round of revisions and a calendar gap, not just an email.
- Integrations. A CRM, a booking system or a payment provider each add testing, and testing surfaces decisions nobody made.
- Languages. A second language doubles the content work and the proofing, whatever the templates suggest.
- An internal owner. Projects without one named person on your side drift, because nobody is chasing your own colleagues.
Which part of the delay is yours rather than the developer's?
Usually most of it. Copy that has not been written, photography that has not been taken, product information nobody can confirm, and sign off that waits for a meeting. None of that is anyone's fault, but it is all on your side of the line and it is all forecastable.
That is good news, because it is the half you control. Put dates against your own inputs before the build starts and the schedule stops being a negotiation. The same discipline makes the content brief worth writing: whoever is producing the words needs the decisions, not encouragement.
Can you generate leads before the site is finished?
Yes, and on most projects you should. A single landing page with one offer, a working form and conversion tracking can be live in days and can run paid traffic while the full site is built. The pipeline does not have to wait for the homepage.
This is the part most timeline guides miss, because they are written from the build side. From the acquisition side, every week without a page you can send traffic to is a week of demand you either do not capture or pay for twice later. If the business needs enquiries this quarter, the full site is not the first deliverable, it is the second.
What should go live first?
The shortest path from an advert to an enquiry. In practice that is one page for your best offer, one form that reaches a real inbox and a CRM, tracking that records the submission, and a thank you page. Four assets, days of work, and the acquisition programme can start.
- One offer page. Your strongest offer, one action, no navigation competing with it.
- One form that routes. Fields you will actually use, landing somewhere with an owner and a timestamp.
- Tracking that fires. A conversion event you have watched register, not one you assume works.
- A thank you page. The page that makes the conversion countable and tells the enquirer what happens next.
- A follow up rule. Who answers, and how fast, because speed to lead decides what those enquiries are worth.
Everything else in the build can proceed behind that page. When the full site launches, the offer page either folds into it or stays as a campaign destination, which is usually the better answer anyway.
How do you hold a timeline without inventing a deadline?
Date the inputs rather than the launch. Commit to when copy is delivered, when assets arrive, when each approval happens and who gives it. Then the build date becomes arithmetic instead of a promise, and a slipped input is visible in the week it slips rather than at the end.
It also changes the conversation when something does slip. A schedule built on dated inputs tells you what the new launch date is the same afternoon, which is a far easier message to carry into a management meeting than a vague apology in week ten.
What should launch week include?
Checks, not celebration. Redirects from every old address, forms tested from a phone on mobile data, conversion events confirmed firing, analytics and search tools verified, and someone watching enquiry volume for a fortnight. A launch that skips these loses leads quietly for weeks before anyone notices.
The quiet losses are the expensive ones, and they have a known shape: our notes on launch checks that protect leads and on changing domain without losing leads both exist because the same handful of things break every time. Budget a day for them in the plan, before the plan needs a day it does not have.
If the real constraint is enquiries this quarter rather than a finished website, we build the acquisition path first and let the site catch up. That is how our digital marketing engagements start, and the full sequence sits inside the Decision-Maker Pipeline. Tell us when you need enquiries by and we will work the plan backwards from that date.