How to brief a web designer in NZ: a checklist that prevents scope creep

Short answer: a good brief reduces rework. Include goals, audiences, competitors, content readiness, must-have integrations, and what “success” means in measurable terms.

Most website friction comes from hidden assumptions: the owner imagines a booking system “like that big brand site”, while the designer priced a brochure build. A brief does not need to be fancy—just explicit.

What business context should you include?

• What you sell, to whom, and in which regions.
• Your typical customer journey (phone vs form vs walk-in).
• Three competitor sites you like—or dislike—and why.
• Constraints: timeline, budget band, legal/compliance needs.

What technical details matter—even if you are non-technical?

List domains you own, current hosting/registrar logins (or who holds them), existing email setup, and any systems you must integrate (CRM, booking, POS, accounting). If you do not know, say so—discovery can be scoped.

How should you handle content?

Decide who writes final copy, who supplies photos, and whether you need photography or stock images. Content delays are the most common launch blocker. If you need help, scope copywriting separately from design.

What does a strong success metric look like?

Instead of “look modern”, use: “increase qualified form fills by X% in six months” or “reduce phone time spent answering pricing questions”. Metrics guide IA and page priorities.

What should you ask designers to return in a proposal?

• Phased deliverables and what is excluded.
• Assumptions and dependencies (content readiness, third-party APIs).
• Warranty/support window and SLAs for critical bugs.
• Training and handover artefacts.

Looking for a NZ team to respond to a brief?

Contact NZDH with this checklist filled in as far as you can—you will get a more accurate conversation faster.

Frequently asked questions