A useful website brief for a Dunedin small business starts with its customers and the tasks they need to complete. It should not begin with an assumption that every customer is a student, tourist or mobile visitor, or that one type of supplier automatically fits every local business.
Disclosure: This guide is written by No Brainer Creative, based in Auckland. It is not an independent ranking of Dunedin designers. We do not claim a Dunedin office or verified Dunedin client results here. Apply the same brief and evidence questions to our proposals as to alternatives.
Collect the questions customers actually ask
Start with the recurring questions staff answer and the information a customer needs before taking the next step. Review available enquiry and search evidence where you have appropriate access, separating genuine requests from tests or spam. If the evidence is limited, record that rather than inventing a local trend.
For example, a service business may need to explain scope and coverage before quoting. A booking-led business may need to clarify availability and confirmation. A product business may need specifications and purchase information. These are planning examples, not measured descriptions of Dunedin demand.
Map each priority to content and a next step
Choose the main customer tasks the business can fulfil, then describe the page or feature that supports each one. Identify the responsible person on the business side so the designer knows where accurate information will come from.
| Customer question | Content or route to plan | Business input to confirm |
|---|---|---|
| Is this the service I need? | Clear service scope and relevant examples | What is included, excluded and available |
| Can this business serve me? | Accurate premises or coverage information | Real delivery area and any limits |
| What happens if I enquire? | Labelled contact route and next-step explanation | Who receives and qualifies the request |
| Can I book or buy? | Connection to the appropriate system | Availability, payment and confirmation rules |
| Where do I get ongoing help? | Relevant existing-customer support route | Actual support contact and hours |
A separate page is useful when it answers a distinct question with specific information. Do not split the same service into repeated city or suburb pages simply to add more keywords.
Decide what belongs in the first release
Mark essential requirements, useful later improvements and questions that still need investigation. A booking integration, a catalogue and a simple enquiry form are different scopes. State whether content, photography, copywriting, translations or specialist reviews are included or supplied separately.
For an existing website, identify useful content and current URLs before proposing a move. Describe the actual problem: missing information, a confusing route, editing difficulty, performance or a system connection. Compare targeted repairs with a rebuild instead of assuming a platform expires after a few months. The website migration planning guide provides further questions.
Ask a provider to respond to the brief
Give each provider the same priorities and ask it to explain the proposed approach, dependencies and exclusions. A freelancer, studio, remote agency or owner-managed platform can be assessed against those requirements. Avoid a comparison based on an invented price range, universal delivery time or a stereotype about support.
Ask for relevant published work and the provider’s actual contribution. Then ask how it will learn the details of your business and get content approved. A local address may help arrange visits, but it does not establish every capability; a remote team should explain how it will gather information and work with staff.
Plan the checks alongside the build
Agree how the business will confirm that the website meets the brief. Use representative content and customer tasks rather than relying only on attractive mockups. Review phone and desktop layouts, service information, contact links and any external booking or purchase route.
If a form or notification test is needed, agree the recipient, scope and test record before submission. Check what the confirmation actually establishes: a sent request, a delivered message or an accepted booking are different. Keep test traffic out of genuine enquiry or sales reporting.
Clarify search work and ongoing ownership
If SEO is included, ask which implementation tasks and reporting are part of the proposal. Define the starting evidence and meaningful review periods. A newly published site, a tool score or an indexing check does not prove that qualified enquiries have increased.
Record the business’s access arrangements, subscriptions, renewal owners and support contact. Confirm what staff can edit, which changes need assistance and what documentation will be handed over. The project schedule should reflect its actual content and approval dependencies rather than a fixed three-to-six-week promise for every business.
Working with No Brainer
No Brainer is based in Auckland. Our website design service can be discussed against a clear project brief, including any remote working or external-system requirements. Our published work offers examples to ask about; it is not evidence of a best-in-Dunedin ranking.
Start with the customer task and the scope you need covered. Branding, search work and continuing support should be specified rather than assumed to come with every build.
Website brief questions
Does this guide name the best web design agency in Dunedin?
No. It is written by No Brainer Creative, an Auckland-based agency, and is not an independent provider ranking. It does not claim a Dunedin office or verified Dunedin client results.
Should every Dunedin website be designed for students or tourists?
No. Establish who the particular business serves and what those customers need. A city-wide assumption does not establish the audience, device mix or buying journey for an individual business.
What should we prepare before asking for quotes?
Bring the existing website, main customer tasks, service or product information, content ownership, required connections and known constraints. Distinguish essential launch requirements from optional ideas.
Do we need a complete rebuild?
Diagnose the actual limitation first. Compare targeted improvements with a rebuild or platform change, including content, navigation, editing, external systems and migration responsibilities.
Can a freelancer or an existing website platform meet the brief?
Assess the actual person or system against the requirements and support needs. Provider category and platform name alone do not establish capability, cost, ownership or future performance.
How should we assess a provider’s local understanding?
Ask it to explain how it will learn about your customers, services and genuine coverage. Look for a sensible research and approval process rather than accepting a broad claim about the city or its population.
What should the launch review prove?
It should verify the agreed content, customer routes, representative layouts and relevant handoffs, and record limitations. Website publication, indexing, rankings and qualified enquiries remain separate outcomes.
Further planning
- Prepare a website brief and requirements
- Compare affordable website scope
- Plan a small-business website
Share your website brief with our Auckland team and ask us to respond to the same requirements as other providers.