Hays Digital Works

Our Delivery Process

Discovery to care

A stage is complete when the evidence and decision are visible.

Communication cadence is set at kickoff. Each stage identifies what the client supplies, what Hays delivers, who approves, the known risk, and the transition into the next stage.

Discover

Client input: Goals, audiences, current evidence, constraints, stakeholders, access, and known dates.
Hays deliverable: Problem statement, journey and content findings, requirements, assumptions, risks, and success measures.
Approval: Confirm that we are solving the right problem before scope.
Risk: Unavailable decision-makers, hidden integrations, or content without an owner.

Scope

Client input: Priority, budget context, dependencies, ownership choices, and acceptance of exclusions.
Hays deliverable: Proposal, deliverables, responsibilities, timeline, review rounds, change process, and acceptance criteria.
Approval: Signed scope and required deposit or authorization.
Risk: Treating an estimate as a guarantee while assumptions remain unresolved.

Content & design

Client input: Source content, brand assets, factual review, consolidated feedback, and one accountable approver.
Hays deliverable: Sitemap, content model, prototypes, responsive visual system, and decision log.
Approval: Approve structure and key journeys before full build.
Risk: Late content, conflicting feedback, or visual approval without reading real copy.

Build & review

Client input: Timely access, integration decisions, test users/data, and feedback against approved criteria.
Hays deliverable: Working implementation, review releases, integration handling, issue tracking, and documentation in progress.
Approval: Accept priority flows and content in the staging environment.
Risk: Scope expansion, vendor limitations, data quality, or reviewing only one device.

Verify & launch

Client input: Final legal/content approval, account ownership, launch window, internal contacts, and change freeze.
Hays deliverable: Accessibility/performance/browser QA, redirects, backups, cutover and rollback plan, analytics, training, and handoff.
Approval: Written launch authorization after known issues are reviewed.
Risk: DNS/email ownership, untested recovery, last-minute content, or unavailable approvers.

Care & learn

Client input: Named support contacts, prompt incident context, business changes, and outcome feedback.
Hays deliverable: Defined maintenance, monitoring, reports, content support, improvement recommendations, and retrospective.
Approval: Plan renewal, improvement scope, or documented offboarding.
Risk: Unclear support boundaries, abandoned accounts, or measuring activity instead of outcomes.

Start with discovery