Professional website delivery is a pipeline of phases, each producing tangible artifacts. Skip or reorder phases and you pay in mid-flight redesigns, placeholder launches, or organic rankings without intent coverage. Shared understanding of the process aligns agencies and internal teams on timing, approvals, and rework boundaries.
Launch dates become credible when MVP scope, content readiness, and acceptance tests are frozen — not wished.
Phase map — outputs and approvals
| Phase | Typical output | Client approval |
|---|---|---|
| Discovery / brief | goals, personas, integrations | business sponsor |
| IA + content | site map, copy skeleton | marketing + legal where needed |
| UX | flows, wireframes, prototype | product owner |
| UI | design system, key templates | brand/marketing |
| Development | staging, APIs, CRM hooks | business UAT + IT |
| QA + a11y + perf | bug backlog, vitals thresholds | quality gate owners |
| Technical SEO | meta, schema, redirects | SEO/marketing |
| Launch + hypercare | production, monitoring | per contract |
End-to-end sequence
- Discovery — requirements, MoSCoW, tool access.
- Information architecture — URL intents, SEO/conversion mapping.
- UX — mobile/desktop journeys, error states, forms.
- UI — reusable components, accessibility-minded specs.
- Development — environments, integrations, reviews.
- Content + migrations — CMS population, legacy redirects.
- QA and vitals — device coverage and performance budgets.
- Technical SEO — canonicals, sitemaps, Search Console readiness.
- Launch and iterate — analytics, alerts, backlog.
Discovery anchors everything
Close “what” and “why” before high-fidelity design. Even a one-page brief beats verbal ambiguity — conversion goals, integrations, compliance, and timelines must be explicit.
IA and content readiness
Decide which intents deserve dedicated URLs and who owns final copy. Late content is the most common schedule killer.
UX / UI — flow before decoration
UX removes friction to primary actions; UI encodes brand consistently. Lock representative templates before multiplying variants.
Development and integrations
Validate CRM/analytics hooks on staging early — integrations drive timeline risk more than landing page counts.
QA, accessibility, Core Web Vitals
- test critical paths end-to-end
- WCAG checks per agreed level
- measure vitals on real devices — not desktop-only lab scores
Technical SEO before scaling crawl
301 strategy from legacy URLs, canonical hygiene, robots/sitemap correctness — ship before opening the floodgates to indexing.
Launch starts measurement — conversions, 404s, logs, Search Console — not the party.
Risk patterns
| Symptom | Cause | Mitigation |
|---|---|---|
| Scope creep | no frozen MVP | written CR + timeline impact |
| Late content | no copy owner | content deadlines before UI lock |
| Broken integrations at end | late sandbox access | early PoC + keys |
| SEO loss post-migration | weak redirects | URL mapping + preflight audit |
Go-live checklist (short)
- rollback plan + backups
- uptime + form submission alerts
- cookie/consent alignment
- CMS training + support contacts
Related
- Website project brief
- UX and conversion
- Web technologies in 2026
- Core Web Vitals before launch
- Technical SEO
FAQ
Frequently Asked Questions
- Often weeks to a few months — driven by integrations, languages, and content readiness, not slide counts.
- You can phase pages, but IA and URL strategy should be planned early to avoid expensive restructuring later.
- Someone with authority, availability for approvals, and access to sales/legal/IT stakeholders.
- Critical journeys and integrations should — especially forms and payments — even if datasets differ.
- Hypercare monitoring, analytics tuning, UX fixes — plus ongoing content and internal linking for SEO.