Written by IILL Editorial
Last updated: 12 August 2026
“How many weeks does a website take?” cannot be answered from the page count alone. The schedule depends less on the last screen to be finished than on the time copy, photography, approvals, features, and domain migration spend waiting for one another.
If an early launch matters, reduce the scope required for the first release and separate later work instead of trying to rush everything.
Production ranges for planning
These planning ranges combine public Korean timelines checked on 30 July 2026 with common production stages. They are not contractual delivery guarantees. Treat them as a starting point when materials are ready and decision-makers are named.
| Project | Planning range | Largest schedule influence |
|---|---|---|
| Campaign landing page | 1–3 weeks | Final offer and copy, form, and measurement |
| Informational site of about five pages | 3–6 weeks | Copy and photography, design approval |
| Healthcare, legal, or other content-led site | 5–10 weeks | Expert material, regulatory review, and many detail pages |
| Custom booking, membership, or payment site | 8 weeks or more | Feature specification, external APIs, data, and operational testing |
Public cost and timeline material suggests one to two weeks for a landing page, two to three weeks for a basic site, three to five weeks for an intermediate site, and five to eight weeks for custom features. Specialist healthcare agencies commonly describe new builds and redesigns as taking three to eight or four to eight weeks. Photography, clinician information, medical content, and extra approval make it unrealistic to schedule a healthcare site like a simple company profile.
A realistic schedule in six stages
1. Define scope and responsibility
Do not spend the first week agreeing only on page count. Record the website goal, first-release scope, required features, copy and photography owners, and final approver in one document. An unresolved decision here returns as a revision later.
Done when: The menu, task list, exclusions, owners, and approval deadlines are agreed.
2. Collect materials and write copy
Gather company information, services, expert profiles, real cases, pricing rules, contact details, and policies. Even when the agency writes the copy, someone must verify facts and identify their sources.
Done when: Each page has core facts and missing-item markers, image rights are known, and information that must not be published is listed.
3. Design the information and interface
Confirm information order and calls to action in wireframes before applying the visual design. Approving desktop screens alone creates extra work when titles, tables, and forms must later be repaired on mobile.
Done when: Desktop and mobile flows for key pages and shared design rules are approved.
4. Develop and enter real content
Connect responsive screens, forms, management features, and external services. Layout problems appear only with full-length copy and real images. Filling an empty mockup with final copy on the last day is a common source of delay.
Done when: A staging URL contains real content and has a test list for each feature.
5. Configure QA, search, and analytics
Check mobile and desktop, keyboard use, major browsers, form errors, and success states. Test titles and descriptions, canonicals, sitemaps, redirects, and GA4 events before launch. For speed, consider LCP, INP, and CLS alongside heavy images and scripts rather than relying on one score. If an existing site is being replaced, complete the website redesign SEO migration checklist before the launch date is locked.
Done when: There are zero critical defects, known limitations are recorded, and conversion and search settings have passed a checklist.
6. Launch the domain and observe
Check how DNS and SSL changes affect email, then launch at a low-traffic time. Do not stop when the new site opens. Recheck old URLs, form notifications, analytics collection, crawler access, and 404s.
Done when: The launch checklist, rollback method, owner, and first review date are documented.
Why schedules slip
- Several people make decisions, but there is no final approver.
- Photography and expert-profile approval move behind design work.
- “Booking integration” is defined after signing as either a link or a live API.
- A redesign begins before anyone counts the articles and URLs to migrate.
- New menus and features keep appearing after design approval.
- Domain and email account access is checked for the first time on launch day.
The best way to protect the schedule is not to impose an arbitrary revision limit. Agree on what each stage decides and where deferred requirements will be recorded.
How much time can AI save?
AI can organise competitor material and rapidly produce copy options, repeated components, and test lists. It cannot remove the time needed to verify expert experience, approve regulated claims, conduct photography, obtain external API access, or make final decisions.
Use AI to show a draft sooner and shorten feedback cycles, not merely to increase output. Our AI website production service explains how IILL divides automation from human judgement.
Checklist before setting a launch date
- First-release pages are separated from pages deferred to the next release.
- Copy, photography, and profile owners have deadlines.
- There is one final approver with a response deadline.
- External integration methods and test accounts are available.
- Existing URLs, domain, DNS, and email access are confirmed.
- Mobile designs and full-length content will be reviewed.
- The schedule includes QA and a post-launch observation period.
- A delay rule says whether to reduce features or move the launch date.
If you are unsure whether you need a full site or a single campaign page, start with the website and landing page comparison guide. Once the scope is clear, review IILL’s professional-practice website portfolio or start a project enquiry in English.
Need a clearer first step for your website?
Start with the situation and outcome. We will help define the scope and next step.