// Dunedin / Web design

MAKE THE NEXT STEP OBVIOUS.

// The useful starting point

A Dunedin website should give people confidence about the offer and clarity about what happens next. Thoughtful structure, useful evidence and practical functionality.

// 01 / The short answer

Web design in Dunedin works best when the website explains the real process.

A person booking a workshop, a property owner arranging work remotely and a group organiser comparing venues need different information. I design the website around those tasks, so the page does more than introduce the business.

The practical details matter: where the service takes place, who confirms availability, what information is needed and who responds. For products or expertise sold beyond Otago, the site also needs enough detail to support a decision without an in-person visit.

I’m Dan, based in Christchurch and working directly with Dunedin clients remotely. The scope covers agreed structure, design and implementation. We select WordPress, Shopify or Wix around the content, systems and editing tasks the business actually needs.

// 02 / Where this fits

A better website needs a defined job.

Use the brief to identify where customers or staff are losing time.

// 01

The next step is ambiguous

A submitted form looks like a booking, or a quote request lacks essential details. Make the process and confirmation clear.

// 02

Different audiences get the same page

Residents, visiting organisers and specialist buyers need different information. Give priority offers distinct, connected routes.

// 03

Staff struggle to maintain changes

Programme dates, team details or service terms are difficult to update. Build an editing structure that fits the people responsible.

// 03 / What I do

Turn the brief into a usable website.

Good design connects the offer, evidence and operation.

// 01

Plan the information

Map customer questions and priority services. Organise pages so someone can understand the offer and find the evidence needed to proceed.

// 02

Design the experience

Develop a visual direction from the business’s identity and approved material. Check reading, navigation and forms on smaller screens.

// 03

Build the right functions

Assess existing booking, membership and commerce systems. Define the difference between a useful link, an embedded tool and a custom integration.

// 04

Prepare the handover

Check agreed journeys, plan changed URLs and establish editing responsibilities. Document account access, licences and ongoing support.

// 04 / In application

Three Dunedin website requirements.

Illustrative briefs, separate from the published project evidence below.

// Trades and property services

Collect the information needed for remote coordination

An owner elsewhere arranges work at a Dunedin property through a local access contact.

The approachConsider WordPress for service detail and a focused enquiry form that distinguishes the customer, site and coordination needs.

What to checkComplete briefs and fewer follow-up requests for missing essentials.

// Furniture and products

Support the buyer who cannot visit

A maker sells selected products outside Otago while custom pieces require a discussion.

The approachAssess Shopify for clear standard product and shipping rules, with a separate custom route for dimensions, finish and delivery questions.

What to checkCompleted orders and useful custom enquiries.

// Coaching and venues

Keep programme and event information easy to maintain

A provider changes programme dates and receives group enquiries alongside ordinary bookings.

The approachAssess Wix against editing and integration needs. Separate programme information, availability requests and confirmed bookings.

What to checkCorrectly routed enquiries and accurate current content.

// Illustrative website decisions

What does the customer need before sending the form?

Dunedin projects can involve several locations or decision-makers.

What does the customer need before sending the form?
Customer situationWebsite decisionBusiness input required
An owner arranges work from another citySeparate property details from contact detailsWho authorises work and who coordinates access
A customer requests a workshop timeLabel the confirmation step explicitlyWhether the diary is live or staff-confirmed
An organiser plans an event in DunedinExplain facilities and group requirementsApproved capacity, dates and enquiry process
A customer orders a custom product remotelyRequest a useful specificationRequired dimensions, options and shipping information
// 05 / The method

Resolve the process before building the interface.

// 01

Brief and structure

Review the current website and systems. Agree the pages, customer routes and content ownership.

// 02

Content and design review

Confirm copy, imagery and design direction. Check any proposed integrations before implementation.

// 03

Build, test and launch

Implement the approved scope, test agreed journeys and coordinate launch. Provide editing guidance and confirm support arrangements.

// 06 / A clear agreement

A website proposal with practical boundaries.

The right scope makes the work useful. Agree the deliverables, dependencies and responsibilities before starting.

Included in the agreed work

  • Specified pages, visual design and platform build.
  • Agreed forms, integrations and content work.
  • Launch checks and a defined handover.

Separate or out of scope

  • Custom booking or membership software unless scoped.
  • Photography, extensive copywriting, product data preparation or branding unless included.
  • Ongoing marketing, maintenance and subscriptions as an automatic bundle.

What shapes the cost

Content complexity, integrations, product rules and migration work affect cost. The proposal distinguishes the build from ongoing platform charges and identifies who prepares the material.

What shapes the timing

Launch depends on approved content, access and working integrations. For programme or event pages, current information and an owner for future updates are established before publication.

Who owns what

You approve facts, terms, images and customer processes. I deliver the agreed website. Your business retains core account control, with ownership, licences, editing access and support documented.

// 07 / Work you can inspect

See how different customer journeys become clearer.

The published case studies show website design and structure you can inspect. They describe the delivered work and provide useful comparisons for your own requirements.

Russley Golf Centre

A Christchurch Wix project connecting course, coaching and membership routes.

The Motor Company Service Centre

A Christchurch WordPress project with staff-confirmed booking requests.

// 08 / Useful questions

Before we start.

Do we need online booking or a booking-request form?

That depends on the operation. Live booking needs reliable availability and rules. A request form can be suitable when staff must confirm the service, timing or customer requirements.

Can our website support people arranging work remotely?

Yes. We explain the process and collect the site and contact information needed for coordination. The form should request useful essentials while keeping sensitive information out of an ordinary initial enquiry.

Which platform is right for us?

We compare WordPress, Shopify and Wix against content, commerce, integrations and editing needs. Existing systems and recurring costs are part of the decision.

Can you retain current content and URLs?

We review what is useful before rebuilding. Important pages inform the structure, and changed paths can require redirect planning and migration checks within the scope.

How will our team manage changing dates?

We agree who updates them and design a manageable content structure. The handover covers those tasks, while more involved design or technical work can be included in ongoing support.

// A useful next step

MAKE THE PROCESS CLEAR.

Show me the current site and where customers get stuck. We can turn that into a useful website brief.