Custom website development process: what to expect at each stage

Stage-by-stage roadmap for the custom website development process, with deliverables, client vs developer responsibilities, SEO checks, and Calgary-specific.

Custom website development process: what to expect at each stage

Custom website development process: what to expect at each stage
Custom website development process: what to expect at each stage

Custom website development process: what to expect at each stage

When you hire a local agency for a custom website, you should get a predictable flow of work, concrete deliverables, and clear approvals at every step. This article maps the eight standard stages of a custom website development process and explains what to expect, who does what, essential SEO and content checks, and practical verification steps you can use if you are a Calgary business owner preparing to engage a web partner.

Stage 1: Discovery and scope, define goals, users, and constraints

Purpose: clarify business goals, primary users, technical constraints, existing systems, and project boundaries so the team and client share a single definition of success.

Deliverables

Expect a written scope or statement of work, a project brief with agreed success metrics, a stakeholder contact list, and an initial timeline estimate. Professional teams stress a written scope because verbal agreements lead to misunderstandings and scope creep, a common failure point in web projects, so insist on documentation before work begins (see guidance from Optimal ITS).

Client responsibilities

  • Provide access to analytics, existing brand assets, and decision maker availability.
  • Share mandatory compliance, legal, or industry constraints.
  • Confirm an approximate budget range and procurement rules where relevant.

Developer responsibilities

  • Produce a documented scope with explicit assumptions and acceptance criteria.
  • List required integrations and any exclusions from the proposal.
  • Schedule discovery workshops or interviews with stakeholders.

Verification checklist

  • Do you have a written scope or statement of work? If not, pause hiring.
  • Are assumptions, deliverables, and approval gates explicit?
  • Is there a named project owner on both sides?

Practical Calgary note: ask whether the agency can meet in person or run a local workshop at their office, and confirm the office address and phone for follow-up. Global iTech Systems Ltd lists a Calgary office and phone on their site for local meetings and support.

Stage 2: Strategy and SEO structure, sitemap and keyword mapping

Purpose: translate business goals from discovery into a prioritized sitemap and page blueprint, and map target keywords to pages so SEO is baked in from the start. Process frameworks that place information architecture and SEO early reduce rework later (see Pulsebay and Playcode outlines).

Deliverables

  • Sitemap or information architecture diagram showing primary pages and navigation.
  • SEO keyword map assigning intent-focused keywords to pages.
  • Page-level SEO briefs with title and meta suggestions where applicable.

Who owns keyword work

Agencies typically supply keyword research and a recommended structure, while clients confirm business priorities and local terms to target. Verify the sitemap includes local pages if you serve Calgary, Airdrie, or Cochrane.

Verification checklist

  • Are target keywords documented with intent and priority?
  • Will the agency include structured data and consistent NAP in schema?
  • Are canonical URL patterns and redirect strategy defined?

Stage 3: Content and information architecture, who writes what

Purpose: decide content ownership, produce content briefs, and plan migration for existing material. Content drives SEO and conversions, so specify responsibilities and deadlines in the scope.

Deliverables

  • Per-page content briefs that include target keyword, CTA, length guidance, and required media.
  • Media inventory and taxonomy rules for product or service pages.
  • Migration plan if an existing site is being replaced.

Client responsibilities

  • Provide final copy or name a content owner and approval timeline.
  • Supply product data, images, and legal text where applicable.

Developer responsibilities

  • Offer content templates, CMS field definitions, and import scripts if needed.
  • Ensure meta and structured data specifications are included in briefs.

Verification checklist

  • Does the scope specify who supplies content and deadlines?
  • Are SEO meta rules and structured data requirements included?
  • Is there a fallback for missing content to avoid launch delays?

Stage 4: UX, wireframes, and prototypes, validate structure before design

Stage 4: UX, wireframes, and prototypes, validate structure before design — custom website development process

Purpose: convert the sitemap and briefs into page-level wireframes that show user journeys, CTAs, form flows, and conversion points. Validating layout and flow before visual design reduces rework and clarifies technical feasibility, a best practice in custom projects (Pulsebay, Playcode).

Deliverables

  • Low-fidelity desktop and mobile wireframes for primary page types.
  • A simple interactive prototype demonstrating core user flows for review.
  • An approvals record showing sign-offs on critical pages.

Verification checklist

  • Does the prototype show the full checkout or lead flow end to end?
  • Has the client signed off on critical conversion pages before design?
  • Are any complex interactions validated for technical feasibility?

Stage 5: Visual design and approvals, high-fidelity mockups and design system

Purpose: apply branding, create a design system, and produce high-fidelity screens for desktop and mobile. Many teams use Figma or equivalent so developers receive a pixel-accurate handoff (Pulsebay, GitNexa).

Deliverables

  • Clickable Figma or design files, a style guide, and a revision log.
  • Design tokens or component documentation for developers.

Verification checklist

  • How many design revisions are included in the scope?
  • Is there a complete handoff package with exportable assets and specs?
  • Are responsive breakpoints and basic accessibility needs documented?

Stage 6: Development and integrations, build, APIs, and clean code

Purpose: implement the visual design in code, integrate the CMS, payment gateways, CRM, and any APIs, and produce a working staging site for review. Custom development emphasizes clean, secure code and a documented deployment process (see GitNexa and Optimal ITS for process notes).

Deliverables

  • Working staging site, developer documentation, repository access, and a deployment and rollback plan.
  • Test credentials for third-party integrations and a backup schedule for the staging environment.

Verification checklist

  • Is a staging URL available for independent review and testing?
  • Does the scope define code ownership, repository access, and license terms?
  • Is there a rollback plan and automated backups before launch?

Local question to ask the agency: who will manage hosting, DNS, SSL, and business email setup, and can they support in-person DNS signoff if required?

Stage 7: Quality assurance and staging, testing, performance, and security

Stage 7: Quality assurance and staging, testing, performance, and security — custom website development process

Purpose: perform functional, cross-browser, mobile, performance, accessibility, and security testing on staging and produce a test report. Professional teams use both manual and automated tests and track issues in a bug log before release (Playcode, OuterBox).

Deliverables

  • QA test plan and issue log, performance score summary, accessibility notes, and acceptance criteria sign-off.

Verification checklist

  • Has the site passed agreed acceptance tests and performance targets?
  • Are fixes tracked and closed in a transparent issue tracker?
  • Is a final backup scheduled before the production push?

Stage 8: Launch, handover, and post-launch support

Purpose: move the site to production with a launch checklist, finalize DNS changes, confirm monitoring and backups, complete a training session, and agree post-launch support and SEO campaigns. The handover should leave you with admin access, documentation, and a short monitoring plan (GetDevDone, Hooman, Pulsebay).

Deliverables

  • Launch checklist, repository and CMS admin access, recorded training walkthrough, release notes, and a 30 to 90-day monitoring plan.
  • Options for retainer-based maintenance, security updates, and SEO campaigns.

Verification checklist

  • Is there a fallback plan if the live launch fails?
  • Who owns hosting and SSL after launch?
  • Have admin accounts and documentation been handed over and tested?

Calgary-specific follow-up: verify and optimize your Google Business Profile and local schema, and confirm the agency can provide in-person support if needed. Global iTech Systems Ltd lists a Calgary office at #230, 2635 37 Ave NE, Calgary, AB T1Y 5Z6 and phone (403) 402-1727 for local meetings and follow-up.

Common red flags to watch for

  • No written scope or only a verbal agreement.
  • Missing SEO or content planning in early phases.
  • No staging environment or inability to show a working preview.
  • Vague support terms with no rollback, backup, or SLA language.
  • Unclear ownership of code, assets, or repository access.

Quick launch readiness checklist

  • Signed scope and approved sitemap.
  • Content for all pages or a content-deficit plan.
  • Staging site with passing QA and performance tests.
  • Backup and rollback plan documented.
  • Admin accounts, documentation, and recorded training delivered.

Frequently asked questions

How long does a custom website typically take from discovery to launch

It varies by scope and complexity. Timelines depend on features, content readiness, and review cycles. Avoid vendors who promise fixed durations before completing discovery.

What do I need to provide before development starts

At minimum, brand assets, access to analytics, content owners, product or service data, and any required third-party account credentials. The written scope should list exact deliverables the client must supply.

Will my site be SEO-ready on launch

Sites can be launched with on-page SEO basics in place, including meta tags, URL structure, and schema, but ongoing SEO is usually required to build visibility. Confirm that keyword mapping and page-level SEO briefs were completed during the strategy stage.

What ongoing support should I expect after launch

Typical options include retainer-based maintenance for security and updates, ongoing SEO campaigns, monitoring and performance tuning, and ad hoc feature work. Make sure support terms, response times, and billing rates are in a written SLA.

What is included in handover and training

Handover normally includes CMS admin accounts, repository links, documentation for common tasks, and a recorded or live training session that shows how to update content, manage backups, and raise support tickets.

Key references and process examples are available in professional outlines for custom development, including the stages described by Pulsebay, GitNexa, and Playcode, and the practical notes about scope and deliverables from Optimal ITS and OuterBox.

Ready to discuss your custom website development process in more detail? Contact Global iTech Systems Ltd to schedule a discovery call or request a scope checklist.