Insights:Website Development Process: How Many Steps from Contract to Launch
Step 1: Requirements Gathering
- Business objectives: presentation, lead generation, transactions, branding.
- List of sections and pages.
- Reference websites and preferences.
- Budget and go-live timeline.
Deliverable: Requirements summary.
Client involvement: Clearly identify the decision-maker to avoid conflicting feedback.
Step 2: Proposal and Quotation
- Technical proposal.
- Number of pages and functional scope.
- Design iterations and revision limits.
- Who provides the content.
- Deliverables and after-sales support.
Deliverables: Proposal document + quotation sheet.
Step 3: Contract and Scheduling
- Scope, duration, and payment milestones.
- Acceptance criteria.
- Ownership of source code and database.
- Change management and pricing adjustment rules.
- Confidentiality and after-sales support.
Deliverables: Contract + project schedule.
Step 4: Design and Approval
- Homepage style.
- Inner page templates.
- Mobile version.
- Interactions and forms.
Deliverable: Design mockups.
Approval point: Obtain written confirmation before development begins to prevent mid-project changes.
Step 5: Development
- Frontend pages and responsive design.
- Admin panel content management.
- Forms, search functionality, and access permissions.
- Basic SEO structure implementation.
Deliverable: Testing environment setup.
Step 6: Content Entry
- Copies, images, and product information.
- Sections and navigation structure.
Client collaboration: Provide materials according to the checklist; avoid rushing to prepare them right before launch.
Step 7: Testing and Acceptance
- Mainstream browsers and mobile devices.
- Forms, email, and payment flows.
- 404 pages, redirects, and sitemaps.
- Speed and basic security.
Deliverables: Test report + acceptance form.
Step 8: Launch and Maintenance
- Domain DNS resolution, certificate installation, and deployment.
- Search console submission.
- Backup and monitoring setup.
- Training and post-launch support.
Deliverables: Launch confirmation + operations documentation.
Timeline Reference
| Type | Typical Duration |
|---|---|
| Template site | 1–3 weeks |
| Custom corporate website | 4–8 weeks |
| Marketing / international trade site | 6–12 weeks |
| With business system integration | Scheduled by module |
The timeline is heavily influenced by how quickly content is prepared and confirmed.
Three Ways to Reduce Rework
- Define all pages and features clearly during the requirements phase.
- Confirm design in one round; avoid making changes while development is underway.
- Prepare content in advance according to the checklist.
Boundaries
This process reduces rework and delays, but it cannot guarantee a flawless first delivery. Scope changes, delayed materials, and overly long decision chains can still affect progress; these should be governed by the contract and change management mechanism.
Related reading: