Asked how long a website takes, an honest developer will say "it depends", and the dependence is almost never on typing speed. It is on decisions, words and approvals.
Where the time goes
| Phase | What happens | What usually delays it |
|---|---|---|
| Discovery | Goals, audience, current numbers, structure | Access to accounts and data |
| Content | Copy, images, proof, service details | Waiting for the client to write or approve. Often the longest phase |
| Design | Layouts, look and feel, approvals | Several people with different opinions |
| Build | Pages, forms, tracking, speed work | Late changes to content or scope |
| Testing | Phones, browsers, forms, tracking | Issues found late |
| Launch | Address switch, redirects, monitoring | Domain and hosting access |
The bottleneck is content
A designer cannot lay out words that do not exist. Sites stall waiting for a bio, a service description, a photograph or a decision on what the offer actually is. If you want a fast project, start writing before the design begins, and name one person who can approve.
Size matters, but not linearly
A single landing page is far quicker than a fifteen-page site, because there is less to write, design and check. But complexity adds time faster than pages do: bookings, payments, integrations and custom features each need building and testing.
What a fixed-scope package shows
Our Medora doctor website is delivered on a published timeline of 7 working days for a fixed 15-page package, according to the Medora page as of September 2026. That is only possible because the scope is fixed, the structure is set and content is collected up front through a welcome kit. It is a useful reminder that speed comes from decisions made early, not from working harder. A custom project has more variables, so expect longer, and treat any promise of an exact date before the content is ready with some caution.
How to shorten your own project
- Decide the pages and the offer before you brief anyone.
- Gather logo, photographs and testimonials with permission in advance.
- Assign one approver with authority.
- Agree how many rounds of changes are included.
- Have domain and hosting access ready.
The cost of slow approvals
Every review cycle adds days. If three people must approve each page and each takes a few days to reply, a modest site can take weeks longer than it should. Agree a fixed turnaround for feedback, and name one person who has the final say.
Being realistic about a date
If you have a firm date, tell the team at the start, and be honest about what will be ready. It is better to launch a smaller, good site on time than a larger one that is rushed. You can add pages after launch.
A pre-kickoff checklist
- Goals and target audience, in writing.
- List of pages and services.
- Draft copy or a person assigned to write it.
- Logo, colours and photographs.
- Access to domain, hosting and analytics.
- One named approver.
What can run in parallel
Content writing, photography and domain arrangements can happen while design is under way. Testing can begin while final content is polished. A good project plan overlaps these, so the calendar is shorter than the sum of its parts.
Launch is not the last step
Plan a few weeks after launch for fixes and improvements. Real visitors find things that testers do not, and small adjustments in that period often make the difference to results.
If you have a hard date
For an event, a release or a launch, reduce the scope to fit the date. Build the page that carries the campaign first and expand later. The reasoning is in landing page or full website. For redesigns, protect existing visibility by following the redesign checklist.