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
Do I need a brand guide?
Not always, but provide logos (vector if possible), colours, fonts, and tone guidance.
Should I buy a template first?
Often better to choose with your designer—compatibility and licensing matter.
How long should a brief be?
Two to four pages is plenty if it answers goals, audience, content, and integrations.
What a strong website brief actually contains
Start with business goals—not "we need a new website" but "we want 30% more qualified quote requests from Hamilton and Waikato within 12 months." Name your audiences (homeowners, commercial clients, insurers), competitors you respect, and sites you dislike (with reasons). List mandatory features: booking, ecommerce, multilingual, CRM integration, member areas.
Attach brand assets, logo files, colour references, and who signs off content. Clarify who writes copy—you, the agency, or shared. Our website blueprint generator produces a scope summary you can paste into a brief.
Timeline, budget, and success metrics
State launch deadline drivers (season, event, lease) and budget range—silence here produces mismatched quotes. Define success: form fills, calls, online sales, reduced support calls. After launch, measure against those metrics, not vanity traffic. Read what moves website pricing in NZ before comparing proposals.
After you send the brief
Good agencies ask clarifying questions—that is a positive signal. Compare proposals on scope, not price alone. Contact NZDH with your brief for a tailored quote, or browse recent work to see if our style fits.
More guides in this topic
- Website design pricing in NZ: what actually moves the number?
- Mobile-first layout decisions for NZ service businesses
- Wireframes vs prototypes: what to ask your designer to deliver
- Stock photography choices that still feel credible
- Navigation patterns: keeping primary tasks obvious on small sites
Browse the full Design & planning guide hub or return to the guides home.
Explore on NZDH.co.nz
- All practical guides
- Website design services
- SEO services
- Recent website projects
- Frequently asked questions
- What website do I need? — short quiz to clarify scope before you brief a designer
Authoritative further reading
These independent resources complement this guide. Search engines and customers both reward accurate, helpful information—we link out where official documentation or regulators explain the topic better than a generic blog post could.