Plan content, design, technical access, stakeholder reviews, and launch-day checks. This guide is a starting point for planning, not a substitute for a scoped proposal or technical audit.

01

Discovery and requirements

Start by clarifying the specific business requirement. Different websites need different levels of work, and a useful estimate starts with a clear list of decisions rather than a generic package label.

What to ask: What are we trying to achieve, what depends on this choice, and how will we know it works?
02

Content and assets

Ask what is included, what is assumed, and what will be supplied by your team. This prevents surprises after the project starts and makes competing quotes easier to compare.

What to ask: What are we trying to achieve, what depends on this choice, and how will we know it works?
03

Design and build review

Consider how this decision affects editing, maintenance, performance, accessibility and search visibility. What looks convenient at launch may create ongoing cost or operational friction.

What to ask: What are we trying to achieve, what depends on this choice, and how will we know it works?
04

Launch and handover

Write down the decision, the responsible person and the next action. A brief checklist is often more useful than an overly complicated specification.

What to ask: What are we trying to achieve, what depends on this choice, and how will we know it works?

What to do next

Use these questions to define your requirements, compare providers fairly and identify where specialist help would save time or reduce risk.

Explore related service ↗